search

ropg / heltec_esp32_lora_v3

Proper working Arduino library for the Heltec ESP32 LoRa v3 board, as well as for Wireless Stick v3 and Wireless Stick Lite v3. Uses RadioLib
MIT License
363 stars 19 forks source link

example LoRaWAN_TTN not working #40

Open BennoB666 opened 2 months ago

BennoB666 commented 2 months ago

Hello Ropg,

Luckily I found your library. The Heltec libraries and instructions are terrible. I have a device on which I have installed the Lora example. After entering the TTN access data via the serial console I always get the following error message. What could be my mistake?

Enter LoRaWAN band (e.g. EU868 or US915)  [EU868]
Enter subband for your frequency plan, if applicable. Otherwise just press Enter.  []
Enter joinEUI (64 bits, 16 hex characters.) Press enter to use all zeroes.  [0000110220330440]
Enter devEUI (64 bits, 16 hex characters)  [70B3D57EDBD69B2C]
Enter appKey (128 bits, 32 hex characters)  [1B799FCFA9EABED1FE6863AC31237181]
Enter nwkKey (128 bits, 32 hex characters)  [1773074BA234B63D1683A13F76CCF6D1]
Thank you. Provisioning information saved to flash.
Now joining network.
Could not join network. We'll try again later.
Going to deep sleep now
Next TX in 900 s
BennoB666 commented 2 months ago

FireShot Capture 118 - Live data - heltec-lora32-dev - The Things Network_ - eu1 cloud thethings network

ropg commented 2 months ago

The log you have included, and the image do not seem to fit together as the DevAddr does not match the devEUI. Can that be? Beyond that I don't know at first sight what the problem is. Why are you using this particular joinEUI?

BennoB666 commented 2 months ago

DeviceAdr. is 260B2A97 in TTN

BennoB666 commented 2 months ago

The devEUI a changed before i post.

BennoB666 commented 2 months ago

I will delete the device later. The DevEUI is 70B3D57ED0069B2C

BennoB666 commented 2 months ago

I tried JoinEUI all zero also. Same result.

BennoB666 commented 2 months ago

next attempt: i make a new manual device in TTN

Frequency plan: Europe 863-870 MHz (SF9 for RX2 - recommended) LoRaWAN version: LoRaWAN Specification 1.1.0 Regional Parameters version: RP001 Regional Parameters 1.1 revision A JoinEUI: 0000000000000000 DevEUI: 70B3D57ED0069DF7 AppKey: CB6A6354BB51A70DD2A40975BEF20C36 NwkKey: 06000CA0F3DF930CF77351A0CB16AE0A

Heltec_Lorawan_V3 board with EXAMPLE LoRaWAN_TTN from Heltec_ESP32_LoRa_V3

General Settings - Join Settings - Reset join nonces -> enable

Config via serial console:

Enter LoRaWAN band (e.g. EU868 or US915) [EU868] Enter subband for your frequency plan, if applicable. Otherwise just press Enter. [] Enter joinEUI (64 bits, 16 hex characters.) Press enter to use all zeroes. [0000000000000000] Enter devEUI (64 bits, 16 hex characters) [70B3D57ED0069DF7] Enter appKey (128 bits, 32 hex characters) [CB6A6354BB51A70DD2A40975BEF20C36] Enter nwkKey (128 bits, 32 hex characters) [06000CA0F3DF930CF77351A0CB16AE0A] Thank you. Provisioning information saved to flash. Now joining network. Could not join network. We'll try again later. Going to deep sleep now Next TX in 900 s

Livedata from TTN: FireShot Capture 119 - Live data - testtetsttest - The Things Network - eu1 cloud thethings network

No idea whats wrong.

FlorianHeigl commented 2 months ago

@BennoB666 did you find anything more? same issue here, or worse. I didn't manage to get as far as seeing messages in TTN any more after switching to this library. (I can't recall specifics anymore, most of today I lost figuring out I needed to use Lora version 1.1 over the 1.0.2 from Heltec's docs)

ropg commented 2 months ago

Are you sure you are close enough to a working gateway? Does other software (on same board if possible) get a connection?

BennoB666 commented 2 months ago

1 m away from the gateway. With the Heltec library and same setup it connects immediately. For now i go back to the Heltec Library.

FlorianHeigl commented 1 month ago

i was able to reach the gw with the heltec stack - though that was using Lora 1.0.2. I don't understand enough of the stuff yet to know what matters and what doesn't. And I just wanted to say I'm interested to help make it work, but I'll come not back before a month-ish, so your shoulder is hopefully fine again & already forgotten by then ;-)

ropg commented 1 month ago

I'm guessing this may be a protocol issue of some kind at/behind your gateway. I haven't really played with LoRaWAN prior to 1.1.0, and I don't know what, if anything, changes on the network side by selecting one or the other when creating a node at the TTN side.

carlosmdarribas commented 3 weeks ago

Hello! Same issue here, and everything you guys said is also checked... are there any way to debug? It just keeps trying to connect in loop.

Captura de pantalla 2024-10-11 a las 12 23 37

ropg commented 3 weeks ago

Hello! Same issue here, and everything you guys said is also checked... are there any way to debug? It just keeps trying to connect in loop.

And this is running the unmodified TTN example from the latest version of this library, on the regular Heltec v3 board?

If so: it works for me. (I use all zeroes for the JoinEUI, but do not see how that could be relevant.) I do not understand how my code could do multiple joins in quick succession given that there is no branch and always a goToSleep() (long deep sleep) right after the send. Your output shows different values for DevAddr, indicating that it indeed starts a new session very shortly after the join. Are you sure you're not powercycling your device or have a power supply issue of some kind? The device briefly losing power (and thus state) would explain this behavior.

Here's the TTN provision data for a (now deleted) end device that worked for me:

image
ropg commented 3 weeks ago

Eh, just noticed you have "reset join nonces" on at TTN. That should not be needed (but should still not be causing this immediate rejoin.)

If you are sure the board is not resetting for some hardware/power reason, maybe describe your entire setup: what version of all the relevant libraries? (this library, RadioLib, LoRaWAN_ESP32), photo of all hardware, and if possible a screen movie (phone video is fine) showing serial entry of data from new TTN account while TTN log for that account is visible in other window.

carlosmdarribas commented 3 weeks ago

First of all, thank you for your quick response! Yes, using the Wireless Stick V3 of Heltec.

I've created a new one to match yours in case I misconfigured something:

Captura de pantalla 2024-10-11 a las 21 04 06

And the source code is just the same, just added the line "#define HELTEC_WIRELESS_STICK":

Captura de pantalla 2024-10-11 a las 21 17 23

The quick ones that happened was my fault, I modified not to wait 900s just 4

carlosmdarribas commented 3 weeks ago

Regarding versions:

Regarding hardware setup, is just this board connected via USB C to my mac. The gateway is a Mikrotik LR8 Kit connected to a self-hosted TTS... Everything out-of-the-box

ropg commented 3 weeks ago

And what does the TTN side show? Can you test by using an application on TTNs sandbox just to make everything as much the same as my environment as possible?

ropg commented 3 weeks ago

Also you used all zeroes as joinEUI on the device and D8 .. FD on the other end, it seems.

carlosmdarribas commented 3 weeks ago

Moving to TTN sandbox... meanwhile it was just an old screenshow :D that's now

Captura de pantalla 2024-10-12 a las 0 00 52
ropg commented 3 weeks ago

Curious what happened when you tested what you sent....

ropg commented 3 weeks ago

I haven't tested TTN with a stick, I think. Will do that to see if that's the difference if this doesn't solve it.

carlosmdarribas commented 3 weeks ago

I'm sorry about that, my fault.

Now I've duplicated the values on the gateway (now points to 2 servers: on premise and TTN EU), and the same config (including Rev A) on both ones. Same behavior. I receive the "ping" but empty data on both:

Captura de pantalla 2024-10-12 a las 0 17 19

And yes, as you said Arduino IDE for MacOS also v2.3.3. This is quite a mistery! (Again, thanks for your help)

ropg commented 3 weeks ago

Can I see the whole log from TTN?

carlosmdarribas commented 3 weeks ago

of course, this is:

Captura de pantalla 2024-10-12 a las 0 28 50
carlosmdarribas commented 3 weeks ago

with verbose option, if it helps:

Captura de pantalla 2024-10-12 a las 0 33 08
ropg commented 3 weeks ago

