Fire Alarm Package (Doorswitch) and return to WatchDog mode

[CK1-CK]

Hi folks,

i have a question regarding the timing of Lora MCCI.

My UseCase:

• Send every 20 min a WatchDog Signal to TTN.
• Send immediately a Alarm-Signal if a Door (Doorswitch) is open
• If the door is open, for a longer time, repeat Alarm-Signal every 10 min
• If the door is closed, the the WatchDog Signal should transmit (20 min)

Here is my main.cpp:
https://github.com/CK1-CK/Arduino-Pro-Mini-LoRa-Sensor-Node/blob/master/src/main.cpp

Problem:
If there is a Alarm (Door open) the Alarm-Signal will transfer. But unfortunately if the door will be closed, the WatchDog Signal doen't start again. There will be no more Transfers anymore.

In the readme of the Lib there is a hint regarding timing. Before i fire a Alarm-Signal i check if (!os_queryTimeCriticalJobs(ms2osticks(500))). But i don't understand why the controller doesn't return to WatchDog Mode.

https://github.com/mcci-catena/arduino-lmic#timing-issues
...
However, in the current implementation, the LMIC is tracking the completion of uplink transmits. This is done by checking for transmit-complete indications, which is done by polling. So you must also continually call os_runloop_once() while waiting for a transmit to be completed. This is an area for future improvement.
...

Maybe you can give me a hint/tipp, that a can solve my problem.
Do i need a check for "EV_TXCOMPLETE" Event?

Best regards
CK1

[CK1-CK]

I have found a solution for my problem.

Before i queue a new package now i clear the send-queue.

os_clearCallback(&sendjob); //Clear the SendQueue
https://github.com/CK1-CK/Arduino-Pro-Mini-LoRa-Sensor-Node/blob/118f4fa760f954668719d641ad45afbbb99f5890/src/lorawan.cpp#L163

With this I ensure that the OS does not get confused/muddled.

Thank you for the effort you make!

[terrillmoore]

Hi @CK1-CK, yes, submitting sendjob while it is in use is very likely to cause problems.

Also, please be sure to use LMIC_setTxData2() or LMIC_sendWithCallback() to send your data (or the _strict) variants, and check the result code. Otherwise if the result is != 0, you'll think you started a transmit, but you'll never get a completion. The examples unfortunately have not been rewritten to do this.