slyworld

12 minutes ago, F350Platinum said:

Thanks for the heads up Slyworld, appreciate you dropping in. 👍 

Most people are reluctant enough to update, let alone go through a second process.

So we can just update the WS6 and do not need to update headphones and other things?

Of Course ! that's why I said : WS6 only 😉 the 2 other firmware (RC and WSA2) haven't changed !

On 9/13/2023 at 12:18 AM, Chase Goldman said:

CPT - Thanks for the report on the remote.  Let's see what Bob comes up with when he gets a chance to test the magnetic reject on his beach.  Simon - I agree the WS6 pinpoint bugs are egregious but with a common thread of conductive soil subtraction, they obviously botched a specific subroutine associated with pinpoint.  As far as I'm concerned, if the bugs are limited to the WS6 Master mode, then it doesn't prevent me from utilizing the benefits from the update because I don't even use the WS6 puck at all (in Master or Slave Audio mode).  On the other hand, since the bugs are so obvious, its likely that a new update will follow relatively quickly.  So I'll hold off for now until the WS6 is patched so I don't have to enter my custom programs twice.  

Hi all,

A new firmware for WS6 only is already available on the web updater to correct the pinpoint with soil substraction programs (just select the same version 2.00 and you'll see the little changelog)

Have a good day :)

7 hours ago, raziel900 said:

I don't understand, are you saying that having the silencer on 3 
increases the possibility of digging good targets between the iron??
I've always known the opposite in the middle of the iron the silencer must be set to 0!

At 0 and 1, the silencer is wide open and helps you find some good targets in the middle of iron but you have to dig a lot !

at 3 and more, the silencer transform some false signals from iron to pure iron signal so it's more comfortable if you have plenty of little iron.

on the V1.0, the silencer is a little more effective at high values if I remember well so to not change too much the program 3, XP decided to change from old silencer at 2 to new silencer at 3 (as I understand)

is it more clear this way ? tell me 🙂

23 minutes ago, Jeff McClendon said:

I downloaded the English version 1.0 manual when it was released and then downloaded the English version 1.1 manual today and printed the factory program default spec page for both manuals. The silencer settings for #3 Sensitive FT were different with 2 being the published default in v1.0 and 3 being the published default in v1.1. I did not check to see if that was actually the default settings using my Deus 2 remote.

When Xp published the V1.0, the manual had an error on this point that had been corrected later 😉 Check the V1.0 and you'll see that the silencer on the prog 3 is already at 3.

2 hours ago, Jeff McClendon said:

I am guessing that what you are referring to when using the words "recover" and "neutral" is Silencer on 1 in iron mineralized soil may be enough to quiet down some falsing from man-made and natural iron but Silencer on 0 is much less likely to mask some non ferrous targets with poor orientation or shift the responses of smaller targets with IDs near the ferrous/non-ferrous tone break over to ferrous due to too much iron filtering on mineralized ground.

Sorry, I don't exactly understand what you're talking about. I try to turn my explanation in another way : Silencer is an active filter even at 0 because it recover some target from the ground values so if your goal is to find the less "active" state of the silencer, the more neutral state, it is at 1. (I hope it's more clear, sorry for my bad english...)

2 hours ago, Jeff McClendon said:

The latest online manual shows that XP changed the Program 3 Sensitive FT default Silencer setting from 2 (version 1.0) to 3 (version 1.1).

No, the silencer changes to 3 since the V1.0 not since the V1.1 and it's because this silencer (from the V1.0) is more "aggressive" to help you find some good targets near to iron.

14 hours ago, Chase Goldman said:

However, if you have info direct from the XP R&D team that confirms your original statement on base program equivalency, that would be helpful to know.

Yes, it's the case 👍

For your second question, about silencer, when XP said "With settings below 2, it improve performance on mineralized ground." in the manual, it's because with silencer at 0, the algorithm can analyse the ground area to "recover" some targets. So if you want the most "neutral" position of the silencer, it could be found at 1.

On 5/23/2023 at 8:33 AM, AlwaysCocaCola said:

Agree.

Also about new features in update.

For example, WS6 v1.0 add frequency scan for long press "-" button.

Very useful, but there is no information about it anywhere. 

Just check the user's manual ! 😉 it has been updated since the release of the V1.0.

https://www.xpmetaldetectors.com/uploads/files/document/gb-rc-deusii.pdf Page 33

On 5/22/2023 at 3:48 AM, Chase Goldman said:

XP has never really explained what frequency addition means.  So that could definitely affect the FMF frequency spectrum for modes that otherwise "look" identicsl.

However, the beach modes use conductive ground subtraction which makes sense in the beach modes, as salt conductivity is being notched out.  Perhaps Beach Sensitive, in addition to having a higher Max F, has less of a salt "notch" to provide greater sensitivity to small beach gold.

Still surprised they behave that differently.

Dan - Can you be more specific about how you set up the two modes to be identical and what was different about how they behaved?  Specifically, did you set up Beach to emulate Beach Sensitive or vice versa or both.  I know it shouldn't matter if they are identical.

The only adjustable parameter defaults that are different between Beach and Beach Sensitive are Max F (24 and 40 khz, respectively) and Salt sensitivity (9 and 7, respectively), I believe.

Thanks for checking that out, Dan.

 

 

Hi,

To stay simple, Frequency addition means that you take every response of a target from the different frequency the D2 use, you average all the results and you convert to a sound. so for example, you take a little piece of aluminium that can't be taken by far with low frequency and you take a very high conductor that have a scratchy sound with high frequency, with a program who have frequency addition, you can have a good signal on both target because you use the response of all the frequency range between high frequencies and low frequencies.

For the conductive ground substraction, you do the same but because you use multi simultaneous frencies, you can compare every signals and you can identify the signature of the conductive ground and you can litteraly substract it from the final audio signal. the salt sens can widen or narrow the window of this substraction. the big difference between ground substraction and notching is that with notching, you detector see the notched target but it cut the sound so there is a masking effect. With the substraction, it's like pure magic, the conductive soil is wiped out so your detector can pass trough and even if you have a little target witch will normally be masked, here you can see it clearly like in an air test 🙂

all these explanations is my way of seeing from the explanations I received from R&D XP team.

Hi all,

For your first question about differences between factory programs, except what you can change by yourself (including Freq. Max), program 2,4,5 and 6 are identical. Same for 10, 11 and 12.

Or you have also this custom program form at the end of this XP document : https://www.xpmetaldetectors.com/documents/0/gb_rc_deusii_v1.0_changes.pdf

😁

Have a great day !

22 hours ago, Chase Goldman said:

Thanks, that's a passable workaround, but the processing and sensitivity in the disc modes even at -6.4 disc is still not the same as Goldfield (you can see that when comparing that setup with Gold Field in the Deus 1 on micro mid conductive targets).  Also, beside the loss of the "two tone" ferrous/non-ferrous audio you get with IAR, you also lose the Gold Field/ Relic threshold functionality doing it that way.  Mono Gold Field should eventually be provided.

When you select Pitch, you have the threshold available in any program 😉

On 5/22/2022 at 3:34 PM, Chase Goldman said:

Since the detector can't differentiate a ground anomaly from a legit target, if you notch 00 then yes, you will exclude the audio of a 00 target (you will still see 00 displayed as notch only suppresses audio)

When you notch an ID, you will not hear it, yes but you will not see it anymore too ! the only clue that there is a silent target under your coil is the horseshoe or the XY that display the target signal.

On 5/23/2022 at 3:31 AM, Chase Goldman said:

But remember, on Deus 1 GF is switchable single frequency and can be used anywhere from 4 to 80 khz depending on the Deus 1 coil that is used.  IMO, XP needs to explore providing a selectable single frequency variant of GF/Relic on the D2 as a future update, similar to the D2 Deus Mono Program 7 for the "Discrimination" modes, to give GF/Relic some additional capability for specific target groups such as sub gram gold and high conductors.  For smaller target sensitivity and tight spots, a 5x10 coil would also be a welcome addition.

If you want to have a single frequency GF program on the D2, you can try to set the prog 7 with a -6.4 discri and the Pitch setting, of course, you'll not have the IAR discri but you can use the ID display to help you choose if you want to dig or not 😉

Sly

On 5/5/2022 at 6:56 PM, CPT_GhostLight said:

Thanks, guys! I remember the bit in the video about 00-00 being the catch-all bin for an unknown target. So you are saying that OFF lets the unknowns through and 00-00 notches them out, correct?

 

Unknown targets usually don't display any ID's, targets with 00 ID stand for all ground targets like deep target that have their ID pull down by the mineralization but also hot rocks, ferrites, potteries and some kinds of very thin and damaged iron too. So if you enable the 00-00 notch window, in reality, you notch all the ground part of ID's, in other words, you notch the -6.4 to 0 window.

12 minutes ago, Carolina said:

Well it worked for me 6 weeks ago and been fine ever since.

Happy to hear it but I think it's not the "hard as hell" press that works, maybe only the long press :)

3 hours ago, phrunt said:

reset your remote? Do you mean recover the corrupted firmware?

Do you know if the flash tool reads/writes/verifies or is it just flashing and hoping for the best?

Normally, to recover from this situation, you have to send your remote to your dealer/distributor to let him open the remote, disconnect and reconnect the battery in order to reset it. It's a special procedure that preserve the warranty in case of water sealing problems. So, as far as I know, it's not a firmware corrupted problem.

7 hours ago, Carolina said:

This will sound really crazy, but mine did that and after pushing the start button hard as hell and holding, it came to life . Now it works with normal pressure on and off. Good luck to you.

"Hard as hell" 😓 please don't do that for the sake of your remote ! there is no pression sensitive button on the Déus II remote 😉

On 4/28/2022 at 8:25 PM, Naildiggerpro said:

Just updated and unplugged from computer and my remote won’t turn on it was fully charged , any ideas on what to do?

Sorry to hear that....Contact your local dealer to know what to do (normally, you have to return the remote to him or to the US distributor) they will reset your remote and send it back to you.

1 hour ago, PeterED said:

On the XP update page, we could be warned in advance when the customer programs will be deleted again. I was not the first to be surprised by this. I just signed up for the newsletter. Let's see if I will be informed about updates.

https://www.xpmetaldetectors.com/en/ba/the-blog/deus-ii-v0-71-update-instructions.php

 

As I understand the update process, you have to take in account the version who is actually in your remote before the update ! example : if you update to 0.71 from a v0.5 or 0.6, it will erase the custom programs but if you do the same from v0.7, it will not. With this fact in mind, you can easily understand the problem to explain to users if the new version erase or not custom programs and headphones pairing.....

17 minutes ago, PeterED said:

Update to 0.71 performed. Customer programs were not deleted this time.

Of course :) v0.7 and v0.71 is very close to each other. If there is no modification concerning settings recorded in custom programs between 2 versions, the update don't erase custom programs.

Version 0.71 out !

It correct little bugs you have shed the light on.

the ChangeLog :

https://www.xpmetaldetectors.com/en/ba/the-blog/deus-ii-v0-71-update-instructions.php

10 hours ago, 67GTA said:

The only key setting I've seen so far is discrimination. I can't duplicate this unless discrim is at -6.4. You can leave all other settings unchanged apart from the discrim and it will still work.

This bug is based on a negative discri setting (no matter if it's at -6.4 or -0.1)

Other users reported this bug from the other side: problem to identify some iron

Xp already corrected it on the upcoming version 😉

13 hours ago, Chase Goldman said:

Sly - as someone who apparently has ties directly to XP or at least first hand comms, any perspective you can shed on whether the issues regarding visual target ID responsiveness and dependency on tone selection (i.e., target ID response on a given  target varying due solely to whether a user has selected multi-tones, full tone, or pitch) as demonstrated in user videos and anecdotal reports have any validity and, if so, whether the issue is being evaluated by XP?  There is some trepidation amongst users to loading this update due these reported issues.

I have seen these videos and I have tried to reproduce this behavior with more or less success so I don't personnaly did a Bug report on that point but maybe someone else did.

Concerning XP, I really don't know if they beeing already evaluated this, I had no return on that, sorry.

13 hours ago, PeterED said:

Oh, thank you 😀

Confirmed, already corrected for the next update.

2 hours ago, PeterED said:

Save a program to P20, P22, P23 or P24. The name of the memory location is always P2.
I reported this to XP France in februrary. No reply to my feedback.

Reported few minutes ago, thx to you and the person who report it on FB ! 

1 hour ago, slyworld said:

And this time, you have the opportinity to go back to v0.6 😉

happy updating ! 😄

and the v0.6 that is available now is the ORIGINAL from january ! so you can compare if you want 😉