GPS-Sport ForenRun.GPS GeneralConvert Zephyr r-r hr-data.dat to BPM
Bitte einloggen, um neue Kommentare zu erstellen Foren durchsuchen
Erste Seite<Seite1von2>Letzte Seite
Tom 22.05.2012 08:06:23 UTC



We have found a bug regarding hr-data.dat file: the app cuts all heart beat durations below 400 ms.
We'll fix this bug in the next release, which should be on Market soon.
peakbagger66 24.02.2012 16:36:22 UTC



I have seen this behaviour - but if the last heart rate observed is 160 followed by a bunch of errors, wouldn't it log the r-r of 375 to the hr-data.dat file? There are no values lower than 400 ms even when bpm >150 has been observed consistently. I will live with it until I can test with another phone.
admin 24.02.2012 09:14:23 UTC



If Run.GPS encounters an error/missing heart rate, it will show the last heart rate reading on the screen, but log the error in the file. This could explain the behaviour.

Also, the heart rate is slightly smoothed (averaged) for display.

Probably this is also the case for fuzzy monkey: erroneous readings are ignored, the heart rate remains unchanged.
peakbagger66 24.02.2012 06:54:35 UTC geändert am 24.02.2012 07:00:56 UTC



Yes, I had thought that too, so early on in troubleshooting made sure to clean the strap and use some gel to improve contact. The thing is, is that run.gps reports the heart rate correctly, it just doesn't record it correctly (any r-r value less than 400 is not recorded to the hr-data.dat file)
Today I tested it again and compared to another application (fuzzy monkey's app). During this time run.gps reported my hr at 148 to 156. This is an excerpt from the hr-data.dat:


3207695 600
3208099 404
3208503 404
3208907 404
3209311 404
3209707 0
3210119 412
3210527 408
3210931 404
3211331 400
3211735 404
3212139 404
3212543 404
3212931 0
3213299 0
3213715 416
3214135 420
3214387 0
3214739 0
3215107 0
3215357 0
3215753 0
3216149 0
3216485 0
3216945 460
3217329 0
3217645 0
3218145 500
3218537 0
3218937 400
3219333 0
3219725 0
3220121 0
3220517 0
3220897 0
3221285 0

I then stopped run.gps and started fuzzy monkey's 'Heart Rate Monitor For Android'. These are the results (excerpted):


1330053983769.00 154
1330053984507.00 154
1330053985614.00 154
1330053986727.00 154
1330053987465.00 154
1330053988577.00 154
1330053989709.00 153
1330053990808.00 153
1330053991546.00 153
1330053992673.00 153
1330053993757.00 153
1330053994496.00 153
1330053995611.00 154
1330053997085.00 154
1330053997456.00 154
1330053998570.00 154
1330053999687.00 154
1330054000789.00 154
1330054001531.00 154
1330054002645.00 154
1330054003759.00 154
1330054004488.00 154
1330054005597.00 155
1330054006706.00 156
1330054007448.00 157
1330054008561.00 158
1330054009673.00 158
1330054011144.00 158
1330054011516.00 158
1330054012628.00 158
1330054013753.00 158
1330054014477.00 158
1330054015586.00 158
1330054016699.00 158
1330054017436.00 158
1330054018551.00 158
1330054019668.00 158
1330054020766.00 158
1330054021507.00 158

You can see it is consistently over 150. So it is recording correctly. Since no one has complained I can only assume that it is something to do with this specific phone and run.gps, unless someone can replicate the problem with a different zephyr and phone.
admin 23.02.2012 11:20:39 UTC



The data look to me as if the Zephyr had a problem with the electrodes because there are so many errors. You could try cleaning the contacts or making the electrodes wetter or maybe using electrode gel.

peakbagger66 23.02.2012 05:55:53 UTC



Well, the phone was brought back to factory spec - clean. Installed run.gps from the market and paired with the Zephyr. The results are still the same. Totally clueless now. Can live with it for endurance zone training but once we start into the higher hr zone stuff we are unfortunately going to have to find another solution. Too bad because this is a really nice app and we'd like to use it through the whole training cycle (plus it cost a mint, relatively speaking).

Since no one else is complaining about it, I am going to have to chalk it up to the phone. Curious to see if it works ok when the phone is upgraded.
peakbagger66 17.02.2012 05:40:22 UTC



OK, we were indeed using an old version 2.3.9 build 2326. We updated the app to 2.3.9n build 2415. Phone is Samsung Captivate running 2.3.3.

The data is still the same - no values under 400 appear. Do we need to do a complete uninstall/reinstall maybe? I still see the older version on the phone as a separate application. Odd..shouldn't it overwrite the old or something?
admin 16.02.2012 09:00:11 UTC



Thing is, the data look horrible. There should be only a few zeros in the second column, as the zeros are basically errors.

So I need some information about the system you are using:
- which phone?
- which OS version?
- which Run.GPS software release?

This *could* happen because you're using an old version of Run.GPS. I remember there was a bug in the Zephyr's driver a long time ago that may produce this problem.

Thanks,
Admin
peakbagger66 16.02.2012 05:56:58 UTC geändert am 16.02.2012 05:58:07 UTC



This is from a session where no observed bpms were under 150 bpm. We made sure to start recording when the heart rate was over 150. I added a third column to show time. I think what is happening is that if they are 400 or less they get written out as zeroes.


40217 0 0:00:40
40605 0 0:00:41
40989 0 0:00:41
41373 0 0:00:41
41757 0 0:00:42
42121 0 0:00:42
42529 408 0:00:43
42913 0 0:00:43
43297 0 0:00:43
43677 0 0:00:44
44061 0 0:00:44
44445 0 0:00:44
44829 0 0:00:45
45209 0 0:00:45
45589 0 0:00:46
45973 0 0:00:46
46353 0 0:00:46
46733 0 0:00:47
47117 0 0:00:47
47497 0 0:00:47
47877 0 0:00:48
48253 0 0:00:48
48633 0 0:00:49
49393 760 0:00:49
Tom 15.02.2012 10:19:48 UTC



Are there any values below 400 in the second column of the file (interval duration)? 400 ms interval duration = 150 bpm

Can you post an excerpt of the file showing high heart rates?

Erste Seite<Seite1von2>Letzte Seite
© 2024 | Impressum | Allgemeine Geschäftsbedingungen | Nutzungsbedigungen | Datenschutzerklärung | Widerruf und Rücksendung | Batterieentsorgung