Jump to content

iron_buzz

Full Member
  • Posts

    61
  • Joined

  • Last visited

 Content Type 

Forums

Detector Prospector Home

Detector Database

Downloads

Posts posted by iron_buzz

  1. 4 hours ago, Chase Goldman said:

     

    They need to change the coil charging clip design, definitely.  It is interesting they went USB C on the new Xtreme Hunter coil.  

    The problem with a magnetic connector on the coil itself would be that it would eventually magnetize and  collect a ton of magnetic oxide particles and other magnetic debris, risking damage, unreliability, or overheating during charging (due to a high resistance connection) and a debris cleaning/removal hassle for the end user to avoid these issues.

    But there are a ton of more elegant coil charging interface solutions that could be incorporated going forward and many that could also be backfit onto the existing coils.  XP should make a decision to just rip the bandaid off and move to USB C, while at the same time designing a better coil charging solution.

    I would not be surprised if Minelab got a patent on the magnetic coupling, but you'd think they could certainly come up with some sort of wireless induction charging.  Perhaps even utilizing the coils of wire already in the coil. (NOT an electrical engineer here... there may be practical reasons this wouldn't work)

  2. 15 hours ago, Chase Goldman said:

     

    What TNSS is saying is that if you have Relic set up to give you a pure iron signal in the nail/nickel/swing configuration shown (as expected when you swing down the barrell of the nail) and then you transition to any other program (other than Gold Field) and then return to relic, you will get intermittent non-ferrous audio and TIDs (that don't correspond to the nickel TID, they look to be in the high 80's when I was able to catch a glimpse of the screen).  Indicating that perhaps IAR has been altered which may be causing iron falsing or some other unknown bug/issue.

    Anyway, despite several attempts with the same setup, I have not been able to replicate TNSS's "bug" at all.  Not even close.  I can make blips occur with certain coil edge manipulations (even without transitioning out of Relic) but with a normal swing down the barrel of the nail, solid iron tone and ID no matter how many transitions out of relic or other non-relic program adjustments I do. 

    Maybe he has a coil issue or a buggy install.  Though Jeff's statement that TNSS has seen this on previous versions, indicates it may not be unique to ver 2.00, pointing again to perhaps a TNSS unique hardware or configuration issue.

    I don't have the "issue" and really am not losing sleep over it, regardless based on my tests and hundreds of successful hours on v 2.0 Relic Program (yes, it's my "Go To" program).  And I do a lot of target interrogation which has me frequently transition out of relic.

    I would be interested to know if anyone else has been able to replicate it (other than the one or two folks who commented on his channel who said they saw it too).  I'm actually kind of surprised by people just taking these findings (mine included) at face value as gospel rather than proving to themselves whether they are present for their specific setups based on how simple the test is to set up and run.  Especially since they may manifest differently for different combinations of equipment and targets.

    Without additional replication by other D2 experienced folks, I'm attributing this something unique with TNSS's gear.

    Whatever the case, TNSS has done the right thing and has passed this on to XP to sort out and address, if necessary.  XP has not acknowledged an issue but they are looking into it at TNSS's request.

    Thanks, Chase.  Yeah, I agree that it sounds like much ado about next to nothing.  It does sound (former programmer here) that some variable or parameter is not getting cleared or reset properly, but under extremely unlikely circumstances.   Its something that XP would want to know about and correct, of course, but I'm not losing any sleep over it, I guess.

    Thanks for doing the translation for me... you're a true MVP!

  3. 8 hours ago, Jeff McClendon said:

    I’m originally from Georgia and I have trouble understanding the video maker too. Same thing happens when some people make my name…Jeff….have 4 or more syllables. When I visit some of my relatives I don’t realize they are talking to me sometimes.

    Anyway, moral of the story using V2.0 software is, don’t run the Relic Program with disc IAR on 5, then switch to Sensitive FT and change silencer to 1 and then switch back to the same Relic program. The bug may also involve using Goldfield and other programs alternately with a similar configuration. 

    I have never used disc IAR set on 5 in real life using the Relic or Goldfield programs. A setting of 1 is plenty for me.

    Hope that helps.

    I know this link is not about metal detecting but listening to some of my relatives and not knowing what the hell they just said reminds me of this:

     

    Hah!  Fun and informative both, Jeff.  Much thanks. 

    I Do use Relic with AIR 5 and frequently switch over to SFT, so I may have to keep an eye on this.   I haven't updated to 2.0 yet, but I guess we don't know for sure if this started there, or if it existed already in 1.1

  4. I don't speak Tennesseean and have a hard time understanding his videos, and it gets even harder when he's going through the settings with glare on his screen or the camera cutting off part of it.  I do use the Relic program pretty regularly though.  Could somebody give a short written explanation of this bug so I will at least know if it is something that I should be concerned about enough to try to decypher the video?  Thanks.

  5. On 2/29/2024 at 9:03 PM, Lodge Scent said:

    Mark, that's normal behavior for the D2. Nonferrous at the edge of detection can sound like ferrous. I'm not surprised that when you raised your coil when over a faint deep target that it went from "good to bad".

    Yeah, a dime at 8 inches is just on the edge of the detection zone for the soil in my area, at any rate.

  6. On 3/19/2024 at 3:16 AM, UKD2User said:

    There's a big difference between falsing and (un)masking.

    1) Falsing = iron sounding better than it should (usually because of size/shape/holes/corners/rust).

    2) Masking = iron making an adjacent nonferrous target sound worse than it should.

    Increasing Silencer will move the decision-point towards iron in both the above types of situation. Silencer will help to reduce falsing but effectively increase masking (a trade-off as per usual). I nearly always use Silencer=0 and use other methods to spot falsing.

    Exactly.

     

    The way that I understand masking (or, at least the way that I'm using the term) is when the RF from the coil hits iron and causes a magnetic field around it that hides the non-ferrous object.  That's why reducing power can sometimes help to minimize it.

  7. On 3/16/2024 at 2:17 PM, Gary XP said:

    Great review, thanks for your feedback 🤝👍

    Gary,

     

    I don't think I've heard how you came to hear about Tekkna.  You are certainly the one that has made it a household word but who put it together?

     

    Also, (and more importantly) do you know why discrim was set to 42, and not 41 or 43 or some other number?

  8. On 3/10/2024 at 3:18 PM, UKD2User said:

    I noticed that Gary says in one of his videos "XP don't fix it!". I see on a different YT vid by IffySignals that unmasking is not very good with Tekkna - at least if based on Sensitive FT prog 3.

    I think that one of the reasons people like these settings is perhaps simply because it makes it easier to 'see the wood for the trees' in an otherwise 'busy' (audio) environment - psychoacoustics?

    As I understand it, there are only a few settings that can really do any true "unmasking"... a lower sensitivity to reduce induced magnetism,  and a higher reactivity to speed up the processing from one target to the next.  And in a sense, I suppose it could be argued that silencer helps with unmasking.  

  9. On 12/31/2023 at 7:22 AM, F350Platinum said:

    Nah, you're implying that I'm misinforming people. 😏 I'm not going to preface everything I write now and in the future with "IMO" because the high and mighty Iron Buzz called me out. 😠 This is the second time you have gainsaid me from an armchair.

    I would not have answered this person if I didn't see the same results myself and discussed it with others. I offered a solution, twice. Might have been a little hard on him but he's a nice person. No one else attempted to help him.

    Show me the results then. "Source". Let's see some hard documented proof that you're so experienced with the D2 you can make an opposite claim and cause conflict. I'm waiting. Perhaps I'm so prolific I annoy you, but I'm not going to stop offering observations. Fact.

    I'm sorry that you are taking what I said so personally... it was never meant to be anything other than a general criticism of offering subjective observations as actual fact, no matter who does it.   I didn't call you names, such as the one you just called me... it wasn't personal, but calling me "the high and mighty Iron Buzz" is.  What's so hard about preferencing your opinion with "IMO", anyway?

  10. 12 hours ago, F350Platinum said:

    That I'm sure is fine, but my whole point here was that manufacturers will fix hardware and make changes, and reserve the right not to tell you. I don't think a single company tells you everything.

    Did they "source" that V1.0-V2 made the detector more bump sensitive? No. In that simple respect, every program was changed. Heh, about the only one I don't use is Goldfield.

    It's a plain fact that the D2 is now overall more bump sensitive. 🙂 Have you been using V2? I even told the OP when I noticed it.

    I feel as though you were implying I'm misinforming, since you quoted me. 🤔 Hey, I'll take a gauntlet to the face anytime. 😏

    My mistake was assuming the OP was afraid to update, and then he explained why. We're good. If he doesn't want to roll with the new punches, that's his choice, and I wish him well. He wanted to know if it was just him that noticed it. 🙂 It's not just him.

    > feel as though you were implying I'm misinforming

     

    Not at all.  I was simply taking exception that you stated opinion as an absolute fact.  Unless you have some sort of inside knowledge,  then you don't know any more than we do.  Your opinion may be better informed than someone else's, but it is still opinion.

    Yes, I have been using V2 and I have not seen a difference in bump sensitivity, and I often detect in harvested corn fields where I am constantly bumping corn stalks.

     

     

  11. On 12/28/2023 at 5:35 AM, F350Platinum said:

    You don't understand because you don't see it in a changelog? 🤔

    My friend, If I lived my life having to see something in print to believe it, I'd have walked off a cliff while looking at my phone for directions. 🤪

    All companies that make electronic devices reserve the right to change some things without telling you to protect themselves from liability, for security, and to avoid embarrassing situations. We are telling you that more has changed than they print.

    We are the people who have used this detector since it first sold. I personally have hundreds of hours using every version, I have every coil, headphone and accessory.

    I'm thinking you may be afraid to update the machine. If so that is fine, but don't argue with experience. 🙂

    There is a LOT of speculation, 2nd guessing, subjectivity, and outright misinformation in this hobby. I DO like to see information sourced.  I'm sorry but I have about as much experience with the Deus and Deus II as you do, I'm sure, yet I also haven't heard anything from XP about the improvements that you say they included in the V2 update.  I suspect XP engineers and programmers get a big chuckle out of the claims they see in the forums about things that never happened.

  12. 5 hours ago, Sinclair said:

    That will be the main reason you've missed presumably small stuff. There will be a lot of trash in that range, but some good things hide in those lower numbers ☺️

    Sometimes I'm willing to risk that though, if it reduces the signal/noise ratio for me.

  13. That's interesting, but not enough information yet.  What were the conditions like there... both ground mineralization and nails (and anything else that may be relevant, like hot rocks, etc)?  What were the other settings, and why did you notch out (zero volume) 0-38?

  14. 6 hours ago, CPT_GhostLight said:

    You folks in the North Star State are a hearty breed! 😎

    I try to detect all Winter too between freezes and thaws. At some point it usually freezes everything hard and many places will stay frozen until the Spring thaw. We've had more early freezes this year though so I just try to get out when I can. 😉

    I dug a 1904 Barber dime today, and my partner an 1888 Seated dime.  The ground was not one bit frozen!

×
×
  • Create New...