Ver 1.0, 1.1, 2.0 Update Consolidated Information - Post Your Unbiased Impressions And Observations Here

[Daniel Tn]

My last time using the D2 was with the .71 version.  I liked it then but ended up letting the unit go.  I hadn't even followed any of the updates or anything...been busy with other hobbies.  For some reason though, I decided to give the D2 another try.  In doing so I saw they were up to version 2.0 now.  I have used it only a few times but I can already tell...this thing isn't going anywhere.  Pretty significant improvements from .71 to 2.0 IMO.   It runs really well and smooth and I just like it. Everything about it.  I'm actually getting ready to price all my other detectors now and just keep this one. 

[F350Platinum]

11 minutes ago, Daniel Tn said:

My last time using the D2 was with the .71 version.  I liked it then but ended up letting the unit go.  I hadn't even followed any of the updates or anything...been busy with other hobbies.  For some reason though, I decided to give the D2 another try.  In doing so I saw they were up to version 2.0 now.  I have used it only a few times but I can already tell...this thing isn't going anywhere.  Pretty significant improvements from .71 to 2.0 IMO.   It runs really well and smooth and I just like it. Everything about it.  I'm actually getting ready to price all my other detectors now and just keep this one. 

Wow Daniel, that's a bold move and statement. I ended up buying a second RC so I won't miss out if one goes bad. ?

I usually have faith in updates and have been on 2.0 for a while now, it really did make a big improvement.

Glad you didn't give up on the D2 but keep something on hand... ?

[Lodge Scent]

I've been using Version 1.1 since it came out and figured last night it was high time to go to V 2.0. The controller updated no problem. Piece of cake. Next up was the WSA IIs. I followed all the steps, hit the update button and it deletes the old software then freezes up on the upload. Tried it several more times including different USB ports, no luck. Now I can't even shut off the WSA IIs. OK, next up is the WS6. Same thing happens. It erases the old software but won't install the new software. Now the WS6 is also stuck in the update mode and won't turn off. I mumble a few choice words and decide to deal with it in the morning.

This morning both the WSA and the WS6 are still powered on from last night. I plug the WSA IIs into the my laptop, hit Update and boom....perfect. Plug in the WS6, hit Update and boom.....perfect. I guess the server in France just needed a good night's sleep. ?

[Mark T]

Has anyone noticed any depth loss with 2.0 compared with previous versions?

 

[F350Platinum]

1 minute ago, Mark T said:

Has anyone noticed any depth loss with 2.0 compared with previous versions?

 

Absolutely not. ?

[Jeff McClendon]

On 1/2/2024 at 7:18 AM, Mark T said:

Has anyone noticed any depth loss with 2.0 compared with previous versions?

 

I haven't noticed any depth loss after updating from V1.1 to V2.0.

Similar to Daniel Tn, my experience with Deus 2 through all of the software updates has been that Deus 2 is now a much better detector than it was running even V.71 especially in the soil conditions around here. Better sensitivity (especially with the improvements to Goldfield), better overall depth, handles tough ground conditions even better than before, still super fast and remarkably target ID stable.

This time last year I was wondering if I would keep Deus 2. Now a year later and a few software updates later......it's a keeper.

[broadfield]

On 1/2/2024 at 2:18 PM, Mark T said:

Has anyone noticed any depth loss with 2.0 compared with previous versions?

 

No actually the complete opposite, I’ve found v2.0 the deepest of all versions.

[Jeff McClendon]

There  is a guy over on Friendly Forum that is reporting a loss of pinpoint volume level between V1.1 (1.0) and V2.0. He made a video of Beach Sensitive that purports to show a lower volume level for the pinpoint function in V2.0 using the remote with speaker volume on maximum and comparing it to V1.1 Beach Sensitive pinpoint function using the remote with speaker volume on maximum. He claims he was using default Beach sensitive from fresh downloads and that he maxed the speaker volume. His testing technique is totally wrong=waving a coin over a stationary 13X11" coil really fast with no standardized height for his fast coins swings. Also, the maxed volume for each software version test sounds really different to me. V1.1 speaker output sounds a lot louder than V2.0 even before the pinpoint test. Maybe that is my imagination.

https://metaldetectingforum.com/index.php?threads/deus-2-pinpoint.306275/

I have not noticed a pinpoint volume difference between the two software versions. I know there was an issue with the pinpoint function on the initial V2.0 WS6 Master software.

People commenting about how this is no big deal/irrelevant because they don't use the pinpoint function or use the coil pull back method is not helpful for this issue. Some people actually have to use the onboard pinpoint function for several legitimate reasons.

If anyone has two remotes with one having V1.1 and one having V2.0 software, could you at least check Beach Sensitive's pinpoint volume on a stationary common coin target  and use some kind of block about 2" high near the coin as a guide so that coil height will stay the same when pinpointing using the different software versions? Make sure the master volume level for speaker or headphones is the same for both software version tests.

 

thanks

[F350Platinum]

5 hours ago, Jeff McClendon said:

There  is a guy over on Friendly Forum that is reporting a loss of pinpoint volume level between V1.1 (1.0) and V2.0.

I noticed this and mentioned it a while back, I've read other posts that also mention it. I've also noticed the clock being wrong now more than ever.

I'll see what I can do, both my remotes are back at V2 but I don't have a lot of programs so I guess I could take a step back again on one to verify this. That is the advantage of having two.

I'm another one that doesn't use pinpoint much if at all, so it hasn't mattered much. I do use the clock a lot.