Rob I searched and found you recommended running 0 tone for rejected items. I made a custom tone level for most all coins. I understand this most likely takes a little load off the detector. Question is do you turn on all Discrimiation and set up 0 tones or leave on the Discrimination. I want to do whatever will make my V3i the most effecient. I have not been posting much but I am still hunting. Found a Wheat Penny yesterday and never even looked at the date. I also found a Nylotis Compact made in 1920 or so.
Find's Treasure Forums
Welcome to Find's Treasure Forums, Guests!
You are viewing this forums as a guest which limits you to read only status.
Only registered members may post stories, questions, classifieds, reply to other posts, contact other members using built in messaging and use many other features found on these forums.
Why not register and join us today? It's free! (We don't share your email addresses with anyone.) We keep email addresses of our users to protect them and others from bad people posting things they shouldn't.
Click here to register!
Need Support Help?
Cannot log in?, click here to have new password emailed to you
Changed email? Forgot to update your account with new email address? Need assistance with something else?, click here to go to Find's Support Form and fill out the form.
VDI Tone 0
- Thread starter daddyflea
- Start date
WHY Zero Tones
The main reason I don’t reject VDI is “The way the code is written the detector can react faster by having it accept all targets and setting a 0 tone to the ones you don't want to hear, rather than rejecting targets. “(From Anne who wrote the software)
Now it depends on what you want.
There can be a little difference.
1) For an example, say you have VDIs -5 to +17 discriminated out or rejected and +18 on up accepted. Then you have a target that starts ringing in at +19 (in the accepted range) but as the signal gets stronger, it shifts to +15 (rejected). You can potentially hear the 19 and then the tone for +15 for a short time before the audio decays to silent. So, in this case, you hear a little bit of the rejected VDI due to the decay function of discrimination.
2) Now rather than having -5 to +17 discriminated out, you have them accepted, and you set the audio for those VDIs to 0. For the same target, what you will hear is the +19 tone (for a very short time as above) but when it shifts to +15, it will immediately be silent. There is no audio decay in this case.
3) Some people like to do both.
If you accept the range, but have the audio set to zero, you will still see (zeroed) VDI's on the screen. If you reject the range, you won't hear anything different - audio will still immediately go quiet on the rejected range, but the (rejected) VDI's won't display.
The main reason I don’t reject VDI is “The way the code is written the detector can react faster by having it accept all targets and setting a 0 tone to the ones you don't want to hear, rather than rejecting targets. “(From Anne who wrote the software)
Now it depends on what you want.
There can be a little difference.
1) For an example, say you have VDIs -5 to +17 discriminated out or rejected and +18 on up accepted. Then you have a target that starts ringing in at +19 (in the accepted range) but as the signal gets stronger, it shifts to +15 (rejected). You can potentially hear the 19 and then the tone for +15 for a short time before the audio decays to silent. So, in this case, you hear a little bit of the rejected VDI due to the decay function of discrimination.
2) Now rather than having -5 to +17 discriminated out, you have them accepted, and you set the audio for those VDIs to 0. For the same target, what you will hear is the +19 tone (for a very short time as above) but when it shifts to +15, it will immediately be silent. There is no audio decay in this case.
3) Some people like to do both.
If you accept the range, but have the audio set to zero, you will still see (zeroed) VDI's on the screen. If you reject the range, you won't hear anything different - audio will still immediately go quiet on the rejected range, but the (rejected) VDI's won't display.
Thanks Rob that is what I was after. I can tell you I am an EX Tesoro user and I really liked the Cortes. Problem with the Cortes was that if you actually used the notch, you missed many signals. I found many targets by running the Notch and listening for a slight bump. Often going back over the target, the target was gone never to return. Then I cut off the Notch and the target came right through. I suspect that the V3i like most detectors can and will function better and quicker if it has to do less rejection. I will let you know what I think.
Here is my report back on the change. I can not prove the change would work for everybody but here is what it did for me.
As with any big change in a Metal Detector you can not evaluate a change unless you go to a good spot that has been hammered in the past. I went to an old house where I have hunted with a Tesoro Cortes, a Tesoro Deleon, and my V3i at least three times. I did not get long to hunt so I concentrated on high probability areas.
I found a few pennies that may or may not have had a coil over them in the past. Two were wheats. All were at least 6" inches deep.
One of those areas was a big Pecan tree that had been boardered by a brick walk at one time. I have literally hammered this area because it was where the kids played and just outside the back door. I got a good ID of 52 that was repeatable. I dig Zincs but was not sure why I missed this in the past.
I watched the ID as I checked the target and saw it flash to 70 then back to 52. I started digging and did not find the target where I thought it should have been. A quick check with the Detector and I saw the ID had changed to a steady 70 or higher.
I dug down and found a Rosie Silver Dime. I stood up and ran my Detector over the hole and hit 21. Using the Pro Pointer I found a Buffalo Nickle in my dug dirt. I have never found a Buffalo so this was my Dream Coin. I figure the bricks had these Coins on edge and close together making these hard to see for the Detector.
Can not prove accepting all signals and assigning bad targets a 0 tone works better but it definitely worked good for me today. Depth and ID seemed deeper. I need to let everyone know that I use a SEF 8X6 Coil so my IDs run just a little different, usually higher than a stock coil.
1 1946D Wheat
1 1942 Wheat
1 1956 Rosie
MSL Pennies
and my Dream Coin a no date Buffalo Nickle
As with any big change in a Metal Detector you can not evaluate a change unless you go to a good spot that has been hammered in the past. I went to an old house where I have hunted with a Tesoro Cortes, a Tesoro Deleon, and my V3i at least three times. I did not get long to hunt so I concentrated on high probability areas.
I found a few pennies that may or may not have had a coil over them in the past. Two were wheats. All were at least 6" inches deep.
One of those areas was a big Pecan tree that had been boardered by a brick walk at one time. I have literally hammered this area because it was where the kids played and just outside the back door. I got a good ID of 52 that was repeatable. I dig Zincs but was not sure why I missed this in the past.
I watched the ID as I checked the target and saw it flash to 70 then back to 52. I started digging and did not find the target where I thought it should have been. A quick check with the Detector and I saw the ID had changed to a steady 70 or higher.
I dug down and found a Rosie Silver Dime. I stood up and ran my Detector over the hole and hit 21. Using the Pro Pointer I found a Buffalo Nickle in my dug dirt. I have never found a Buffalo so this was my Dream Coin. I figure the bricks had these Coins on edge and close together making these hard to see for the Detector.
Can not prove accepting all signals and assigning bad targets a 0 tone works better but it definitely worked good for me today. Depth and ID seemed deeper. I need to let everyone know that I use a SEF 8X6 Coil so my IDs run just a little different, usually higher than a stock coil.
1 1946D Wheat
1 1942 Wheat
1 1956 Rosie
MSL Pennies
and my Dream Coin a no date Buffalo Nickle
Good you had some luck.
"I watched the ID as I checked the target and saw it flash to 70 then back to 52. I started digging and did not find the target where I thought it should have been. A quick check with the Detector and I saw the ID had changed to a steady 70 or higher."
I always pinpoint these type of targets first and then can get a more accurate reading.
"I watched the ID as I checked the target and saw it flash to 70 then back to 52. I started digging and did not find the target where I thought it should have been. A quick check with the Detector and I saw the ID had changed to a steady 70 or higher."
I always pinpoint these type of targets first and then can get a more accurate reading.
Ytcoinshooter
Well-known member
When the software engineer says such, it's a great tip. Just finished setting my V3i up to zero tones for all negative numbers and the entire VDI range -95 to +95 is accepted. I had it set to standard tones with everything accepted through -30. Rejected range -31 through -95. Looking forward to seeing how this may speed up target response, that and adjusting the recovery delay dependent upon coil and site.
HH - Bruce
HH - Bruce
Ytcoinshooter said:
I am similiar except I set the tone at I believe 235 (High) for all Coin readings 19-22, then 52-93. I actually went to 0 Tone for the Notch from 23 to 51. I know about rings but I figure I very rarely get over one anyway. I figure it is less for the Detector to change the tones when a good signal is found. From reading the post I do need to Lock down my GB more often as well.
Ytcoinshooter
Well-known member
Zero tone or silent on the rejected numbers worked well in my test area, but it will take getting used to it. I'll probably like it most of the time in the field. I sometimes use mixed mode stereo as a way of knowing everything by tone without having to look at the display. Also the default negative tones told me without looking I was getting into iron. But if this speeds it up - takes some small instruction load off the processor it's good. I like using the default range of tones for the positive range because I don't like grouping targets into a singl tone. The descriptive, variable audio does help me mentally know the conductivity of the target. I never notched anything because so many types of targets (like buttons) because of the variance of composition and size can show up over a broad range. Now my V3i reminds me of my Sov & Excal that null on iron, though that's where any similarities end. Being able to customize the V3i with the horsepower it has makes it unique.daddyflea said:
HH - Bruce