Packet Queue #891
Replies: 3 comments
-
The packet queued is printed by the setup() routine, which is only called once. After that, the flow is driven by completions. Meanwhile ChirpStack is (probably) sending a bunch of instructions as MAC commands after the join. My version of ChirpStack sets the packet rep count to 3 initially; but in any case, the LMIC will keep TXing as long as it's getting downlink MAC messages during the RX window. Based on the timing, you're getting downlink messages during RX1 (until the last one). You should look at the ChripStack logs to see more about what it's doing. Things look fine from here. |
Beta Was this translation helpful? Give feedback.
-
Thanks. |
Beta Was this translation helpful? Give feedback.
-
Looks more like network control ("MAC") packets being downlinked. Don't recall how to see them on ChirpStack; the device will print them in hex if you run the compliance sketch. Anyway, this is getting to be more of a question about ChripStack and how LoRaWAN works than about the LMIC. Converting to a discussino. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm using the ttn-otaa example and the mcci-catena arduino-lmic library.
When I run the example I see the following in the terminal:
Why packet queue is only printed once?
Why is a new uplink sent without respecting TX_INTERNAL=60?
Beta Was this translation helpful? Give feedback.
All reactions