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 Connect says my Forerunner 610 firmware needs updating ....

Former Member over 10 years ago

But i'm on the latest 2.90

It happens every time i log in. I have tried to let it update to see if it stops the message from appearing and also dismissed it a number of times. But everytime i log in it tells me my Forerunner 610 is on 2.80 (which it's not) and needs updating.

It's only happened since switching to the modern version. Any ideas?

0 travis.vitek over 10 years ago

Have you tried removing the device from Garmin Express and adding it back?

0 Former Member over 10 years ago

Have you tried removing the device from Garmin Express and adding it back?

Nope, i tried to remove my device last night, but couldn't figure out how to do it?

0 travis.vitek over 10 years ago

In Garmin Express, select your 610 from the dropdown on the left and click the Device link on the right. Near the top of the page you should see a picture of the device and two links; one to rename the device and another to delete it.

0 Former Member over 10 years ago

In Garmin Express, select your 610 from the dropdown on the left and click the Device link on the right. Near the top of the page you should see a picture of the device and two links; one to rename the device and another to delete it.

Sorry should've said, i'm on a Mac.

0 travis.vitek over 10 years ago

Garmin Express should be the same (except for what appears in the title bar on Windows) between operating systems. You should still have a device dropdown and the Updates and Device buttons.

0 Former Member over 10 years ago

Garmin Express should be the same (except for what appears in the title bar on Windows) between operating systems. You should still have a device dropdown and the Updates and Device buttons.

ok figured it out, i didn't realise you could click on the "device" bit.

First time i logged in it did a map update, then 2nd time no update so looks like it may have worked, thanks.