I am not familiar with the txStandBy() function but I note that the library says "This is not required if auto-ack is enabled."
I tried without txStandBy() - nothing changed. As I said previously txStandBy/writeBlocking/writeFast described without details, with low-level comments (do not keep tx-stand-by- I mode more than 40 ms...). So it is hard to understand how it is intended to work.
Blocking the Arduino with other code for 500 millisecs is very long.
Agree, but it is just example, and changing this timeframe does not influence on the issue.
Because writeBlocking (based on documentation) was designed for "big data" send. Sure, in my case can be implemented approach when each next log entry requested separately from master side. But what if we will need pass huge set of data? For instance some picture or even video? Requesting separately each 32 byte of information will lead to very slow data transmition speed.
So finally, we can implement some workaround:
Detect false-positive request and perform new attempt (as was implemented by me, see previous posts attachments);
Implement "ping-pong" approach - request each next 32 bytes separately, as was suggested by Robin2;
Implement functionality with using AckPayload mode. This mode intended to be used for sensors polling, but I assume that in some cases it can be applicable.
But I'm interesting how to pass "big data"? One of my future project is to pass remotely pictures - kind of security system.
Going to look through existing issues in RF24 library and probably create new one.
This is my same problem
Just to confirm - my modules powered by 3.3V too. I even tried to replace them with another modules.