V3.1 Problem On Beach

[Lokator]

Been testing v3.1 along with all the beta versions on the salt wet sand beaches with the 13x11 and 11” FMF coils and cannot get the machine to TID on many signals at all.

I have had one silver ring that would not throw up an ID number that was only 9-10 inches deep and lots of other stuff that will not ID at all or very briefly.
Something is really wrong as V2 is just fine and IDs just fine on all but the very deepest of signals.

Is anyone else having this problem?
 

 

 

 

 

 

 

 

[Jeff McClendon]

I haven’t used Deus 2 with Beta 3 software at any saltwater beaches.

The places I have used Deus 2 with Beta 3.03, 3.04, 3.07 and 3.08 software using the HF2 and 11” FMF coil have all been areas with high iron ground mineralization. I have had zero issues with target IDs or depth. However, I used wired XP headphones for most of my hunting until public beta 3.08 because it was my understanding that up until then, the remote, WS6 and WSA ll were not totally supported when used together. 

[Lokator]

I also have no problems at all with inland detecting with TIDs etc and I really like the new features that have been available in the 3x versions but there is something really not right on the beach with all the standard coils.

its a bit similar to having Magnetic set to ON (accept) setting in other versions and going over conductive magnetic materials (you get No ID number but a signal allowing you to identify them but will still give a good ID on wanted targets.

On V3x with this setting on reject you still get this phenomena with lots of good targets.

it seems to mostly throw a number on first locating a target but subsequently locks up showing the - - ID most of the time.

 

[Lokator]

I have also noticed that the threshold tone no longer nulls out each time a target is approached and is now just a constant faint sound in the background that does absolutely nothing!

I used to use this a lot in V2.0 for several reasons so this now no longer works as it should on certain programs

This is applicable to all the beach programs the relic and general program which share the same issue. All other programs still work just fine with the threshold doing the job it is intended to do (nulling out in the presence of a target)

I hope someone can share their thoughts on this and confirm that they have the same issues.

 

 

 

 

[Jeff McClendon]

I have not tested or used any of the Beach programs. I also haven't updated to V3.1 yet either.

I did extensively test Goldfield a lot and Relic a little in the last three beta versions. I have not noticed any anomalies with those two programs since B3.07 private and B3.08 public were released. However, the new Pitch 2 (I think) is the default audio selection in the Goldfield program and Audio Filter is set to 3 (at least in public beta 3.08). Not sure about Relic. At least with Goldfield Beta 3.08 using Pitch 2, the threshold only faintly nulls when targets are detected. If I switch to the original Pitch 1 the threshold tone nulls quite a bit when targets are detected or when ground conditions change. In Beta 3.08, Relic does not have a nulling threshold that I can hear. I rarely used the threshold in those two programs in V2.00 since they did not offer much help for small gold prospecting and the volume ramp up was too quick at least in Goldfield V2

I asked XP to work on the Goldfield threshold volume ramp up and make it more gradual. They appear to have improved it in that way.

I don't know of any major changes to the Beach programs from V2 to V3.1 since I don't use them very often. Maybe there was a default settings change?????

[Lokator]

I have tried many different settings to maybe help with the issues but no joy.

if I could have V2.0 with the new pitch2 setting along with the expanded ground/iron break feature (for use with the FMF coils only) along with the auto scan feature when turning on that would be perfect for me in every way as I have no need to use the HF coil for any application.

i guess il have to stay with V2.0 but I’m a bit gutted that il never have the above features available anymore especially after being teased with them on V3. 
Shame really.

i hope someone can attest to the TID problem on wet sand and let me know their thoughts/solutions if any.

 

[raziel900]

are you having problems with the tid only with the beach programs or also with the general or relic program?

[Lokator]

I have not tried the general program on the wet salt sand for TID so could not really say as it’s home is inland (no problems there with it though)

I only really referenced the relic and general programs along with all the beach ones because of the threshold issues.

thinking about it it seems that all the programs that use conductive soil subtraction are also the ones that the threshold does not null out on.

has anyone used V3 on beach with FMF coils? 
I appreciate everyone’s posts thus far on suggestions and help!

 

 

 

 

 

 

 

[Jeff McClendon]

Sorry I gave a whole post to Goldfield. It was late and I should have gone to bed 😅

I did some testing with the General program using Pitch 1 and Pitch 2, iron volume off and threshold on 20. I could clearly hear the threshold nulling on ferrous targets using both forms of pitch audio. Staying with both forms of pitch audio, I had no issues with target IDs on 9" deep targets in my test garden that has dirt that completely fills up the mineralization meter using the 11" coil.

Sorry I can't help with the Beach programs. Do you get the same poor results using tones other than Pitch 1 and Pitch 2?

Maybe F350Platinum will chime in soon since he has done some saltwater beach hunts recently using Beta 3 software and just updated to V3.1 here in the USA.