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

Temperature Sensor Correction

With major bug like the bad Elevation number behind us (!), there's two minor problems that are still bugging me !

1. I want to deactivate the Virtual Partner because I don't use it. I know it's a feature...

2. And the possibility to adjust the Temperature sensor. My wife and I always have +2 °C difference. If my temperature sensor display 20,0°C, my wife has 18,0°C. One of us is not correct or both.

  • I cannot imagine how can we manually adjust a Temp sensor...based on what info? have an old Hg style thermometer handy?

    But again I even tried to add an external garmin Temp sensor to the Edge list ...won't do it. The Edge is measuring internal temperature as well the ambient and most likely averaging it out somehow...

    but if we could attach the external sensor somewhere in a shade (like below a seat)...??

    My VA3 have a internal temp sensor as well but I could add the external Temp sensor to the list of sensors at least

  • I would add a way to calibrage my sensor like a + or - % field. My sensor seems to be stable but different from my wife sensor. We could adjust the sensor with an external thermometer reading or an average from a group of sensor. We already can manually adjust the local altitude why not the temperature sensor. 

  • I cannot imagine how can we manually adjust a Temp sensor.

    Its simply.

    My edge constantly shows temperature lower 2 Celsius .

  • I cannot imagine how can we manually adjust a Temp sensor...based on what info? have an old Hg style thermometer handy?

    Sure, why not? It's not that hard to imagine comparing the Edge reading to an external measurement.

  • There is a IQ datafield HMs DIY which offers (amongst many many others) temperature which can be manipulated by a given offset in setup.

    But to use it only for this purpose is probably not worth the effort. Wink

  • Seconded - 100% on both points.  Virtual Partner keeps making me rethink Garmin for cycling computers.  We shouldn't be forced to use this.  I want a simple GPS device that tracks things.  And my temperature sensor is irresponsibly off - I depend on this as a guide when riding in near-freezing conditions.  Fortunately, it reads low.  But I want it to be closer to correct.  It would be nice to allow a user-offset for known drift in accuracy for a particular unit.

  • In addition to the Edge 1030, I've got an Edge 520 and the Garmin Temple sensor which can send data to a VA3. They all read low unless in the sun (and the Tempe is in a permanently shady place under a rack (with bag on it) and above a mudguard. I think Garmin deliberately program the sensors to read low so that the average for a whole ride might be about right. If the sun isn't shining then I know to add about 3C to what the Edges report. If there's strong sunshine then the Edges will read high (radiation from the road adds to the direct solar radiation). Garmin probably also configured the Tempe on the assumption that it would be exposed to the sunshine (black isn't a good choice of colour).

    Sensibly, Garmin would (i) allow the Edge devices to connect to a Tempe sensor and (ii) allow users to make a temperature correction so that riders who want good temperature data can fit the sensor somewhere free from external radiation, calibrate it and then have meaningful temperature data. However, so far the please to let the Edges connect to the Temp have fallen on deaf ears.

  • I have an edge 1030 and a  Tempe sensor.  When enabled using the IQ field (https://apps.garmin.com/en-US/apps/bedd1447-4816-40a9-83e1-0ed22c5bbcc3 )  I can see both internal (1030) and external (Tempe on frame out of direct sunlight wrapped in white insulation tape).

    The differences are not linear, so unfortunately, an offset would not help.  My observations have been....

    Below 10C on the 1030 it is reading about 2C lower than the Tempe

    At 5C (lowest this year) it is nearly three degrees lower than the Tempe.

    At 18C to 22C they are pretty much the same (so long as there is no sunshine to warm the 1030)

    About 22C the 1030 starts to read higher than the Tempe (by a degree or so).

    As someone who rides all round the year, knowing when ice is likely is important to me, so I'm very grateful to crt_hun for making this device work with the 1030.

  • Thanks. I hadn't noticed the arrival of that IQ field Tempe app but have now installed it. A check against some other thermometers suggests that my Tempe is reading about 1.5C low. I wonder if the app developer can add a correction option.

    I wouldn't expect to see a constant difference between the Tempe and the Edge as the latter is far more susceptible to being influenced by radiation but I'll see for myself when I next go cycling. As for warning of the risk of ice, my car is set to warn me if the air temperature is below 3C as the ground surface cools faster than the air above it.

  • Three rides and on each the CRTTempeField app works OK for about five minutes and then appears to stop receiving data (IQ with an exclamation mark gets shown on the display). I've reported this to the developer.