TID Display Refresh Time ?

[Pacetrac]

I have a question about the TID on the E-Trac.
I have used the emulator and watched several videos showing the TID operation on an E-Trac.
What I have noticed is the TID on the emu and videos show the TID show up quickly and
refresh with each pass of the coil over the target. But on my E-Trac, the TID usually will not show up
until I have slowly passed over the target several times and does not refresh on new targets for several passes.
My E-trac is about 2 weeks old and has behaved this way since new (stock coil)

I have tried deep on and off, fast recovery on and off. but does not seem to help.

Is this normal???

 

[Kenova]

check your DISPLAY TIMEOUT in the PREFERENCES MENU on the etrac

If you have it set to ON it will keep the last numbers and target crosshair for 5 seconds
Set it to OFF and it will change with every new target that is detected.

Hope this helps

 

[Jason in Enid]

What the hell happened to my reply? GRRRRR.

OK, short and sweet recap. The target ID won't display until you clear the coil of targets. If you have a lot of targets in the same area it can be very hard to get the TID response. The audio responce will still be what you expect.

 

[The Beep Goes On]

Sometimes I find myself having to clear the target lock by raising the coil and letting it get a threshold tone. The amount of trash at the site and your coil size can affect this issue. Your machine is fine.

 

[Pacetrac]

Ok, I must have misunderstood the target timeout feature.
I was thinking it would refresh with each pass THEN hold the last ID for 5 seconds.

I will try that this evening, thanks for the replies.....

 

[Jason in Enid]

Pacetrac, check your setting with an airtest first. This will show you the "perfect" responses for your chosen settings.

 

[Kenova]

Ok, I must have misunderstood the target timeout feature.
I was thinking it would refresh with each pass THEN hold the last ID for 5 seconds.

I will try that this evening, thanks for the replies.....

Yep, if you have it set to ON then that is most likely the problem.

 

[The Beep Goes On]

I have tested this previously in the field and on the bench. The timeout does indeed result in a faster display. At the same time, when the machine locks onto a target, it sometimes doesn't want to let go. For a test, use a couple of different coins a short distance apart and run the coil slowly over the targets...first one then the other in a straight line. You will find that, even with timeout off, the machine doesn't always respond the the second target. It will respond audibly just fine, but the dispaly may not always update if the time between targets is less than the recovery delay. With Minelabs, slow is good, and can minimize this occurrence. Having Fast On probably will help a small amount as well.