Jump to content

Chase Goldman

Full Member
  • Posts

    6,131
  • Joined

  • Last visited

 Content Type 

Forums

Detector Prospector Home

Detector Database

Downloads

Everything posted by Chase Goldman

  1. People who perennially play with backyard boxes and desktop coffee cups are great. But how about some actual detecting and finds... You swing from one extreme to the other it's hard to take what you say with any seriousness. One moment you're in "heaven" with the new Ver 1.0 audio, the next moment Ver 1.0 is "useless" because of a desktop test of an arcane expert setting under one specific condition. You cherry pick video air tests with tailored setups yet ignore real world results here and here. So which is more "ridiculous"? Don't get me wrong. It's good to get the word out there that it appears the silencer behaves differently, perhsps more aggressively, on ver 1.0 - presumably XP's response to the complaints of iron falsing (which neither of these test videos address, btw). It doesn't make Ver 1 useless, it just proves the timeless fact of life that if you use a filter to address one issue you may impact performance. It's called balancing tradeoffs and the informed and savvy detectorist knows when silencer is of benefit and when it is not. The demonstration of the less aggressive silencer on ver .71 only showed the difference in masking but did not show if the ver 0.71 silencer was effective at mitigating iron falsing, which is it's purpose. Based on the numerous complaints regarding falsing on ver 0.71, I suspect it was inadequate at what it was designed to mitigate. Frankly, if you want to be sure a legit target is not masked by a filter setting under an extreme case of iron co-location, then turn the Silencer off. If falsing is ruining your hunt, turn silencer on and take your chances. It's a detectorists judgment call not a magic wand. Simple.
  2. I'm certainly not seeing 1.0 as useless and more specifically that the silencer has a "major problem" or that the video has even proven the silencer to be a problem at this stage. Holding out judgement until I form my own opinions based on real world situations and experience which is going to take hundreds of hours of swing time. I certainly don't want XP making knee jerk mods to this update because of some nails sitting on top of a coffee cup on someone's desk. Anyway, simple solution, roll back to your beloved ver 0.71 until the dust settles and monitor whether XP feels a change is needed.
  3. XP has never really explained what frequency addition means. So that could definitely affect the FMF frequency spectrum for modes that otherwise "look" identicsl. However, the beach modes use conductive ground subtraction which makes sense in the beach modes, as salt conductivity is being notched out. Perhaps Beach Sensitive, in addition to having a higher Max F, has less of a salt "notch" to provide greater sensitivity to small beach gold. Still surprised they behave that differently. Dan - Can you be more specific about how you set up the two modes to be identical and what was different about how they behaved? Specifically, did you set up Beach to emulate Beach Sensitive or vice versa or both. I know it shouldn't matter if they are identical. The only adjustable parameter defaults that are different between Beach and Beach Sensitive are Max F (24 and 40 khz, respectively) and Salt sensitivity (9 and 7, respectively), I believe. Thanks for checking that out, Dan.
  4. Agreed. The more I think about it, I think Garrett made the right move pivoting to take on ML on the PI front, where no one else has really challenged them. The market is saturated with SMF derivatives of Equinox/Manticore (Legend, Deus 2, and the forthcoming Quest V60/80). Garrett basically released a proof of principle SMF with Apex to demonstrate they still had the engineering chops to stay relevant with the latest IB VLF detecting tech trend but focused their development horsepower on Axiom. After Quest drops their SMF offering out there, I anticipate a lull in new releases of mid-to-high-end SMF detectors. Perhaps a perfect time for Garrett to make a splash with a new AT SMF flagship of their own while others (Nokta and Quest) try to counter ML's XTP.
  5. Yeah, you showed them Simon by waiting at least a month before getting that Manticore. Sorry, couldn't resist. Glad you are showing strength by not hopping on the XTP. I Broke down and just purchased a ML product myself...
  6. Surprised it’s so popular. For me, I avoid Camo on my detector gear because I want to be able to find it again if I intentionally or unintentionally leave it behind in the field (like if I have to go back to my vehicle to fetch something). I guess some folks find it useful for keeping a low profile, or something?
  7. Would have kept one of them as a backup, but getting $500 for both is not too bad a deal.
  8. Do you mean less falsing or less iron tones? The latter makes sense because at disc -6.4, you lose iron tone/volume, unless you force the next multi tone bin to a low pitch. On Full Tone (FT), in 0.71, you had no non-iron volume pitch adjustment. Now, with 1.0, you can adjust the pitch and offset of the 2nd Bin even in FT because XP added tone bin groups. If you are running Pitch tone at -6.4 disc, everything will sound non-ferrous.
  9. Yes, you can roll back to v 0.71 The login page is: https://updater.xpmetaldetectors.com/#/login, but the browser may not show https:// in the address bar, which is normal browser behavior.
  10. That’s certainly a strange one. Hopefully, it’s not a bug like we had early on as described here where with disc set at -6.4, you would get no iron tone (which would be sort of the opposite of what you were describing, Lodge). Frankly, if the detector is falsing on iron with a TID well above the disc limit (iron tone break) shifting disc up or down a few points should not theoretically make falsing noticeably better or worse. The main factors should be, as you noted, Silencer and Max F. BTW note that the max silencer setting is now 7, so maybe increasing it further is what is needed for 40 kHz Max so you can re-invoke disc and at least don’t get non-ferrous tones on all targets. Will have to play with that one. The only real way to verify is to find a falsing nail and see if it really stops falsing at -6.4 disc. Yep that is really odd behavior but sometimes weird behaviors an anomalies show up at the extreme endpoints of parameter settings’ ranges.
  11. The update page (English language link below) takes you to the Account Login page when you click on the “UPDATE NOW” button. https://www.xpmetaldetectors.com/en/ba/the-blog/deus-ii-v1-0-update-instructions.php The direct link to the Account Login page is: https://updater.xpmetaldetectors.com/#/login
  12. @cookie58 - Reading through your previous posts here and in previous the other thread, I suspect you may be using the wrong form to create your account. You appeared to be attempting to fill out the "Comment" form not the "Account Creation" form. If you scroll to the bottom of the XP Website page describing the update changes you see the following: Don't fill out the comments form, click on "UPDATE NOW". That will take you to an account login page as shown below: Click on "Create account". Tha will take you to the following form where you can fill in the personal information needed to create an account as shown below: After filling out all the required fields, click on create account and you will be prompted to go the automated email sent to the email address you entered above to validate/verify your account and when you do that in your email program the verify link you click in the email will take you back to the login page (second image above) where you can log in with the email and password you entered into the account creation/registration form. That should then take you to the page where you can update your machine using the online prompts and plugging it into your computer when prompted using the cables supplied with your machine (the three-headed charge cable with the special connector for your remote and the single USB cable for your WS6/WSA headphone puck. Hope this helps. Let us know how it goes...
  13. He must have wired it to the regular headphone pins on the sealed remote connector, then. That multi-pin connector supports bone phones which has a connector that is keyed to the bone phone pins on the remote connector, this tells the remote to only provide square audio. You can also wire up regular speaker or piezo submersible phones to the same connector on a different set of pins and the remote will provide both PWM and SQUARE audio out.
  14. Doesn’t exist and will likely never exist. If I need to cover ALL the bases, I need at last two different types of detectors. A PI and an induction balance VLF. If I were forced to only possess two detectors (not counting a pinpointer) they would be (right now) the Garrett Axiom and the Deus 2 - I would have prospecting, hot dirt relic/coin, salt beach, submerged fresh and saltwater, coin and jewelry shooting, meteorite hunting, contest hunting, hoard hunting all covered. They are able to be broken down such that I could put them both in a backpack and pack them in to a remote area on foot, e bike, or ATV.
  15. Confused. I thought if you wired the phones to the bone phone pins then that locks the remote into Square.
  16. Some things to think about or try: Did everything indicate the update completed sat? Did the lock up occur after you disconnected the puck and self restart or on a subsequent power up? Were you just checking that it powered up fine or were you trying to pair with the remote or a coil in Master mode? If attempting pair with the remote, attempt re- pairing by holding down the minus button as suggested above? Is it paired with a coil? If so, is the coil in range (it may be trying to search for the coil to do the shift)? Did you try plugging the puck back into the laptop with the updater loaded to see if that snaps it out of the lockup? Worst case, you might have to wait for the puck battery to be depleted so it can power off reset on its own. Contact XP in the mean time. HTH
  17. Tom - Jeff answered your question with a link to the relevant post. But since that didn't quite answer your question... D2 is highly versatile under a variety of detecting situations and objectives and is ultra light and ultra configurable (e.g., WS6 Master config) due to its wireless coil based system. However. some detectors can give D2 a run for the money or are superior in specific ways over the D2. Legend - Better Overall Value/Great accessory coil selection. Nox 800/900 - Better at sub gram gold detection. Though the 900 TIDs are less stable than D2. Manticore - As good or deeper than D2 in wet salt sand, doesn't require antenna claptrap that is required by D2. Manticore TID stability is also lacking vs. the D2.
  18. Along those lines, I kind of wish they they flexed back on the Base Factory Default Programs to a bare minimum that would give us the basic base program building blocks necessary to branch out and create the custom programs suited to our needs. The reason being, that you can free up slots for saving additional custom prorams. To that Point The Base Factory Default Programs Could be Distilled Down To: 1 - General - Subtraction - 24 khz 2 - Sensitive - Addition - 40 khz (As a minimum, the existing Sensitive FT and Fast Factory Programs which are both based on Sensitive are somewhat redundant and just take up program slots). 3 - Deep - Addition - 14 khz (not essential if covered by Program 2 above) 4 - Mono 5 - Gold Field - Addition - 40 khz 6 - Relic - Subtraction - 24 khz 7 - Deep Salt - 14 khz 8 - Sensitive Salt - 40 khz (not essential - covered by 7 above) Freeing up an additional 4 to 6 Custom Program Slots. If I could request an additional Program it would be Mono variant of the Gold Field/Relic process. Also, the manual input of Custom Programs works but is tedious without a full keyboard for alphanumeric character inputs. On the long-term wishlist: Either provide a means to enter custom programs via phone or computer interface. It is good that custom programs are not wiped after minor version updates. So, hoping if a minor bugfix version is issued in short order (e.g., ver. 1.1) thet my custom programs are not wiped during the update.
  19. CPT and Rattlehead, I always liked Silver Slayer based of Deep HC vice Fast so that's basically what is going on by doing that, I think, because they are both 14 khz and frequency addition processes (now with the ability to adjust Max FMF). I am looking at a hierarchy of base program process settings to see what programs will behave identically if set up identically. You can then use a combination of a selected base program with the frequency or soil conductivity process you prefer target specific situations such as using a lower frequency with General for Silver Slaying in wet soil (Conductive Soil Subtraction). See this post which expands further on that train of thought.
  20. I was starting to think about how the ability to adjust Max FMF for any Factory Program might affect our ability to better customize Deus II FMF for just about any situation and to better visualize the similarity between base Factory Program capabilities with the additional degree of freedom this new feature proivides. First I had to organize the programs into a specific hierarchy. It is a work in progress but it basically racks out as follows: FMF or Selectable Single Frequency (Under Single we only have Program 7 - Mono) Under FMF there are basically Three Groups Disc Process (e.g., all the non-salt, discrimination programs such as General, Sensitive, Park, Deep HC) IAR Process (i.e., Gold Field and Relic) Disc - Salt Process (i.e., Dive, Beach, and Beach Sensitive) Under 2 of the 3 base processes above you have two categories (Note: Disc - Salt only uses Conductive soil subtraction) Frequency Addition (Disc Example: Sensitive; IAR Example: Gold Field; Disc - Salt Example: None) or Conductive Soil Subtraction (Disc Example: General; IAR Example: Relic; Disc - Salt Example: Diving) Finally, under each of these processes you can select one of 3 Max FMF Frequencies: 14, 24, or 40 In tabular form it looks like this: MAX FMF FREQ (kHz) FAST MULTI-FREQUENCY (FMF) SEL SINGLE FREQ DISC IAR SALT MONO - 7 ADD SUB ADD SUB ADD SUB 14 DEEP HC - 6 X X X N/A DIVING - 10 24 PARK - 5 X X RELIC - 9 N/A BEACH - 11 40 SENSITIVE/FT/FAST - 2, 3, 4 GENERAL - 1 GOLD FIELD - 8 X N/A BEACH SENS - 12 Sorry about the clunky formatting, but just trying to do this fast on the fly. The X's mark areas that are not covered by a default Factory Program. So, for example, you can create a custom Silver Slayer variant that can perhaps deal better with wet soil (conductive soil subtraction) by using General and set MAX FMF to 14. Similarly, per this table it appears that Silver Slayer using FAST with MAX FMF changed to 14 as the base program or using DEEP HC with the same Reactivity Setting as Fast as the base program should behave identically. Similarly, you can perhaps better chase micro targets in wet soil by using Relic with FMF Max set to 40. Or maybe Gold Field set to 24 or 14 might do well better for relic hunting than relic under different soil moisture conditions or different iron pollution levels. Definitely, room for experimentation here. Also, notice, that none of the Dive/Beach programs have a frequency addition counterpart. This makes sense, because the whole point is to subtract out salt soil conductivity. So on dry sand, you might be better off using an inland program (just as is recommended in the Deus 2 User Guide). Finally, another thing to keep in mind, since you can now vary Max FMF Frequency is that battery drain will be mostly dependent on the FMF Max frequency you select, with the lower FMF Max frequencies (not just with Deep HC or Diving) causing higher battery drain. I noticed that the battery drain table in the User Guide was not updated to reflect this. FWIW. Welcome your comments and thoughts on this.
  21. To give you something to complain about. Unfortunately, it's a data grab for marketing purposes at this point, but it may also be a way to further control paid subscription feature tiers in the future for the Go Terrain app or the actual machines which, of course, is a double edged sword. Good in the sense that you don't pay for features you don't personally need or want, bad in the sense their may be additional paid tiers and those tiers may be lifetime or periodic subscription renewal.
  22. Like the design. Prefer olive drab to camo like your screamer accessories. Is the control head sun shade Velcro attached and removable?
  23. You need to Long press on the gear icon button from there to get the update confirmation screen.
×
×
  • Create New...