Taking A Pass On V3.10!

[damatman88]

I was cautiously optimistic about the new update 3.10. I was however pleased to see negative silencer settings and the new Pitch 2. I downloaded the new version yesterday.

I am predominantly a beach hunter on the east coast and have extensive experience with the D2 on wet salt sand. 

After a roughly 3 hour beach hunt today and tweaking my settings based off Beach Sens (to mimic my old setting on V1.1 mostly the same), this is what I found: Trying the new Pitch 2, I noticed that the normal mild falsing I got with the regular Pitch tones was accentuated in Pitch 2 to the point that it was giving too many good sounding signals to stop you, but there was nothing there when it was investigated further. I switched back to Pitch. My second issue was volume. I could not get the volume to match the V1.1 with the new V3.1, loud, but just not the same clarity. Lastly, my biggest issue, and this is the deal breaker: Target ID does not appear on the screen on deeper targets or even just a few inches down. Also very small targets did not ID effectively. Only when I scooped the target out would it ID. This is completely different from the old version. I would often brag to other detectorists about how dead-on the ID is on the D2, even at extreme depths. I also own a Manticore, and it does not compare ID-wise with the D2 (V1.1). Luckily, I dig everything sans obvious iron targets on the beach. I just can't give up the ID, nor should I.

I'll be switching back to V1.1 until XP can fix these bugs.

[Lokator]

You have just confirmed and summed it all up in much more detail than me (another post I made on the TID problems)

All the other problems you describe have also been my experience too!

I assume you have used the Standard FMF coils?

The best I could do was to use the 14khz frequency which does improve things somewhat but I still found it unacceptable.

i have emailed XP and they replied and said they have not seen any TID issues with the V3.10 software on the beach and require a video showing the problems.

I’ve had enough and have just simply gone back to V2.0 

 

[damatman88]

1 hour ago, Lokator said:

You have just confirmed and summed it all up in much more detail than me (another post I made on the TID problems)

All the other problems you describe have also been my experience too!

I assume you have used the Standard FMF coils?

The best I could do was to use the 14khz frequency which does improve things somewhat but I still found it unacceptable.

i have emailed XP and they replied and said they have not seen any TID issues with the V3.10 software on the beach and require a video showing the problems.

I’ve had enough and have just simply gone back to V2.0 

 

Thank you for emailing XP. And yes, I was using the 11" FMF coil as always on the beach. We can't be the only ones having these issues. 

Anyone else?

[Chase Goldman]

I also took V 3.1 for a spin at a local tidal salt bay beach site this past weekend.  Perhaps not as high salinity as an ocean beach site but it did exhibit salt conditions in the wet sand and shallow water.  

I too can confirm that Pitch 2 in Beach Sensitive with the 11" FMF coil resulted in unacceptable falsing on most ferrous targets and also hindered "manual" coil edge pinpointing on all targets.  This appeared to be because the Pitch 2 signal was very coarse and did not show leading and trailing edge intensity ramps as you swung over the target compared to Pitch 1.  Because of this behavior, I defaulted back to Pitch 1 and the falsing was greatly reduced and I could resume normal coil edge-based pinpointing which I find to be more effective than the built-in coik based pinpointing mode.  If XP could implement Manticore-like pinpointing behavior, that would be ideal.

I will note that I was not experiencing any target ID blanking behavior at any depth with a variety of coin, sinker, jewelry, and toy car targets recovered in the wet salt sand with V 3.1, Beach Sensitive with the 11" FMF coil, contrary to Lokator and dataman88's observations.  Not refuting Lokator's and dataman88's independent observations on this salt beach TID blanking/delay issue, just saying I was looking for it and did not see it.  Maybe it has something to do with salinity levels.  At this particular beach I am able to run salt sensitivity to 9 with stable operation and the occasional moving salt water/sand noise glitch.

Bottom line is that I will only run V3.1 on a dedicated remote or WS6 Master Puck to accommodate the HF2 coil only as that is my only option with that coil, while retaining a dedicated V2.0 setup for the black FMF coils until this V3.1 falsing tendency and is addressed.  Very curious about this Beach mode TID blanking issue based on two independent reports even though I did not observe it myself.

[F350Platinum]

I too have tested the HF2 and V3.10 in both relic and beach situations now, just got back from my small beach, and last weekend I did a short relic hunt out back.

My "test beach" is a small white sand beach about 100 yards long. It's usually quite mild other than the brackish water salt from the river, but the river is really more fresh this year because of all the rain. 

Out back the soil is very mild, a blue marl clay mixed with quite a bit of sand.

In both situations the HF2 falsed on iron big time, in many cases giving a solid mid tone and ID on forged iron. I used my modified Relic program that is just perfect on V2, but this version not so much.

