Greetings,
First post!
The main detector I use is the Garrett GTI2500, for coin hunting.
Unfortunately this detector has only two tone outputs (ignoring the high-conductivity BOING!!! sound) - a "normal" tone for most metals and a lower tone for targets below 3 on their (rather coarse) conductivity scale. This 2-tone setting is not the default, you have to switch on "bi-level" for it to work.
I hunt with discrimination set to zero and bi-level on. I don't use "coin" discrimination as it is set too high for many NZ coins, and anyway it's annoying if you get a ping and then it "disappears" when you do the next sweep because the detector is still picking up the target but it's be re-allocated to a lower conductivity and hence gets blanked.
Even still, because the "bi-level" point is set at conductivity level 3, I have to continuously check the (rather small) conductivity display whenever I get the higher of the 2 tones, and ignore if it is below 4.5 (for conditions here in NZ).
It would be SOOOOOO MUCH better if Garrett allowed the "bi-level" point to be adjusted up to wherever the user wanted it - or maybe even better - made it so the higher the conductivity the higher the tone frequency. That would allow me to walk along listening for the right tone and watch the scenery go by rather than having to continuously look down at the display only to find the target is one I'm not interested in.
But I suspect the chances of them adding this function to the GTI2500 is remote. So I wonder, could I disassemble the code on the 2 socketed ROM's in the unit, and adjust the "bi-level" point myself?
Has anyone here dug into the internals of the GTI2500 to make changes to the microcode?
Is it an easy matter to zero in on the code that runs this feature, or am I taking on something that is extremely tricky to do and I would be better off concentrating on building my own detector so I can have positive input into the feature list?
The thing is, I like the depth indication on the GTI2500 and not sure that's been built into any of the homebrew machines yet?
Comments invited...
First post!
The main detector I use is the Garrett GTI2500, for coin hunting.
Unfortunately this detector has only two tone outputs (ignoring the high-conductivity BOING!!! sound) - a "normal" tone for most metals and a lower tone for targets below 3 on their (rather coarse) conductivity scale. This 2-tone setting is not the default, you have to switch on "bi-level" for it to work.
I hunt with discrimination set to zero and bi-level on. I don't use "coin" discrimination as it is set too high for many NZ coins, and anyway it's annoying if you get a ping and then it "disappears" when you do the next sweep because the detector is still picking up the target but it's be re-allocated to a lower conductivity and hence gets blanked.
Even still, because the "bi-level" point is set at conductivity level 3, I have to continuously check the (rather small) conductivity display whenever I get the higher of the 2 tones, and ignore if it is below 4.5 (for conditions here in NZ).
It would be SOOOOOO MUCH better if Garrett allowed the "bi-level" point to be adjusted up to wherever the user wanted it - or maybe even better - made it so the higher the conductivity the higher the tone frequency. That would allow me to walk along listening for the right tone and watch the scenery go by rather than having to continuously look down at the display only to find the target is one I'm not interested in.
But I suspect the chances of them adding this function to the GTI2500 is remote. So I wonder, could I disassemble the code on the 2 socketed ROM's in the unit, and adjust the "bi-level" point myself?
Has anyone here dug into the internals of the GTI2500 to make changes to the microcode?
Is it an easy matter to zero in on the code that runs this feature, or am I taking on something that is extremely tricky to do and I would be better off concentrating on building my own detector so I can have positive input into the feature list?
The thing is, I like the depth indication on the GTI2500 and not sure that's been built into any of the homebrew machines yet?
Comments invited...
Comment