Request to improve Barometer performance (Fenix 7X Pro)

Dear Development Team,

I trust this message finds you well. Firstly, I would like to express my sincere appreciation for the exceptional product you have created, particularly the Garmin Fenix 7X Pro – it has truly enhanced my experience.

I have been thoroughly enjoying the features of the watch, with a specific focus on the barometer and its accuracy, a vital aspect for me. I would like to suggest an enhancement for consideration in future updates.

Moreover, I have a couple of suggestions related to the storm alert feature. Firstly, extending the duration of the storm alert beeping by a few more seconds would greatly improve its effectiveness. This adjustment could provide users with a better chance to notice and respond to the alert promptly.

Additionally, it would be beneficial to include an alert for rapid increases in air pressure. This feature could offer valuable insights into changing weather conditions, enhancing the overall utility of the watch.

I genuinely hope these comments prove helpful, and I am optimistic that they will be taken into consideration for future updates. Thank you once again for your commitment to delivering outstanding products.

Best regards,

Top Replies

All Replies

  • We are heading toward sub-1m accuracy in 2D positioning

    However, this does not apply to watches. Their antenna is not made for this.

    Even with a GPSmap (65s) I can achieve a maximum accuracy of 1.2 meters in good conditions. And the GPSmap devices have a better (and externally mounted) antenna.

    However, the greatest influencing factor remains the Earth's atmosphere. Differences in transit time caused by the atmosphere have an effect on accuracy.

  • I said “are heading” ;-). Anyway we are much closer to a vertical accuracy of 1.5 m than 400 feet, arent we?

  • I have not much knowledge about accelerometers and gyroscopes, but if they are good enough to replicate the horizontal move under bridges, in tunnels, they evidently has to be good enough to replicate the vertical move. At least it is my logics.

    Yes, if you know you are at relatively high know entry velocity, in a a practically 1D system, where the accelerometer is in a fix position, on a known trajectory, and you do not expect more than continuous driving with just a limited range of acceleration / deceleration, you can make some successful estimation of the speed and distance.

    Not so with a watch constantly moving in all possible directions, and with a wild range of acceleration, permanently crossing the critical zero state on any of its axis (hitting so the hysteresis spot with zero sensitivity). The accelerometer has a limited sensitivity, it means there is certain hysteresis around the zero. And zero acceleration can happen both in static state, as well as during steady motion with constant velocity (i.e. in a lift, or climbing a slope of a constant grade, or driving in a car at a constant speed on a slope, etc.

    The same goes for the gyro, which is needed to determine the orientation of the watch in the space. Besides the limited sensitivity, many Garmin watch models do not have gyro at all (F7 does have it, though). Without gyro you do not know in which direction the watch is acceleration, so the velocity or distance estimation is not possible at all, unless you have a system with the accelerometer mounted in a fixed way, so that it cannot change its orientation in the space at all.

    As regards the GPS accuracy let me highlight that you cited a 15-20 years old safeside Garmin statement mirroring the accuracy of the then consumer GPS receivers.

    The vertical accuracy is much worse than the horizontal one because of a simple reason limiting the accuracy of the trigonometric functions - the visible satellites are all on almost the same plane. Only the most distant ones (with weak signal) are a little bit lower, because of the shape of the orbit. That makes the trigonometric calculation of the altitude more challenging than the triangulation of the position on the horizontal plane. 

  • Yes, if you know you are at relatively high know entry velocity, in a a practically 1D system, where the accelerometer is in a fix position, on a known trajectory, and you do not expect more than continuous driving with just a limited range of acceleration / deceleration, you can make some successful estimation of the speed and distance.

    Not so with a watch constantly moving in all possible directions, and with a wild range of acceleration, permanently crossing the critical zero state on any of its axis (hitting so the hysteresis spot with zero sensitivity). The accelerometer has a limited sensitivity, it means there is certain hysteresis around the zero. And zero acceleration can happen both in static state, as well as during steady motion with constant velocity (i.e. in a lift, or climbing a slope of a constant grade, or driving in a car at a constant speed on a slope, etc.

    The same goes for the gyro, which is needed to determine the orientation of the watch in the space. Besides the limited sensitivity, many Garmin watch models do not have gyro at all (F7 does have it, though). Without gyro you do not know in which direction the watch is acceleration, so the velocity or distance estimation is not possible at all, unless you have a system with the accelerometer mounted in a fixed way, so that it cannot change its orientation in the space at all.

    First of all thank you for your answer of high standard. For me the new piece of info in this answer was the hysteresis spot of accelerometers/gyros .

    And zero acceleration can happen both in static state, as well as during steady motion with constant velocity (i.e. in a lift, or climbing a slope of a constant grade, or driving in a car at a constant speed on a slope, etc.

    Sure, but if you are constantly using an accelerometer you have collected information about not just the previous acceleration data, but the previous speed data itself So if you face with zero acceleration you should have a knowledge about whether you just are moving at a non-zero constant speed, or practically you are not moving.

    Unless your previous speed (before measuring zero acceleration) was so close to zero that your device cannot identify it as zero speed or "almost zero speed".

    Yes, if you know you are at relatively high know entry velocity, in a a practically 1D system, where the accelerometer is in a fix position, on a known trajectory, and you do not expect more than continuous driving with just a limited range of acceleration / deceleration, you can make some successful estimation of the speed and distance.

    Not so with a watch constantly moving in all possible directions,

    So it implies that a device needs more accelerometers than one, presumably three covering 3 dimensions, or a special 3-axis accelerometer which has 3 internal accelerometers mounted orthogonally. Does not it help?

    The same goes for the gyro, which is needed to determine the orientation of the watch in the space.

    To be honest until your answer I had assumed that gyro is needed not to determine the actual orientation, more like an additional sensor above 3-axis accelerometers to handle the rotating moves of the watch. So when the center of mass of your watch is not moving, but you are rotating your watch along one or more axis.

    The vertical accuracy is much worse than the horizontal one because of a simple reason limiting the accuracy of the trigonometric functions - the visible satellites are all on almost the same plane. Only the most distant ones (with weak signal) are a little bit lower, because of the shape of the orbit. That makes the trigonometric calculation of the altitude more challenging than the triangulation of the position on the horizontal plane. 

    It is also a pretty logical reasoning, so I decided to look for the data that I remembered from a long time ago. I mean the ratio of 1.5 to 1 as regards vertical accuracy to horizontal one.

    The first hit in google for "gps vertical accuracy vs horizontal accuracy" gives a datum of 1.7. At least for me.

    see https://junipersys.com/support/article/6614#:~:text=Just%20as%20a%20general%20observation,to%202%20m%20vertical%20accuracy.  

    I found other hits of course, and although there are much fewer words about the vertical accuracy then about horizontal one the majority of the hits speaks about a ratio of 1.5-2 , eg https://tlcgis.org/About/Who-We-Are/Precision-Mapping

    I mean even if my comment of "we are heading toward sub-1 m accuracy in 2D  positioning" should have been rephrased like "in 2D positioning an accuracy of 3-4 meters is not a dream any longer" and adding "not just for receivers with external quad helix antennas, but even for watches" (thx Bluefish for making me remember about it), so the vertical error of a GPS receiver can be kept around 8 meters, which is still just an error of 1 mbar in pressure. And this time I was on the cautious side.

    Having accepted all the details you provided I still feel that Garmin artificially understates the accuracy, just because there may be some details in the design of their products where they sacrifice some of the theoretical vertical accuracy and it is safer to say that "forget the GPS based vertical accuracy". Or saying accelerometers and gyro does not help even if the whole activity tracking feature family is based on  accelerometers / gyros.

    I hope you also feel the contradiction: even if you slowly walk your watch is good enough to identify you made a step, even if you slowly move your arm it is good enough to identify it and the display switches on, BUT the same sensors are not sensitive enough to measure the change in elevation. 

    Maybe I am stubborn a bit, and sorry for that, but I have a good intention: this time I say a product must be better then it is officially said. ;-)

    EDIT: I forgot to mention that Garmin made a choice when they opted for DEM data, and maybe it was not the best choice, although it is quite understandable.

  • Sure, but if you are constantly using an accelerometer you have collected information about not just the previous acceleration data, but the previous speed data itself

    You forget about the the sensitivity limits (the hysteresis problem). Principally it means you can guess distance for example at steps with relatively good accuracy, because the acceleration curve during the stride is well known, and rather dynamic, but in the moment you have long periods with zero or very low acceleration around the zero point, you do not know at all whether you are absolutely static, or moving for example with the speed of 10 cm per sec. Although it is a negligible and unimportant speed for the instantaneous analysis (like the Running Dynamics), in just over an hour, it would lead to the error of 360 meters, which is already unusable for any elevation adjustments.

  • I̶ ̶f̶e̶e̶l̶ ̶ ̶g̶o̶t̶ ̶w̶h̶a̶t̶ ̶y̶o̶u̶ ̶m̶e̶a̶n̶t̶,̶ ̶b̶u̶t̶ ̶b̶e̶f̶o̶r̶e̶ ̶g̶e̶t̶t̶i̶n̶g̶ ̶t̶o̶ ̶a̶ ̶s̶t̶a̶t̶e̶ ̶o̶f̶ ̶m̶o̶v̶i̶n̶g̶ ̶a̶t̶ ̶ ̶0̶.̶1̶ ̶m̶/̶s̶,̶ ̶w̶h̶i̶c̶h̶ ̶d̶a̶t̶a̶ ̶s̶h̶o̶u̶l̶d̶ ̶b̶e̶ ̶r̶e̶a̶d̶ ̶a̶s̶ ̶"̶z̶e̶r̶o̶ ̶o̶r̶ ̶a̶l̶m̶o̶s̶t̶ ̶z̶e̶r̶o̶,̶ ̶w̶e̶ ̶d̶o̶n̶t̶ ̶k̶n̶o̶w̶"̶,̶ ̶t̶h̶e̶ ̶s̶e̶n̶s̶o̶r̶ ̶h̶a̶s̶ ̶h̶e̶l̶p̶e̶d̶ ̶t̶o̶ ̶i̶d̶e̶n̶t̶i̶f̶y̶ ̶y̶o̶u̶r̶ ̶w̶a̶t̶c̶h̶ ̶w̶a̶s̶ ̶m̶o̶v̶i̶n̶g̶ ̶a̶t̶ ̶a̶ ̶d̶e̶f̶i̶n̶i̶t̶e̶l̶y̶ ̶n̶o̶n̶-̶z̶e̶r̶o̶ ̶s̶p̶e̶e̶d̶,̶ ̶b̶e̶c̶a̶u̶s̶e̶ ̶t̶h̶e̶ ̶m̶e̶a̶s̶u̶r̶e̶d̶ ̶a̶c̶c̶e̶l̶e̶r̶a̶t̶i̶o̶n̶ ̶w̶a̶s̶ ̶s̶u̶b̶s̶t̶a̶n̶t̶i̶a̶l̶,̶ ̶a̶n̶d̶ ̶n̶o̶t̶ ̶a̶r̶o̶u̶n̶d̶ ̶t̶h̶e̶ ̶z̶e̶r̶o̶ ̶p̶o̶i̶n̶t̶.̶ ̶I̶f̶ ̶t̶h̶e̶ ̶w̶a̶t̶c̶h̶ ̶a̶s̶s̶u̶m̶e̶s̶ ̶t̶h̶a̶t̶ ̶t̶h̶i̶s̶ ̶s̶p̶e̶e̶d̶ ̶i̶s̶ ̶s̶t̶i̶l̶l̶ ̶v̶a̶l̶i̶d̶ ̶u̶n̶t̶i̶l̶ ̶i̶t̶ ̶m̶e̶a̶s̶u̶r̶e̶s̶ ̶a̶g̶a̶i̶n̶ ̶a̶n̶ ̶a̶c̶c̶e̶l̶e̶r̶a̶t̶i̶o̶n̶ ̶o̶f̶ ̶N̶O̶T̶ ̶a̶r̶o̶u̶n̶d̶ ̶t̶h̶e̶ ̶z̶e̶r̶o̶ ̶p̶o̶i̶n̶t̶,̶ ̶d̶o̶e̶s̶ ̶i̶t̶ ̶m̶a̶k̶e̶ ̶a̶ ̶m̶i̶s̶t̶a̶k̶e̶?̶
    ̶
    ̶M̶o̶v̶i̶n̶g̶ ̶h̶u̶m̶a̶n̶ ̶b̶o̶d̶i̶e̶s̶ ̶t̶y̶p̶i̶c̶a̶l̶l̶y̶ ̶s̶t̶o̶p̶s̶ ̶s̶u̶d̶d̶e̶n̶l̶y̶,̶ ̶o̶r̶ ̶w̶i̶t̶h̶ ̶a̶ ̶r̶e̶l̶a̶t̶i̶v̶e̶l̶y̶ ̶s̶u̶b̶s̶t̶a̶n̶t̶i̶a̶l̶ ̶d̶e̶c̶e̶l̶e̶r̶a̶t̶i̶o̶n̶.̶ ̶N̶o̶t̶ ̶l̶i̶k̶e̶ ̶a̶ ̶c̶a̶r̶g̶o̶ ̶t̶r̶a̶i̶l̶ ̶s̶l̶o̶w̶i̶n̶g̶ ̶d̶o̶w̶n̶ ̶w̶i̶t̶h̶o̶u̶t̶ ̶b̶r̶a̶k̶i̶n̶g̶ ̶a̶t̶ ̶a̶l̶l̶,̶ ̶j̶u̶s̶t̶ ̶d̶u̶e̶ ̶t̶o̶ ̶f̶r̶i̶c̶t̶i̶o̶n̶.̶
    ̶
    ̶C̶e̶r̶t̶a̶i̶n̶l̶y̶ ̶m̶a̶y̶b̶e̶ ̶t̶h̶e̶ ̶h̶y̶s̶t̶e̶r̶e̶s̶i̶s̶ ̶p̶r̶o̶b̶l̶e̶m̶ ̶i̶s̶ ̶e̶v̶e̶n̶ ̶b̶i̶g̶g̶e̶r̶ ̶t̶h̶a̶n̶ ̶I̶ ̶s̶u̶p̶p̶o̶s̶e̶.̶.̶.̶.̶.̶

    Oh, now I got it. I mixed up the horizontal movements and the vertical one. Even if your horizontal accelerometers can define your speed, but since normally you move slowly vertically, except for real climbing over 10%, your vertical accelerometer have no chance.

  • Or let me put it in another way. If you are walking at a grade of 1% or 2% at a speed of 1-2 m/s,  but your arm with the watch is wildly swinging, your watch may be good for elevation adjustment. But if you are walking on the same route and at the same speed, but you are checking for your watch for a minute, you have lost the chance to use it for the same elevation adjustment.

    Is it a correct example?

  • Even if your horizontal accelerometers

    There is no horizontal or vertical accelerometer. The accelerometer gives a 3D acceleration vector which is based on the physical orientation of the watch (relative to the watch, not to the Earth). It does not know whether the watch is oriented vertically, horizontally, or at an angle. You need a gyro for that. Not all watches have it. And the gyro has a similar problem with the sensitivity and hysteresis as the accelerometer.