My work will stay free of course, but if you would like to donate and support me: https://www.paypal.me/FlipStone</p><p></p><p>(I was an idiot and actually had a wrong paypal link here before, fixed now :/ )</p><p></p><p>-----------------</p><p></p><p>This datafield is largely the same as:</p><p></p><p>BSXInsight Datafield:</p><p>https://apps.garmin.com/en-US/apps/3e33449b-db56-40d3-b512-b74bfe78e9ee</p>
-1.71 Attempt so many to fix crash/writing fit values</p><p></p><p>-1.7 Added more supported devices</p><p></p><p>-1.6 Possible fix for issue where tHb values were rounded resulting in weird graphs...</p><p></p><p>-1.5</p><p>Force writing to fit files by removing memory restrictions causing it to not write to fit on 'older' devices (might cause undesirable side effects though, hard to predict... please let me know!)</p>
이 앱은 다음에 대한 액세스 권한이 필요합니다.
Tearl B.
2018년 4월 20일 |
버전 1.1-upd
The app wks fine in start / stopping & displaying the BSX Insight SmO2 & tHb data on my Garmin 1000. However, in reviewing the data within Garmin Connect, there are a few problems. 1. The Connect IQ SmO2 chart is NOT displayed as a % but, rather in g/dl. The graph y axis goes up to 2000. Having a value of 1,324 g/dl (for example) doesn't offer much value. 2. The Connect IQ tHb chart is NOT displayed in g/dl but, rather as a %. The graph y axis goes up to 1000. Having a value of 715.0 % (for example) doesn't offer any value. Could it be that the code was inadvertently written backwards w/ respect to the graphical displays within Garmin Connect? These were the values displayed (Garmin Connect) on a recent cycling activity: 1,337.00 g/dl SmO2 716.0 % tHb Please advise. Thanks.
개발자 회신
2018년 4월 21일,
FlipStone
The labels were swappped and the values stored in the fit file were multiplied by 100 (tHb) and 10 (SmO2). Just released a version fixing the labels and allowing you to choose to save the actual tHb and SmO2 values in the .fit file (only works for future activities, not past ones)