OTAA and data works to TTN, but stopped after reboot #949

jkarjanl · 2024-01-29T21:04:17Z

jkarjanl
Jan 29, 2024

Hi!

I'm not sure if this is related to Radiolib or not... But when I register new end device on The Things Network console everything works as expected. OTA activation works and Hello World payload get transmitted every minute to the Live Data view.

After I restart device everything looks same, serial monitor show transmitted etc... However TTN Console does not show traffic anymore. In Gateway view it clearly indicates that gateway forwards packets to TTN cloud, but Applications -> End Devices does not show any signs of received data.

If I manually delete End Device from console and recreate it using same EUIs and Keys it doesn't work. I must generate complete new keys and compile/upload new firmware to device and only after that it works again.

However, after I updated to Radiolib 6.4.2 and uploaded new firmware to device, TTN cloud Live Data view started to view packets. But again after I restarted device everything stopped.

Core: Raspberry Pi Pico/RP2040 by Earle F. Philhower III
Radiolib: 6.4.0 and 6.4.2
Official Arduino IDE
Waveshare Pico-LoRa-SX126X HAT

When things is not working there are two extra lines visible compared to working scenario:

Uplink MAC payload (1 commands):
0000000 0b 01                                           | ..

Whole output (not working example):

[LoRaWAN] Sending uplink packet ...
Channel frequency UL = 868.099976 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Uplink MAC payload (1 commands):
0000000 0b 01                                           | ..
uplinkMsg pre-MIC:
0000000 a2 22 a2 a2 a2 a2 a2 a2 a2 26 05 00 d1 10 00 00 | .".......&......
0000010 40 82 2b 0b 26 82 06 00 56 e5 0a 18 ce 26 07 42 | @.+.&...V....&.B
0000020 f5 39 b5 5f d4 27 33 e0 cc 0c 8b 44 d6 f6       | .9._.'3....D..
uplinkMsg:
0000000 49 00 00 00 00 00 82 2b 0b 26 06 00 00 00 00 1a | I......+.&......
0000010 40 82 2b 0b 26 82 06 00 56 e5 0a 18 ce 26 07 42 | @.+.&...V....&.B
0000020 f5 39 b5 5f d4 27 33 e0 cc 0c 21 0e 09 ae       | .9._.'3...!...
Timeout in 107904 us
Uplink sent <-- Rx Delay start

Channel frequency DL = 868.099976 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Opening Rx1 window (45856 us timeout)... <-- Rx Delay end
closing
DR 56: LORA (SF: 9, BW: 125.000000, CR: 5)
Opening Rx2 window (123424 us timeout)... <-- Rx Delay end
closing
no downlink!

Answered by StevenCellist

Jan 31, 2024

Ahh, "there comes the monkey out of the sleeve" - we say in Dutch.
The main takeaway here is that RadioLib implements LoRaWAN v1.1 which requires persistent sessions, or at the very least a persistent DevNonce/JoinNonce counter. And since LoRaWAN is mostly battery-powered, it's best to save/restore the whole session anyway.

And (hopefully) I'm not completely stupid and know about the limited lifetime of flash storage (10k per spec, usually lasts fine up to 100k), so there is quite a bit of logic to make sure that flash lifetime is prolonged as much as possible under normal expected behaviour! E.g. there are 50 bytes available for the lowest byte of the FCntUp, meaning that instead of (>)1…

View full answer

StevenCellist · 2024-01-30T06:57:33Z

StevenCellist
Jan 30, 2024
Collaborator

Hi @jkarjanl thanks for reaching out and providing useful information in the very first post. Two questions:

can you provide the logs of what happens right after a reboot? In that case, it should be able to restore the session. You may want to add a delay(5000) as first thing in your setup() to make sure that you can catch the debug output. It sounds like it is not completely restoring the session and reusing any Nonce or FCnt, as the node thinks it's working fine but it doesn't end up at your device console.
can you provide some insight into your gateway data? This helps verifying if the node is actually uplinking and at what frame counter / joining using certain DevNonce.

Maybe enabling Verbose mode on TTN device console shows a bit more as well.

14 replies

jkarjanl Jan 31, 2024
Author

Here is output:

[SX1262] Initializing ...
RadioLib Debug Info
Version:  6.4.2.0
Platform: Raspberry Pi Pico (unofficial)
Compiled: Jan 31 2024 19:34:44

