1. Pressure sensor not working below 3 m of water by design and is a disgrace for Garmin when most of any other brands of watches can do more, is apple better than Garmin? - fēnix 7 Series - Wearables - Garmin Forums
   URL: https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-7-series/379047/pressure-sensor-not-working-below-3-m-of-water-by-design-and-is-a-disgrace-for-garmin-when-most-of-any-other-brands-of-watches-can-do-more-is-apple-better-than-garmin
   Pressure sensor not working below 3 m of water by design and is a disgrace for Garmin when most of any other brands of watches can do more, is apple better than Garmin? - fēnix 7 Series - Wearables - Garmin Forums

Related

Options

# Pressure sensor not working below 3 m of water by design and is a disgrace for Garmin when most of any other brands of watches can do more, is apple better than Garmin?

Disclaimer: I'm not a diver or an experienced freediver.

I'm incredibly frustrated with Garmin because I want to use my fantastic Fenix 7 Pro watch for snorkeling and shallow freedives up to 10 meters for a few seconds, but it's impossible with this model.

Garmin has deliberately limited the functionality of their watches, including the Fenix 7, Epix, Forerunner, and others, to push consumers toward buying their specialized Descent model. This feels like a blatant cash grab.

Let's not start with the 10 ATM rating. I understand the limitations, but I’m not asking for a full dive computer. I just want to enjoy some simple underwater activities during the summer.

For that purpose, the Fenix 7 Pro is utterly USELESS under water!!!

What makes this even more frustrating is that, despite my hatred to Apple products, I have to admit that the Apple Watch is a better option for anyone seeking a truly multipurpose watch. It not only handles these activities with ease but is also somehow cheaper!

It’s disappointing that Garmin has chosen this route. They’ve turned what could be an amazing, versatile piece of technology into something that falls short for no good reason other than profit.

If you want to use Garmin watch underwater just for fun is best not to buy it, just buy an Apple watch.

This post probably will be deleted or locked by Garmin so i will repost it anywhere i can

- Sign in to reply
- Lim_Cy likes this" data-format="{count}" data-configuration="Format=%7Bcount%7D&IncludeTip=true">
- Cancel

## Top Replies

It’s disappointing that Garmin has chosen this route. They’ve turned what…

- You should read a little before you bought it. Since Fenix 5 Garmin limits barometer usage to 3 meter depth. Second, as somebody wrote it, Fenix is not advertised for diving, you could swim, you could snorkel…

## All Replies

What makes you believe that the barometer in the Fenix is capable of detecting pressure changes down to 10m or beyond?

It’s disappointing that Garmin has chosen this route. They’ve turned what could be an amazing, versatile piece of technology into something that falls short for no good reason other than profit.

Do you know that the sensor in both the Descent and the Fenix are identical and that Garmin has limited its functionality via software?

It's likely that the Apple watch Ultra and Descent have two sets of sensors - a barometer which is going to hit the stops the moment it gets plunged underwater (given that these devices are inherently delicate), and a second sensor which is able to measure pressure depth. I don't know that for certain, but I'm not about to become enraged over the issue without understanding more about it.

This post probably will be deleted or locked by Garmin so i will repost it anywhere i can

Remember that *you* purchased this watch knowing its functionality and limitations. I get that you're upset, but you really need to take accountability for your purchasing choices. If you continually find yourself being surprised and angered, then that is perhaps an indicator that you need to slow down and do a little more research.

Maybe take a couple of breaths and work out whether or not the Fenix is the right device for you. Perhaps an Apple Watch Ultra or a descent is more suitable for your use case.

Let me be clear, i hate apple.

The problem is that i love the fenix series i had the 3 - 5 and now 7 , and up to 5 i was able to use the multiple third party apps for freediving, only for shallow water if I'm just going for a swim, if I'm going spearfishing i always use my aeris 10 . So i did research it a lot that's why I'm disappointed with Garmin they have made a fantastic watch and deliberately limit it's capabilities.

The f7 is not advertised to support underwater activities and the Descent has a depth sensor in addition. Indeed, it would be overkill for snorkling money-wise.

I don't think Garmin limits capabilties of the f7 to prevent third party apps from providing snorkling activities. How would the watch detect it is underwater? Can the barometer be used to determine the water depth?

You should read a little before you bought it. Since Fenix 5 Garmin limits barometer usage to 3 meter depth. Second, as somebody wrote it, Fenix is not advertised for diving, you could swim, you could snorkel with it, if you want do scuba diving go for Descent, it is designed for scuba, for example have second barometer dedicated to depth measure

With Apple Watch you need to buy Ultra and extra app to do diving with it. And to be honest, I still will not believe them that I will be fully secure.

As i already said, i have the fenix 5 and is working fine, also the fenix 6 was working and after the update they limit it to 3 m .

Read what i wrote i don't want it to go for diving i have my dive computer for that, and yes the barometer is working perfectly fine for shallow water

I’m using Garmin watches since 2016 (Fenix 3) and you are right, for Fenix 3 it was external app available which gives you ability to use it as dice computer. Never had Fenix 5 and cannot say how it was for it, but since Fenix 6 (I had Fenix 6 and Fenix 7) this app was never usable because Garmin limited depth sensor usage to 10 feets officially saying (we don’t guarantee accuracy of these measurements). You could complain about it but nothing change it, leave with it or change your watch.

2. Freediving Depth Data Field - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/4028/freediving-depth-data-field/1391311
   Freediving Depth Data Field - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- Cancel
- More
- German Forum
- Beta Program
- Developer
- Pilots
- Sports & Fitness
- Outdoor Recreation
- Apps & Software

- Users 0 members are here
- Views 4883 views
- Subscribers 19 subscribers
- Replies 12 replies

Options

- Cancel
- More
- Share

Related

# Freediving Depth Data Field

Recently I noticed that the very useful freediving data field called "Depth" has disappeared from the Connect IQ Store. I have no Idea why and I also don't remember the author of this data field. Because I need this data field and because I want to be able to record the data, I now try to code it myself. Only problem is that I currently run into some difficulties: -There seems to be no way to get the pressure reading from the barometer into a data field, because it would use the Sensor module which is not allowed to be used for a data field, only for an app (Gives error when put in manifest file). -And taken that it could be done anyhow, it most likely could not be done with Info.pressure because according to the API documentation this would return a pressure value corrected with the current altitude, whereas I would need the raw value to calculate the diving depth. So, my big question is: How did the author of this freediving depth data field achieve this?? Can anybody give me a hint with this? PS: Yes, I know that there exists a diving computer app at www.diveiq.com. But it’s quite expensive and not ideal for freediving. What I really want is just a data field to show me the current depth, which creates a FIT-File to show the depth as a graph in Garmin Connect.

- Cancel
- Sign in to reply

## Top Replies

- Don't confuse the water rating (how deep you can take the watch) with what pressures you can read with the watch. If I recall, some devices max out pressure readings at a depth that would work for…

## All Replies

Don't confuse the water rating (how deep you can take the watch) with what pressures you can read with the watch. If I recall, some devices max out pressure readings at a depth that would work for swimming - it's so non-diving watches aren't used to record diving. If you want an Instinct for diving, there is the Descent G1: https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/garmin-introduces-the-descent-g1-series

No way...You sir just made my Day.Didn't know this existed.Price is okayisch but still on the Very Expensive side...The Max Rating is an Important Point you made here, I found https://www.apnea.me/ but their FAQ Mentions the Problem you described.Thank you, Sir.

3. fēnix 6 Series Owners Manual - Data Fields
   URL: https://www8.garmin.com/manuals/webhelp/fenix6-6ssport/EN-US/GUID-5176B6E4-F272-4437-BDA7-85B31231CB3E.html
   fēnix 6 Series Owners Manual - Data Fields

Data Fields

# Data Fields

NOTE: Not all data fields are available for all activity types. Some data fields require ANT+® or Bluetooth® accessories to display data.

% Functional Threshold Power

The current power output as a percentage of functional threshold power.

% Heart Rate Reserve

The percentage of heart rate reserve (maximum heart rate minus resting heart rate).

10s Balance

The 10-second moving average of the left/right power balance.

10s Power

The 10-second moving average of power output.

24-Hour Maximum

The maximum temperature recorded in the last 24 hours from a compatible temperature sensor.

24-Hour Minimum

The minimum temperature recorded in the last 24 hours from a compatible temperature sensor.

30s Balance

The 30-second moving average of the left/right power balance.

30s Power

The 30-second moving average of power output.

3s Balance

The three-second moving average of the left/right power balance.

3s Power

The 3-second moving average of power output.

500m Pace

The current rowing pace per 500 meters.

Aerobic Training Effect

The impact of the current activity on your aerobic fitness level.

Ambient Pressure

The uncalibrated environmental pressure.

Anaerobic Training Effect

The impact of the current activity on your anaerobic fitness level.

Average % Heart Rate Reserve

The average percentage of heart rate reserve (maximum heart rate minus resting heart rate) for the current activity.

Average 500m Pace

The average rowing pace per 500 meters for the current activity.

Average Ascent

The average vertical distance of ascent since the last reset.

Average Balance

The average left/right power balance for the current activity.

Average Cadence

Cycling. The average cadence for the current activity.

Average Cadence

Running. The average cadence for the current activity.

Average Descent

The average vertical distance of descent since the last reset.

Average Distance Per Stroke

Swimming. The average distance traveled per stroke during the current activity.

Average Distance Per Stroke

Paddle sports. The average distance traveled per stroke during the current activity.

Average GCT Balance

The average ground contact time balance for the current session.

Average Ground Contact Time

The average amount of ground contact time for the current activity.

Average Heart Rate

The average heart rate for the current activity.

Average Heart Rate %Max.

The average percentage of maximum heart rate for the current activity.

Average Lap Time

The average lap time for the current activity.

Average Left Power Phase

The average power phase angle for the left leg for the current activity.

Average Moving Speed

The average speed when moving for the current activity.

Average Nautical Speed

The average speed in knots for the current activity.

Average Overall Speed

The average speed for the current activity, including both moving and stopped speeds.

Average Pace

The average pace for the current activity.

Average Power

The average power output for the current activity.

Average Right Power Phase

The average power phase angle for the right leg for the current activity.

Average Speed

The average speed for the current activity.

Average Stride Length

The average stride length for the current session.

Average Stroke Rate

Paddle sports. The average number of strokes per minute (spm) during the current activity.

Average Strokes Per Length

The average number of strokes per pool length during the current activity.

Average Swolf

The average swolf score for the current activity. Your swolf score is the sum of the time for one length plus the number of strokes for that length (Swim Terminology). In open water swimming, 25 meters is used to calculate your swolf score.

Average Vertical Oscillation

The average amount of vertical oscillation for the current activity.

Average Vertical Ratio

The average ratio of vertical oscillation to stride length for the current session.

Avg. Left Peak Power Phase

The average power phase peak angle for the left leg for the current activity.

Avg. Nautical SOG

The average speed of travel in knots for the current activity, regardless of the course steered and temporary variations in heading.

Avg. Platform Center Offset

The average platform center offset for the current activity.

Avg. Right Peak Power Phase

The average power phase peak angle for the right leg for the current activity.

Avg. SOG

The average speed of travel for the current activity, regardless of the course steered and temporary variations in heading.

Balance

The current left/right power balance.

Barometric Pressure

The current calibrated environmental pressure.

Battery Hours

The number of hours remaining before the battery power is depleted.

Battery Percentage

The percentage of the battery power remaining.

Bearing

The direction from your current location to a destination. You must be navigating for this data to appear.

Cadence

Cycling. The number of revolutions of the crank arm. Your device must be connected to a cadence accessory for this data to appear.

Cadence

Running. The steps per minute (right and left).

Cadence Gauge

Running. A color gauge showing your current cadence range.

Calories

The amount of total calories burned.

COG

The actual direction of travel, regardless of the course steered and temporary variations in heading.

Compass Gauge

The direction you are moving based on the compass.

Compass Heading

The direction you are moving based on the compass.

Course

The direction from your starting location to a destination. Course can be viewed as a planned or set route. You must be navigating for this data to appear.

Destination Location

The position of your final destination.

Destination Waypoint

The last point on the route to the destination. You must be navigating for this data to appear.

Di2 Battery

The remaining battery power of a Di2 sensor.

Distance

The distance traveled for the current track or activity.

Distance Per Stroke

Paddle sports. The distance traveled per stroke.

Distance Remaining

The remaining distance to the final destination. You must be navigating for this data to appear.

Distance To Next

The remaining distance to the next waypoint on the route. You must be navigating for this data to appear.

eBike Battery

The remaining battery power of an ebike.

eBike Range

The estimated remaining distance the ebike can provide assistance.

Elapsed Time

The total time recorded. For example, if you start the timer and run for 10 minutes, then stop the timer for 5 minutes, then start the timer and run for 20 minutes, your elapsed time is 35 minutes.

Elevation

The altitude of your current location above or below sea level.

Estimated Total Distance

The estimated distance from the start to the final destination. You must be navigating for this data to appear.

ETA

The estimated time of day when you will reach the final destination (adjusted to the local time of the destination). You must be navigating for this data to appear.

ETA at Next

The estimated time of day when you will reach the next waypoint on the route (adjusted to the local time of the waypoint). You must be navigating for this data to appear.

ETE

The estimated time remaining until you reach the final destination. You must be navigating for this data to appear.

Floors Climbed

The total number of floors climbed up for the day.

Floors Descended

The total number of floors climbed down for the day.

Floors per Minute

The number of floors climbed up per minute.

Flow

The measurement of how consistently you maintain speed and smoothness through turns in the current activity.

Front

The front bike gear from a gear position sensor.

GCT Balance

The left/right balance of ground contact time while running.

GCT Balance Gauge

A color gauge showing the left/right balance of ground contact time while running.

Gear Battery

The battery status of a gear position sensor.

Gear Combo

The current gear combination from a gear position sensor.

Gear Ratio

The number of teeth on the front and rear bike gears, as detected by a gear position sensor.

Gears

The front and rear bike gears from a gear position sensor.

Glide Ratio

The ratio of horizontal distance traveled to the change in vertical distance.

Glide Ratio to Destination

The glide ratio required to descend from your current position to the destination elevation. You must be navigating for this data to appear.

GPS

The strength of the GPS satellite signal.

GPS Elevation

The altitude of your current location using GPS.

GPS Heading

The direction you are moving based on GPS.

Grade

The calculation of rise (elevation) over run (distance). For example, if for every 3 m (10 ft.) you climb you travel 60 m (200 ft.), the grade is 5%.

Grit

The measurement of difficulty for the current activity based on elevation, gradient, and rapid changes in direction.

Ground Contact Time

The amount of time in each step that you spend on the ground while running, measured in milliseconds. Ground contact time is not calculated while walking.

Ground Contact Time Gauge

A color gauge showing the amount of time in each step that you spend on the ground while running, measured in milliseconds.

Heading

The direction you are moving.

Heart Rate

Your heart rate in beats per minute (bpm). Your device must have wrist-based heart rate or be connected to a compatible heart rate monitor.

Heart Rate %Max.

The percentage of maximum heart rate.

Heart Rate Gauge

A color gauge showing your current heart rate zone.

Heart Rate Zone

The current range of your heart rate (1 to 5). The default zones are based on your user profile and maximum heart rate (220 minus your age).

Intensity Factor

The Intensity Factor™ for the current activity.

Interval Average %HRR

The average percentage of heart rate reserve (maximum heart rate minus resting heart rate) for the current swim interval.

Interval Average %Max.

The average percentage of maximum heart rate for the current swim interval.

Interval Average Heart Rate

The average heart rate for the current swim interval.

Interval Distance

The distance traveled for the current interval.

Interval Lengths

The number of pool lengths completed during the current interval.

Interval Maximum %HRR

The maximum percentage of heart rate reserve (maximum heart rate minus resting heart rate) for the current swim interval.

Interval Maximum %Max.

The maximum percentage of maximum heart rate for the current swim interval.

Interval Maximum Heart Rate

The maximum heart rate for the current swim interval.

Interval Pace

The average pace for the current interval.

Interval Stroke Rate

The average number of strokes per minute (spm) during the current interval.

Interval Strokes Per Length

The average number of strokes per pool length during the current interval.

Interval Stroke Type

The current stroke type for the interval.

Interval Swolf

The average swolf score for the current interval.

Interval Time

The stopwatch time for the current interval.

Lap % Heart Rate Reserve

The average percentage of heart rate reserve (maximum heart rate minus resting heart rate) for the current lap.

Lap 500m Pace

The average rowing pace per 500 meters for the current lap.

Lap Ascent

The vertical distance of ascent for the current lap.

Lap Balance

The average left/right power balance for the current lap.

Lap Cadence

Cycling. The average cadence for the current lap.

Lap Cadence

Running. The average cadence for the current lap.

Lap Descent

The vertical distance of descent for the current lap.

Lap Distance

The distance traveled for the current lap.

Lap Distance Per Stroke

Swimming. The average distance traveled per stroke during the current lap.

Lap Distance Per Stroke

Paddle sports. The average distance traveled per stroke during the current lap.

Lap Flow

The overall flow score for the current lap.

Lap GCT Balance

The average ground contact time balance for the current lap.

Lap Grit

The overall grit score for the current lap.

Lap Ground Contact Time

The average amount of ground contact time for the current lap.

Lap Heart Rate

The average heart rate for the current lap.

Lap Heart Rate %Max.

The average percentage of maximum heart rate for the current lap.

Lap Left Peak Power Phase

The average power phase peak angle for the left leg for the current lap.

Lap Left Power Phase

The average power phase angle for the left leg for the current lap.

Lap Normalized Power

The average Normalized Power for the current lap.

Lap Pace

The average pace for the current lap.

Lap Platform Center Offset

The average platform center offset for the current lap.

Lap Power

The average power output for the current lap.

Lap Right Peak Power Phase

The average power phase peak angle for the right leg for the current lap.

Lap Right Power Phase

The average power phase angle for the right leg for the current lap.

Laps

The number of laps completed for the current activity.

Lap SOG

The average speed of travel for the current lap, regardless of the course steered and temporary variations in heading.

Lap Speed

The average speed for the current lap.

Lap Stride Length

The average stride length for the current lap.

Lap Stroke Rate

Swimming. The average number of strokes per minute (spm) during the current lap.

Lap Stroke Rate

Paddle sports. The average number of strokes per minute (spm) during the current lap.

Lap Strokes

Swimming. The total number of strokes for the current lap.

Lap Strokes

Paddle sports. The total number of strokes for the current lap.

Lap Swolf

The swolf score for the current lap.

Lap Time

The stopwatch time for the current lap.

Lap Vertical Oscillation

The average amount of vertical oscillation for the current lap.

Lap Vertical Ratio

The average ratio of vertical oscillation to stride length for the current lap.

Last Lap %HRR

The average percentage of heart rate reserve (maximum heart rate minus resting heart rate) for the last completed lap.

Last Lap 500m Pace

The average rowing pace per 500 meters for the last lap.

Last Lap Ascent

The vertical distance of ascent for the last completed lap.

Last Lap Cadence

Cycling. The average cadence for the last completed lap.

Last Lap Cadence

Running. The average cadence for the last completed lap.

Last Lap Descent

The vertical distance of descent for the last completed lap.

Last Lap Distance

The distance traveled for the last completed lap.

Last Lap Distance Per Stroke

Swimming. The average distance traveled per stroke during the last completed lap.

Last Lap Distance Per Stroke

Paddle sports. The average distance traveled per stroke during the last completed lap.

Last Lap Heart Rate

The average heart rate for the last completed lap.

Last Lap Heart Rate %Max.

The average percentage of maximum heart rate for the last completed lap.

Last Lap Max. Power

The top power output for the last completed lap.

Last Lap Normalized Power

The average Normalized Power for the last completed lap.

Last Lap Pace

The average pace for the last completed lap.

Last Lap Power

The average power output for the last completed lap.

Last Lap SOG

The average speed of travel for the last completed lap, regardless of the course steered and temporary variations in heading.

Last Lap Speed

The average speed for the last completed lap.

Last Lap Stroke Rate

Swimming. The average number of strokes per minute (spm) during the last completed lap.

Last Lap Stroke Rate

Paddle sports. The average number of strokes per minute (spm) during the last completed lap.

Last Lap Strokes

Swimming. The total number of strokes for the last completed lap.

Last Lap Strokes

Paddle sports. The total number of strokes for the last completed lap.

Last Lap Swolf

The swolf score for the last completed lap.

Last Lap Time

The stopwatch time for the last completed lap.

Last Length Pace

The average pace for your last completed pool length.

Last Length Stroke Rate

The average number strokes per minute (spm) during the last completed pool length.

Last Length Strokes

The total number of strokes for the last completed pool length.

Last Length Stroke Type

The stroke type used during the last completed pool length.

Last Length Swolf

The swolf score for the last completed pool length.

Lat/Lon

The current position in latitude and longitude regardless of the selected position format setting.

Left Peak Power Phase

The current power phase peak angle for the left leg. Power phase peak is the angle range over which the rider produces the peak portion of the driving force.

Left Power Phase

The current power phase angle for the left leg. Power phase is the pedal stroke region where positive power is produced.

Lengths

The number of pool lengths completed during the current activity.

Load

The training load for the current activity. Training load is the amount of excess post-exercise oxygen consumption (EPOC), which indicates the strenuousness of your workout.

Location

The current position using the selected position format setting.

Max. Nautical SOG

The maximum speed of travel in knots for the current activity, regardless of the course steered and temporary variations in heading.

Maximum Ascent

The maximum rate of ascent in feet per minute or meters per minute since the last reset.

Maximum Descent

The maximum rate of descent in meters per minute or feet per minute since the last reset.

Maximum Elevation

The highest elevation reached since the last reset.

Maximum Lap Power

The top power output for the current lap.

Maximum Nautical Speed

The maximum speed in knots for the current activity.

Maximum Power

The top power output for the current activity.

Maximum SOG

The maximum speed of travel for the current activity, regardless of the course steered and temporary variations in heading.

Maximum Speed

The top speed for the current activity.

Minimum Elevation

The lowest elevation reached since the last reset.

Moving Time

The total time moving for the current activity.

Multisport Time

The total time for all sports in a multisport activity, including transitions.

Muscle O2 Saturation %

The estimated muscle oxygen saturation percentage for the current activity.

Nautical Distance

The distance traveled in nautical meters or nautical feet.

Nautical SOG

The actual speed of travel in knots, regardless of the course steered and temporary variations in heading.

Nautical Speed

The current speed in knots.

Next Split Distance

Running. The total distance of the next split.

Next Split Target Pace

Running. The target pace for the next split.

Next Waypoint

The next point on the route. You must be navigating for this data to appear.

Normalized Power

The Normalized Power™ for the current activity.

Off Course

The distance to the left or right by which you have strayed from the original path of travel. You must be navigating for this data to appear.

Overall Ahead/Behind

Running. The overall time ahead or behind of the target pace.

Pace

The current pace.

PacePro Gauge

Running. Your current split pace and your target split pace.

Pedal Smoothness

The measurement of how evenly a rider is applying force to the pedals throughout each pedal stroke.

Performance Condition

The performance condition score is a real-time assessment of your ability to perform.

Platform Center Offset

The platform center offset. Platform center offset is the location on the pedal platform where force is applied.

Power

Cycling. The current power output in watts.

Power

Skiing. The current power output in watts. Your device must be connected to a compatible heart rate monitor.

Power Gauge

A color gauge showing your current power zone.

Power to Weight

The current power measured in watts per kilogram.

Power Zone

The current range of power output (1 to 7) based on your FTP or custom settings.

Rear

The rear bike gear from a gear position sensor.

Repeat On

The timer for the last interval plus the current rest (pool swimming).

Reps

During a strength training activity, the number of repetitions in a workout set.

Respiration Rate

Your respiration rate in breaths per minute (brpm).

Rest Timer

The timer for the current rest (pool swimming).

Right Peak Power Phase

The current power phase peak angle for the right leg. Power phase peak is the angle range over which the rider produces the peak portion of the driving force.

Right Power Phase

The current power phase angle for the right leg. Power phase is the pedal stroke region where positive power is produced.

Set Timer

During a strength training activity, the amount of time spent in the current workout set.

Speed

The current rate of travel.

Speed Over Ground

The actual speed of travel, regardless of the course steered and temporary variations in heading.

Split Distance

Running. The total distance of the current split.

Split Distance Remaining

Running. The remaining distance of the current split.

Split Pace

Running. The pace for the current split.

Split Target Pace

Running. The target pace for the current split.

Steps

The number of steps taken during the current activity.

Stopped Time

The total time stopped for the current activity.

Stress

Your current stress level.

Stride Length

The length of your stride from one footfall to the next, measured in meters.

Stroke Rate

Swimming. The number of strokes per minute (spm).

Stroke Rate

Paddle sports. The number of strokes per minute (spm).

Strokes

Swimming. The total number of strokes for the current activity.

Strokes

Paddle sports. The total number of strokes for the current activity.

Sunrise

The time of sunrise based on your GPS position.

Sunset

The time of sunset based on your GPS position.

Swim Time

The swimming time for the current activity, not including rest time.

Temperature

The environmental temperature during the activity. Your body temperature affects the temperature sensor. You can pair a tempe™ sensor with your device to provide a consistent source of accurate temperature data.

Time in Zone

The time elapsed in each heart rate or power zone.

Time of Day

The time of day based on your current location and time settings (format, time zone, daylight saving time).

Time of Day (Seconds)

The time of day including seconds.

Timer

The current time of the countdown timer.

Time Seated

The time spent seated while pedaling for the current activity.

Time Seated Lap

The time spent seated while pedaling for the current lap.

Time Standing

The time spent standing while pedaling for the current activity.

Time Standing Lap

The time spent standing while pedaling for the current lap.

Time to Next

The estimated time remaining before you reach the next waypoint in the route. You must be navigating for this data to appear.

Torque Efficiency

The measurement of how efficiently a rider is pedaling.

Total Ascent

The total elevation distance ascended since the last reset.

Total Ascent/Descent Gauge

The total elevation distances ascended and descended during the activity or since the last reset.

Total Descent

The total elevation distance descended since the last reset.

Total Hemoglobin

The estimated total hemoglobin concentration in the muscle.

Training Effect Gauge

The impact of the current activity on your aerobic and anaerobic fitness levels.

Training Stress Score

The Training Stress Score™ for the current activity.

Velocity Made Good

The speed at which you are closing on a destination along a route. You must be navigating for this data to appear.

Vertical Dist. to Dest.

The elevation distance between your current position and the final destination. You must be navigating for this data to appear.

Vertical Oscillation

The amount of bounce while you are running. The vertical motion of your torso, measured in centimeters for each step.

Vertical Oscillation Gauge

A color gauge showing the amount of bounce while you are running.

Vertical Ratio

The ratio of vertical oscillation to stride length.

Vertical Ratio Gauge

A color gauge showing the ratio of vertical oscillation to stride length.

Vertical Speed

The rate of ascent or descent over time.

Vertical Speed to Target

The rate of ascent or descent to a predetermined altitude. You must be navigating for this data to appear.

Work

The accumulated work performed (power output) in kilojoules.

GUID-DF9BDE35-F592-4CD8-872D-A2910FAFC147 v8

4. Diving activities in Garmin Fenix 7 - fēnix 7 Series - Wearables - Garmin Forums
   URL: https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-7-series/260357/diving-activities-in-garmin-fenix-7/1245073
   Diving activities in Garmin Fenix 7 - fēnix 7 Series - Wearables - Garmin Forums

Related

Options

# Diving activities in Garmin Fenix 7

Hello everybody

Wouldn't you like the Fenix 7 to have some possibility of diving activities?

I know that the Garmin Descent MK2 exists and I think it is a wonderful device, but I am not going to dive more than once or twice a year, and that if I am lucky.So I can't justify the money to buy one.

So I think it would be a good opportunity to include the most basic functions of the Descent MK2's dive computer and put them in the Fenix 7 (we are talking about no mixed gas dive and basic apnea).

I know this is possible, in fact, I used a Garmin IQ downloadable app for my Fenix 5s and it worked like a charm, just like my dedicated dive computer.

This would be a great reason to buy a Fenix 7.

- Sign in to reply
- Cancel

## Top Replies

I wear my Epix all the time while snorkeling and doing light freediving. It's been working fine. What's the issue you're having? In that entire very lengthy post you didn't mention…

- It would be neat, but diving computers have stricter hardware and performance requirements than the Fenix offers, which is why Descent is more expensive. For example, the standard atmospheric barometer…
- 1. The "100M" certification of the fenix does NOT correspond to certification for diving (EN13319).2. the fenix simply does not have a depth gauge.100 m: Can be used for all types of swimming…

## All Replies

It would be neat, but diving computers have stricter hardware and performance requirements than the Fenix offers, which is why Descent is more expensive. For example, the standard atmospheric barometer doesn't work for accurately measuring water pressure/depth - that requires a different kind of sensor. Yes, the atmospheric barometer can have some algorithms tossed at it that simulate/estimate water depths, but despite your positive experience with the CIQ app, it's really not accurate enough to safely use it for such.

The problem is, if they add diving features and market it as a diving device, without making the proper (more expensive) hardware and performance upgrades necessary for a diving computer, then lives could be at stake. It would be a massive liability issue for Garmin.

So, while it's possible to add diving features, they really shouldn't because it will ramp up the MSRP significantly, and price out the many Fenix buyers who don't care about diving. That's why Garmin currently has, and IMHO always should have, a different device specific for people who want to spend more for a proper diving computer.

It's much better for everyone (both the consumers who want to save money, and Garmin who doesn't want to lose customers or gain unnecessary liability) to keep the Fenix series as a watch that can handle going to diving depths, but that doesn't really offer any diving-specific functions.

So, while it's possible to add diving features, they really shouldn't because it will ramp up the MSRP significantly, and price out the many Fenix buyers who don't care about diving.

Agreed.

without making the proper (more expensive) hardware and performance upgrades necessary for a diving computer, then lives could be at stake. It would be a massive liability issue for Garmin.

Have you read the dive warnings on page 2 or the disclaimers in the manual? There is nothing on the Descent watch that if it were to fail, that Garmin would take responsibility. Liability isn't an issue here as their lawyers have this covered with disclaimers. This can simply be added to the manual of any device.

yeah- except there are plenty of cheap $200 dive computers out there- so I'm sure it's possible for a reasonable price.

The Fenix 6 pressure sensor isn't set up with the range to handle depth pressure, so nobody can create an IQ app for the Fenix 6.

I too dive just a couple times a year, and would love my Fenix to be able to do dives as well. It would certainly be a feature that would entice me to upgrade to an F7. The F6P is so good, other than "thinner, better battery life, bigger screen"- I'm not really sure what else I'd want from a watch that the Fenix 6 doesn't already have. Taking 2 mm off the thickness and giving me 10 extra battery hours isn't enough for me to upgrade. But Dive capability? yeah- that would do it. I agree with the OP, and believe it's completely possible within the already steep price of the Fenix line.

or, just create a Fenix 6 Pro Dive model for $100 more- and that would be a great product. Heck- more useful that the Solar version that adds an extra 6 min of battery life.

Have you read the dive warnings on page 2 or the disclaimers in the manual? There is nothing on the Descent watch that if it were to fail, that Garmin would take responsibility. Liability isn't an issue here as their lawyers have this covered with disclaimers. This can simply be added to the manual of any device.

It's not quite so simple. There are implied warranties, reliance on marketing statements, consumer protection and product liability laws, UDAP laws, and a host of other things that would give rise to claims, and which cannot just be disclaimed in a manual.

The theory that you could market and sell a dive computer that doesn't work, and rely on some disclaimer or contract of adhesion to absolve you of liability wouldn't typically fly in the US. And plenty of other countries have also had it with practices involving unequal bargaining power, unfairness/unconscionability, unfair surprise, unequal bargaining power, lack of notice, etc., and have prohibited the waiving of consumer protections rights through contract.

1. The "100M" certification of the fenix does NOT correspond to certification for diving (EN13319).

2. the fenix simply does not have a depth gauge.

100 m: Can be used for all types of swimming, poolside diving or snorkelling, but is NOT suitable for scuba diving.

The theory that you could market and sell a dive computer that doesn't work

Who said anything about selling a dive computer that doesn't work? You're talking about apples and oranges. Of course it a product line was known to be defective and was intentionally put on the market then a company can be held liable. The Descent isn't one of those products, so if your watch failed for one reason or another, you think you could hold Garmin liable? Name one example of how it could fail and you think you're going to cash in? Just one.

If you are a diver and care about your life you know you should only use equipment that is designed to use for diving. So no, keep the Fenix as it.

I have both a Descent Mk2, and a Fenix 6X solar. While the fenix gets many more updates it never seems to do everything up to spec at any one time. At the moment by "big" issues with the fenix 6 are intensity minutes, sleep and battery life. I alternate every week or 2 between them. The Descent just works as specified sleep is perfect, intensity minutes accurate. I agree some way of recording your dive with a Fenix6 would be great. I still use a dedicated air integrated dive computer as my main aid, but like to record the dive on the descent (writing too small for old eyes).

All activities in 1 place!

Oops, I might have spoken too soon. I see software version 8 is available for the descent and includes on watch sleep calculation! To upgrade or not?

People in this forum claim that the Fenix 6 is already ”not fit for purpose” since it does not smooth the graphs for current pace while running. Or that the WHR is not accurate in all situations. Or that the GPS is off by a few meters..

And you suggest that it should support diving even though it does not have what it takes to do that accurately.

I’m glad I’m not a product manager at Garmin because people in this forum sure is a tough crowd to please.

5. Ambient pressure and pressure history don't match - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/244746/ambient-pressure-and-pressure-history-don-t-match
   Ambient pressure and pressure history don't match - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- Replies 24 replies
- Subscribers 18 subscribers
- Views 5648 views
- Users 0 members are here

Options

Related

# Ambient pressure and pressure history don't match

Hey all, does anyone know what pressure the pressure history is storing? I have tested with putting both on screen and my ambient pressure is always higher than my max pressure history (over last 30 mins) so what is this doing?

If I look at my watch now it shows PH getMax to be 101833 and my AP now to be 102996. The PH never been above 101... if I put it in water (20cm) the AP goes up to 104888 which shows AP sensor is moving but PH never changes or goes near it.

Any insights would be great as I am trying to see historical pressure history to make a "guess" on no fly time for diving.

Many thanks,

Ben

- Sign in to reply
- Cancel

I'm not sure how SH.getPressureHistory deals with being under water. If I recall it's MSL pressure. Also, how often it's saved likely varies by device, where you can find the interval by comparing "when" in two adjacent samples.

And getting Sensor.Info.pressure can vary from what you see in Activity.Info.ambientPressure/Activity.Info.rawAmbientPressure

Ahh fiddle sticks... MSL pressure is of no use to me and that explains why it doesn't seem to change in the history even when submerged in water for 10 minutes. Must also be adjusting for depth of water (as this is the MK2 so has a depth sensor but cannot access it through CIQ I don't think?)

Basically, doesn't look like I can do what I want so will have to use the standard Garmin faces when diving and custom one when not :(

Thanks for the info Jim, appreciate it!

Actually stupid question, could I not just get raw and store date and time in a variable and do it that way..? The code doesn't reset each refresh does it? That would work I think :)

Actually that won't work as the WF has to be active to measure anything which it won't during a dive.

Also, Jim, does the memory/variables reset when you navigate away from the WF and back to it do you know? Thanks again.

Yes, you can build your own list of data and time. You might be able to do it in the main app, but you can also use a background service to take a reading every X minutes. In either case, you'll want to store the data using Application.Storage. You have to handle missing data.

I just saw your new post, but with a background process you can probably run the background while doing a dive.

Interesting, will look into that. Don't want to lag or run battery down for this so will see what performance is like on it :)

Thanks again for the info! :)

Here's a widget I did that does a graph of temperature using a background process. In general, the way it works is I save up to 96 samples with a time stamp. For a 4hr graph, the background runs every 4 minutes, but for a 48hr graph, every 30 minutes. Try it on your next dive. For missing readings, you'll see a pink mark under the graph.

The background in this is actually pretty minor, with the heavy lifting done in the widget itself.

Great, thanks. Will have a look at running background processes and see if that can work. Out of curiosity, why wouldn't you use temperature history for this or was it more of an experiment to see if it worked? (also this is a default widget isn't it or did you make it before that became standard?)

Thanks again Jim, you seem to be the fountain of knowledge on these forums because the Garmin library docs are terrible! :) hehe

SH.getTemperatureHistory only provides about 4hrs of data, and I wanted to allow for a couple days of data, so I did my own caching. And this doesn't require the widget itself to be run on a regular basis.

Ah of course, mine does say last 4 hours to be fair. Cool, will give this a go :)

Found a blog post you referenced 3 years ago but it is broken :( I cannot find any examples but is it a case of using a registerForTemporalEvent and setting it every say 10 minutes and then adding data to the Application.Storage? That how this would work? Sorry for all the Q's but I work better off examples and cannot find any I understand and this monkey C is pretty new to me

Thanks again

6. Retrieve ambient pressure in foreground - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/288741/retrieve-ambient-pressure-in-foreground
   Retrieve ambient pressure in foreground - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- Replies 11 replies
- Subscribers 18 subscribers
- Views 1953 views
- Users 0 members are here

Options

Related

# Retrieve ambient pressure in foreground

Toybox.Sensor.getInfo().ambientPressure needs the permission Toybox.Sensor - I don't have added this permission yet because until now I used the pressure history.

I realised that ambientPressure is the value I want to display and not the one from the history and want to change this now.

1) it seems like ambientPressure value can't be retrieved from history, correct?

2) I realised that Toybox.Sensor also needs the background permission, does this mean I can only read the ambientPressure in the background?

Actually I don't want to add 2 permissions for this single data value to my watchface, is there no alternative way to get the current pressure (or last in one from history)?

- Sign in to reply
- Cancel

With a watch face, you can only access Sensor data in a background service.

Try Activity.getActivityInfo().ambientPressure in the foreground

Be sure to handle devices without a baro altimeter

In the sim I can access ambientPressure without an exception but it returns null (without adding the necessary permissions though)... But you say, the foreground access won't work on a real device anyway, that's the important information for me. Btw, adding background + sensor permission approx. halves the available memory for a watchface (ERROR: PRG generated exceeds the memory limit of 'background' applications for device id 'fenix6xpro': 63883 bytes) - is this something I have to accept or can I circumvent this side effect?

Can't I alternatively convert pressure to ambientPressure with the history data?

In the sim, are you simulating data? Try Activity.Info on a real device with a baro if you have doubts.

Once you add background permission, you want to make sure you use the (:background) annotation where needed, otherwise it will try to load the entire WF when the background runs, inclusing when onAppInstall() or onAppUpdate() are called.

Now that I simulate data it shows a value - thanks. Even without adding additional permissions.

Oh, now I remember that in need to add :background annotations where needed to avoid my whole WF is running in the background - thanks.

So actually you say something different than I though - that real devices with baro allow to access Activity.getActivityInfo().ambientPressure in the foreground? So I just have to add the permissions, make sure my WF is running in foreground and it will work on a real device? Or will it work without the additional permissions in the foreground on a real device (as this is what I see in the sim)?

hi, no permission is need for Activity.getActivityInfo().ambientPressure

when Jim said "Be sure to handle devices without a baro altimeter" I think he means to check if the device has a Baro with

if(Activity.getActivityInfo() has :ambientPressure){...}

if you use this method, you don't need :Background annotation or permission.

Thanks, that answers all open questions. The unsure phrase for me was "you can only access Sensor data in a background service"

yes the module Sensor. but Activity is available from foreground.

Don't forget to check null statment

thanks for clarifying that. Btw, isn't the null check enough for class variables? I actually though the :has must only be used for functions...

hi, no it is not enough, if you try for exemple Activity.getActivityInfo().ambientPressure on a F45, it will crash since FR45 does not have ABC sensor.

see the API doc, you have lots of exemple of :has

You want to do the has check too. Devices like the fr45, fr55, fr245 and venu sq don't have a baro altimeter.

7. Please add diving support to the fenix series - fēnix 6 Series - Wearables - Garmin Forums
   URL: https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/172190/please-add-diving-support-to-the-fenix-series/1148509
   Please add diving support to the fenix series - fēnix 6 Series - Wearables - Garmin Forums

- Cancel
- More
- German Forum
- Beta Program
- Developer
- Pilots
- Sports & Fitness
- Outdoor Recreation
- Apps & Software

Related

Options

- Cancel
- More
- RSS

# Please add diving support to the fenix series

Hi,

thank you Garmin for introducing the F6 series. The watches are great!

However, with this thread I want to ask for a feature; maybe for the upcoming fenix series.

Would it not be possible to also PROPERLY (no hack) provide the diving modes in upcoming fenix watches?

I can understand that you would like to target the diving segment with the Descent series but I think there are also a lot of users who do outdoor/fitness AND scuba diving. And in my understanding, it should not be that difficult to also include it in the fenix series (the most difficult part should be the water rating and to implement the pressure sensor, or?)

I'm a loyal fenix buyer but I hesitate a bit with buying TWO expensive watches. On the other side, if i would have to pay a bit more on a new fenix watch which would also include the diving modes, i would do it. I don't know, if other users see this similar, but for me I can state this.

Thank your respones.

- Cancel
- Psylocibine

8. Water depth with instinct 2 - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/290491/water-depth-with-instinct-2
   Water depth with instinct 2 - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- Replies 25 replies
- Subscribers 20 subscribers
- Views 10189 views
- Users 0 members are here

Options

- Share
- More
- Cancel

Related

# Water depth with instinct 2

Good afternoon all

My instinct2 has the same barometer sensor as the G1 so iv been told. Im trying to make a water depth data field, but the simulator app crashes. I'm fairly new to monkey c could one of you experts read it over and tell me where im going wrong

```
import Toybox.Activity;
import Toybox.Lang;
import Toybox.Time;
import Toybox.WatchUi;
import Toybox.Sensor;

class valueView extends WatchUi.SimpleDataField {

    function initialize() {
        SimpleDataField.initialize();
        label = "Water depth M";
    }

     var x = Activity.getActivityInfo().ambientPressure;
     var y = ((x - 1013)/9.9) ; //1013 average sea level pressure Pr, h=(P-Pr)/(rho * g '=9.9')
    function compute(info as Activity.Info) as Numeric or Duration or String or Null {
        return y ;
    }

}
```

- Sign in to reply
- Cancel

## Top Replies

- There is a missing "}"after line 17. and a missing ";" on line 17

## All Replies

The two lines starting with var x and var y need to be inside of compute, as you want to get Acitivity.Info each time compute is called. And the paramete pass to compute is actually Activitity.Info, so,

```
    function compute(info as Activity.Info) as Numeric or Duration or String or Null {
        var x=info.ambientPressure;
        var y=0;
        if(x!=null) {
            y = ((x - 1013)/9.9) ; //1013 average sea level pressure Pr, h=(P-Pr)/(rho * g '=9.9')
        }
        return y ;
    }
```

Since the Instinct2 isn't a diving watch, the value ofr ambienPressure may be limited by the FW.

Thanks for that, it seems to return an error. im not sure what's wrong

```
import Toybox.Activity;
import Toybox.Lang;
import Toybox.Time;
import Toybox.WatchUi;
import Toybox.Sensor;

class valueView extends WatchUi.SimpleDataField {

    function initialize() {
        SimpleDataField.initialize();
        label = "Water depth M";
    }
   function compute(info as Activity.Info) as Numeric or Duration or String or Null {
        var x=info.ambientPressure;
        var y=0;
        if(x!=null) {
            y = ((x - 1013)/9.9) ; //1013 average sea level pressure Pr, h=(P-Pr)/(rho * g '=9.9')
       return y ;
        }
   }
```

extraneous input ' ' expecting

Post the error.

There is a missing "}"after line 17. and a missing ";" on line 17

Thanks for the help. Seems to be working I will have to invest more time in learning monkey

I'm assuming ambient pressure is measured in pascals as to convert to Mb I just needed to /100 to get a realist figure.

Hi

its interesting if i read ambient pressure only it displays 96803 assuming would be 968.02mb but my barometer reads 998.0mb on the watch app itself. any ideas if im selecting the correct data field, it goes up and down with hills. do garmin have to calibrate pressure readings ?

Notice there is ambientPressure as well as rawAmbientPressure and also

for ambientPressure

The data is smoothed by a two-stage filter to reduce noise and instantaneous variation.

for rawAmbientPressure

The data is the temperature compensated information read directly from the internal sensor.

Ok seems strange how it's so far off, going with the filtered data it's saying I'm almost 3000ft high when in reality I'm 200ft. I'm wondering if they just use an offset to calibrate it for the main watch barometer.

9. Freediving depth meter + surf time - Third-Party App Ideas - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/app-ideas/974/freediving-depth-meter-surf-time
   Freediving depth meter + surf time - Third-Party App Ideas - Connect IQ - Garmin Forums

- Cancel
- More
- German Forum
- Beta Program
- Developer
- Pilots
- Sports & Fitness
- Outdoor Recreation
- Apps & Software

- Users 0 members are here
- Views 8183 views
- Subscribers 12 subscribers
- Replies 25 replies

Options

- Cancel
- More
- Share

Related

# Freediving depth meter + surf time

Hello, I would like to make simple freediving app 1) Depth meter Ive played with that on Suunto Ambit 2 this should be formula which worked with Suunt - (pressure - 1013.25) / (10.26*9.81) 2) Surf time Time count which start when you reach surface (based on pressure) and should be reseted to 0 once you swim to -1m I dont have much time to work on it but should start this weekend and will see

- Cancel
- Sign in to reply

1) OK, but I would not show the actual depth until it does not exceed 0,5 m (like most Dive computers) 2) My Suunto Dive computer resets Surf time to 0 at depth 0,5 m

> 1) OK, but I would not show the actual depth until it does not exceed 0,5 m (like most Dive computers) 2) My Suunto Dive computer resets Surf time to 0 at depth 0,5 m

Yeah that make sense

HiFirst step for making any freediving Applications is to get the depth.One problem for calculating depth is, that the barometric pressure, that can be retrived from the sensor API, is not accessible for making datafields.But I've come up with a work-around, and that is to use the attitude data from the activity API.I've made this work and shared the code a the end of my post. (Use at your own risk :))I've tested it on my Fenix3 in the local public pool. The stated depth of the pool is 3.5m. My depth gauge measured 3.46m.So the presicion is definetly good enough for me. I'm not sure that happens at greater depths.(Maybe I should get it tested in a pressure chamber at a local Watch shop.)One thing that doesn't work too well is that it takes about 10 sec for the gauge to settle at the depth. But I guess that the attitude function averages the pressure data using a 10 sec running average, to keep the reading stable.Using the pressure gauge for depth wouldn't need this averaging, so I guess that the Depth function could be made more responsive if acces to the un-averaged data were possble.I'm going to try and make other freediving datafields, but are also looking forward to your ideas and Developments.//! ----- Code begin -----//!SimpleDataFieldclass DataField extends Ui.SimpleDataField{ var LowestPressure; //! Constructor function initialize() { label = "Depth"; LowestPressure = 6000.00; } //! Handle the update event function compute(info) { var Pressure = null; var AltEQ = null; var Calc = null; var Depth = null; //! Pressure calculated from a formula found on wikipedia and//! rearranged in the following form://! Pressure[mBar] = ((1-HeightInMeters/a)^b)*c//! Where://! a = 44307.69 (Different value needed in imperial mode)//! b = 5.255303//! c = 1013.25 if( info.altitude != null ) { AltEQ = info.altitude; Calc = 1 - AltEQ/44307.69; AltEQ = Math.pow(Calc , 5.255303); Pressure = AltEQ * 1013.25; if(LowestPressure > Pressure ) { LowestPressure = Pressure; //! Save lowest pressure for sea-level pressure correction. } Depth = (Pressure - LowestPressure)*1.02/100; //! 1.02 : Water density correction; 1.019 for fresh water or 1.02 to 1.029 for sea water } return Depth; }}//! ----- Code end -----

HiI've just uploaded an updated version for Connect IQ. It should take only a few days before it becomes availabe.

> Hi I've just uploaded an updated version for Connect IQ. It should take only a few days before it becomes availabe.

It is already available on https://apps.garmin.com/en-US/apps/1121d6d5-596b-4b48-9341-97c3d76fae8f

Hi AgainNow I've also uploaded a "Freediving Maximum Depth Gauge " . I guess it will be availabe within the Next 24h.

Hello Miguel,Ive finally tested your app and it works great. So far just 5m wish there was no limitation in refresh but I guess there is no other way arround. When you setup custom screen you can get actual depth, max depth and lap/interval time. Lap and interval timer you can reset on surface that way you can check breath up time and dive time :)

Hi SEMI666 I'm glad you like it. :) 5 meters is also the deepest I've been, so far. I'm actually working on a surface-time datafield, the code is written and compiles, but when I install it in the watch, and have selected the datafield for use in an app. Then, when I want to use the app, my Fenix3 somehow replaces the datafield with a "timer"-datafield ...? I'm still trying to figure out what goes wrong. If you've any suggestions to what could be wrong, I'm all ears :confused: Initially I thought it was a good idea to make freediving datafields and then you'd be able to configure your own custom made app with them. But now I've discovered that you're only allowed to use two ConnectIQ datafields in an app, which somewhat kill's that idea. It would probably be better to make independent app or to make datafields with two or even three sets of freediving specific data in them. Another advantage of making an independent app, could be that; app's have access to the sensor class and maybe the data from the raw "sensor.pressure" is faster and with less averaging.

