ANT Forum

In my app, I'm want to support combined bike speed and cadence
devices but when I try to connect to a combined bike speed and
cadence device via the AntPlusBikeCadencePcc.requestAccess(...)
and AntPlusBikeSpeedDistancePcc.requestAccess(...) the following
problem appears.

After initializing, I request access to the cadence sensor via
AntPlusBikeCadencePcc.requestAccess(mContext, deviceNumber, 0, combinedSensor, new MyResultReceiver<AntPlusBikeCadencePcc>(), new MyDeviceStateChangeReceiver());
and similarly for the speedAndDistance data.

After some time (when the device is found), the method
MyResultReceiver<AntPlusBikeCadencePcc>.onResultReceived(...) is
called (with resultCode=SUCCESS, initialDeviceState=TRACKING).
Within this method, I subscribe for the new cadence data via
cadencePcc.subscribeCalculatedCadenceEvent(new
ICalculatedCadenceReceiver() {...}); Unfortunately, when doing
so, I find the following error in the LogCat: Tag:AntPluginPcc,
Text: BBD20000: Subscribing to event 301 failed with code -3

When subscribing to other Events, I get the same error message
but with other event codes.

Interestingly, the same code works well for a stand alon cadence sensors, i.e, when combinedSensor==false.

I have the same problem with the AntPlusBikeSpeedDistancePcc.requestAccess(...).

To be more precise, the AntPlusBikeCadencePcc.requestAccess(...)
and AntPlusBikeSpeedDistancePcc.requestAccess(...) are called
shortly afterwards. I also observed that only one of these
searches becomes successfull, the other ends with a
SEARCH_TIMEOUT.
     

Thanks for helping me with this problem.

Unfortunately, I am currently not in front of the code, so the
following answers are based on my memory of some previous tests.
As soon as I get back to the code, I will do some more tests and
give more precise answers.

I observed this problem only when connecting to a combined biek
speed and cadence sensor. As already stated it also appears with
the AntPlusBikeSpeedDistancePcc.requestAccess(...) call.

I also thought, the problem might be related to parallel
searches. So I limited the search to the combined device
only (still AntPlusBikeSpeedDistancePcc.requestAccess(...) and
AntPlusBikeCadencePcc.requestAccess(...) shortly after each
other. Unfortunately, I don't know the order) but this did not
help.
I once also limited to only one requestAccess(...) call (but do
not remember which one it was) but this did not solve the problem.

As already stated, I get the same error also for the subscription
to the other Events like subscribeBatteryStatusEvent(...),
subscribeManufacturerIdentificationEvent(...),
subscribeProductInformationEvent(...) but with other numbers.


The deviceNumber is found by an AsynScan, where
AntPlusBikeSpdCadCommonPcc.BikeSpdCadAsyncScanResultDeviceInfo.isSpdAndCadComboSensor
is checked and then stored in a database. When searching for
devices, I get the deviceNumber from this database.


I hope, these answers help you to find the problem. As soon as I
am back on the code, I can do some more tests to get more precise
ansers.      

Now, I did a test where I only search for one device at each
time. More precisely, only for the cadence or speed part of the
combined speed and cadence device.


I get the problem when I only search for the cadence part, i.e., via
AntPlusBikeCadencePcc.requestAccess(context, deviceNumber, 0, true, new MyResultReceiver<AntPlusBikeCadencePcc>(), new MyDeviceStateChangeReceiver());
Thereby, I observe the following problems:
When calling subscribeCumulativeOperatingTimeEvent(), I get BBD20000: Subscribing to event 204 failed with code -3.
When calling subscribeManufacturerAndSerialEvent(), I get BBD20000: Subscribing to event 205 failed with code -3.
When calling subscribeVersionAndModelEvent(), I get BBD20000: Subscribing to event 206 failed with code -3.

Interestingly, when only searching for the speed part, i.e., via
AntPlusBikeSpeedDistancePcc.requestAccess(context, deviceNumber, 0, true, new MyResultReceiver<AntPlusBikeSpeedDistancePcc>(), new MyDeviceStateChangeReceiver());
there are no problems with the subscribeCalculatedSpeedEvent() and subscribeCalculatedAccumulatedDistanceEvent() calls.

However, for the other calls, I get:
When calling subscribeCumulativeOperatingTimeEvent(), I get BBD20000: Subscribing to event 204 failed with code -3.
When calling subscribeManufacturerAndSerialEvent(), I get BBD20000: Subscribing to event 205 failed with code -3.
When calling subscribeVersionAndModelEvent(), I get BBD20000: Subscribing to event 206 failed with code -3.

     

Oh, In my previous post, I oversaw that calling
subscribeCalculatedCadenceEvent() now works. However, I still
get the messages for the other subscriptions.
     

Now, I did one more test/experiment.
When searching for both parts, the order seems to be relevant.

When first searching for the speed and then for the cadence part,
the speed part is indeed first found and I get for the calls of
the speed part:
subscribeCalculatedSpeedEvent => BBD20000: Subscribing to event 201 failed with code -3
subscribeCalculatedAccumulatedDistanceEvent => BBD20000: Subscribing to event 202 failed with code -3
subscribeCumulativeOperatingTimeEvent => BBD20000: Subscribing to event 204 failed with code -3
subscribeManufacturerAndSerialEvent => BBD20000: Subscribing to event 205 failed with code -3
subscribeVersionAndModelEvent => BBD20000: Subscribing to event 206 failed with code -3

The search for the cadence part ends with resultCode=SEARCH_TIMEOUT, initialDeviceState=DEAD


When first searching for the cadence and then for the speed part,
the cadence part is indeed first found and I get for the calls of
the cadende part:
subscribeCalculatedCadenceEvent() => BBD20000: Subscribing to event 301 failed with code -3
subscribeCumulativeOperatingTimeEvent() => BBD20000: Subscribing to event 204 failed with code -3
subscribeManufacturerAndSerialEvent() => BBD20000: Subscribing to event 205 failed with code -3
subscribeVersionAndModelEvent() => BBD20000: Subscribing to event 206 failed with code -3

The search for the speed part ends with resultCode=SEARCH_TIMEOUT, initialDeviceState=DEAD


Hope that helps.      

Ok, I now search for one part after the other and everything works as it should.
So thanks for your help.