Found SX126x: RADIOLIB_SX126X_REG_VERSION_STRING:
0000320 53 58 31 32 36 31 20 56 32 44 20 32 44 30 32 00 | SX1261 V2D 2D02.

M       SX126x
success!
[LoRaWAN] Attempting over-the-air activation ... Found existing session; restoring...
Dumping complete NVM:
0000000 02 00 00 aa 01 83 c3 01 00 00 00 00 82 2b 0b 26 | .............+.&
0000010 2b 4d b4 95 d7 12 05 67 4d a5 5a 76 a7 35 87 92 | +M.....gM.Zv.5..
0000020 9c 1e 04 2b 7d 13 ed 52 d6 a1 43 06 d7 6c 6a 99 | ...+}..R..C..lj.
0000030 cb 46 72 36 cb 68 2f 2d ec 5a 98 60 6f 71 06 71 | .Fr6.h/-.Z.`oq.q
0000040 de 52 4b 85 7a 05 2f 03 50 b4 ef fa 9e 23 90 1f | .RK.z./.P....#..
0000050 01 00 00 00 01 00 00 00 13 00 00 00 00 00 00 00 | ................
0000060 00 00 00 00 ff ff ff ff ff ff ff ff 00 00 00 00 | ................
0000070 00 00 00 00 00 00 00 00 00 80 00 00 00 00 00 00 | ................
0000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000a0 54 ff 00 01 07 03 d2 ad 84 05 05 65 fa 00 00 00 | T..........e....
00000b0 00 00 00 00 00 00 01 02 0b 01 00 00 00 00 01 40 | ...............@
00000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 | ................
0000110 18 4f 84 50 04 e8 56 84 50 05 b8 5e 84 50 06 88 | .O.P..V.P..^.P..
0000120 66 84 50 07 58 6e 84 50 00 00 00 00 00 00 00 00 | f.P.Xn.P........
0000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00001a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
LoRaWAN session: v1.1
Setting up dynamic channels
Channel UL/DL 0 frequency = 868.099976 MHz
Channel UL/DL 1 frequency = 868.299988 MHz
Channel UL/DL 2 frequency = 868.500000 MHz
exe MAC CID = 07, len = 5
New channel: index = 3, freq = 867.099976 MHz, maxDr = 5, minDr = 0
UL: 3 1 867.10 (0 - 5) | DL: 3 1 867.10 (0 - 5)
exe MAC CID = 07, len = 5
New channel: index = 4, freq = 867.299988 MHz, maxDr = 5, minDr = 0
UL: 4 1 867.30 (0 - 5) | DL: 4 1 867.30 (0 - 5)
exe MAC CID = 07, len = 5
New channel: index = 5, freq = 867.500000 MHz, maxDr = 5, minDr = 0
UL: 5 1 867.50 (0 - 5) | DL: 5 1 867.50 (0 - 5)
exe MAC CID = 07, len = 5
New channel: index = 6, freq = 867.700012 MHz, maxDr = 5, minDr = 0
UL: 6 1 867.70 (0 - 5) | DL: 6 1 867.70 (0 - 5)
exe MAC CID = 07, len = 5
New channel: index = 7, freq = 867.900024 MHz, maxDr = 5, minDr = 0
UL: 7 1 867.90 (0 - 5) | DL: 7 1 867.90 (0 - 5)
exe MAC CID = 03, len = 4
ADR REQ: dataRate = 5, txPower = 4, chMask = 0x00ff, chMaskCntl = 00, nbTrans = 1
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
ADR channel 0: 1 --> 1
ADR channel 1: 1 --> 1
ADR channel 2: 1 --> 1
ADR channel 3: 1 --> 1
ADR channel 4: 1 --> 1
ADR channel 5: 1 --> 1
ADR channel 6: 1 --> 1
ADR channel 7: 1 --> 1
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
UL: 0 1 868.10 (0 - 5) | DL: 0 1 868.10 (0 - 5)
UL: 1 1 868.30 (0 - 5) | DL: 1 1 868.30 (0 - 5)
UL: 2 1 868.50 (0 - 5) | DL: 2 1 868.50 (0 - 5)
UL: 3 1 867.10 (0 - 5) | DL: 3 1 867.10 (0 - 5)
UL: 4 1 867.30 (0 - 5) | DL: 4 1 867.30 (0 - 5)
UL: 5 1 867.50 (0 - 5) | DL: 5 1 867.50 (0 - 5)
UL: 6 1 867.70 (0 - 5) | DL: 6 1 867.70 (0 - 5)
UL: 7 1 867.90 (0 - 5) | DL: 7 1 867.90 (0 - 5)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
ADR ANS: status = 0x07
exe MAC CID = 04, len = 1
Max duty cycle: 1/2^7
exe MAC CID = 05, len = 4
Rx param REQ: rx1DrOffset = 0, rx2DataRate = 3, freq = 869.525024
Rx param ANS: status = 0x07
exe MAC CID = 08, len = 1
RX timing: delay = 5 sec
exe MAC CID = 09, len = 1
TX timing: dlDwell = 0, ulDwell = 0, maxEirp = 16 dBm
exe MAC CID = 0c, len = 1
ADR param setup: limitExp = 6, delayExp = 5
exe MAC CID = 0f, len = 1
Rejoin setup: maxTime = 15, maxCount = 10
Number of MAC commands: 1
success!
[LoRaWAN] Sending uplink packet ...
Channel frequency UL = 867.900024 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Uplink MAC payload (1 commands):
11: len 1, repeat 64
0000000 0b 01                                           | ..
Uplink: FCnt 1, FPort 10
uplinkMsg pre-MIC:
0000000 a2 22 a2 a2 a2 05 2f 03 50 b4 ef fa f9 10 00 00 | ."..../.P.......
0000010 40 82 2b 0b 26 82 01 00 93 53 0a 1c 0f cc 63 0a | @.+.&....S....c.
0000020 ee 03 23 45 79 22 5e 5a e0 dc ff ff 00 00       | ..#Ey"^Z......
uplinkMsg:
0000000 49 00 00 00 00 00 82 2b 0b 26 01 00 00 00 00 1a | I......+.&......
0000010 40 82 2b 0b 26 82 01 00 93 53 0a 1c 0f cc 63 0a | @.+.&....S....c.
0000020 ee 03 23 45 79 22 5e 5a e0 dc e0 fd 70 12       | ..#Ey"^Z....p.
Timeout in 107904 us
Uplink sent <-- Rx Delay start

Channel frequency DL = 867.900024 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Opening Rx1 window (45856 us timeout)... <-- Rx Delay end
closing
DR 56: LORA (SF: 9, BW: 125.000000, CR: 5)
Opening Rx2 window (123424 us timeout)... <-- Rx Delay end
closing
no downlink!
[LoRaWAN] Sending uplink packet ...
Channel frequency UL = 867.900024 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Uplink MAC payload (1 commands):
11: len 1, repeat 63
0000000 0b 01                                           | ..
Uplink: FCnt 2, FPort 10
uplinkMsg pre-MIC:
0000000 a2 22 a2 a2 a2 a2 a2 a2 a2 00 00 00 d1 10 00 00 | ."..............
0000010 40 82 2b 0b 26 82 02 00 32 4b 0a dc 2d bb 62 93 | @.+.&...2K..-.b.
0000020 e3 54 01 d5 5b 12 06 8a 7b 5b ee 03 23 45       | .T..[...{[..#E
uplinkMsg:
0000000 49 00 00 00 00 00 82 2b 0b 26 02 00 00 00 00 1a | I......+.&......
0000010 40 82 2b 0b 26 82 02 00 32 4b 0a dc 2d bb 62 93 | @.+.&...2K..-.b.
0000020 e3 54 01 d5 5b 12 06 8a 7b 5b 92 ce b2 4a       | .T..[...{[...J
Timeout in 107904 us
Uplink sent <-- Rx Delay start

Channel frequency DL = 867.900024 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Opening Rx1 window (45856 us timeout)... <-- Rx Delay end
closing
DR 56: LORA (SF: 9, BW: 125.000000, CR: 5)
Opening Rx2 window (123424 us timeout)... <-- Rx Delay end
closing
no downlink!

And here second attempt:

[SX1262] Initializing ...
RadioLib Debug Info
Version:  6.4.2.0
Platform: Raspberry Pi Pico (unofficial)
Compiled: Jan 31 2024 19:34:44

Found SX126x: RADIOLIB_SX126X_REG_VERSION_STRING:
0000320 53 58 31 32 36 31 20 56 32 44 20 32 44 30 32 00 | SX1261 V2D 2D02.

M       SX126x
success!
[LoRaWAN] Attempting over-the-air activation ... Found existing session; restoring...
Dumping complete NVM:
0000000 02 00 00 aa 01 83 c3 01 00 00 00 00 82 2b 0b 26 | .............+.&
0000010 2b 4d b4 95 d7 12 05 67 4d a5 5a 76 a7 35 87 92 | +M.....gM.Zv.5..
0000020 9c 1e 04 2b 7d 13 ed 52 d6 a1 43 06 d7 6c 6a 99 | ...+}..R..C..lj.
0000030 cb 46 72 36 cb 68 2f 2d ec 5a 98 60 6f 71 06 71 | .Fr6.h/-.Z.`oq.q
0000040 de 52 4b 85 7a 05 2f 03 50 b4 ef fa 9e 23 90 1f | .RK.z./.P....#..
0000050 01 00 00 00 01 00 00 00 13 00 00 00 00 00 00 00 | ................
0000060 00 00 00 00 ff ff ff ff ff ff ff ff 00 00 00 00 | ................
0000070 00 00 00 00 00 00 00 00 00 80 00 00 00 00 00 00 | ................
0000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000a0 54 ff 00 01 07 03 d2 ad 84 05 05 65 fa 00 00 00 | T..........e....
00000b0 00 00 00 00 00 00 01 02 0b 01 00 00 00 00 01 40 | ...............@
00000c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00000f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 | ................
0000110 18 4f 84 50 04 e8 56 84 50 05 b8 5e 84 50 06 88 | .O.P..V.P..^.P..
0000120 66 84 50 07 58 6e 84 50 00 00 00 00 00 00 00 00 | f.P.Xn.P........
0000130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00001a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
00001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
LoRaWAN session: v1.1
Setting up dynamic channels
Channel UL/DL 0 frequency = 868.099976 MHz
Channel UL/DL 1 frequency = 868.299988 MHz
Channel UL/DL 2 frequency = 868.500000 MHz
exe MAC CID = 07, len = 5
New channel: index = 3, freq = 867.099976 MHz, maxDr = 5, minDr = 0
UL: 3 1 867.10 (0 - 5) | DL: 3 1 867.10 (0 - 5)
exe MAC CID = 07, len = 5
New channel: index = 4, freq = 867.299988 MHz, maxDr = 5, minDr = 0
UL: 4 1 867.30 (0 - 5) | DL: 4 1 867.30 (0 - 5)
exe MAC CID = 07, len = 5
New channel: index = 5, freq = 867.500000 MHz, maxDr = 5, minDr = 0
UL: 5 1 867.50 (0 - 5) | DL: 5 1 867.50 (0 - 5)
exe MAC CID = 07, len = 5
New channel: index = 6, freq = 867.700012 MHz, maxDr = 5, minDr = 0
UL: 6 1 867.70 (0 - 5) | DL: 6 1 867.70 (0 - 5)
exe MAC CID = 07, len = 5
New channel: index = 7, freq = 867.900024 MHz, maxDr = 5, minDr = 0
UL: 7 1 867.90 (0 - 5) | DL: 7 1 867.90 (0 - 5)
exe MAC CID = 03, len = 4
ADR REQ: dataRate = 5, txPower = 4, chMask = 0x00ff, chMaskCntl = 00, nbTrans = 1
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
ADR channel 0: 1 --> 1
ADR channel 1: 1 --> 1
ADR channel 2: 1 --> 1
ADR channel 3: 1 --> 1
ADR channel 4: 1 --> 1
ADR channel 5: 1 --> 1
ADR channel 6: 1 --> 1
ADR channel 7: 1 --> 1
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
ADR channel 255: 0 --> 0
UL: 0 1 868.10 (0 - 5) | DL: 0 1 868.10 (0 - 5)
UL: 1 1 868.30 (0 - 5) | DL: 1 1 868.30 (0 - 5)
UL: 2 1 868.50 (0 - 5) | DL: 2 1 868.50 (0 - 5)
UL: 3 1 867.10 (0 - 5) | DL: 3 1 867.10 (0 - 5)
UL: 4 1 867.30 (0 - 5) | DL: 4 1 867.30 (0 - 5)
UL: 5 1 867.50 (0 - 5) | DL: 5 1 867.50 (0 - 5)
UL: 6 1 867.70 (0 - 5) | DL: 6 1 867.70 (0 - 5)
UL: 7 1 867.90 (0 - 5) | DL: 7 1 867.90 (0 - 5)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
UL: 255 0  0.00 (0 - 0) | DL: 0 0  0.00 (0 - 0)
ADR ANS: status = 0x07
exe MAC CID = 04, len = 1
Max duty cycle: 1/2^7
exe MAC CID = 05, len = 4
Rx param REQ: rx1DrOffset = 0, rx2DataRate = 3, freq = 869.525024
Rx param ANS: status = 0x07
exe MAC CID = 08, len = 1
RX timing: delay = 5 sec
exe MAC CID = 09, len = 1
TX timing: dlDwell = 0, ulDwell = 0, maxEirp = 16 dBm
exe MAC CID = 0c, len = 1
ADR param setup: limitExp = 6, delayExp = 5
exe MAC CID = 0f, len = 1
Rejoin setup: maxTime = 15, maxCount = 10
Number of MAC commands: 1
success!
[LoRaWAN] Sending uplink packet ...
Channel frequency UL = 867.500000 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Uplink MAC payload (1 commands):
11: len 1, repeat 64
0000000 0b 01                                           | ..
Uplink: FCnt 1, FPort 10
uplinkMsg pre-MIC:
0000000 a2 22 a2 a2 a2 05 2f 03 50 b4 ef fa f9 10 00 00 | ."..../.P.......
0000010 40 82 2b 0b 26 82 01 00 93 53 0a 1c 0f cc 63 0a | @.+.&....S....c.
0000020 ee 03 23 45 79 22 5e 5a e0 dc ff ff 00 00       | ..#Ey"^Z......
uplinkMsg:
0000000 49 00 00 00 00 00 82 2b 0b 26 01 00 00 00 00 1a | I......+.&......
0000010 40 82 2b 0b 26 82 01 00 93 53 0a 1c 0f cc 63 0a | @.+.&....S....c.
0000020 ee 03 23 45 79 22 5e 5a e0 dc 17 e7 70 12       | ..#Ey"^Z....p.
Timeout in 107904 us
Uplink sent <-- Rx Delay start

