-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
write
, writeFast
and writeBlocking
methods confusions
#816
Comments
The main difference between the normal The normal write will block until a payload is sent and an ack is received, (when auto-ack is enabled) then go back to standby mode. The This can be demonstrated by using the The Hope that makes sense... |
Since TMRh20 discussed the applicable differences, I'll just focus on the questions posed.
|
@flexphperia I'll be closing this issue if there is no more activity over the next month. If you would like to add clarity to the docs, we would welcome a PR that might better explain the differences from a user's perspective. It is a common problem when writing docs that they can inadvertently assume too much of the user's understanding. |
Yes, this information was helpful. My understanding of these methods was not good. Unfortunately, I will not help with PR, but you may want to add a link to this thread in the documentation. |
I am trying to understand the
write
,writeFast
andwriteBlocking
methods but I need some answers:1.
writeFast
andwriteBlocking
methods have in the code:So their main operation takes place when the TX FIFO is full (it has 3 payloads in queue). But I can use
writeFast
function like this and it works:I don't call
writeFast
3 times and it works.Although there is an example that calls it 3 times in the documentation for the
txStandby
function:2. Why do I have to call the
txStandBy
method after callingwriteBlocking
- after allwriteBlocking
method itself has a timeout?Maybe someone could explain more precisely what these 3 methods differ and when to use them:
write
,writeFast
,wirteBlocking
?The text was updated successfully, but these errors were encountered: