Chase Goldman

Dave, you haven't given us your baseline program settings so these suggestions are now just throwing stuff at the wall to see what sticks. I haven't encountered true black sand yet in 50 or so beach swing hours. Most of these like the salt sensitivity suggestion previously go to salt chatter, but hey, you never know. First of all, don't be afraid to go lower than 90 on sensitivity, if necessary. 90 - 93 is like the sweet spot for ops, so if you haven't lowered it below that then you really aren't attacking stability. Obviously if you press down to 80 you'll want to see how much depth you lose. I think you start falling off the depth curve rapidly in the low 80's and below. But again this goes more to salt stability than black sand. Tried GB in tracking? Using beach sensitive or beach? Have you tried Dive mode? I believe that lowers transmit power (not sure, I know it is less sensitive to micro targets at a top end of 14 khz) so might help with the headlights in the fog analogy. Where do you have disk set? Do you have iron volume on or off? Pitch or multi tones? Tried notching the TIDs associated with the black sand chatter? Increase reactivity to 2 or above. See if applying the silencer filter has any beneficial impact. Lower Audio Response.

Did you lower salt sensitivity before lowering sensitivity? I presume you left magnetic reject enabled (default).

It's more filling the 4500/5000 void created when ML decided to go full auto with the 6000 and didn't bother updating the form factor/ergonomics for those older form factor dinosaurs. With manual settings and decent iron blanking, those machines can still do certain things (at least for relic and treasure hunters) better than the 6000, not to mention that they have more coil options and they're cheaper. So Garrett threaded the needle there quite nicely with more versatility than the 6000 offers and probably plenty of 4.5/5K umph. I thought immediately of you hardNox when the Axiom reveal was complete.

Hey, I still have the Deus 2 But yeah, the GPX won't likely go until Axiom proves itself to me in the hot stuff. The ATX, however, hasn't really served as a backup for some time and should have put it up a couple of years ago.

It will no doubt handle the hot stuff. Already in line so I can give it a go in Culpeper this fall. You will likely see an ATX and 4800 on the classifieds soon.

Gawd, I hope it's not $6.8K (4×Gold Spot)...but I guess that would be an upper bound as that nugget isn't necessarily pure. I'm thinking 3K to 4K with the 2 coils max. We'll know soon enough. Jen you should start a price guess pool.

Hey, just let us enjoy our "hoopla" for awhile...we'll do the reality check later...

Guess I called it. Just didn't have the name - Axiom. I like what they showed. Can't wait to hear about performance from independent 3rd parties, don't trust that Steve H guy . Guessing we're talking $2 to 3K (including the dual coil packages).

