Actually I took that value from the CIQ docs. Apon reading "ANT Message Protocol and Usage Rev 5.1" it seems both the search timeouts should allow 0...255. Have they been restricted to prevent the device waiting too long? Is there a need to protect the programmer from themselves?
Actually I took that value from the CIQ docs. Apon reading "ANT Message Protocol and Usage Rev 5.1" it seems both the search timeouts should allow 0...255. Have they been restricted to prevent the device waiting too long? Is there a need to protect the programmer from themselves?
You are correct, this is to prevent a device from waiting too long.
This is done not to protect programmers from themselves but to protect ANT channels from other channels. It is possible that in the background the watch is tracking a HRM / Bike Power / Footpod sensor that has been pre-paired with the watch to be used during an activity. If at the same time a Connect IQ app is operating a receiving (slave) channel the high priority search timeout of this channel needs to be limited so as to not interfere with any of these other channels (if these channels start searching). It was important to handle a case where a Connect IQ channel would stay in high priority search timeout indefinitely and block any of these other underlying channels that are in use.
This high priority search timeout has been set to 5s to prevent this blocking (this is also the upper bound used in the Android ANT APIs).
