Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New Approach R10 DUD?

5072063
over 3 years ago

Just got my R10 today, tried to pair with my phone and the dang thing just went into a solid blue face on front and won't pair or turn off, kind of frustrated and not sure what to do now.

Talked to Garmin support, they suggested to update on Garmin Express, I have done that, than unit still wouldn't turn off even though it updated properly connected to PC, updated to 4.0. The solid blue light remains and won't change....did I just wait all these months for a dud?

Wonder how long it will take to run out of power lol, man this sucks, was looking forward to it so much.

 

  • 0 over 3 years ago

    Have you paired with your phone? Have you turned on the app?

  • 0 over 3 years ago in reply to 4868276

    I was trying to pair to my phone earlier thru the App. Then all of a sudden that constant blue light kicked in and I haven’t been able to do anything since. 

    I already had the app cause I have an s62 watch, so went thru my devices and tried to connect it. 

    I took it home and hooked it up to my PC and updated the device (R10) thru Garmin Express and linked it to my account. 

    Tried to connect thru my phone again and it won’t. Sometimes it shows up and it acts like it’s gonna connect than says Error Garming Connect Server.

    I’ve been talking to Garmin tech support all afternoon about it and every troubleshooting thing they give me to try, is not working.

    im hoping the battery drains, blue solid light turns off and it resets the operating system within the unit itself and is able to function properly after that happens. If it doesn’t work after battery dies than I guess I gotta send it back or something.

  • 0 over 3 years ago

    Garmin Approach R10 Error Codes Logs.txt 
    3622 (Approach R10) SW ver: 400
Build Type: RELEASE
Commit:5adf0a143e0aa3900a3f4748072f3924e22aa773
ESN: 3415699135
01/01/15 00:00:00
AP
PWR RST CTRL: 0x00000040

3622 (Approach R10) SW ver: 400
Build Type: RELEASE
Commit:5adf0a143e0aa3900a3f4748072f3924e22aa773
ESN: 3415699135
01/01/15 00:00:00
AP
PWR RST CTRL: 0x00000040

3622 (Approach R10) SW ver: 400
Build Type: RELEASE
Commit:5adf0a143e0aa3900a3f4748072f3924e22aa773
ESN: 3415699135
01/01/15 00:00:00
AP
PWR RST CTRL: 0x00000040

3622 (Approach R10) SW ver: 400
Build Type: RELEASE
Commit:5adf0a143e0aa3900a3f4748072f3924e22aa773
ESN: 3415699135
01/01/15 00:00:00
AP
PWR RST CTRL: 0x00000040

3622 (Approach R10) SW ver: 400
Build Type: RELEASE
Commit:5adf0a143e0aa3900a3f4748072f3924e22aa773
ESN: 3415699135
01/01/15 00:00:00
AP
PWR RST CTRL: 0x00000040

3622 (Approach R10) SW ver: 400
Build Type: RELEASE
Commit:5adf0a143e0aa3900a3f4748072f3924e22aa773
ESN: 3415699135
01/01/15 00:00:00
AP
PWR RST CTRL: 0x00000040

3622 (Approach R10) SW ver: 400
Build Type: RELEASE
Commit:5adf0a143e0aa3900a3f4748072f3924e22aa773
ESN: 3415699135
01/01/15 00:00:00
AP
PWR RST CTRL: 0x00000040

    here are the error logs when I looked into the Garmin files. Hasn’t been connected at all yet and tryna turn it off I’m assuming is triggering these logs.

    Any admins wanna forward to their technical guys that can translate this and give any feedback??

  • +1 over 3 years ago in reply to 5072063

    Hello, if updating the device as suggested by product support did not resolve this issue, please reach back out to them so we can assist you further in this matter.

    It does sound like service of the device may be required if suggested troubleshooting is not working, but they will be able to walk you through that process if that is deemed the case.