This is a topic relevant to every(?) form of detecting -- ground coverage. I'll list several questions concerns I've had but any replies of course aren't limited to these, nor do they need to address any of them. Just tossing out some ideas to prompt further discussion.
1) What methods and efforts do you apply to ensure full ground coverage in the cases where that is one of your goals?
2) Is your sweep a straight line path or an arc?
3) How long is your sweep?
4) How much do you overlap consecutive sweeps in the direction you walk?
5) How much do you overlap side-to-side swings when following parallel paths (e.g. when walking two side-by-side swaths in the same direction how much does the left end of one path overlap the right end of the next path or vice-versa)?
6) Have you ever measured your coverage? How well do detectors with GPS (e.g. Minelab GPZ-7000 and Minelab CTX-3030) monitor ground coverage to this detail? Have you used other devices to measure ground coverage. E.g. I can imagine a drone with camera could provide useful data. Are there smartphones app that would help quantify coverage?
If this question has been addressed elsewhere, I apologize in advance and hope someone can give me a link for it. I have noticed that other companies besides Minelab are coming out with PI detectors for less than $3K. How do these detectors compare to the best Minelab detectors for Gold and also relic hunting?
On the Anfibio Multi (and I think Kruzer & others) there is a definite step in sensitivity between 39&40 Gain and again between 69&70 Gain. Is this a change in the Internal Threshold? In a way this would be the inverse of the way the F75 adjusts sensitivity according to Mike Hillis. Regardless, it is a very good set up in difficult sites. Most NM users know about the difference in response speed between 89 & 90 Gain on 3DI. This is different. I had read about these steps in a forum post that quoted Alper of NM. I can't seem to find that post now that I want to re read it.
Hello, now here’s an opener that might just get me banned on my first post!
Bear with me, my intentions are pure :)
Does anyone know if it would be possible to jam an MD signal? The reason I ask is to combat the evident problem we have in the UK with “nighthawks”, illegal detectorists.
Over here, any landowner can grant permission for detecting on their land (with caveats, known historic sites are protected by law). What often happens is that such a permission is granted and a detectorist innocently sets about his / her business. Someone less scrupulous spots this person and assumes there may be something important there, so shows up at night with a couple of friends and the landowner awakens to a field / lawn full of holes, then bans metal detecting.
Historic sites are also looted.
Just an off the wall question, how tricky would it be to build a device to block this on a piece of land? Anyone any ideas?
99% of my detecting is done on central Florida beaches. Since it’s impossible to establish a well stocked test garden at a public beach, I sorta brought the beach home with me and developed my own private beach garden!
I cut slots in two large empty chlorine tablet buckets at various depths as shown from 2 -16 inches. I then filled one with New Smyrna Beach sand and the other with soil...for the few times I land hunt around here.
I embedded numerous examples of ferrous and non ferrous targets into paint stirring sticks. I also have several blank sticks I use for gold and silver jewelry as well as artifacts that I don’t want permanently attached to a stick.
I then insert the target(s) in the slots, each at its desired depth, and start scanning.
This allows me to rapidly change the targets, depth and relative position of each. I can now test for sensitivity at depth as well as separation of ferrous and non-ferrous targets in a variety of scenarios using actual beach sand where I do my detecting.
If I want to test in wet salt sand, I just soak the bucket sand with authentic sea water that I also brought home from New Smyrna Beach...and the Atlantic Ocean never even missed it. 😉
Works for me.....