Chase Goldman

Because we're on the third variant of 0.6 beta software. It's obviously still in beta with a punch list of low priority features that need to be addressed. I suspect they are working on improving threshold functionality.

Thanks Cipher - great list! Here’s some more for consideration… I would consider this light weight but effective 3D printed stem stand that will keep your detector from toppling over when you set it down https://www.ebay.com/itm/XP-DEUS-DEUS-2-ORX-stand-/115329220030 …or design/home brew your own. And this stem mounted pinpointer holder is also a great accessory… https://www.ebay.com/itm/XP-Pinpointer-Stem-Mount-for-XP-ORX-and-DEUS-PPCLIPSTEMKIT-/254565933091 Third party alternatives to the back phones also abound: https://www.detectingdoodads.com/store/p43/Over_the_ear_Treasure_Phones.html https://www.seriousdetecting.com/product/hd-compatible-wireless-headphones-for-xp-deus-deus-ii-module/ (these are hard to find in stock-just keep searching some dealers do have these in their inventory) https://highplainsprospectors.com/products/detector-pro-gray-ghost-xp-platinum-series-wireless-headphones-for-xp-deus-xp-deus-ii https://highplainsprospectors.com/products/detector-pro-gray-ghost-xp-headphones Not sure why you need to pay $20 more for acceptable crystal clear audio (Platinum series) vs. the standard phones (or that much total for dedicated XP Deus compatible only phones) but hey, they are an option. XP also lists all D2 compatible official XP accessories on page 44 of the user manual. https://www.xpmetaldetectors.com/uploads/files/document/manual-deus-ii-uk.pdf Still waiting for someone to come up with a remote control lanyard to capture your remote should it become inadvertently dislodged from your mount. The Detecting Doodads lanyard (see the site for the first set of headphones) is only compatible with the dimensionally smaller D1 remote control…

Jeff, IAR and threshold on the D2 VCO modes (Gold Field, Relic) is a completely different beast than it is on the D1/ORX. The threshold, unfortunately, is just a reference tone and does not break or null. Invoking IAR at any level other than 0 invokes ferrous “disc” such that any TID less than 0 or high on the iron probability level on on horseshoe display invokes an odd sounding iron tone (i.e., iron volume applies), whereas 00 sounds like ground noise, and then you get the standard VCO pitch tone on the “non-ferrous” targets that increases in pitch and intensity proportional to target signal strength. This was an eye opener to me and just recently discovered. I was used to IAR breaking up all target signals in hot dirt so I normally kept it at zero. More assessment and discovery needed by me now that I have determined it works differently. To me there is no finessing it by bothering with lower IAR settings from what I can tell. It just does not behave at all like the D1 in that regard. Now I can use relic mode as a true two tone ferrous/non-ferrous beep dig mode but will have to learn to ignore the 00 ground noise signals that may stick around even after you do a ground grab. It’s sort of intriguing, weird, and disappointing all at the same time. Learning how to “walk” all over again when it comes to Relic mode and non-zero IAR. I have not figured out how to optimally harness it yet…. You might want to hold off throwing your D1/ORX goldfield standard operating procedure and tips out there in response to the D2 Goldfield/Relic threads until you’ve had a chance to try it for yourself, otherwise you might end up confusing D2 owners who are newcomers the XP Deus platform. It’s implemented on D2 in a fashion similar to the D1 in some respects and in other respects (IAR, iron volume, threshold) it’s completely different. Would really like to see XP consider a mono variant of Gold Field to complement the two FMF variants on D2.

Legend covers all the simplex bases except accessory coil choices (for the moment), suggest selling the Simplex if you need to get rid of one, and the Legend will eventually get the accessory coils needed for those special situations. Legend and D2 (similar to Equinox and D2) make a formidable, complimentary pair of detectors that should cover most of the situations any detectorist might encounter. IMO.