Somehow the join acknowledgement is not making it back to the endpoint. We're gonna need the RadioLib debug output. Modify /src/BuildOptUser.h in the RadioLib library directory and uncomment this line:

//#define RADIOLIB_DEBUG_PROTOCOL

Then try again and send output

ropg commented 3 weeks ago

(I'm also not sure about this business with "now points to 2 servers: on premise and TTN EU". Never ran my own, no idea if that's not somehow causing this.)

ropg commented 3 weeks ago

(You'll notice my LoRaWAN_ESP32 lib adds its own output in the debug output, prefixed with [persist])

carlosmdarribas commented 3 weeks ago

I modified but it did not show any more output (recompiled, rerun, cleared flash...), but I think I am not seeing logs, as I don't see any log starting with this prefix... maybe am I missing something?

these are the ones I see:

Captura de pantalla 2024-10-12 a las 0 44 51
ropg commented 3 weeks ago

That temperature seems a bit on the high side, and RadioLib should definitely be producing much more output with RADIOLIB_DEBUG_PROTOCOL turned on. Start over with a new endpoint on TTN, clear the flash so that you can enter that new endpoint.

If RadioLib is really not producing more output, you may be using (some?) libraries from a different directory than you think, or something crazy like that.

Anyway, I gave you some pointers to experiment, I'm off to bed. Will see in the morning where you landed.

Hasta luego y buenas noches

carlosmdarribas commented 3 weeks ago

I'll be reinstalling all the stack until I get more output... I'll keep you updated.

Guten Abend, und vielen Dank!

carlosmdarribas commented 3 weeks ago

here again! after reinstalling everything and trying to use directly RadioLib library (with no success, looks like something about keys, not important to me) now I've got working logs where I see some interesting things:

This log message:

RLB_PRO: [persist] Nonces and session data restored from RTC RAM
RLB_PRO: The Session buffer (0000) does not match the Nonces buffer (09e1)

After that, this is the moment when it fails:

LB_PRO: PHY:  Frequency DL = 869.525 MHz
RLB_PRO: LoRa: SF = 12, TX = 16 dBm, BW = 125.0 kHz, CR = 4/5
RLB_PRO: Opening Rx2 window (688 ms timeout)... <-- Rx Delay end 
RLB_PRO: Closing Rx2 window
RLB_PRO: [persist] Nonces and session data saved to RTC RAM
RLB_PRO: [persist] Nonces saved to NVS. (Only actually written if changed.)
Could not join network. We'll try again later.
Going to deep sleep now
RLB_PRO: [persist] Nonces and session data saved to RTC RAM
RLB_PRO: [persist] Nonces saved to NVS. (Only actually written if changed.)

does it mean anything for you?

ropg commented 3 weeks ago

Session buffer [...] does not match the Nonces buffer is a checksum mechanism used by the LoRaWAN code in RadioLib to see if the two kinds of data it stores long-term describe the same state. The 0000 seems to indicate to me that somehow the RTC RAM, where my code stores the session state, is not kept.

Do you have the Stick (with little screen), or the Stick Lite (no screen) ?

ropg commented 3 weeks ago

And do you have a battery connected?

carlosmdarribas commented 3 weeks ago

The Wireless Stick with display, even though I've got it software disabled. No battery, just connected to my mac via its USB C port

ropg commented 3 weeks ago

I've replicated your situation as closely as I know how to and I must say it works for me.

image 
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x28 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3818,len:0x109c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xb50
load:0x403cc700,len:0x2fe4
entry 0x403c98ac
Temperature: 27.80 °C
Radio init
RLB_PRO: [persist] Reading from NVS
RLB_PRO: [persist] No or incomplete provisioning. Getting from console.
No provisioning data found in flash.
Please enter the provisioning information needed to join the LoRaWAN network.

Enter LoRaWAN band (e.g. EU868 or US915)  [EU868]
Enter subband for your frequency plan, if applicable. Otherwise just press Enter.  []
Enter joinEUI (64 bits, 16 hex characters.) Press enter to use all zeroes.  [0000000000000000]
Enter devEUI (64 bits, 16 hex characters)  [70B3D57ED006B0A0]
Enter appKey (128 bits, 32 hex characters)  [51322616E7E6F0A1C0FAB578AFA77E16]
Enter nwkKey (128 bits, 32 hex characters)  [E698A10DEAA159A4CF57121C06F68BD0]
RLB_PRO: [persist] Reading from NVS
RLB_PRO: [persist]      band: EU868
RLB_PRO: [persist]   joinEUI: 0000000000000000
RLB_PRO: [persist]    devEUI: 70b3d57ed006b0a0
RLB_PRO: [persist]    appKey: 
RLB_PRO: 00000000: 51 32 26 16 e7 e6 f0 a1 c0 fa b5 78 af a7 7e 16  Q2&........x..~.
RLB_PRO: [persist]    nwkKey: 
RLB_PRO: 00000000: e6 98 a1 0d ea a1 59 a4 cf 57 12 1c 06 f6 8b d0  ......Y..W......
Thank you. Provisioning information saved to flash.
Now joining network.
RLB_PRO: [persist] beginOTAA
RLB_PRO: [persist] bootcount == 0
RLB_PRO: [persist] No nonces found in NVS
RLB_PRO: [persist] activateOTAA
RLB_PRO: Setting up dynamic channels
RLB_PRO: UL:   0 1 868.100 (0 - 5) | DL:   0 1 868.100 (0 - 5)
RLB_PRO: UL:   1 1 868.300 (0 - 5) | DL:   1 1 868.300 (0 - 5)
RLB_PRO: UL:   2 1 868.500 (0 - 5) | DL:   2 1 868.500 (0 - 5)
RLB_PRO: [MAC] 0x03
RLB_PRO: 00000000: 20                                                                 
RLB_PRO: LinkAdrReq: dataRate = 2, txSteps = 0, nbTrans = 0
RLB_PRO: LinkAdrAns: 07
RLB_PRO: [MAC] 0x04
RLB_PRO: 00000000: 07                                               .                 
RLB_PRO: DutyCycleReq: max duty cycle = 1/2^7
RLB_PRO: [MAC] 0x05
RLB_PRO: 00000000: 00 d2 ad 84                                      ....              
RLB_PRO: RXParamSetupReq: Rx1DrOffset = 0, rx2DataRate = 0, freq = 869.525
RLB_PRO: [MAC] 0x08
RLB_PRO: 00000000: 01                                               .                 
RLB_PRO: RXTimingSetupReq: delay = 1 sec
RLB_PRO: [MAC] 0x09
RLB_PRO: 00000000: 05                                               .                 
RLB_PRO: [MAC] 0x0c
RLB_PRO: 00000000: 65                                               e                 
RLB_PRO: ADRParamSetupReq: limitExp = 6, delayExp = 5
RLB_PRO: [MAC] 0x0f
RLB_PRO: 00000000: fa                                               .                 
RLB_PRO: RejoinParamSetupReq: maxTime = 15, maxCount = 10
RLB_PRO: 
RLB_PRO: PHY:  Frequency UL = 868.100 MHz
RLB_PRO: LoRa: SF = 10, TX = 16 dBm, BW = 125.0 kHz, CR = 4/5
RLB_PRO: JoinRequest sent (DevNonce = 0) <-- Rx Delay start
RLB_PRO: 00000000: 00 00 00 00 00 00 00 00 00 a0 b0 06 d0 7e d5 b3  .............~..
RLB_PRO: 00000010: 70 00 00 35 76 f1 3e                             p..5v.>           
RLB_PRO: 
RLB_PRO: PHY:  Frequency DL = 868.100 MHz
RLB_PRO: LoRa: SF = 10, TX = 16 dBm, BW = 125.0 kHz, CR = 4/5
RLB_PRO: Opening Rx1 window (231 ms timeout)... <-- Rx Delay end 
RLB_PRO: Closing Rx1 window
RLB_PRO: JoinAccept (JoinNonce = 1, previously 0):
RLB_PRO: 00000000: 20 01 00 00 13 00 00 75 08 0b 26 83 05 18 4f 84   ......u..&...O.
RLB_PRO: 00000010: e8 56 84 b8 5e 84 88 66 84 58 6e 84 00 48 be c4  .V..^..f.Xn..H..
RLB_PRO: 00000020: 16                                               .                 
RLB_PRO: LoRaWAN revision: 1.1
RLB_PRO: Setting up dynamic channels
RLB_PRO: UL:   0 1 868.100 (0 - 5) | DL:   0 1 868.100 (0 - 5)
RLB_PRO: UL:   1 1 868.300 (0 - 5) | DL:   1 1 868.300 (0 - 5)
RLB_PRO: UL:   2 1 868.500 (0 - 5) | DL:   2 1 868.500 (0 - 5)
RLB_PRO: [MAC] 0x05
RLB_PRO: 00000000: 03 d2 ad 84                                      ....              
RLB_PRO: RXParamSetupReq: Rx1DrOffset = 0, rx2DataRate = 3, freq = 869.525
RLB_PRO: [MAC] 0x08
RLB_PRO: 00000000: 05                                               .                 
RLB_PRO: RXTimingSetupReq: delay = 5 sec
RLB_PRO: Processing CFList
RLB_PRO: [MAC] 0x07
RLB_PRO: 00000000: 03 18 4f 84 50                                   ..O.P             
RLB_PRO: UL:   3 1 867.100 (0 - 5) | DL:   3 1 867.100 (0 - 5)
RLB_PRO: [MAC] 0x07
RLB_PRO: 00000000: 04 e8 56 84 50                                   ..V.P             
RLB_PRO: UL:   4 1 867.300 (0 - 5) | DL:   4 1 867.300 (0 - 5)
RLB_PRO: [MAC] 0x07
RLB_PRO: 00000000: 05 b8 5e 84 50                                   ..^.P             
RLB_PRO: UL:   5 1 867.500 (0 - 5) | DL:   5 1 867.500 (0 - 5)
RLB_PRO: [MAC] 0x07
RLB_PRO: 00000000: 06 88 66 84 50                                   ..f.P             
RLB_PRO: UL:   6 1 867.700 (0 - 5) | DL:   6 1 867.700 (0 - 5)
RLB_PRO: [MAC] 0x07
RLB_PRO: 00000000: 07 58 6e 84 50                                   .Xn.P             
RLB_PRO: UL:   7 1 867.900 (0 - 5) | DL:   7 1 867.900 (0 - 5)
RLB_PRO: [persist] Activation successful
RLB_PRO: [persist] Nonces and session data saved to RTC RAM
RLB_PRO: [persist] Nonces saved to NVS. (Only actually written if changed.)
RLB_PRO: Uplink MAC payload:
RLB_PRO: 00000000: 0b 01                                            ..                
RLB_PRO: Uplink (FCntUp = 0) decoded:
RLB_PRO: 00000000: d8 cd 04 3c 00 00 00 00 00 00 00 00 f8 9b ce 3f  ...<...........?
RLB_PRO: 00000010: 40 75 08 0b 26 82 00 00 85 1c 01 37 5e 12 ba ab  @u..&......7^...
RLB_PRO: 00000020: 14                                               .                 
RLB_PRO: 
RLB_PRO: PHY:  Frequency UL = 867.500 MHz
RLB_PRO: LoRa: SF = 10, TX = 16 dBm, BW = 125.0 kHz, CR = 4/5
RLB_PRO: Uplink sent <-- Rx Delay start
RLB_PRO: 
RLB_PRO: PHY:  Frequency DL = 867.500 MHz
RLB_PRO: LoRa: SF = 10, TX = 16 dBm, BW = 125.0 kHz, CR = 4/5
RLB_PRO: Opening Rx1 window (231 ms timeout)... <-- Rx Delay end 
RLB_PRO: Closing Rx1 window
RLB_PRO: Downlink (NFCntDown = 0) encoded:
RLB_PRO: 00000000: 49 00 00 00 00 01 75 08 0b 26 00 00 00 00 00 10  I.....u..&......
RLB_PRO: 00000010: 60 75 08 0b 26 88 00 00 fa 52 75 50 ed b7 81 68  `u..&....RuP...h
RLB_PRO: 00000020: 88 d6 ee db                                      ....              
RLB_PRO: [MAC] 0x0b
RLB_PRO: 00000000: 01                                               .                 
RLB_PRO: RekeyConf: server version = 1.1
RLB_PRO: [MAC] 0x03
RLB_PRO: 00000000: 41 ff 00 00 00 00 00 00 00 00 00 00 00 01        A.............    
RLB_PRO: LinkAdrReq: dataRate = 4, txSteps = 1, nbTrans = 1
RLB_PRO: UL:   0 1 868.100 (0 - 5) | DL:   0 1 868.100 (0 - 5)
RLB_PRO: UL:   1 1 868.300 (0 - 5) | DL:   1 1 868.300 (0 - 5)
RLB_PRO: UL:   2 1 868.500 (0 - 5) | DL:   2 1 868.500 (0 - 5)
RLB_PRO: UL:   3 1 867.100 (0 - 5) | DL:   3 1 867.100 (0 - 5)
RLB_PRO: UL:   4 1 867.300 (0 - 5) | DL:   4 1 867.300 (0 - 5)
RLB_PRO: UL:   5 1 867.500 (0 - 5) | DL:   5 1 867.500 (0 - 5)
RLB_PRO: UL:   6 1 867.700 (0 - 5) | DL:   6 1 867.700 (0 - 5)
RLB_PRO: UL:   7 1 867.900 (0 - 5) | DL:   7 1 867.900 (0 - 5)
RLB_PRO: LinkAdrAns: 07
RLB_PRO: [MAC] 0x06
RLB_PRO: DevStatusAns: status = 0xff08
Message sent, downlink received.
Going to deep sleep now
RLB_PRO: [persist] Nonces and session data saved to RTC RAM
RLB_PRO: [persist] Nonces saved to NVS. (Only actually written if changed.)
Next TX in 1194 s

Which makes my data show up at TTN:

image

I have seriously no clue what could be different on your end at this point, but at least now you have a complete working situation to compare against.

Good luck!

ropg commented 3 weeks ago

(Note that copy-pasting from the Arduino interface is harder than it needs to be, so I just updated the serial monitor output so it no longer misses a chunk in the middle)

askmurphy commented 5 days ago

I have the same issue with my Heltec Wireless stick v3 (with small screen)..
Connected with a powered HUB, no batterie.

Serial Output:

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x9 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3818,len:0x109c
load:0x403c9700,len:0x4
load:0x403c9704,len:0xb50
load:0x403cc700,len:0x2fe4
entry 0x403c98ac
Temperature: 27.3 °C
Radio init
RLB_PRO: [persist] Reading from NVS
RLB_PRO: [persist] No or incomplete provisioning. Getting from console.
No provisioning data found in flash.
Please enter the provisioning information needed to join the LoRaWAN network.

Enter LoRaWAN band (e.g. EU868 or US915)  [EU868]
Enter subband for your frequency plan, if applicable. Otherwise just press Enter.  []
Enter joinEUI (64 bits, 16 hex characters.) Press enter to use all zeroes.  [0000000000000000]
Enter devEUI (64 bits, 16 hex characters)  [70B3D57ED006B877]
Enter appKey (128 bits, 32 hex characters)  [11835B33ED5CFF08512B2E51FBD2ABA5]
Enter nwkKey (128 bits, 32 hex characters)  [C1DDE373BB1D023D59F125535E5E814C]
RLB_PRO: [persist] Reading from NVS
RLB_PRO: [persist]      band: EU868
RLB_PRO: [persist]   joinEUI: 0000000000000000
RLB_PRO: [persist]    devEUI: 70b3d57ed006b877
RLB_PRO: [persist]    appKey: 
RLB_PRO: 00000000: 11 83 5b 33 ed 5c ff 08 51 2b 2e 51 fb d2 ab a5  ..[3.\..Q+.Q....
RLB_PRO: [persist]    nwkKey: 
RLB_PRO: 00000000: c1 dd e3 73 bb 1d 02 3d 59 f1 25 53 5e 5e 81 4c  ...s...=Y.%S^^.L
Thank you. Provisioning information saved to flash.
Now joining network.
RLB_PRO: [persist] beginOTAA
RLB_PRO: [persist] bootcount == 0
RLB_PRO: [persist] No nonces found in NVS
RLB_PRO: [persist] activateOTAA
RLB_PRO: Setting up dynamic channels
RLB_PRO: UL:   0 1 868.100 (0 - 5) | DL:   0 1 868.100 (0 - 5)
RLB_PRO: UL:   1 1 868.300 (0 - 5) | DL:   1 1 868.300 (0 - 5)
RLB_PRO: UL:   2 1 868.500 (0 - 5) | DL:   2 1 868.500 (0 - 5)
RLB_PRO: [MAC] 0x03
RLB_PRO: 00000000: 20                                                                 
RLB_PRO: LinkAdrReq: dataRate = 2, txSteps = 0, nbTrans = 0
RLB_PRO: LinkAdrAns: 07
RLB_PRO: [MAC] 0x04
RLB_PRO: 00000000: 07                                               .                 
RLB_PRO: DutyCycleReq: max duty cycle = 1/2^7
RLB_PRO: [MAC] 0x05
RLB_PRO: 00000000: 00 d2 ad 84                                      ....              
RLB_PRO: RXParamSetupReq: Rx1DrOffset = 0, rx2DataRate = 0, freq = 869.525
RLB_PRO: [MAC] 0x08
RLB_PRO: 00000000: 01                                               .                 
RLB_PRO: RXTimingSetupReq: delay = 1 sec
RLB_PRO: [MAC] 0x09
RLB_PRO: 00000000: 05                                               .                 
RLB_PRO: [MAC] 0x0c
RLB_PRO: 00000000: 65                                               e                 
RLB_PRO: ADRParamSetupReq: limitExp = 6, delayExp = 5
RLB_PRO: [MAC] 0x0f
RLB_PRO: 00000000: fa                                               .                 
RLB_PRO: RejoinParamSetupReq: maxTime = 15, maxCount = 10
RLB_PRO: 
RLB_PRO: PHY:  Frequency = 868.300 MHz, TX = 16 dBm
RLB_PRO: LoRa: SF = 10, BW = 125.0 kHz, CR = 4/5, IQ: U
RLB_PRO: JoinRequest sent (DevNonce = 0) <-- Rx Delay start
RLB_PRO: 00000000: 00 00 00 00 00 00 00 00 00 77 b8 06 d0 7e d5 b3  .........w...~..
RLB_PRO: 00000010: 70 00 00 e7 b7 50 99                             p....P.           
RLB_PRO: 
RLB_PRO: PHY:  Frequency = 868.300 MHz, TX = 16 dBm
RLB_PRO: LoRa: SF = 10, BW = 125.0 kHz, CR = 4/5, IQ: D
RLB_PRO: Opening Rx1 window (231 ms timeout)... <-- Rx Delay end 
RLB_PRO: Closing Rx1 window
RLB_PRO: 
RLB_PRO: PHY:  Frequency = 869.525 MHz, TX = 16 dBm
RLB_PRO: LoRa: SF = 12, BW = 125.0 kHz, CR = 4/5, IQ: D
RLB_PRO: Opening Rx2 window (688 ms timeout)... <-- Rx Delay end 
RLB_PRO: Closing Rx2 window
RLB_PRO: [persist] Nonces and session data saved to RTC RAM
RLB_PRO: [persist] Nonces saved to NVS. (Only actually written if changed.)
Could not join network. We'll try again later.
Going to deep sleep now
RLB_PRO: [persist] Nonces and session data saved to RTC RAM
RLB_PRO: [persist] Nonces saved to NVS. (Only actually written if changed.)
Next TX in 120 s

afbeelding afbeelding

(I know I must change all the registration details later ;-)

Arduino IDE: afbeelding afbeelding

I have my own LoRa gateway, several Dragino LoRa devices are connected with TTN and working great..

ropg commented 5 days ago

Oddly enough all the reports for non-working connections have rather high temperatures, as measured by the ESP32 internally. If you power it down for the night, does it come up with a temp like this?

carlosmdarribas commented 5 days ago

In my case (I still haven't made it work) it didn't matter the uptime. I bought other modules (the lite v3, the LoRa v2) with identical results, and even when they were just connected after some time without being used, they still worked the same.

—

El 1 nov 2024, 14:22 +0100, Rop Gonggrijp @.***>, escribió:

Oddly enough all the reports for non-working connections have rather high temperatures, as measured by the ESP32 internally. If you power it down for the night, does it come up with a temp like this? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

askmurphy commented 5 days ago

In my case (I still haven't made it work) it didn't matter the uptime. I bought other modules (the lite v3, the LoRa v2) with identical results, and even when they were just connected after some time without being used, they still worked the same.

Have you re-compiled it again ?