Every piece of iron in the above photo was a positive tone and ID from the 50s to the 70s. 🫤

I did find a couple of relics: 

A Tombac buckle piece stamped "SB", and a small flat lead disc cut like a pistareen.

Beach was all junk, the bottle caps pretty much sounded right but at the higher frequencies the small bits of iron showed up. I got nothing good there which tells me either the beach was detected recently or no one lost anything good. My first skunk of the year! 🫤 I haven't been there in quite some time now. There I used a modified Beach Sensitive program that again is deadly on V2.

53 and 89 kHz not only slide coins to a new set of IDs, but they also make iron sound great. I had to use 29khz but switched between them when I find something to check. No dice on getting an iron tone and ID on anything but 29 kHz for the most part.

I really wanted to compare the HF2 to the 9" round black coil, but I just don't have enough time right now. 😅 Life is getting in the way. I do know it maintains the same frequencies as before, but what else it does I don't know. 🤔

Would I recommend the HF2 for relic or beach hunting right now? 

Sadly, no. I'm glad I have 2 RC'S. Too much change in the software. 

🍀

[lowtone]

Thank you for this post, I just loaded 3.10 from 1.1. I also mostly detect the beaches in N.C.  I will probably go back to 1.1.   With 1.1 there was hardly any Falsing. 

[Lokator]

5 hours ago, Chase Goldman said:

I also took V 3.1 for a spin at a local tidal salt bay beach site this past weekend.  Perhaps not as high salinity as an ocean beach site but it did exhibit salt conditions in the wet sand and shallow water.  

I too can confirm that Pitch 2 in Beach Sensitive with the 11" FMF coil resulted in unacceptable falsing on most ferrous targets and also hindered "manual" coil edge pinpointing on all targets.  This appeared to be because the Pitch 2 signal was very coarse and did not show leading and trailing edge intensity ramps as you swung over the target compared to Pitch 1.  Because of this behavior, I defaulted back to Pitch 1 and the falsing was greatly reduced and I could resume normal coil edge-based pinpointing which I find to be more effective than the built-in coik based pinpointing mode.  If XP could implement Manticore-like pinpointing behavior, that would be ideal.

I will note that I was not experiencing any target ID blanking behavior at any depth with a variety of coin, sinker, jewelry, and toy car targets recovered in the wet salt sand with V 3.1, Beach Sensitive with the 11" FMF coil, contrary to Lokator and dataman88's observations.  Not refuting Lokator's and dataman88's independent observations on this salt beach TID blanking/delay issue, just saying I was looking for it and did not see it.  Maybe it has something to do with salinity levels.  At this particular beach I am able to run salt sensitivity to 9 with stable operation and the occasional moving salt water/sand noise glitch.

Bottom line is that I will only run V3.1 on a dedicated remote or WS6 Master Puck to accommodate the HF2 coil only as that is my only option with that coil, while retaining a dedicated V2.0 setup for the black FMF coils until this V3.1 falsing tendency and is addressed.  Very curious about this Beach mode TID blanking issue based on two independent reports even though I did not observe it myself.

I normally have to run salt Sens @ 3-5 on beach sensitive and beach @ 7 on my wet sand beaches here in the UK.

14khz can be pretty much maxed out on salt Sens @9 reactivity 0 and Sens @ 97

Some of the craters I dig for really deep targets (in 40/24 KHz) will just continue to sound off even after the target has been removed and is in the spoil.

sometimes you can dig a tiny target that is really shallow but you think it is really deep so you keep on digging down chasing ghost signals until you give up.

lots of times I have resorted to spreading the spoil out flat and received the signal only to find extremely small fragments that I could not locate in the spoil because it was not flattened out enough for the 13x11” coil to see it (hence why I keep digging down getting only a halo/ghost signal every time.

14 khz is much better which stands to reason and it will hardly ever false on open deep holes.

40khz is a real pain in the backside tho and seems far to sensitive for me and is the worst offender when it comes to open holes with nothing there.

Notching 00-00 does nothing to elevate the problems.

I've tried keeping GB perfectly balanced, tried reactivity settings etc but to no avail!

[ColonelDan]

My decision to pass has been reinforced once again. 
Good reports on an unfortunate situation.

[F350Platinum]

8 hours ago, lowtone said:

Thank you for this post, I just loaded 3.10 from 1.1. I also mostly detect the beaches in N.C.  I will probably go back to 1.1.   With 1.1 there was hardly any Falsing. 

You'd be much better off with V2, I also detect NC beaches. 🙂 The improvements they made with V2 were quite dramatic as well, many good things.