dropouts with Keiser new ‘M connect’ computer introduced mid ‘21 onwards
nealjane opened this issue · comments
newly introduced Keiser computer mid 2021 (upgrade available to users from mid 2021) standard on 2022 us bikes I believe.
dropouts in Power over ant+ seen - (previous ant+ position fine prior to computer upgrade - and even positioned next to watch still saw drops in signal)
this was using power and cadence profile from Gymnasticon over ant+, and speed cadence from the new Keiser computer over bluetooth to fenix 6 - at same time.
As Gymnasticon now provides speed - it’s whether it was the speed connection over Bluetooth from new Keiser computer that causes interference??
(I don’t think I tested it without Keiser speed connected). Def Looks like I need to swap over to my newer computers again to see if problem still persists for newer Keiser M3i computer users.
I’m off work as it’s half term so will try this week.
Removing ic4 profile etc hasn’t helped at all, reading on fb groups others having dropouts using Keiser BLE connection (old m3 BLE) - so it’s looking more like an issue with the new computer rather than gymnasticon. (Although no dropouts seen using the keiser app to connect)
Right, I’ve been testing this for weeks now (on pi zero 1). Tested it with zwift connected to new Keiser computer (M connect) - https://www.keiser.com/lp/m-connect-display
which sends out fitness bike profile over BLE, Gymnasticon connected to Keiser direct BLE connection (standard connection) and sending the ant+ to my Garmin watch.
On pi zero (v1) and it’s working pretty much flawlessly. Changes I made, full apt update gymnasticon Keiser file I set dropout from 2s to 3. Only minor drops seen in image-
Using the same sd card in a pi zero 2 - it’s still dropping out for 30s at a regular intervals -
Tried apt update all and nothing has improved over ant+/Bluetooth.
@chriselsen - any other suggestions to try?? It’s clearly related to pi hardware..Bluetooth upgrade in pi02 is bl4.2..??
The only idea I could come up with is to use a USB extension cable and move the ANT+ stick away from the Pi and its Bluetooth/Wifi antennas.
I usually do that anyways to brink the ANT+ stick closer to the bike handle, where my wrist with the Garmin watch is and have pretty much no connectivity issues with ANT+ that way.
Funnily enough that was the first thing I tried when I saw the issue as I assumed it was interference from the additional Bluetooth. Made no difference unfortunately with a 2m long extension for ant+. Also moved pi away from bike computer etc.
connecting pi and the keiser app to the bike (both using same Keiser direct BLE - and when pi drops to 0 for 30s the app is still working showing correct stats so Keiser computer is definitely still sending data - so it looks like it’s a pi02 issue.