RF51822 packet loss can't recover

RE: RF51822 packet loss can't recover

Hung Bui — Wed, 30 Nov 2016 09:27:34 GMT

Please focus on the topic in the question. If you have other questions, open another case.

RE: RF51822 packet loss can't recover

D-Nordic — Wed, 30 Nov 2016 01:22:23 GMT

I want to send the packet with 1ms space, and don't want to use delay(nrf_delay_ms(1)) because if so mcu can't do other things, can I use timer? How to use timer in RF51822.

Another question: From the SDK sample, we can config 125 channels, but what's the corresponding frequency?

RE: RF51822 packet loss can't recover

Hung Bui — Tue, 29 Nov 2016 11:51:08 GMT

I assume you find packet loss by checking on the RX side ? since it's always success on TX side.

Note that there could be interference from other devices, such as wifi, you should try to test with different channels.

Please try to test with the default example in the SDK and let us know if you observe the same thing. In addition, please send your schematic and layout of your boards.

RE: RF51822 packet loss can't recover

D-Nordic — Tue, 29 Nov 2016 11:39:55 GMT

SDK version is nRF5_SDK_11.0.0_89a8197

Yes, i want the channel to be fully used by TX->RX, so don't expect ACK, and the receiver will discard the useless packet.

Another question is sometimes the received data are all zero.

RE: RF51822 packet loss can't recover

Hung Bui — Fri, 25 Nov 2016 12:21:37 GMT

Could you let me know which SDK version you are using ? If you use selective ACK and set noack= true, I don't think you will receive NRF_ESB_EVENT_TX_FAILED. With uESB we will already return NRF_ESB_EVENT_TX_SUCCESS if there is no ACK required. It's pretty straight forward, if you don't expect ACK how could you know the packet will be success or not ? You will always assume the packet is successfully transmitted.