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.

Numeric I.D. Averaging Function on Coin$trike

onpoint

New member
Could someone please explain this function (Numeric I.D. Averaging Function) for me in more detail.

What would be an ideal situation to have on and off ?

Thanks Clinton :ukflag:
 
When it is turned on it takes an average reading of the target it see's under the coil, and reports it on the VDI screen. When turned off, the unit reports a reading in real time, (instant), and does not report it to the screen as a average.

Example of use: Detecting in a trashy site with many targets, you may want to set it to "off" so you can try, and get a reading on all targets that respond. If you have it set to "on", it is going to average out the targets it see's, and report that figure. You may not want to have it do that.

With it off, the target numbers will jump around a bit, because it's reading instantly. Target reading will be more steady in the averaging mode.

They certainly didn't write up much about that function in the manual. It is a cut & dry adjustment based on your personal preferences, but a little more explanation would have helped.
 
Many thanks Mr. Bill for this info,

Could I ask an other Question ?

I went out today for the first time and my coin$trike readout started going erratic up & down, This happened when I was in disc & all metal mode. (I was using 525 settings) It even happened

when I held the Detector up in the air !

I was quite close to a Train line, ( 100 feet or so ) Could this be the reason for this erratic behavior ? I then gave up and went home :sad: because I didn't know what to do about it and

thought I would ask some one on this forum.
 
I would have no idea what to answer with. It could have been one of a hundred things I can think of. One need's to go try it in a different place to see how it acts. If it continues, then send it into Fisher. :shrug:
 
[quote onpoint]

Could I ask an other Question ?

I went out today for the first time and my coin$trike readout started going erratic up & down, This happened when I was in disc & all metal mode. (I was using 525 settings) It even happened

when I held the Detector up in the air !

I was quite close to a Train line, ( 100 feet or so ) Could this be the reason for this erratic behavior ? .[/quote]

OK, it's simple, the CS has a frequency that is speculated to be around 5khz. So like almost all low frequency machines
it won't run around electrical interference (RF). This will often include hi-tension transmission lines, transformers,
grounded pipes, telephone lines, electric train rails, CB radios, Ham radios, short hop microwave and just
about anything that spews RF. I can't use the CS in most urban areas, but I mostly hunt relics in the country
so that works out.

You can get a second detector that uses a high frequency or dual frequency to run around RF.
I use an Fisher made X5 for this, but fisher CZs would fill this criteria too. There are many units out
there with frequencies above 12khz that behave well around RF.

hh

-=john=-

just type coinstrike in google and hit the feeling lucky button
 
Top