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

Dakota 20 and Tempe

Having received a Tempe sensor for Christmas I'm struggling to make it work. It pairs no problem with the Dakota 20 and shows the temperature on the unit but is not recording the temperature in the track log - and hence does not upload to Garmin Connect.

I read a thread about a similar problem with the Oregon and as a result updated to the latest software version for the Dakota which suggests in the release notes that the issue has been addressed. Does anyone know if there is something else I need to do in order to make the unit record the temperature?

Thanks

0 Former Member over 12 years ago

I'd report the issue to Garmin support. I have an Oregon 450 and had the same issue with my tempe. As you know Garmin fixed that with a firmware release but it took about 6 weeks after a number of complaints got them moving.

There's nothing special to do. Pair the tempe and if it's working and you're creating a track log temperature will be recorded in it.

0 Former Member over 12 years ago

I read a thread about a similar problem with the Oregon and as a result updated to the latest software version for the Dakota which suggests in the release notes that the issue has been addressed.

Garmin's servers are having issues today but I managed to find the (cached) Dakota release notes I think you're referring to.

Changes made from version 5.40 to 5.50:

* Fixed inability to edit archived tracks.
* Fixed potential issue with reporting tempe temperature data.
* Improved map drawing at low zoom levels.

Unfortunately if the Oregon history is any guide that does not refer to the tempe track log issue.

0 Former Member over 11 years ago

I know this is thread necromancy but I couldn't find this information anywhere. I have a Dakota 20 on 5.50 and a Tempe, and although the Tempe showed live temps and the track log also showed temp data, Connect didn't show me the temp graph when I uploaded the current track. The solution is to first save the current track from within the Dakota, then upload that to Connect manually; then you see the historical temp data. Hope this helps someone as it too me ages to work out.