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

Improvements & questions list

fneuf
over 4 years ago

Hello,

After some rides with my 830, I have various improvement ideas / questions and would like to discuss/share them with the community:

  • Strava Segment => display options
    • I find the default representation of such segments quite space consuming and color aggressive.
    • For instance I’d like to be able to not display them while just looking at the map (outside of an ongoing activity), as I find those cluttering
    • It would be great to define the way they are represented, along with being able to only display them when and where the user want
  • Incident Detection => Have its sensitivity based on engaged Activity
    • So far, I've seen quite a few false triggers of this function, while doing DH (downhill MTB) runs. This lead to impractical situations where you actually have to interact with the device, while in a run, to shut the function to absolutely not alert your emergency contacts. As much as this Incident Detection function is great, avoinding false emergency message is what will keep it valuable. After the 10th message received on the same day, I'm quite sure no relative will still fill engaged to verify my well being quickly. The whole "cry wolf" story over again.
    • Proposal : mts overal sensitivity based and dependent of the currently running Activity Profile, to differenciate more gravity activities. And also ading a user set multi-level parameter for an in-activity sensitivity. Because just a "MTB profile" parameter will not be enough to take in account that not everybody performing MTB activities is doing bike-park tracks, natural DH tracks, jumps and so on.
  • Internal Temperature correction
    • In might current weather, seems the internal sensor is always 3 to 5°C too generous on the real temperature. Why not give the user an offset parameter to correct that?
  • Automatically associate profiles (gravel, road, mtb, etc) to specific user equipment
    • When uploading activities to Garmin Connect, it would be great that it auto infers which equipement was used during the activity, based on which sensors were connected.
  • 0 over 4 years ago

    I think the most simple solution for incident detection will be that the Edge has to be fully at standstill after trigger of incident detection for, say, a minute at least. Then either you are in problem or sitting for a coffee/beer.

    Temperature has been discussed before in other threads. As the temperature sensor in inside on the pcb it measures the temperature of the...pcb. So slow response and influenced by the heat generated by the electronics as a general and the components nearby.

    Driving wind will cool the unit, which is higher at level road than uphill etc.

    A temperature sensor as closed to the outside, far away from pcb and shielded for the sun would be best. But it is a bike computer and not a meteorology station

  • 0 over 4 years ago in reply to Martin Borsje

    I agree for the Incident Detection feature. That would even be simpler to implement. "Toom much quiet ? No good".

    Yes, this is not a meteorology station. That's why I believe nobody here is expecting a +/-0.2 % deviation on actual temperature. But that should not made us lower our expectation either way to have proper temperature readings.

    I mean, the product does state it is measuring temperature. And I don't believe Garmin to be ironic enough to pretend the aim is to measure the PCB temperature.

    As you describe, getting a better placement of the sensor is not rocket science. And those units are roughly made of CMS components, a SoC a battery and a display. PCB space constraint is not an issue here. I previously had a Bryton unit, same parts type list and its thermal reading were far more reliable.

    And even if Garmin do not want (or for the sake of argument do not can) to optimize their PCB topology to improve thermal reading, it is still be possible for them to build some simple laws to modelize how the internal temperature impact the external reading/guessing.

    My point around that is not to resurrect old discussions, rather to find an acceptable solution to the current situation. Hence my offset proposal. An actitvity constant offset is not perfect, but at least we'd get some leverage on the values and be able to get closer to reality.

  • 0 over 4 years ago

    Garmin have as you sure know a small device called Tempe. I got this device, (stay in the original box,same as my Edge 830) when they (dream) will allow temperatur reading with decimal in GC i will take it out and use it again. Same with Edge 830, when ( Dream again) they add intensy minutes i will start use it. Until then i use the Fenix 6 for cycling, if the physio true up had worked as intended i could have used the Edge, but it’s not even close, and for me it’s better with one statistic than a lot of different numbers all over. 

  • 0 over 4 years ago in reply to Jano22222

    I believe the temperature sensor in the 830 (and other Edge units) is part of the baro sensor and measures the baro sensor temp for the purpose of correcting  the baro sensor for temperature effects.  If it's measuring the baro sensor's temp, it's doing it's job.  Using it as an ambient temp sensor is an afterthought.

  • 0 over 4 years ago in reply to looigi

    Maybe, but if your technical guess and your interpretation is right, then why Garmin has not -yet- included the ANT+ environment profile to allow proper temperature reading by any Edge unit?