|
Post by kusaioyaji on Aug 14, 2020 18:26:43 GMT -8
Shows SMF alla time!
Bought a refurb. Compass shows SMF. returned. New refurb sent. Same problem! Am I doing/not doing something?
On or off the rifle, same story. In the House, or outside, same. Compass function INOP!
Sure could use some help. At wits end. Have reloaded most recent software, done shutdown and restarts, charged fully, and have simply run out of things to try.
|
|
|
Post by cummings66 on Oct 21, 2020 12:41:52 GMT -8
Use a regular compass. See if you have a strong magnetic field near your house. I have seen that happen one time, so it's possible. In this case it was an old house with iron I Beams.
|
|
|
Post by mike72ss on Dec 1, 2020 9:09:07 GMT -8
I had the same problem after updating firmware on a new ATN 4K Pro. What I did was to start rotating the scope on it's three axis like it mentions when performing a compass cal. It switched to CAL and I just continued rotating the scope on all three axis's and it finally starting working ok.
|
|
|
Post by macgyver on Feb 13, 2022 13:33:13 GMT -8
Mine always says "SMF" but have not had it outside my house, too cold. So, it may or may not be functioning correctly. Right now, I am not too worried about it.
|
|
|
Post by magnum on Dec 18, 2022 6:38:20 GMT -8
I had the same (SMF) problem with my 4K pro. Exhausted by using the 3 dim. rotation,I called atn. They told me to download the "elf" firmware. Also, they told me to remove scope or leave it mounted. Take scope outside and in a vertical position and don't be gentle, rotate it left to right and at the same time move up and down. Do this for 45 seconds. Then lay it down on a level spot and wait 1 minute. It worked! Eventually, the problem reoccured so I removed scope did a firmware reload and did their calibration movement. IT calibrated, but came back the next time I turned on the scope. Removed scope, did the original 3d cal and it worked. SMF still comes back, but I can shack it (scope mounted) roughly, gps starts working. At one time, an atn associate told me the next firmware should address this problem. We can only HOPE!
|
|