A
Anonymous
Guest
The manual suggests a 2 second sweep(or 4 seconds left-right-left). Does going slower make any difference in depth or detection? i'm new to this and 2 seconds seems kind of fast to me. Thanks in advance.
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.
A
Anonymous
Guest
The MXT does perform nicely at slow sweep speeds but I can't say I've ever swept it slower than 4 seconds. You say you're new to this and that may be why I think 4 seconds is slow. If you had used XLT's, XL Pro's etc you'd see how fast you have to swing most other detectors for optimum performance. The slower swing speed of the MXT is one of my favorite features. Enjoy your new MXT. It's a fine machine. <img src="/metal/html/smile.gif" border=0 width=15 height=15 alt="
">
">
A
Anonymous
Guest
I was thinking of about 8-10 seconds being about right. Would that affect performance? If so, in what way?
A
Anonymous
Guest
Try an air test with that sweep speed and tell us what happens.
A
Anonymous
Guest
In some areas I can swing along quite fast looking for the newer coins, or in areas where there is not many signals. If I am in a older park chance are there will be more signals to check out plus deeper ones that may be iffy, this is where I slow down quite a bit so I can hear them.
I also feel if you go too fast and the ground conditon changes the tracing may not be able to keep up either. So like I say it all depends on the area you are in, if not much signals you can go faster, but if there is a lot of signals you will have to slow down for the MXT to see them.
Rick
I also feel if you go too fast and the ground conditon changes the tracing may not be able to keep up either. So like I say it all depends on the area you are in, if not much signals you can go faster, but if there is a lot of signals you will have to slow down for the MXT to see them.
Rick
A
Anonymous
Guest
Try this, go out in your yard, find a clean spot. Bury a quarter 3-4 inches deep. Now sweep over the coin fast then slow then super sloooowwwwww. See what it does.
Ray
Ray
A
Anonymous
Guest
I'll get back to you with that report around May 1st unless the weather really changes.
A
Anonymous
Guest
is about correct. That suggested 2-second sweep time is more or less an industry recognized standard for the time required to sweep the coil <STRONG>one</STRONG> direction, from right-to-left, when covering a swath of about 4'. Then it would require about 2-seconds to sweep back the other direction, right-to-left, after advancing the coil for an efficient overlap.
This <EM>"2 feet per second"</EM> sweep rate has been an industry standard more or less forever. Thirty year old information published by Charles Garrett in his book suggesed that the sweep speed ought to be about 1' per second when starting out, but with experience that sweep rate should increase to about 2' per second. This was prior to the development of modern motion discriminators.
Also from earlier publications, we can read E.S. 'Rocky' LeGaye's suggestion that a left-to-right scan ought to typically cover about 2'-3', and that <EM>"1 foor per second is a fair average."</EM> Again, that suggestion, from his book printed in 1969, came about a half dozen years before we had ground cancelling discriminators. (aka 'motion discriminators')
Another source to find an answer is in "The Official Handbook of Metal Detectors" by Dr. Arnold Kortejarvi in which he also states that sweep speed should be about 1 ft. per second, unless the manufactuere's literature tells you otherwise. This was also from pre-VLF/Ground Cancelling circuitry days. Actually, this 1969 publication predates popular discrimination circuitry!
Most of these earlier publications had suggestions based upon the operator's manuals that were supplied with the various models they used in writing their books. To be a little more 'up-to-date,' let me refer to some operator's manuals that I have on hand.
Compass Scanner series: <EM>"Search at a slow, comfortable sweep speed."</EM>
Tesoro Toltec 100: <EM>"Swing the detector from side to side in about a three foot arc, ..... The Toltec was designd to get maximum depth without the frantic pace required by earlier motion detectors."</EM> These identical instructions are found in the manual for the Silver Sabre Plus, 'original' Bandido, Silver Sabre
This <EM>"2 feet per second"</EM> sweep rate has been an industry standard more or less forever. Thirty year old information published by Charles Garrett in his book suggesed that the sweep speed ought to be about 1' per second when starting out, but with experience that sweep rate should increase to about 2' per second. This was prior to the development of modern motion discriminators.
Also from earlier publications, we can read E.S. 'Rocky' LeGaye's suggestion that a left-to-right scan ought to typically cover about 2'-3', and that <EM>"1 foor per second is a fair average."</EM> Again, that suggestion, from his book printed in 1969, came about a half dozen years before we had ground cancelling discriminators. (aka 'motion discriminators')
Another source to find an answer is in "The Official Handbook of Metal Detectors" by Dr. Arnold Kortejarvi in which he also states that sweep speed should be about 1 ft. per second, unless the manufactuere's literature tells you otherwise. This was also from pre-VLF/Ground Cancelling circuitry days. Actually, this 1969 publication predates popular discrimination circuitry!
Most of these earlier publications had suggestions based upon the operator's manuals that were supplied with the various models they used in writing their books. To be a little more 'up-to-date,' let me refer to some operator's manuals that I have on hand.
Compass Scanner series: <EM>"Search at a slow, comfortable sweep speed."</EM>
Tesoro Toltec 100: <EM>"Swing the detector from side to side in about a three foot arc, ..... The Toltec was designd to get maximum depth without the frantic pace required by earlier motion detectors."</EM> These identical instructions are found in the manual for the Silver Sabre Plus, 'original' Bandido, Silver Sabre
A
Anonymous
Guest
Thank you for the informative post. It has been my assumption that going too fast would cause the detector to loose depth as well as ability to recognize targets due to it not being able to 'catch up' to the information that it is recieving. Thus a slower sweep speed would allow it to 'recognize' a fainter signal. Like I said before...this is my first detector and I'm new to all of this. There is much to learn and unfortunately due to the weather I can not get any practicle experience.
A
Anonymous
Guest
Used a fired minie, silver dollar and new quarter. All results were the same. On shallow targets it hit good no matter the sweep speed. However, on deeper targets the extremely slow sweep speed's (10 seconds to a pass as you mentioned) performance was horrible. Sometimes it wouldn't hit the target but even when it did it never read nearly what the VDI truly is and wouldn't lock at all on the target. If I ran the disc up to notch out nickels and pull tabs I never got another signal on a deep target with a 10 sec pass sweep speed. I sped it up to about 5-6 seconds and it hit the target solidly again. No way the MXT can perform with optimal results at such a slow sweep speed with the targets I used.
HH
HH
A
Anonymous
Guest
dudephil...I appreciate your taking the time to run the experiment and answer the question for me. It will cut down the learning curve a bit. HH