Jump to content

shopkins1994

Full Member
  • Posts

    41
  • Joined

  • Last visited

 Content Type 

Forums

Detector Prospector Home

Detector Database

Downloads

Everything posted by shopkins1994

  1. I'm not so sure about that. A few of the modes do detect it both directions.
  2. It’s not very hard. It’s point-and-shoot like the equinox 800. However, unlike the equinox, you can configure it to get the items left behind by everyone else. That’s what you need to learn to do with it. -sam
  3. Any thoughts on my test with the default programs? I didn’t changed any settings. These are default programs straight from turning on the Deus 2.
  4. I appreciate you taking the time to write a big response -- it helps us all when someone takes the time to write a lot of info. To explain the way the electronic manufacturing world works (and a lot of consumer industries) is this example for XP. These numbers are made up and are used only to explain the process. 1. XP Sales team says that there are people who will buy a $1,600 detector. 2. XP Bean counters say to sell a $1,600 machine it must cost XP $500 3. XP Marketing says for people to buy a $1,600 detector it must have X features 4. XP Engineering team has to make a $500 detector with X features. That it how it works. XP engineering doesn't have the luxury of putting in an unlimited CPU. In other words they can't spend $495 on a CPU leaving only $5.00 for the rest of the machine. They have to make trade offs. And you can't let engineers make up their own machine because it'll cost $900,000 by the time they are done. This is why a company like Garrett has 10 different detectors. The engineering team had $100 to make an Ace, $300 to make an AT Max, etc. My guess is that all of the processing power of the Deus 2 is located in the coil instead of the RC. That is why their coils are so expensive. They shot themselves in the foot with that one. I would also say that after using the XP Deus 2 it appears to me that XP does not employ a usability engineer. Happy hunting!
  5. Yes. A detector has both limited processing power and limited time to process a signal. The more time or CPU you can give the the detector the better your ending result. Metal detector manufacturers should start posting what their CPUs are like computer manufacturers do. The moral of the story is to only add on what you need -- and everything comes at a cost.
  6. Geezer you are correct. The more processing time results in more signal review by the CPU. Now bear in mind that the Deus 2 will not detect a Reale placed over an anvil simply by turning things off. The moral of the story is that everything you turn on may hurt you and you should only turn things on that help you and the bare minimum at that.
  7. In that case you should start with everything off and only add the bare minimum.
  8. Hi. I made a mistake that beach mode was detecting it. These coins were found because of the added CPU ticks achieved from the above video. I don't think depth was a depth issue, it was rather they were in a difficult position and the Dues 2 needed more ticks to detect them. I repeated this this again and again today by pulling more coins out of the ground. Each time I found a coin in my program I tested the default programs and they did not detect them. Only my program got them, again presumably from the added ticks.
  9. Hi Everyone. I posted the following video on a response to a different post, but I thought I would post it here for you incase you aren't reading that thread. This is a video explaining how to go the deepest depth possible with the Deus 2 and also how to increase the Deus 2's ability to process complex signals such as coins on edge. Happy swinging!
  10. Hi Chase. Thanks for the response. I figured out what happened. My program is better than the stock programs and did what it was suppose to -- find coins that the Deus II programs can't find, by increasing the CPU ticks available to the RC for processing. More ticks = more more CPU available to process harder signals = more coins. I did not think that I would receive as much CPU ticks as I did. The Deus 2 must waste a lot of CPU ticks on its filters. I made a Youtube for anyone wanting to increase the power of their Deus 2 in both depth and ability to process more complex signals.
  11. I took the Deus 2 out for the first time. I was using my program which was park with everything turned off and the reactivity set to the lowest it would go. I wanted the Deus 2 to dedicate its entire CPU to processing the signal. It found lots of coins at 4”-7” deep with a smashing signal. Before I dug each coin, I went through all of the default programs to see what they sounded like. With the exception of beach mode, the Deus 2 didn’t report anything. Zip. Nada. Any ideas why this could be? Now I’m afraid to hunt with any default programs. Sam
  12. Hi. I just retested with a clad dime and got the same results. After about 2.5 it starts to drop off with 5 getting no results. Sam
  13. I did square nails and a clad quarter in the middle.
  14. In my tests, the Deus can run hotter in EMI. Basically it can be screaming like a pig from EMI but as soon as it detects something its BING BING BING. The Equinox is a cold detector and so has problems. The Deus is a hot detector like the Anfibio. From my experience, the Deus is a configurable multi-frequency Anfibio.
  15. Hi Everyone! I am using the Deus 2 to perform the Monte nail board test. If I set my reactivity to 0 it detects the coin all ways. If I set my reactivity to 5 it no longer detects the coin any way. I would think it should be the opposite -- setting a faster recovery speed should detect more easily between the nails and the coin. That does not seem to be the case. Any ideas why this would be? It seems with these test results that when in an area with high iron that we should set the Deus 2 to 0 reactivity? Sam
  16. Hi everyone! Does anyone know how to submit feature requests to XP? Thanks, Sam
×
×
  • Create New...