Channel frequency DL = 867.500000 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Opening Rx1 window (45856 us timeout)... <-- Rx Delay end
closing
DR 56: LORA (SF: 9, BW: 125.000000, CR: 5)
Opening Rx2 window (123424 us timeout)... <-- Rx Delay end
closing
no downlink!
[LoRaWAN] Sending uplink packet ...
Channel frequency UL = 867.099976 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Uplink MAC payload (1 commands):
11: len 1, repeat 63
0000000 0b 01                                           | ..
Uplink: FCnt 2, FPort 10
uplinkMsg pre-MIC:
0000000 a2 22 a2 a2 a2 a2 a2 a2 a2 00 00 00 d1 10 00 00 | ."..............
0000010 40 82 2b 0b 26 82 02 00 32 4b 0a dc 2d bb 62 93 | @.+.&...2K..-.b.
0000020 e3 54 01 d5 5b 12 06 8a 7b 5b ee 03 23 45       | .T..[...{[..#E
uplinkMsg:
0000000 49 00 00 00 00 00 82 2b 0b 26 02 00 00 00 00 1a | I......+.&......
0000010 40 82 2b 0b 26 82 02 00 32 4b 0a dc 2d bb 62 93 | @.+.&...2K..-.b.
0000020 e3 54 01 d5 5b 12 06 8a 7b 5b 9f 3b b2 4a       | .T..[...{[.;.J
Timeout in 107904 us
Uplink sent <-- Rx Delay start

Channel frequency DL = 867.099976 MHz
DR 24: LORA (SF: 7, BW: 125.000000, CR: 5)
Opening Rx1 window (45856 us timeout)... <-- Rx Delay end
closing
DR 56: LORA (SF: 9, BW: 125.000000, CR: 5)
Opening Rx2 window (123424 us timeout)... <-- Rx Delay end
closing
no downlink!

And here is json from Gateway log view:

{
    "name": "gs.up.receive",
    "time": "2024-01-31T17:44:42.099447691Z",
    "identifiers": [
      {
        "gateway_ids": {
          "gateway_id": "eui-58a0cbfffe805492",
          "eui": "58A0CBFFFE805492"
        }
      }
    ],
    "data": {
      "@type": "type.googleapis.com/ttn.lorawan.v3.GatewayUplinkMessage",
      "message": {
        "raw_payload": "QIIrCyaCBADYEQpSYhC/YDBHDAtxfdu+ZsTkS6Ks",
        "payload": {
          "m_hdr": {
            "m_type": "UNCONFIRMED_UP"
          },
          "mic": "5EuirA==",
          "mac_payload": {
            "f_hdr": {
              "dev_addr": "260B2B82",
              "f_ctrl": {
                "adr": true
              },
              "f_cnt": 4,
              "f_opts": "2BE="
            },
            "f_port": 10,
            "frm_payload": "UmIQv2AwRwwLcX3bvmbE"
          }
        },
        "settings": {
          "data_rate": {
            "lora": {
              "bandwidth": 125000,
              "spreading_factor": 7,
              "coding_rate": "4/5"
            }
          },
          "frequency": "867900000",
          "timestamp": 2283419276,
          "time": "2024-01-31T17:44:42.009541988Z"
        },
        "rx_metadata": [
          {
            "gateway_ids": {
              "gateway_id": "eui-58a0cbfffe805492",
              "eui": "58A0CBFFFE805492"
            },
            "time": "2024-01-31T17:44:42.009541988Z",
            "timestamp": 2283419276,
            "rssi": -53,
            "channel_rssi": -53,
            "snr": 9.5,
            "location": {
              "latitude": 61.68630266311154,
              "longitude": 22.00668533471231,
              "altitude": 51,
              "source": "SOURCE_REGISTRY"
            },
            "uplink_token": "CiIKIAoUZXVpLTU4YTBjYmZmZmU4MDU0OTISCFigy//+gFSSEIzt6MAIGgsIio7qrQYQ4siqLyDgpZSzukI=",
            "received_at": "2024-01-31T17:44:42.025115037Z"
          }
        ],
        "received_at": "2024-01-31T17:44:42.099263586Z",
        "correlation_ids": [
          "gs:uplink:01HNG9YZVKH7038DYMYTHDHGXE"
        ]
      },
      "band_id": "EU_863_870"
    },
    "correlation_ids": [
      "gs:uplink:01HNG9YZVKH7038DYMYTHDHGXE"
    ],
    "origin": "ip-10-100-14-219.eu-west-1.compute.internal",
    "context": {
      "tenant-id": "CgN0dG4="
    },
    "visibility": {
      "rights": [
        "RIGHT_GATEWAY_TRAFFIC_READ"
      ]
    },
    "unique_id": "01HNG9YZVKP2G9EVAFY5ZVGAAW"
  },

StevenCellist Jan 31, 2024
Collaborator

Hmmm.. are you sure you call node.saveSession() after every up/downlink? I don't see obvious mistakes in the logs. What would help though is reverting to the original 6.4.2 code, and adding the fixes you can find in #950. I hope that will help solve the problem, although I'm not completely sure from the logs. Please let me know!

jkarjanl Jan 31, 2024
Author

I must confess that I don't fully understand the mechanics and logic involved with LoraWAN activation process. Because of this the code I was using is first and most simple example, LoRaWAN_End_Device.ino

As you can see there is no calling to node.saveSession() at all in that example. I somehow assumed that its optional, so perhaps joining will be a bit slower without session restore because device must complete full joining procedure every time its power on. It's not problem for me, because devices will not be battery powered. So I'm intrested to make it work without saving and restoring sessions at all, but performing full OTAA joining every time it gets powered on. I wonder if it is possible?

There is another example involving session restore in LoRaWAN_End_Device_Persistent.ino but I wonder if it's incomplete. How device knows if it must perform session restore or initial joining? I am also a bit worried about EEPROM/flash wearing if node.saveSession() writes to flash every minute?

I will try the fixes you mentioned tomorrow. Thank you for your help and patience.

StevenCellist Jan 31, 2024
Collaborator

Ahh, "there comes the monkey out of the sleeve" - we say in Dutch.
The main takeaway here is that RadioLib implements LoRaWAN v1.1 which requires persistent sessions, or at the very least a persistent DevNonce/JoinNonce counter. And since LoRaWAN is mostly battery-powered, it's best to save/restore the whole session anyway.

And (hopefully) I'm not completely stupid and know about the limited lifetime of flash storage (10k per spec, usually lasts fine up to 100k), so there is quite a bit of logic to make sure that flash lifetime is prolonged as much as possible under normal expected behaviour! E.g. there are 50 bytes available for the lowest byte of the FCntUp, meaning that instead of (>)10k uplink frame counter saves, you can get (>)500k frame counter saves.

In short - if you want to use RadioLib, please adhere to LoRaWAN v1.1 with session persistence, otherwise you must enable resetting DevNonces and always set the force argument to true in beginOTAA() function. (But why would you always want to join????)

Answer selected by jkarjanl

jkarjanl Feb 1, 2024
Author

Uhhh... I feel myself a little bit stupid and ashamed. But for my excuse I actually checked "Reset DevNonces" on TTN console, but failed to understand the need of force argument in beginOTAA(). Sorry to bother you, and thank you for your time.

Maybe I'm too concerned about flash wearing, but I think there is 525k minutes in one year. So am I supposed to brick one device per year if sending at fastest rate? I know there is fair use policy on TTN, but perhaps using own gateway and own ChirpStack installation it's possible to hit 500k writes per year?

However I am aware that specification is specification, and all of you make wonderful job to implement such a high quality library. So I have only myself to blame not reading docs enough and not to having sufficient knowledge.
I think the basics is working now and I can continue to actually write my application. Thanks.

StevenCellist Feb 1, 2024
Collaborator

Good questions, good questions. Two years ago I was asking myself "what the actual f is am FCnt" and I didn't know that FPort existed - you're doing fine.

Funny that the 525k minutes a year almost exactly checks out against the 500k writes per datasheet. But now you can be a bit smart: if you are sending once every minute, you are clearly not bothered by power consumption and do not need deepsleep so don't really need to save. So your device is always on. Now if you would want to move the device and cut power, you obviously loose the whole state as you never save - so now you can ask yourself: can I save once every e.g
60 minutes? In that case, you can run for 60 years (per datasheet) - by that time, there are other things to worry about. And now if you'd cut the power to move the node, it may take up to 60 minutes to get back to the actual last FCnt, and then it will happily keep sending again, so you loose only a small amount of data. Which, given that you decided it was time to cut the power anyway, shouldn't be too much of a problem.

TLDR: save once every so often, then loose a few data points if you would ever have to reboot the device.
Hope that helps!

jkarjanl Feb 1, 2024
Author

Ah.. I see... I have a plenty to learn. It's pretty basic optimization for some of us, but seems like a clever programming trick for the rest of the people.
Saving session state / FCnt about once per 15 minutes seems like a good trade-off for me.

StevenCellist Feb 1, 2024
Collaborator

Keep learning! I plan to add some general design recommendations to the Wiki in the (somewhat near) future, which will also include this case, as you won't be the only one with a question like this. And once every 15 frames does indeed sound like a very decent trade-off :)

HeadBoffin · 2024-01-31T15:45:34Z

HeadBoffin
Jan 31, 2024
Collaborator

but I can manage.. @HeadBoffin can confirm!

Not sure how when the OP is clearly breaching the FUP - surely that should put you in to a wait-ready state?

I can cobble together a HAT for some of my dormant Pico's for you to test with, probs Thurs as running out of time today

1 reply

StevenCellist Jan 31, 2024
Collaborator

Actually just decided to add this combo to the school's inventory which very conveniently will pass my desk at some point in the near future ;)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OTAA and data works to TTN, but stopped after reboot #949

{{title}}

Replies: 2 comments 15 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

OTAA and data works to TTN, but stopped after reboot #949

jkarjanl Jan 29, 2024

Replies: 2 comments · 15 replies

StevenCellist Jan 30, 2024 Collaborator

jkarjanl Jan 31, 2024 Author

StevenCellist Jan 31, 2024 Collaborator

jkarjanl Jan 31, 2024 Author

StevenCellist Jan 31, 2024 Collaborator

jkarjanl Feb 1, 2024 Author

StevenCellist Feb 1, 2024 Collaborator

jkarjanl Feb 1, 2024 Author

StevenCellist Feb 1, 2024 Collaborator

HeadBoffin Jan 31, 2024 Collaborator

StevenCellist Jan 31, 2024 Collaborator

jkarjanl
Jan 29, 2024

Replies: 2 comments 15 replies

StevenCellist
Jan 30, 2024
Collaborator

jkarjanl Jan 31, 2024
Author

StevenCellist Jan 31, 2024
Collaborator

jkarjanl Jan 31, 2024
Author

StevenCellist Jan 31, 2024
Collaborator

jkarjanl Feb 1, 2024
Author

StevenCellist Feb 1, 2024
Collaborator

jkarjanl Feb 1, 2024
Author

StevenCellist Feb 1, 2024
Collaborator

HeadBoffin
Jan 31, 2024
Collaborator

StevenCellist Jan 31, 2024
Collaborator