iron_buzz

PWM all the way. I tried square and high square, but keep coming back because I feel that I'm missing too much information. I don't want my Deus to sound like a Manticore or Equinox anyway... I ended up selling both of those, and one big reason was that I was constantly having to check the VDI because the sound didn't tell me enough. (the Manticore, by the way, added a sound profile to make it sound like what they think the Deus sounds like. It is nowhere near the same, though)

You also got an organ reed (top, right) that was almost certainly from an organ that the school teacher played when teaching music. Cool! (it may be stamped to indicate the note it played)

Yeah, I've never had any of the plastic hinges break, but I figure its just a matter of time. Maybe we need to initiate a letter-writing campaign to XP about their charging clips.

Something made by XP that only costs $10? I'm shocked, I tell you... shocked!

I think on the white cord, the metal part of the plug plug is just a little bit longer, and apparently that is needed to make the data connection that is necessary for updates. It seems to charge OK with a shorter one (shorter metal part, I mean). Why they didn't include that instead of the MI6 plug on the 3 plug cord is beyond me. Even if everybody had an MI6 (I don't), headphones need charging more often. And mostly... why did they make the entire thing so short that you can't charge the coil and the RC at the same time without breaking it down into pieces? I love XP's engineering... most of the time. But there are moments. (I'm speaking to you, recharge clip designer and recharge cord designer)

Fixes a bad design.

If you've been using a Deus for any length of time at all, chances are that you have had the plastic spring break on your charging clip. You probably cursed, and then ordered a new one. I was getting tired of that, so instead I made a trip to my local hardware store and fixed the problem once and for all.

I have a phone mount that was designed for bicycles that should work. I haven't got a rugged enough case for my phone to do that, though. This isn't it exactly, but its close enough to give you the idea (not an ad, nor necessarily a recommendation... just communicating an idea): https://www.target.com/p/insten-360-universal-bike-cell-phone-holder-mount-for-motorcycle-bicycle-compatible-with-iphone-12-12-pro-max-11-samsung-galaxy-android-black/-/A-78260364

This summer was awfully dry in Minnesota, too dry to be digging grass, and the farm fields I like to hunt were in crop, so while I had tinkered a bit with fresh water hunting, I got more serious about it this summer and being new to this group, thought I'd post a few of my better finds here. This first one was not a water find... this came from a pasture that was used as a small golf course in the 1920s. It is a 15 gram 14k Yellow Gold Masonic 32nd Degree Scottish Rite Ring. Others were all fresh water hunts, mostly at old beaches that are now just shoreline.

I just remedied that.

Yeah, sorry if I was too sensitive in that post about sensitivity. I've been detecting for 7 seasons now, mostly with an XP Deus. I've owned several others (Garrett Ace 300, Fisher F75, AT Pro, Equinox 800 and most recently, Manticore. Sold them all) but I speak Deus, so Deus it is. Funny you should ask... I just got OnX hunt a couple of days ago. My main detecting partner has had it for a while now. By the way, it took a bit of work, but I finally got one of their support people to pass along to developers the need to be able to link from a landowner's address to Google Maps.... or at least to be able to copy the address to the clipboard. I had the 11", 9", and HF Elliptical for my Deus I but found that the 9" was the Cinderella coil for me, so that's all I have for the Deus II. I am heading to England for my first ever detecting trip next fall though so I may get the 11" for better coverage and a backup.

Your thoughts are very much the same as mine after trying it a couple of times now. Today I tried it in "Push" mode because of the sensitivity problem we discussed previously. But I think after you hit the middle button that you have to get your phone out to accept it, and you certainly do if you want to enter any information, take videos, etc. I may still use it for tracking, on occasion, but basically I'm not impressed with the reality of it.

I'm not a novice at this, but thanks for the advice. I was running what I felt was necessary for the site.

The old farm field home sites that I detect are always extremely trashy. I'm not going to adjust my sensitivity just so the app will work. Maybe the app itself needs a sensitivity setting that is independent from the detector setting.

I'd like it if they would add the name of the program being used to the information it passes.

I tried the app out yesterday and it was going crazy sending me constant notifications and dropping target pins all over the place. I was running on Auto mode, but I think next time I will have to set it to Push (hold down on the middle button to register a target).

I've taken to using Relic (and Gold) programs for the same reason. I do notch up to about 40 in most places I detect because there is little in that range that I would want anyway. I set IAR to 5 to minimize the iron. When I do get a tone, its almost always a "dig".

I tried using it for a while yesterday and it went WAYYYYY overboard on recording targets! I had it on Auto mode because I don't want to be pulling my phone out of my pocket to confirm every target, but if there isn't some way to tame this down, there is no way I'm going to be using it.

I installed it out of curiosity and will give it a try on my next outing, but I'm skeptical. For one, I can't see that it will help me find anything more, but more importantly, when I'm detecting, my phone is in my pocket, I have rubber gloves on my hands, a shovel in my left hand and the detector in my right. If I have to put the detector and shovel down, and take my gloves off to access the phone... even if the gloves are not caked in mud, as they often are... it ain't gonna happen. Where I do see that it may help a little is in showing areas that maybe we missed, but there are already apps out there that will map your path. Nothing new about that, and no subscription needed to use them.

It synced up with my Pixel 7 Pro, but I did have some problems. Not sure if this is what fixed it, but the last thing I tried before it finally worked was switching from Push to Auto in the Options/Setup/Go Terrain menu.

I had a Manticore... for about a month. I've owned a Deus for 7 seasons now, and found that with the Manticore, I was constantly checking the screen to read the TID. About the only time I check the screen on the Deus is when I already know that I've got a pretty good target. It dawned on me the other day that the Deus audio is almost like tapping drywall to locate the studs... you can hear the tinniness of aluminum vs the solidness of a nice, thick brass artifact. I did not have that with the Manticore. I sold it.

I guess it didn't work out to well, then.

Which brings me to another, related question... Gold and Relic in the D II use Iron Amplitude Rejection instead of tradititional discrimination (although notching is still available, which I use often with those programs to make them useable). The idea, if I understand it right, is to reject ferrous targets with the highest magnitudes. I have wondered it it would also be possible to apply that same logic to non-ferrous targets for detecting in places where you want to ignore shallow coins and pulltabs and such so you can focus on the deep targets. Of course, it would have to be used with the caveat that you could be missing important stuff on the surface but there are situations where that might be OK. Is my thinking sound? Could and should this be done?

Yeah, that is a major part of my reason for asking about this. I don't know, but I do suspect, that a lot of the things we hear about discrimination may be holdovers from the days of analog processing. I did some testing on my own to see if discrimination affected depth, and I was satisfied that it does not. But when I posted that finding to my local MD Facebook group, I got blasted with claims to the opposite, but not one who actually tested it themselves.

That is not necessarily true, though, in all cases. For example, I hear a lot of people claiming that the higher you set your discrimination, the more you limit depth, but to me, as a retired computer programmer, I would assume that the discrim level you set is simply a parameter passed to a function.