Yeah. Deep HC is the way to go in your neck of the woods, Bob. I've found it works great even in thick iron as our hunts together have shown. With time, you will be able to audibly discern the tells on big iron and flat iron. Pitch tones helps on that as it can help you trace a target footprint as well as give you a combined iron and non-ferrous tone. At this point, stick with Deep HC and experiment with the various audio options (3,4, or 5 tones vs. Pitch vs. Full tones). For full tones, if you want to hear the iron, you need to lower disc to at least zero or slightly negative (I use -2.0) as there is no iron volume in FT. Pro Tip: Save your favorite "search" program to a custom slot (say the stock Deep HC program unmodified in slot 15). Then save a variant of that program in an adjacent custom program slot (say Deep HC with Pitch audio tones in slot 16) and if desired "full tones" variant in another slot (perhaps the slot BEFORE your "go to" main search program in Slot 14). Then when you hit a target you can cycle between the different programs using the +/- Keys to see how different the target sounds with the various audio setups. I call this interrogating the target and it can potentially unmask big falsing iron or give you other insights as to your dig decision. You can also use this approach to set up different program groups. Say for instance a deep group with reactivity set low or a thick iron group with reactivity set high and sensitivity set lower to keep the iron from overloading the coil as you are going for the shallower "un-masked" non-ferrous (that's the fast Sifter program which "unmasks" the non-ferrous). At the beach, different story, obviously. You'll be using Beach, Beach Sensitive or Beach P (Beach sensitive with Pitch tones). But you can also set up a beach group for beach target interrogation. The possibilities are endless, limited only by the custom slots. JMO but those old school "Sonar", "Deep" programs were great on the mono frequency Deus 1 but FMF Sort of makes them irrelevant, unless EMI or something compels you to have to go with a monofrequency setup (e.g., you want to use 4 khz to punch as deep as possible or you want 40 khz to sift for microjewelry). For example, Deep HC seems to render the Deep program irrelevant because the Deus 1 Deep program relied on a Deus 1 unique Deep target, mono frequency signal processing mode. Congrats and please leave something in the ground for me to dig on my next visit down south, will ya.

You will really want to explore alternative stem and shaft options because the 11x13 coil weight will flex the lower shaft even for shorter extensions. Never been a fan of earlier iterations of that coil (the weight and price premium over the 11 with limited improved depth performance as its a an 11x13 elliptical not 13” round) but it might be just the ticket for maximizing high conductor (HC) depth for the D2 which is proving to be an HC depth monster in milder dirt and obviously gives good swing coverage.

Completely followed what you were saying. It would be neat but it would also be a completely different detector design. The second paragraph of my reply addressed the wired coil option. We're talking about a wholesale detector platform redesign because the Deus/Deus 2 rely on the coil electronics not just for wireless signal transmission but the coil electronics also handles much of signal processing duties. That's why you can run the detector with either the remote or the smart headphone puck as the controller. In other words, as XP says, the brains of the Deus/Deus 2 platform reside in the coil.

Interesting idea, but I think XP would probably just be better off providing an external shaft insert battery like they did with the white elliptical HF coil and make it simply wading submersible like with the white coil. However. XP has also stated that the Deus 2 FMF coil electronics package also presents a challenge fitting into the small coil form factor. So an external power source doesn't necessarily solve that problem. Anyway, presuming the coil would still transmit and receive the control and target signals wirelessly and that the on-board FMF coil signal processing and radio electronics package could fit, it would still require a redesign of the remote connector to add more pins for coil power and you would have to change the power management system on the remote to deliver power to the coil (it only receives charge power). After all that, unless you could somehow fit a higher capacity battery in the remote, run time would be severely limited because both the coil and remote are draining the remote's battery. And as brys said, if you did want it to be operational submerged at shallow depths (even if not dive rated), you would still need to string up the waveguide antenna coax wire between the remote and the coil. If, instead, you wanted the coil to be purely a dumb wired coil you would probably have to redesign the entire platform from the ground up because the remote relies on the coil electronics to do some of the target detection signal processing.

