Pairing with POD or sensors
Dear Stuart this is not correct at all. Regarding Bluetooth the Polar H10 can connect simultaneously to too bluetooth devices and ant+. The Wahoo Tickr can connect simultaneously to three bluetooth devices and ant +.
But the problem still is erveytime when i change my bike i have to redo the pairing process.
If i use the Vantage 2 or the Coros Apex you pair once your sensors and then forget it, because it doesn’t matter wich bike i use, the sensors are found.
The device is functioning as designed, a design choice I find to be myopic at best (and down-right annoying the rest of the time).
A little Bluetooth background: Bluetooth, unlike ANT+, is a 1:1 protocol, so a device can only connect to one other device per channel at a time. Most Bluetooth sensors only have one channel (the only one I can think of with two is the Garmin HRM Pro), so a good rule of thumb is if your sensor is connected to one device Bluetooth device, it can’t connect to any other Bluetooth devices. These connections are normally remembered, so if you switch from H10 to Tickr, it is operating as expected to have to re-pair when you want to use the H10. (I go between an H10 for cycling so I can use a bike computer and get HR on both, and the Suunto sensor so I can get HR during swimming.)
@Ze-Stuart is correct, the Suunto watches will only pair to one type of sensor. If you want to use two different power meters on two different bikes you will have to forget and re-pair each time.
Thanks @brad_olwin. I believe see @Dirk-Münster’s confusion: BT sensors are 1:1, but the receiving device (watch, bike computer) can connect to many devices. These connections are still 1:1, ie 1 BT channel on the sensor can connect to one BT channel on the receiver.
If the H10 can connect to two BT devices concurrently, it’s because it has two channels. If the Tickr can connect to 3 devices, it has 3 channels. (I’m simplifying it a bit, but in terms of how we experience BT’s implementation, it’s accurate.) ANT+ is different to BT, and is broadcast (much like TV or a radio station) and can be received by anything in range. The H10 can connect to two concurrent Bluetooth devices, and for the sake of conversation, n+1 ANT+ devices.
A device with multiple channels can get difficult around pairing: let’s say you set it to pair with your watch, and your bike computer over BT. There’s a chance that both devices will pair to the same channel, and then one won’t work (the second one to connect). You’ll then need to unpair and repair the receiver to connect to an actually free channel. This happens because when a channel on the sensor isn’t connected to something it is advertised as being available: unless you pair the second receiver while the first has a connection to the sensor, there’s a 50% chance (or 33.3% for Tickr) that you’ll have to repeat the pairing sequence.
Regarding Polar’s and Coros’ implementation of BT, I don’t have experience of it but there’s no technical reason why the watch can’t remember multiple sensors: Suunto have chosen to implement a maximum of one sensor per type. I’ve never got an answer as to why, but that is a limitation they’ve imposed: I think when they called a watch line ‘Spartan’ they were referring to an elegant, reduced feature set. (I notice the Coros Apex also has ANT+, so it has more flexibility.)
Back in the old days of Movescount, there was support for configuring Bike POD 1, 2 and 3: examining the firmware on a Suunto Spartan a while ago, I found references to multiple bike pods, something I hope will come back one day. I’d also be delighted if the Suunto HR strap had either multiple BT channels, or ANT+ (I think the chip in it is capable, but the functionality is disabled, I imagine due to licensing fees).
There’s another thread that might interest you around a product called CABLE, from North Pole Engineering:
(Search the forum for CABLE, I’m sure it’ll come up.)
@ze-stuart In the old days of MC the multiple bike pods were for the T-series watches or Ambit1/2 I believe. Once the connected Ambit (A3P) was released, ANT connectivity was dropped and only one sensor per type was allowed. This has not changed. BTW, Suunto was the first to use ANT on its T-series, prior to the more general implementation of ANT+. I think I am recalling these correctly but someone can correct me if I am wrong. I still have a bag full of Suunto ANT Pods.
@brad_olwin I hate to correct but the A3P supports multiple bike PODs (source: I just picked my gorgeous blue A3P off the shelf and had a look in the settings).
I’ll hijack this thread by asking how do you troubleshoot suunto bike pod? I just got new one after 5years (I think), because speed sensor was not working (changed batteries and everything). Now the new one started to do the same after five rides? Cadence is ok all the time. I started to think that I threw away old sensor by mistake
@ze-stuart Thanks. I should have looked at mine.
@likarnik here’s what worked for me: https://zulusierra.co/combination-speed-cadence-sensor-troubleshooting/
I’ll add some photos later.
@ze-stuart thank you, I’ll try with wahoo app. But it always works at the beginning and in shows stupid values in the middle of the ride I appreciate your help and am waiting for photos (especially how did you use zip ties )
@likarnik that sounds like the distance between the speed sensor and the wheel magnet is too great; either of the two are moving.
Have you looked up the NPE CABLE sensor thread on this forum? My understanding is that it allows for the best of both worlds: it can take two ANT+ sensors, and bind them into what the Suunto watch believes is a bike POD. This means you can use accelerometer-based sensors that ‘just work’ and your Suunto.
(Photos got rejected by the forum due to size: I’ll put them on my blog post today.)
Blog post updated with photos!
@ze-stuart thanks for the photos, I feel so stupid now, finding those holes for zip ties after so many years I’ll try to find sugru or something similar in my area, thank you!
@likarnik you’re welcome, it’s magical stuff.