Linux ANT+ Heart Rate recording stability.

45 views
Skip to first unread message

Pierre P

unread,
May 14, 2026, 7:24:03 AM (yesterday) May 14
to golden-cheetah-users

My config :

  • GoldenCheetah 3.7.1
  • Linux Mint Cinnamon 22.3
  • 2 connected devices : 
    • bike CardioStrong BX70i (via BLE) + 
    • Polar H10 via ANT+ using a dongle « Bus 003 Device 040: ID 0fcf:1008 Dynastream Innovations, Inc. ANTUSB2 Stick »

My problem : Heart Rate recording stability.

Instead of continuous recording, i have some line segments and sometimes some "stairs steps"


Last week was almost ok, a few segment a bit more on one day

This week :

  • monday almost no segments,
  • tuesday more segment at beginning and end of the training
  • yesterday : many stairs
  • today : almost only stairs steps, and total flat (stoped?) after about 12 minutes. 

I check the usb journal, no events so it looks like it’s a problem with GC and the sensor management.

Already checked : 
  • The H10 is ok (I see it perfect on the bike), battery full.
  • linux userid permission to use your usb device has been set
  • I disabled power management for the dongle (control on + autosuspend -1 rule)

Other info : last reboot past saturday, I didn’t close GC since I ran it on monday (just disconnect after training and reconnect the following day for the next training).

Any probable cause ?
What should I do to help identify the problem ?

Thanks in advance


Ale Martinez

unread,
May 14, 2026, 9:36:45 AM (yesterday) May 14
to golden-cheetah-users
Electromagnetic interference, ANT+ is a connectionless protocol so when there is interference data is lost silently, using BTLE you would likely see dropped connections, and reconnections if you are using recent GoldenCheetah builds.


What should I do to help identify the problem ?


Pierre P

unread,
May 14, 2026, 4:27:51 PM (yesterday) May 14
to golden-cheetah-users
Thanks again Ale
what's very strange is that it's not every day the same, and when I was with windows I didn't notice any interference...
I'll probably have to try with a cable.
But if interference is the explanation, i still can't explain why it can vary so much from one day to another.

I just tested with --debug option (and with computer wifi off) :
[18:23:27.913] debug: 0 ANT SENSOR ID  120  DETECTED VIA CHANNEL ID EVENT
[18:23:27.928] debug: ** CONNECTION ESTABLISHED channel: 0 device: 5794 **
[18:23:30.130] debug: stale info for channel 0
[18:23:40.767] debug: start...
[18:31:24.135] debug: lost info for channel 0
[18:31:24.135] debug: 0 type= 1 device type= 120 freq= 57
[18:31:24.135] debug: 0 assign channel type RX
[18:31:24.136] debug: 0 assign channel type RX
[18:38:02.879] debug: lost info for channel 0
[18:38:02.880] debug: 0 type= 1 device type= 120 freq= 57
[18:38:02.883] debug: 0 assign channel type RX
[18:38:02.884] debug: 0 assign channel type RX
[18:38:32.874] debug: lost info for channel 0
[18:38:32.875] debug: 0 type= 1 device type= 120 freq= 57
[18:38:32.875] debug: 0 assign channel type RX
[18:38:32.876] debug: 0 assign channel type RX
[18:39:02.876] debug: lost info for channel 0
[18:39:02.877] debug: 0 type= 1 device type= 120 freq= 57
[18:39:02.877] debug: 0 assign channel type RX
[18:39:02.878] debug: 0 assign channel type RX
[18:39:32.878] debug: lost info for channel 0
[18:39:32.878] debug: 0 type= 1 device type= 120 freq= 57
[18:39:32.879] debug: 0 assign channel type RX
[18:39:32.879] debug: 0 assign channel type RX
[18:40:02.879] debug: lost info for channel 0
[18:40:02.880] debug: 0 type= 1 device type= 120 freq= 57
[18:40:02.880] debug: 0 assign channel type RX
[18:40:02.881] debug: 0 assign channel type RX
[18:40:32.871] debug: lost info for channel 0
[18:40:32.872] debug: 0 type= 1 device type= 120 freq= 57
[18:40:32.875] debug: 0 assign channel type RX
[18:40:32.875] debug: 0 assign channel type RX
[18:41:02.625] debug: lost info for channel 0
[18:41:02.625] debug: 0 type= 1 device type= 120 freq= 57
[18:41:02.626] debug: 0 assign channel type RX
[18:41:02.626] debug: 0 assign channel type RX
[18:41:32.126] debug: 0 type= 1 device type= 120 freq= 57
[18:41:32.126] debug: 0 assign channel type RX

Fisrt 7-8 minutes ok (bike wasn't on)
Then i powered the bike and run it (but without connecting it) and it looks that it is when powered that info is lost every 30 seconds, weird isn't it ?
But do you think it confirms the interference probable cause ?

Thanks again

Ale Martinez

unread,
May 14, 2026, 10:12:36 PM (21 hours ago) May 14
to golden-cheetah-users
El jueves, 14 de mayo de 2026 a la(s) 5:27:51 p.m. UTC-3, Pierre P escribió:
Thanks again Ale
what's very strange is that it's not every day the same, and when I was with windows I didn't notice any interference...
I'll probably have to try with a cable.

An extension cable is a good idea, new batteries for the H10 too.
Not really.
 
But do you think it confirms the interference probable cause ?

Pretty much, yes.

Pierre P

unread,
4:49 PM (2 hours ago) 4:49 PM
to golden-che...@googlegroups.com
Thanks again, 
I did a reboot last night, this morning, with a 30cm extension cable (the only I had) it worked.
I checked the battery and change it two weeks ago it still almost 100%
Fingers crossed, i hope the cable will do the trick (and maybe I buy a longer one)

--
_______________________________________________
Golden-Cheetah-Users mailing list
golden-che...@googlegroups.com
http://groups.google.com/group/golden-cheetah-users?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "golden-cheetah-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golden-cheetah-users/B9c2ZfjN-QU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golden-cheetah-u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/golden-cheetah-users/a848252f-df4b-4516-8e3d-10584a683a95n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages