[nRF51422] Continuous scanning mode and transmission data

RE: [nRF51422] Continuous scanning mode and transmission data

Asbjørn — Mon, 03 Nov 2014 11:34:37 GMT

If the VDD_PA pin is always low it means that it is not sending anything. So it sounds like you have a configuration on the nRF51422 side. I would compile the default ant_broadcast_tx example in the SDK and load that into your device to ensure that it actually transmits. If that example works I would start comparing the initialization and sending routine you have with the broadcast example. It must be related to starting the softdevice or enabling the device as a ant master for sending to ANTWare.

RE: [nRF51422] Continuous scanning mode and transmission data

PW — Fri, 31 Oct 2014 10:14:48 GMT

Hello.

BUFFER_SIZE=8. Application is running as I expected, it's stops periodically (1sec) when sending asynchronous frame, and stops when receiving frame from ANTWare. CHIP: N51422QFAAC0, SDK:4.4.2.33551. When ANTWare is configured as Master and sends broadcast, it can receive data from my device. In this case VDD_PA is going high at 200us. When ANTWare is configured in scan mode it doesn't receive any data from my device and VDD_PA is low.

Routine:

sd_ant_broadcast_message_tx(CHANNEL_1, BUFFER_SIZE, tx_frame);

doesn't return any error, but frames are invisible :(.

Best regards, PW

RE: [nRF51422] Continuous scanning mode and transmission data

Asbjørn — Wed, 22 Oct 2014 08:22:23 GMT

What's the value of BUFFER_SIZE? Is it set to 8? If you debug the application, is it running as you expect it to be or is it held up before it's actually getting to the send routine? Which version of the chip, S210 Softdevice and SDK are you using?

You might want to try and set the different channel_id values to 0 on ANTWare to make sure you set them to wild card and that ANTWare is searching for any channel id values.

If you have an oscilloscope available I would check the the VDD_PA pin on the nRF51422. This pins should go up to 1.8 V during the actual TX event, so you should see a repeating pulse on the pin of the example is running as expected.