When using payload ack, the ack replied by the receiving end lags 4 times

Question

When using payload ack, the ack replied by the receiving end lags 4 times

camerakang opened this issue 3 months ago · 10 comments

camerakang commented 3 months ago

What radio module do you use?

nRF24L01+

What driver board(s) do you use?

esp32-s3-devkitc-1

If using Linux, what OS are you using?

No response

If using Linux, what RF24 driver did you select?

None

Describe your problem

I want the payload ack on the receiving end to reply to the last received data at any time other than the first communication, but now I'm finding that I can't receive the ack four frames ago until after my sender has sent it multiple times

What is the RX code?

https://github.com/camerakang/Nrf24_demo_send

What is the TX code?

https://github.com/camerakang/Nrf24_demo_rev

Answer 1 · 2024-09-19T03:48:41.000Z

camerakang commented 3 months ago

Answer 2 · 2024-09-19T03:54:53.000Z

RF24::stopListening() will flush the TX FIFO when ack payloads are enabled.

Answer 3 · 2024-09-19T04:03:19.000Z

If you're sending ACK payloads to multiple devices/pipes, then (I think) the RX device will only transmit the ACK payload in the TX FIFO's top level (first ACK payload queued) when the payload is received on the pipe intended for the ACK payload.

Answer 4 · 2024-09-19T04:03:51.000Z

Its kind of hard to follow everything your code is doing.

Answer 5 · 2024-09-19T04:05:15.000Z

Tip

RF24::writeAckPayload() returns a bool to tell you if the payload was uploaded into the TX FIFO.

Answer 6 · 2024-09-19T04:10:24.000Z

Have you run our AcknowledgementPayload example? It should demonstrate expected behavior to verify your radio is working correctly.

Answer 7 · 2024-09-19T04:16:17.000Z

        if (ackPayload != NULL && ackSize > 0)
        {
            // ackPayload->counter = result.data[2];
            Serial.print(ackPayload->message);
            Serial.println(ackPayload->counter);

            radio.writeAckPayload(result.pipe, ackPayload, ackSize);
        }

Are you sure ackPayload is never null? This seems pretty clear that the ACK payload will not be uploaded to TX FIFO if this condition is not satisfied.

Answer 8 · 2024-09-19T04:18:53.000Z

Honestly, this seems like question for Arduino Forums (or PlatformIO forums). I don't think this is a library bug.

Answer 9 · 2024-09-19T10:02:20.000Z

        if (ackPayload != NULL && ackSize > 0)
        {
            // ackPayload->counter = result.data[2];
            Serial.print(ackPayload->message);
            Serial.println(ackPayload->counter);

            radio.writeAckPayload(result.pipe, ackPayload, ackSize);
        }

你确定ackPayload永远不会为空吗？这似乎很清楚，如果不满足此条件，ACK 有效负载将不会上传到 TX FIFO。

Thank you very much for your reply, I re-read the example about paylod ack and the problem is solved. But I have a problem with setting the channel, I'm modifying the channel using the " radio.setChannel()" function and after the modification I'm printing the current channel via radio.getChannel(), I'm sure that the sender and the receiver are modifying to the same channel but I can't send successfully after the modification. Looking forward to your reply

Answer 10 · 2024-09-19T11:33:27.000Z

Its best to call setChannel() while not listening. If the antenna is being used, the radio has trouble tuning it to the specified frequency.

radio.stopListening(); // this will flush TX FIFO if ACK payloads enabled
// radio is now in an inactive TX mode.
radio.setChannel(87);
radio.startListening(); // resume RX behavior