Agree. It is unlikely. The real problem is not just the demise of APTX-LL but that ML and Nokta (apologies for bringing Nokta into a ML thread, but it's relevant) went all-in on APTX-LL with the GPX 6000 and Legend without providing their proprietary wireless hardware radio systems (Wi-Max for ML and "Green" wireless for Nokta) as built-in backups for their two newest detectors. Doh! Poor decisional foresight in both cases (Equinox supports Wi-Max and BT-LL) and now Nokta has to provide a new wireless pinpointer with a dead-end BT technology (APTX-LL) for compatibility with Legend. Hope they at least retain Nokta "Green" wireless compatibility on the new wireless PP and consider forward fitting their proprietary wireless radios into a future variant of Legend. However, regardless of APTX-LL's demise, there is still plenty of quality, legacy APTX-LL hardware out there (see this thread) like Avantree Torus and other excellent Avantree offerings, Creative has some great APTX-LL phones, and some others that should provide several years of reliable service until the next generation of wireless detectors hit the streets with the APTX Adaptive or whatever comes down the pike at that point.

As a hot dirt relic/treasure hunter where the PI rules over any VLF (except in thick iron), I felt ML abandoned us with the GPX 6000. If ML would have basically delivered a GPX 4500/5000 stuffed into the GPX 6000 form factor with wireless audio (while eliminating some of the arcane GPX 4.5/5K user adjustments that really never get touched but not going full auto like the GPX 6000) with the same GPX 5K timing options and ferrous blanking circuit, EMI performance, and compatibility with GPX coils and I would have been a happy camper (I might even have been able to stomach the GPX 6000 asking price, but would have been hopeful they could have lowered it a couple K). But instead, I would gladly take an ATX in an APEX-like package (but weatherproofed) with the ATX controls/features (including ferrous grunt but would really like the ML GPX ferrous blanking circuit) intact but translated to a decent UI, use of a powerful but light LiPolymer stack that can deliver the required V-A needed for the PI pulse and a variety of DD solid coils (and monos for the gold prospectors) in the 11 to 14" range. I like the GPX threshold and GPX target tone instead of the ATX doorbell bing/bong bong/bing but I could live with that if need be. Just really need it to be light and wireless compatible with decent EMI immunity. Curious if any TDI DNA ends up in this new Garrett if it does turn out to be a PI. But would rather Garrett lean toward the ATX vs. the TDI.

Yeah. That is the way to go if you find the speaker has too much delay using its own built in BT receiver.

Unfortunately, you appear to be mixing apples and oranges. Not surprising since the Bluetooth standard is generally a just a confusing jumble of technical jargon for the average consumer/end user to interpret, manufacturers of BT hardware provide woefully inadequate, ambiguous, imprecise, or incomplete descriptions of equipment features and the BT "standard" itself even presents technical challenges and incompatibilities for the manufacturer trying to incorporate the BT compliant technology into their equipment. BT 5 does not affect latency it is just the latest standard that supports the family of latest BT features, control protocols, codecs, and hardware that could be used. It is up to the audio equipment manufacturer to decide what subset of the BT 5 supported features (such as low latency codecs like APTX LL) to include in their BT 5 compliant equipment. It is the codec (hardware/soft combo that encodes/compresses/transmits/decodes the wireless audio) that affects latency. So BT 5 is not "faster" than 4.2 and BT 5 does not determine latency, but it is true that it theoretically can incorporate lower latency codecs that may not be compatible with the BT 4.2 standard. BT 5 is not a codec like APTX LL it just supports APTX LL, but the fact is BT 4.2 also supported APTX LL. The device itself has to have the proprietary hardware (APTX enabling chipset) to support the low latency codes. If you do a deep dive into the reviews you'll see folks complaining about high latency that in this case manifests in video being out of sync with the wirelessly transmitted audio to the speaker. This latency issue is not just an android issue BTW. Surprised you took the leap on the purchase despite asking for feedback ostensibly before purchase. Some folks find the latency of even APTX low latency wireless (40 ms) to be intolerable others have no problem with delays up to 1/4 second (250 ms) which is likely where this speaker falls out. Anyway, good luck, hope it works out...maybe you will be able to deal with it and it will be a non issue for you as the price is right at $20.

The Avantree Torus neck speaker discussed below and in other threads (just search the forum on Avantree Torus) is a popular choice for GPX 6000 users as, unlike yours, it supports APTX low latency AND you have the option to use the built in earbuds for specific situations. However, unlike yours, it is not waterproof but being wireless, it can be worn on the inside of a hooded rain jacket. Yours is a lot less expensive, but I think you will find the lack of APTX Low Latency compatibility (which is the standard Minelab relies on for the 6000 and also Equinox to remove excessive audio delay present in most non-low-latency bluetooth speakers and headphones/earbuds) to present an intolerable delay that will affect your ability to center on and pinpoint targets.

Looking forward to the finished product, Steve. Meanwhile, nice homebrew rig, Dave, can't wait to hear how it does on your next trip down south.

Set Salt sensitivity as high as you can for stability (less chatter). If you set it lower to gain stability the trade off is loss of sensitivity to small gold (or mid-conductive targets at TID 30 that now look like salt as far as the detector salt sensitvity filter is concerned).

Same here. Supposed to long press the pinpoint button, but could never get Fd to show up. Must be missing something. Love the added features/functions but the obscure icon driven/multi-function menu system is getting a little unwieldy (non-intuitive) with all these "secret" key press combinations to activate/adjust these features. The seldom used ones are hard to recall in the field. Getting to the point where I need to keep notes on my phone or at least a laminated cheat sheet.

We are not XP so not much we can do about it, so yeah, you’re effectively just complaining. But that’s ok. Maybe Gary Black or someone from XP will read your disappointment and bring it back to XP. I am not personally seeing a groundswell of dissatisfaction with D2 other than coil ear wear , so if XP is only hearing a few people complain about pinpointer issues and lack of coils or a future update schedule and it is not hurting sales, not likely to see a change in behavior. I have both Legend and Deus 2 (and Equinox) they are all 3 excellent overall machines and each have unique strengths that I exploit for different situations. So if you want to vote with your wallet and get a Legend and you highly value customer focus, I think you will like Legend. I’m personally happy with 0.71 - it seems like they were responding quickly to issues with ver 0.6 and features requested in the wake of the initial launch of the D2 (e.g, big TID digits), a 95+% solution missing only Mono gold field, small elliptical (I have no use for the 11x13) and finally releasing their companion app. The PP connectivity comes and goes without rhyme or reason.

To be clear, never said it was an excuse, I wanted to make sure people knew "them" was a one guy operation to put order fulfillment times in perspective. I stated clearly in my post that even one person operations need to at least communicate early and often what is going on or lose sales, totally agree on that point. That means when you hang up a shingle as a business run by one person or with 1000 employees you had better at least be answering customer emails quickly whether you are on vacation, sick, or whatever. Especially true for one person ops when quick turnarounds are difficult if product demand surges or when you're sick, on vacation etc. All the more reason to, if anything, communicate MORE frequently than bigger businesses because you will more likely be in a situation where your ability to supply product doesn't meet the expectations of those used to dealing with bigger operations. We have a few one guy business that regularly advertise and post in this forum and who have excellent customer focus and comms. It can be done by one person, provided you are committed to the customer and, thereby, commited to the success of your business.

"Them" is a one-guy operation, not Kellyco, so folks should set their expectations accordingly oturnaround time. On the flip side, if you do decide to embark on a single-handed business model, this thread is a good case study of how you can quickly lose sales simply because you are not communicating well with existing and potential customers.

Providing and uploading a video of the behavior, if possible, would also be helpful.

Noise could be one of several sources - Ground noise (are you sure you are GB properly?), EMI (did you try frequency shift noise cancel), mineralization in the ground/ferrous fragments - so what are your filter settings (Discrimination, bottle cap, and silencer)? For us to help you, it's best for you to start with your custom program. What factory program did you use as your starting point? Then go through your custom settings. A little background on your experience with detectors and detecting would help us understand if there are any general/basic conceptual issues associated with detector setup you may be struggling with, as well. Standing by to help...

I've said it before...XP needs to provide a single (mono) frequency variant of Goldfield (like they did with the D2 discrimination Programs), and preferably a small, high frequency/FMF compatible elliptical coil. Of course, if they manage to pull that off, there really is not much reason for the D1 and Orx to exist (other than 0RX price point due to its limited features/settings). So there's that...

They will once they get to final release (except for any post 1.X version that contained a major bug). As explained in the previous post, any version less than 1.0 is not final release. We're still technically beta testers until 1.0. Not really ideal, but that's the way it is, XP needed the broader user base beyond their initial testers to really shake this out. SInce it's not final release yet, they are going to limit how far you can roll back at this time to ensure you get no further back than the last stable version without major known bugs (i.e., 0.6 version (3-11-22)). At least you can roll back to that version now from 0.71. I DO know that I was pretty upset when the "broken" 0.6 version was released in March (also upset they lost software configuration/version control and released no less than 3 "0.6" versions without using minor revision numbers to alert users but that's a separate story). Perhaps they are waiting for the Go Detect app to be released world wide before they go to Ver 1.0, who knows...

I had a very similar experience with this baby...

Happy. Now, waiting for that LG24 Coil...