You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The application is built with the following command:
$ make sx1261
The cloud application replies to every uplink message with a one-byte message containing a counter incremented for each received uplink message.
The blue button is pushed periodically at a frequency of around 2 pushes per second.
Symptom
For some messages, the application is not immediately informed of the reception of a downlink message. Some of the delivery delays are between 5 and 11 s. Some other delays may be infinite, if the application does not poll the LBM stack, by calling smtc_modem_run_engine.
More information
The attached log file provides more information about what happened:
At 14:20:56.179940, a downlink message containing 0x2F is received, with a LINK ADR REQ command. The message is not returned to the application
At 14:21:00.765042, a downlink message containing 0x30 is received
At 14:21:01.074554, the 0x2F message is returned to the application
At 14:21:06.406773, a downlink message containing 0x31 is received
At 14:21:11.625514, the 0x30 message is returned to the application
At 14:21:14.488792, a downlink message containing 0x32 is received
At 14:21:14.925967, the 0x31 message is returned to the application
At 14:21:14.929914, the application enter sleep state
At 14:21:34.922879, it wakes up. Then LBM returns it the 0x32 message
Yes.
As I was not getting any feedback here, I created a support case on the Semtech website. There, I was asked for information about the client project I'm working on. As this project is currently still confidential, it was not possible for me to provide this information. Consequently, I did not get an answer to my question 🙁
Environment
The example application is modified as follows:
nb_downlink
(smtc_modem.c
) variable is printed:sleep_time_ms
(main_exti.c
) variable is printed:The application is built with the following command:
The cloud application replies to every uplink message with a one-byte message containing a counter incremented for each received uplink message.
The blue button is pushed periodically at a frequency of around 2 pushes per second.
Symptom
For some messages, the application is not immediately informed of the reception of a downlink message. Some of the delivery delays are between 5 and 11 s. Some other delays may be infinite, if the application does not poll the LBM stack, by calling
smtc_modem_run_engine
.More information
The attached log file provides more information about what happened:
0x2F
is received, with aLINK ADR REQ
command. The message is not returned to the application0x30
is received0x2F
message is returned to the application0x31
is received0x30
message is returned to the application0x32
is received0x31
message is returned to the application0x32
message20231205-1420-main_exti-downlink2.txt
The text was updated successfully, but these errors were encountered: