Fenix 6 Pro Vo2 max with external FC, and other doubts and bugs.

Hello,

I have recently got a Fenix 6 Pro (not Sapphire), updated to 4.20 with Garmin Express

I tried some months ago a F5+ so I know basic funtionally but I did´nt tested it in depth so have some doubts. There are issues I thing are bugs, but correct if me I´m wrong.

I also have a Edge Explore (and have tried a 1030).

I was impressed yesterday about the body battery function. I started today my first run with the F6 pro.

- I configured trail running with "chal" energy mode, it swtich off the onboard FC..., so when started the activiy "FC external sensor" message appears.., but my to my surprise is that on performance widget have no V02 data, it says "please run 10 minutes outdoor with FC enabled".., so from what I understand is that all Vo2 max training metrics only work with the onboard FC sensor??

If I set the energy mode to "normal" I get no message of external FC when start activity, unless I take out the watch from the wrist, so I assume the "auto" mode of the FC only swtiches to external if the watch doesn´t detect pulse on onboard sensor, I´m wrong?

If I´m correct, just now, if you want to get values and V02 max history metrics must use the watch sensor.., don´t work with external FC... correct me if I´m doing something wrong..., I guess the internal sensor works ok, but if you want to ride bike.., wrist position is less then ideal and FC sensor is better option, I guess is a no sense can´t include permormance data when bike, or anytime you want use external FC strap..

Bugs: When setting any activity,settings, routing,, Type of activity if select "automobile" or "motorcycle" maps navigation dont work..,. just how a straight line from A to B.

Same when creating a Course, New course, create a straight line from A to B (don´t know if this worked like this on F5+) but Automobile and motorcycle should work.. I have to select Byke.., but is now way to navigate using highway, have to select byke but that doest allow you to use highway.

Doubt: Altitude graph, I´m not sure how worked on F5+, but Edge units shows you the elevation profile from start to destiny., both navigation or loading a Course, if load a Course the graphic is more precise, and navigation to a POi, less precise but shows you the elevation graph from your point to destiny (on Edge you can even zoom in/out the graph),

F6 pro, now only shows you the graph of a course or activity already loaded, but

if you navigate to a POI, you can even activate Climb Pro, you have detail "climpro" splits, (I guess Climbpro detects it using the .dem map), but the elevation graph shows you elevation detail "behind" you..., but info till destiny, and I guess there is something wrong here... because you have two data numbers (already ascended meters and remaining meters) this work and a loaded course or activity, but no data of remaining meters and no graph to destiny...when navitation.. that works on my very basic and cheap Edge Explore ... so I guess must be a bug or not implement yet... if the F6 can get detailed info when navigating from Climbpro, logical is that unit could give a elevation global elevation graph like the Edge Explore..

Auto climb, I tried it but I only get invert colors..., maybe I´m doing something wrong here, maybe any other one can tell me what this feature should show, and also why "only when not navitating" option is for... I don´t understand the point of this option.

The watch is nice really, but seems it stills needs some soft changes from my point of view.

Please let correct me if I´m wrong on anything, I don´t know if Garmin reads this, I should like they have a look.

thank you in advance.

0 carl.andersson over 5 years ago

8566077 said:
- I configured trail running with "chal" energy mode, it swtich off the onboard FC..., so when started the activiy "FC external sensor" message appears.., but my to my surprise is that on performance widget have no V02 data, it says "please run 10 minutes outdoor with FC enabled".., so from what I understand is that all Vo2 max training metrics only work with the onboard FC sensor??

I can't answer the other parts of your question but you can use external garmin HR (I assume FC means HR?) monitors to get Vo2 max data but only in a running activity. If you select Trail Run as your activity then the watch won't calculate Vo2 max data.

0 8566077 over 5 years ago in reply to carl.andersson

Hello, big thank you, yes FC is HR (languaje mistake, I´m spanish)

Great, I haven´t see that specified on the manual.., or I didn´t see it.

So I guess whats the point of using Trail running profile? sounds I should always use Running profile.., or does mean that should give wrong results because it doesn´t take in account altitude effort?

The other thing I miss is the altitude graph on "navigation", only shows the elevation variations "behind" you while my basic Edge shows you the elevation profile to destiny..

Other bugs, Automobile and motorcyle are not so relevant, but should work

Auto climb seems no work at least for me.

Thank you in advance.

0 carl.andersson over 5 years ago in reply to 8566077

The calculations for running Vo2 max from Firstbeat are based on road running so yes trail running potentially messes with the results which is why it doesn't calculate it.

The other thing that the trail run activity does differently is it will automatically switch to an ascent/descent screen when you're running up or down hills. That might be useful? I don't use it but then I'm not a very fast trail runner.

0 8566077 over 5 years ago in reply to carl.andersson

Thank you, that makes sense, I made my first running today using trail run profile, I switched on Auto-climb but maybe thats why I found auto-climb erratic... since it was because switched to the own altitude screen of the profile..,

I´m not sure if there is any relation between auto-climb or if it´s actually unusefull.

In any case, when considering performance and training history, I assume that not all activities are considered, so only running and bike are mainly considered to metrics, week performance.., load and so on? seem most metrics a related to vo2 max, like performance condition.,

I miss a more explicit explanation on the manual about how diferent activy profiles are taken in account in firstbeats.

I´m most missing is the elevation graph when navigating to a point (Poi, or saved location), no sense a cheap Edge Explore shows you a elevation graph to desnity, but not on the F6 pro,

Thank you a lot.

0 3811409 over 5 years ago in reply to 8566077

Garmin should give spme indication that for what all activities VO2 max won't get calculated. I am mot getting any VO2 max may be because i run trails.. hate this guessing game...things are easier in vivoactive 3 where vo2 max could be calculated on demand

0 8566077 over 5 years ago

Reply myself, today connected the F6 pro, and got a "sensor update", (it said that after instalation,"

I dont know if there were hidden fixes on this "sensor update" but most things are solved magically

- Altitude Graph works when navigating, shows remaining/stimated elevation profile, some times works perfect, other times when the destiny is a climb, it shows after a descending curve (like if were a backtrack calculation), but is ramdom, sometimes, the graph shows perfect and ends on the top.

- Now Automobile en motorcycle works, seems calculate like bike, but works (havent changed anything) so I don´t understand why now works.

- New course on the watch makes a direct line (straight route), but I guess is normal since it has no map asigned to that particular feature.

- Auto climb seems no usable, is jsut invert color on the data screens (if use actual screen on ascend, if you are looking and the map, graph or climbpro nothing occurs, so I´ll switch off seems useless.

Climbpro works but make the wath terribly slow, and freezes for some seconds everytime its calculating.

Just missing to test the Vo2 max soon with external HR strap now using the correct profile "run" instead "trail running" as a forum member suggested, but seems will work.

Thank you garmin, it should be nice to get a better feedback of what is being solved on any updates. I still dont understand how the autmobile option works now.

So if you read this, please, can tell why the altitude graph, now working, sometimes shows the end (when destiny is a top), like a mirror..., ascend to top, then like if were trackback? is something realted to the map? or the position of the location? the dem? othe times works perfectlly even I love that when you navigate and dont´obey the route, when the gps recalculates ,a new graph apperars, I love that.

thank you.