where the TXCOMPLETE event is from the join, not for the data uplink.
The event list is cut short in the second example because our firmware was using TXCOMPLETE as the signal to stop calling os_runloop_once, so we dropped out of LMIC processing right after the join and before the uplink was started.
We've changed our firmware but it feels like a bug to have different events emitted depending on whether the join was explicitly started or implicitly started.
Environment
LMIC 4.1.1
TTN
AS923
Feather M0
Expected behavior
Probably the explicit join should not emit the TXCOMPLETE event, and perhaps there should not be a TXSTART after a JOINING?
Description
If you call LMIC_startJoining, wait for the join, then call LMIC_setTxData2 you get the following sequence of events:
whereas if you only call LMIC_setTxData2 and cause an implicit join to happen, these events are emitted:
where the TXCOMPLETE event is from the join, not for the data uplink.
The event list is cut short in the second example because our firmware was using TXCOMPLETE as the signal to stop calling os_runloop_once, so we dropped out of LMIC processing right after the join and before the uplink was started.
We've changed our firmware but it feels like a bug to have different events emitted depending on whether the join was explicitly started or implicitly started.
Environment
LMIC 4.1.1 TTN AS923 Feather M0
Expected behavior
Probably the explicit join should not emit the TXCOMPLETE event, and perhaps there should not be a TXSTART after a JOINING?