Hello Miguel,Nice to see the development of you data fields. I have a small question about your depth calculation. Is there e reason why you use the altitude instead of the pressure field from info structure?

> Hello Miguel,Nice to see the development of you data fields. I have a small question about your depth calculation. Is there e reason why you use the altitude instead of the pressure field from info structure?

He explained in #4:"First step for making any freediving Applications is to get the depth.One problem for calculating depth is, that the barometric pressure, that can be retrived from the sensor API, is not accessible for making datafields.But I've come up with a work-around, and that is to use the attitude data from the activity API."

10. Ambient Pressure and Mean Seal Level Pressure Mismatch - Connect IQ App Development Discussion - Connect IQ - Garmin Forums
   URL: https://forums.garmin.com/developer/connect-iq/f/discussion/324960/ambient-pressure-and-mean-seal-level-pressure-mismatch
   Ambient Pressure and Mean Seal Level Pressure Mismatch - Connect IQ App Development Discussion - Connect IQ - Garmin Forums

- Replies 4 replies
- Subscribers 19 subscribers
- Views 1459 views
- Users 0 members are here

Options

- Share
- More
- Cancel

Related

# Ambient Pressure and Mean Seal Level Pressure Mismatch

I've been seeing a discrepancy between the watch-calculated mean sea level pressure and true calculations based on the watch-observed ambient pressure. Based on the actual mean sea level pressure in the area, the value returned from meanSeaLevelPressure appears inaccurate. Here are more specific details from the simulator using simulated data:

- Activity.Info.meanSeaLevelPressure returns a value of 102154.98 Pa (This is the seemingly incorrect value, should be 101045 Pa).
- Activity.Info.ambientPressure returns a value of 87026.59 Pa
- Activity.Info.altitude returns a value of 1242.70 m
- SensorHistory.getTemperatureHistory (the last value in the iteration) returns a temperature of 25.5 C

Using that ambient pressure (87026 Pa) and altitude (1242 m), the mean sea level pressure should be 101045 Pa1, or 99957 Pa2 with a Temperature correction. The returned meanSeaLevelPressure is substantially off using the Garmin API. There should be only a couple areas where that error could occur

1. The altitude used in meanSeaLevelPressure is substantially (roughly 100m) different than that of Activity.Info.altitude .
2. The temperature correction used in meanSeaLevelPressure is different than returned by SensorHistory.getTemperatureHistory , however the documentation of meanSeaLevelPressure only suggests it is corrected for altitude
3. The formulas used to calculate meanSeaLevelPressure in the API have an error.

Does anyone have any more insight into the specifics of the calculations and data Activity.Info.meanSeaLevelPressure utilizes? I'm consistently seeing errors in my watch face from actual measurements to the displayed data using the API data. Is there anything I may be missing?

---

References for calculations:

1) Elevation, Station (QFE) and Sea Level (QNH) Pressure Calculator (sensorsone.com)

2) Mean sea level pressure calculator (converter) (wind101.net)

- Sign in to reply
- Cancel

This is something you really want to look at on a real device and not the sim. To compute MSL pressure it needs ambient presume and elevation, and based on device there are different ways to calibrate the altitude/elevation. You can enter a specific value, use GPS, or DEM.

And then there's the case where you can be in the same location, but the weather, therefore ambient pressure, changes over time

And then even on a real device, getXyzHistory isn't real time, but is only saved every few minutes (you can tell how often by using the "when" values of two adjacent samples. In the sim some of this data is "canned" and doesn't change over time

Here for example are graphs of getPressureHistory and getTemperatureHistory in the sim. Both are canned and never change:

Thats a great thought --- I'll work on building a quick test app for my actual watch and update the post with that data if I'm seeing the same issue

Update with actual device data (still seeing the same issue as the sim, been monitoring the data for a couple hours):

Using the device measured ambient pressure and altitude, the non-temperature corrected value for MSL Pressure should be 98803.0 Pascals. Although that seems close, it is noticeably off when using inHg values for aviation.

The Garmin API meanSeaLevelPressure converts to an altimeter setting of 29.09 inHg. Using widely accepted calculations from the measured ambientPressure results in 98803.0 Pascals results in an altimeter setting of 29.18 inHg [actual value from weather service is 29.17 inHg].

What is interesting is the Garmin Barometer widget also shows the "correct" calculated value of 29.18 inHg. All this to say that the meanSeaLevelPressure value that is returned from the Garmin API neither matches the Garmin Barometer widget data, nor widely accepted calculation methods. Unless they're using some other method or pulling data from elsewhere, it seems like there's an error in the meanSeaLevelPressure calculations in Toybox.Activity.

I thought altitude was based on GPS reading .. my Mk1 is new to me and i am noticing that the altitude changes over a range of 10 m at my desk near the beach . currently 40m . assumed it was based on tide change (i keep the GPS on) .. . the pressure detection i assume is the same as the one used for depth on a dive which has to be a manometer of sorts (not calculated) & a critical datapoint.

- - Cancel
- - Up 0 Down
- Sign in to reply
- Cancel
- - Cancel
- - Up 0 Down
- Sign in to reply
- Cancel
- - meanSeaLevelPressure returns 98517.5 Pascals (still doesn't match typical calculations, should be 98803.0 Pascals)
- ambientPressure returns 88806.8 Pascals
- altitude returns 890.6 meters [actual altitude at location is 886.5 meters, this is pretty accurate]
- getTemperatureHistory returns 26.7 C
- - Cancel
- - Up 0 Down
- Sign in to reply
- Cancel
- - Cancel
- - Up 0 Down
- Sign in to reply
- Cancel


Great, I have a lot of evidence now. Key findings:

1. From the compatible devices list, fēnix 3/3 HR are API 1.4, fēnix 5/5S/5X/5 Plus/5S Plus/5X Plus are API 3.1/3.3 which supports API 2.4+ features including ambientPressure/rawAmbientPressure.

2. From forums:
- fēnix 5 can read raw pressure and works well for freediving (reports of 40m accuracy)
- fēnix 6/7/8 and Tactix artificially cap pressure readings below ~3m underwater
- fēnix 5 was reported accurate within 0.1m compared to proper dive computer
- fēnix 6 pressure sensor "isn't set up with the range to handle depth pressure"
- Some say fēnix 5 has 10 ATM (100m) water rating but not dive-rated; for snorkeling/freediving to 30m it's physically possible but Garmin doesn't certify it

3. Need to verify water resistance and ANT+ compatibility. Let me search for more specific info about fēnix 5 water resistance and ANT+.

Actually I have enough. Let me also check the official Garmin water resistance docs and maybe verify fēnix 5 Plus/5X specifically support ANT+ (they all do). I should also mention Descent as the proper alternative.

Let me do one more search to verify fēnix 5 water resistance specs.

Question: Garmin fēnix 5 5S 5X water resistance rating 10 ATM 100 meters specifications

Question: Garmin fēnix 5 ANT+ heart rate monitor chest strap compatible HRM-Tri