ESB ACK packet not received?

RE: ESB ACK packet not received?

Philip — Tue, 31 Jul 2018 11:44:37 GMT

Hi Håkon.

Thanks, yes that works bit better solution than the one I posted earlier to get it working. As you say there is no length byte at the start of the payload.

Thanks for your all your help,

Best Regards

Phil

RE: ESB ACK packet not received?

Håkon Alseth — Tue, 31 Jul 2018 11:31:51 GMT

Hi,

Just wondering, if it was working would both the NRF_ESB_EVENT_TX_SUCCESS and the NRF_ESB_EVENT_RX_RECEIVED events be triggered?

You'll see both.

I tried to replicate your scenario, and since the "length" field is disregarded if you use a static length in nRF24L (nRF24L01+ datasheet, chapter 7.3.3.1), you have to hard-code everything to 32 bytes.

Here's a rev2 that does this: devzone.nordicsemi.com/.../nrf_5F00_esb_5F00_statick_5F00_ack_5F00_32b_5F00_rev2.c

Could you try it and see if it works now?

Again; this is highly experimental and given "as is", it may likely break other configurations of nrf_esb, so it should only be used for your scenario!

Best regards,

Håkon

RE: ESB ACK packet not received?

Philip — Tue, 31 Jul 2018 10:21:21 GMT

It is working now thanks! I had to make a couple of extra changes. I have attached an updated version of the c file.

I have done a few tests watching the returned ACK packet contents, and it seems to be correct. Not sure if this will introduce any other little bugs but seems ok at the moment.

Thanks

Phil

devzone.nordicsemi.com/.../nrf_5F00_esb_5F00_static_5F00_ack_5F00_32bV2.c

RE: ESB ACK packet not received?

Philip — Mon, 30 Jul 2018 14:36:36 GMT

Gave that a try, still no NRF_ESB_EVENT_RX_RECEIVED event being triggered still the NRF_ESB_EVENT_TX_SUCCESS.

Just wondering, if it was working would both the NRF_ESB_EVENT_TX_SUCCESS and the NRF_ESB_EVENT_RX_RECEIVED events be triggered? Or would just the NRF_ESB_EVENT_RX_RECEIVED event be triggered?

RE: ESB ACK packet not received?

Håkon Alseth — Mon, 30 Jul 2018 13:37:25 GMT

Ok, thanks. Just needed to double-check, so that I hadn't misunderstood.

What you need to do in this case is to patch the nrf_esb library to always receive 32 bytes ACK. This would require a bit of work (and likely more testing than actual work?), as this is not a scenario that is covered in nrf_esb. First, you'll need to adjust the radio registers payload length to be 32 bytes in state "NRF_ESB_PROTOCOL_ESB" when receiving an ACK, and then you'll need to always assume that there's an 32 byte ACK payload in order to get the evt NRF_ESB_EVENT_RX_RECEIVED.

Here's a quick mock-up that I have not tested, as I do not have this specific setup (may include side-effects!). Could you test it and see if you receive anything on the reverse-channel (ACK payload) ?

devzone.nordicsemi.com/.../nrf_5F00_esb_5F00_static_5F00_ack_5F00_32b.c

(note: Based on SDK 15, and you'll need to define "ALWAYS_32B_ACK")

Best regards,

Håkon

RE: ESB ACK packet not received?

Philip — Mon, 30 Jul 2018 13:18:17 GMT

Yes we always send 32 bytes back to the transmitter in the ACK. We write 0x00 bytes to pad out to 32 bytes if we don't have 32 bytes to send.

In hindsight using dynamic payload would have been good, but this is now a legacy system so would be good to be able to communicate with it using a nRF52...

Thanks

RE: ESB ACK packet not received?

Håkon Alseth — Mon, 30 Jul 2018 13:14:42 GMT

If I understand correctly, then this is a very unusual configuration.

You have DPL=0, but EN_ACK_PAY=1. For this to work, you always have to send the static payload length (32 bytes) back to the transmitter in the ACK. Could you please confirm your configuration?

RE: ESB ACK packet not received?

Philip — Mon, 30 Jul 2018 13:00:24 GMT

Hi Håkon, thanks for getting back to me.

The nRF24L which is in RX mode is configured with ACK enabled, dynamic payload disabled, and 32 bytes are written to the ACK payload to send i.e. max allowed. It is definitely sending an ACK, as we get two way comms with our other legacy kit (what we are trying to replicate with the nRF52832).

The nRF24L is setup as a legacy system so I haven't changed any settings, and it communicates with other nRF24L set up as TX's ok.

On the nRF24L you don't need to enable dynamic payload length to be able to send ACKs. We are very familiar with those modules. You just setup the expected payload size on the nRF24L you setup as the TX.

Ideally we want to be able to read the ACK payload on the nRF52832 without havn't to change any settings on the old legacy nRF24L.

Best Regards

Phil

RE: ESB ACK packet not received?

Håkon Alseth — Mon, 30 Jul 2018 12:31:27 GMT

Hi,

If your nRF24L radio is configured with static length (and thus; no , you should configure nrf_esb with mode NRF_ESB_PROTOCOL_ESB.

How is your nRF24L radio configured, and how are you setting up the nrf_esb?

Are you actually sending an ACK payload from the nRF24L side? If so, then you have to enable the EN_ACK_PAY (and thus the dynamic payload lengths).

Best regards,

Håkon

RE: ESB ACK packet not received?

Philip — Thu, 26 Jul 2018 06:12:38 GMT

I have just found a few similar cases that suggest a data packed can only be received with the ACK if the protocol is NRF_ESB_PROTOCOL_ESB_DPL rather than NRF_ESB_PROTOCOL_ESB i.e. dynamic payload is on.

So does this mean a legacy nRF24L01+ system set up to use static payloads and as a RX, can't communicate back via ACK to a nRF52832 setup as a TX?

Thanks