I've returned my previous device and got a new one .. which works great!
to be on the safe side I tighten the belt a bit more so it doesn't move when I fully breathe in and out.
I wet the belt contacts just a little bit and it suffices.
I think that the HxM is not producing good enough results on a regular basis. I used to have a kind of sure way to get good results, but recently I am struggling to get a whole workout (1h) of correct data. Like other posters mentioned, any unusual movement or breathing makes the values to become completely incorrect. It cannot be that the users have to spend so much effort to get reasonable readings. I have a Polar and no matter how I wear it, it does produce good values consitently for the entire workout. With the HxM I was hoping to combine the heartrate reading in the workout data, but as I use it mostly to control my running and I can attach my polar watch on the running buggy I will now stop using the HxM. BTW, I reported the problems to Zephyr and even got a replacement at some point, but this is also not working well so now I just have enough.
Question: Does anybody know how well the FWRD works with RunGPS?
@Lee_Nover: Zephyr answer was that the heartrate algorithm calculation was being fooled by ECG noise from the sensor.
from your new findings it looks like the ECG noise is mostly due to the contacts, very interesting. I'am waiting on your investigation.
Did a bit more testing and got more information.
If I wet my fingers and hold the knobs of the device (not the belt) then I get good HR detection. If I move my hands a bit, the reading gets weird again. So it really depends on the contact.
Using the belt sometimes gets too good a contact and the device measures all the peaks as R and this quadruples the HR - which can be seen from the values I get. If I move the belt a bit lower then the reading is better, but it's also more sensitive to movements, meaning that a slight movement, even breathing deeply, corrupts the readouts. I've also tried with saline (water+salt) to make it really conductive, but that doesn't change results. I'm going to try with some electrode gel with belt and also with some electrodes.
So it seems the device works fine, it's just the contacts are really bad.
@Lee_Nover:
for me the situation is getting better, using the RR to calculate heartrate and my filtering it is fine (I compare it to my Garmin edge 305 heartrate monitor and it is very close), and using my correction factor mechanism I have distances which are very close to the reality (around 1-2% error).
anybody else's situation getting worse and worse? or maybe any improvements?
I've got the "SDK" but it doesn't seem it will help with anything if the received data is total rubbish.
I'm planning on making a proxy that would take in the data from HxM, correct it and send it out on another port, so RunGPS can connect to that port and get the corrected data. but that's only if I can get some useful data to work with. otherwise I'm returning it .. or throwing it away..
@Keuters: you can only charge up the battery 300 times roughly,
this is a question to be asked to zephyr but I believe at best you would have to send the HxM to Zephyr and get a new one. because the HxM cannot be open to change the battery just like that, it's sealed.
but with 300 charging you have 300X26 hours=7800 hours of usage so a lot of years of usage, I don't think you will need to change it in your lifetime except if you do alot of 24h training.
@rouven: Thanks for the message but my question was perhaps incorrectly expressed. I meant what happens if the battery needs replacing. If the device is then unusable.
12.01.2010 19:09:52 UTCgeändert am 12.01.2010 19:22:30 UTC
Hi Lee_Nover,
your training logs are very bad!
But you have the same issue?
You never (less than now) got any problem and now in every log?
I washed my belt too, but no better results.
But as in my test, the problem is not a problem with the belt.
(I checked it with electrodes..so there was no use of the belt)
Zephyr got mail from us, so we need to wait an see what they telling are us.