I use the puck stem mount adapter as the protection. It's about $15 and also enables you to mount the puck to the stem of the Deus shaft/stem assembly if desired.

Here's an idea based on an eBay listing...these are hard to get given the situation in the Ukraine. https://www.ebay.com/itm/Bracket-for-Mounting-XP-DEUS-XP-ORX-Metal-Detectors-Control-Unit-on-any-Rod-/264321571573

Yes, as many have posted, the clip jack adapter plate works with the WS6 It's universally compatible to the Deus series (Deus, Orx, Deus II) as are 3rd party headphones that incorporate the integrated Deus/Orx/Deus 2 puck mount. And it is not so much a secret, as both the adapter plate and remote headphone adapter cable show up in the user guide as compatible accessories (p. 44)

I am not seeing any issues with the 3-11-22 version of the 0.6 update.

Yes, there is a Deus 2 book in the works...

They are APTX low latency confirmed with the "+" symbol on the Equinox.

Love it!

Make sure you read the manual to clear up your misconception regarding reactivity and transmit power and why 0 reactivity is not an optimal setting for all situations. I cut and pasted the relevant sections of the manual to help you better understand the concept of reactivity in the post below.

Again, no. Reactivity is NOT transmit power and Reactivity "0" is not optimal for all detecting situations. Please read the link below, I took the time to extract the relevant passages from the user manual in an attempt to clear up your misconception and in the hopes that you will quit putting this inaccurate information out there that can result in confusion for those actually trying to learn this newly released detector.

Heck's no, Sir. First of all - he reported the problems before and after a software update using the exact same settings before and after and lost depth. Second, he was probably in one of the Beach modes which have 0 reactivity as the default. With all due respect, transmit power is not the reason the signal strength increases in your video. It's the increased audio processing time of the target signal afforded by the lower recovery speed (please see the screens hots from the Deus manual below). The target signal duration is not cut off in anticipation of the next possible target encounter by the coil. On Deus 1, which was a single frequency detector. you could actually independently adjust reactivity and transmit power. Do you know why? Because they are independent of one another. Please show me where it's documented that transmit power is affected by the reactivity setting on D2. Also your 0 reactivity all the time recommendations are misguided and are refuted by the manual as shown below and in the following quote: "In terms of pure performance, the greatest detection ranges are obtained with low reactivity levels. However, you will find more targets and detect deeper on mineralized ground with medium or high reactivity levels so do not just rely on performance in the air."

First: That statement is technically/factually incorrect wrt transmit power. Second: Has nothing to to with the issue at hand.

Another thing I find annoying is that if you change the frequency of pitch tones it also changes the threshold tone pitch.

George, can't wait to hear how it does. Taking mine to Culpeper next week to see how it does against Equinox and D2 all with 11" coils. I opted out of the 6" round, not my cup of tea. Waiting for NM to release the planned 10x5 coil which is IMO a great form factor for hot dirt relic hunting (small footprint to counter ground noise effects but with decent coverage). Let us know how it goes.

Hold off until there are more reports here from those who experienced problems before but who now have the 3-11 variant that those issues appear to be resolved. I'll have A-B results between the "original" and the "3-11" versions of 0.6 software by Monday.

Couldn’t hurt…or could it. Let us know how it goes with the 3-11 version. Would like to know what the date stamp was on Paystreak’s machine that was acting up with the Big TID update. I’ve got 3-11 now too and this weekend will have access to machine that still has the “original” ver 0.6 to be able to do some A to B comparisons. Still wish XP would get their act together on version control discipline, change logs, and rollback paths going forward. But if they snuck a “fixed” version of the update in there that removes the issues documented during the past week or so, I can live with that for now.

Good stuff. Let us know how it goes with the 3-11 variant.

Yeah, I figured that out when I had a chance to check the RC “Infos” screen but you had already posted so it was insult to injury. Glad I now have some configuration data (date stamp) so I can compare “updated” and “non-updated” version 0.6 variants because XP can’t be bothered to increment version numbers, so thanks again for that…you know, “to be fair”.