-
Notifications
You must be signed in to change notification settings - Fork 55
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
Preconditions for calling myLoRaWAN.SendBuffer()? #209
Comments
matthias-bs
changed the title
Preconditions for calling myLoRaWAN.SendBuffer()
Preconditions for calling myLoRaWAN.SendBuffer()?
Jan 5, 2023
Here is my code. doCfgUplink() is called from the Arduino execution loop if the flag
|
Some more insights - I added checking of GetTxReady() at the beginning and a little debug output:
Resulting in:
The contents of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
My sketch is based on the example simple_sensor_bme280.ino
I am using a modified version of
doUplink(void)
which works just fine.Then I have added a receive callback function named
ReceiveCb
withSetReceiveBufferBufferCb(ReceiveCb)
to handle downlink messages - this works as expected, too.Finally I would like to add another function to call
SendBuffer()
for an uplink of status data (if requested by a command in a downlink message).I have tried a similar approach as in
doUplink()
to check ifSendBuffer()
can be called:The first condition is clear, but I'm not sure how to handle the second one.
Why are there 3 different flags checked in
LMIC.opmode
?What is the difference between this and just calling
GetTxReady()
?With my current trials, I either get no uplink at all (if I compare
LMIC.opmode
as above) or the uplink is reported to have zero payload and an undefined port [how is that possible?] (if I ignoreLMIC.opmode
and just check the status flag ofdoUplink()
).Thanks in advance for your help!
Best regards,
Matthias
The text was updated successfully, but these errors were encountered: