flgliderpilot
Bronze Member
- Apr 28, 2015
- 1,504
- 1,427
- Detector(s) used
- CZ-21, Minelab Equinox, Garrett AT Pro
- Primary Interest:
- Metal Detecting
Just wanted to post my experience for information. My Nox 800 was great the last time out at my beach. Coins were loud, clear, and stable. I was able to find targets in the sand without using pinpoint. I had a killer day with it.
I ran the update a few days before going back to the same beach without any problems but the results were rather terrible. I worked in Beach 1 in the dry sand and Beach 2 down by the tide line/wet sand, all stock settings as before and the Nox was a mess on targets.
Pennies were running 16-22, Quarters 20-30, nickles all the way down to 6. I even dropped a quarter directly on the sand and it still bounced 20 through 30. Last time out coins were within a tight window and now they are all over the scale. That is when they even get seen. The dropped quarter on the sand was very unsure if there was a target or not. It sounded like half of the signal was being canceled mid swing. Did the same thing on an air test with no interference. I spent better than five minutes digging up a matchbox car at 5 inches because of how uncertain the Nox was on where the target actually was. I probably dug 10 false signals on a very clean beach. I turned the sensitivity down to 15 where I was running 20-22 last time. Not that that was the issue. The background was incredibly stable but when there was a target there it was a mess of different signals. I ran a factory reset in the middle of the day to try to get the device right and that did nothing. I cycled through the programs and they were all like that. Tried adjusting swing speed, ground balance, noise cancel, all with no effect.
A quick search showed me that reverting the update should be very easy to do and I plan to do some air tests tonight and then roll it back. I am hoping to get the old functionality back. It was a really great detector and I took care to clean and stow the Nox last time so I don't think it is some kind of damage or anything like that. The only thing I can point to is this update. I am going to test, roll back, and test again to see if that was it and I will update the thread with my results.
I noticed this also and posted about it last week... that is really not good news.