This has thankfully been fixed if you use ErgData because it now has a stroke counter and that number is recorded in your LogBook allowing you to work out your average rating to as many decimal places as you want.Įven 1spm difference, especially if you rating under 20spm makes a huge difference in your heartrate, its like 4 or 5bpm average increase for me dropping from 19spm to 18spm for the same distance covered over a 30 minute row which kind of makes what looks like a 1bpm " HR Error" look kind of irrelevant. The only reason you would want an accurate HR is to do comparisons against previous rows of identical distances and times and until ErgData came along this was pretty much impossible because of the average rating error of rounding down in the monitor. Its actually the least of the problems in the results, the biggest problem for years has been the average stroke rate, its way out. Not quite sure why all of a sudden the HR is a problem in the results for some people. It's not the average HR, but the HR at the end of each split. The rest of the data seems to be spot on. Has anybody else ever noticed this? It looks as if the C2 does log everything correctly but somehow it misrepresents the avg hr. It actually turns out my avg HR was like this.
INTERVAL DATA CONCEPT2 LOGBOOK DOWNLOAD
So I decided to download the log in a CSV and do some Excel magic. Especially on the first interval I remembered I never saw anything above 135 and mainly hovered around the 130 mark. HR for the first interval was 135, second interval 135 and third interval was 138. If you look at the 3x30 minute steady state training in the link below you can see what I mean. HR as displayed on the concept 2 log isn't accurate. If you have any questions or feedback, please contact us.Since I am doing more and more steady state work I am paying close attention to my heartrate. The next release of the Concept2 Utility will have no limitation on when results can be uploaded. Uploading via the Concept2 Utility-The current release of the Concept2 Utility will only upload results for the logbook and ranking season in which the results were completed, so after April 30, you will not be able to upload results done prior to the 2017 Logbook and Ranking Year. The next release of ErgData for Android, in Beta development and due out soon, will have no limitation on when results can be synced.
INTERVAL DATA CONCEPT2 LOGBOOK FOR ANDROID
Uploading via ErgData Android-The current production release of ErgData for Android will only sync/upload results for the logbook and ranking season in which the results were completed, so after April 30, you will not be able to sync results done prior to the 2017 Logbook and Ranking Year. Results completed outside of the current season can be synced/uploaded. Uploading via ErgData iOS-There is no limitation on when results can be synced/uploaded. Results completed outside of the current season can be entered. Starting May 8, the Rankings will only accept results for the 2016/2017 Season.Įntering/Uploading Meters into the LogbookĮntering manually-There is no limitation on when results can be entered. You have until the end of May 7 GMT to manually rank or unrank any pieces for the 2015/2016 Season (to April 30, 2016). We’re working on lots of new features for the upcoming season, including better social media integration, heart rate information, training partner changes and more! Your lifetime meters get carried forward to the new logbook year. On May 1, the previous 12 months of data will be archived on your History page in the 2015/2016 Season, and a new 2016/2017 logbook and ranking year will begin. The 2016/2017 Logbook and Ranking Season begins May 1 and will cover meters rowed or skied from to April 30, 2017. May 1 Begins a New Logbook and Ranking Season! April 22, 2016 May 1 Begins a New Logbook and Ranking Season!.Integrating With Other Fitness Platforms.
0 kommentar(er)
