LoRaWAN JOIN problem on STM32WL55

[CChow.3]

I have a board NUCLEO-WL55JC1 and download a LoRaWAN End-Node Example on it form STM32CubeIDE, but it not join to LoRaWAN network sucessfully.

My LoRa Gateway is Drgaino-LG308 with TTN(The Thing Network) Server, the frequency is EU868.

After some checking, I found the TX is work, the server was accepted and responsed the JOIN request, but my board don't receive any LoRa packet. I also add some log in RadioIrqProcess() when it get irq about Rx but it show nothing.

How do I fix it OR figure out what problem is it?

[SBEN .2]

Hello @CChow.3​ ,

It seems that either your gateways is sending the join-response a little early or late (unlikely), or the RX1 window (or RX2 depending on how your LNS is configured) is not well timed. If you're using the Semtech stack set the MIB_SYSTEM_MAX_RX_ERROR parameter to a higher value (200 for example) and retest it.

Otherwise, please provide more details to make it easier to help you.

Best regards,

@SBEN .2​ 

[CChow.3]

I fixed it, seem there is a problem on my internet, it make the JOIN response delayed. the JOIN process is work when I use a local LoRaWAN server network.

Thank for your suggestion.

[ESchu.1]

Hello i have the same problem: STM32WL55JC1, EndNode Example with STM32Cube IDE 1.7.0

Debug:

###### AppKey: 2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C

###### NwkKey: AC:F3:EE:8D:62:23:49:3B:46:1A:B8:B1:41:EC:BE:99

###### ABP ######

###### AppSKey: 2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C

###### NwkSKey: 2B:7E:15:16:28:AE:D2:A6:AB:F7:15:88:09:CF:4F:3C

###### DevEui: 70:B3:D5:7E:D0:xx:xx:xx

###### AppEui: 01:01:01:01:01:01:01:01

###### DevAddr: 05:00:xx:xx

0s035:TX on freq 868500000 Hz at DR 0

APP_VERSION: V1.1.0

MW_LORAWAN_VERSION: V2.3.0

###### = JOIN FAILED

100s040:temp= 22

100s041:VDDA= 254

100s044:TX on freq 868100000 Hz at DR 0

101s530:MAC txDone

106s564:RX_1 on freq 868100000 Hz at DR 0

106s762:IRQ_RX_TX_TIMEOUT

106s762:MAC rxTimeOut

107s564:RX_2 on freq 869525000 Hz at DR 0

107s762:IRQ_RX_TX_TIMEOUT

107s762:MAC rxTimeOut

The Thing Stack Live Console:

There was an error and the event cannt not be displayedThe raw event can be displayed by clicking this raw

Raw Data:

{

 "name": "ns.up.join.cluster.fail",

 "time": "2021-09-27T16:17:26.339931133Z",

 "identifiers": [

   {

     "device_ids": {

       "device_id": "wl55jc1-01",

       "application_ids": {

         "application_id": "wl55jc1"

       }

     }

   },

   {

     "device_ids": {

       "device_id": "wl55jc1-01",

       "application_ids": {

         "application_id": "wl55jc1"

       },

       "dev_eui": "70B3D57ED004xxxx",

       "join_eui": "0101010101010101"

     }

   }

 ],

 "data": {

   "@type": "type.googleapis.com/ttn.lorawan.v3.ErrorDetails",

   "namespace": "pkg/joinserver",

   "name": "mic_mismatch",

   "message_format": "MIC mismatch",

   "correlation_id": "46b0ed8d76db4c529c903faea65d9c6a",

   "code": 3

 },

 "correlation_ids": [

   "gs:conn:01FGBKBKSE6RB0SV6X9MR24FDM",

   "gs:up:host:01FGBKBKSQGNFE1KA9MM7PDJ1X",

   "gs:uplink:01FGM0QYSVMFD3X629QRW0RHP1",

   "ns:uplink:01FGM0QYSWWNVQSXAGA7EB5Q44",

   "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01FGM0QYSW29HFS79S0NT50999"

 ],

 "origin": "ip-10-100-14-45.eu-west-1.compute.internal",

 "context": {

   "tenant-id": "CgN0dG4="

 },

 "visibility": {

   "rights": [

     "RIGHT_APPLICATION_TRAFFIC_READ",

     "RIGHT_APPLICATION_TRAFFIC_READ"

   ]

 },

 "unique_id": "01FGM0QYT35D14T7E21K4NX0ZZ"

}

[ESchu.1]

In wich file i will find the define-command für MIB_SYSTEM_MAX_RX_ERROR ?

In loraMac.h there is no command

Greetings

E_T

[ESchu.1]

The solution, it is my first try with this bord, the LORAWAN_APP_KEY in se-identity.h was identical with the AppKey in the TTS-Console, but the LORAWAN_NWK_KEY was differend!

Another little silly thing

Greetings

E_T

[EPeht.2]

I got also issue that join request response was lost. It happened after i switched from LSE to LSI. I managed to get it working by using LmHandlerSetSystemMaxRxError( 200 );

This is located in LmHandler.c, function LmHandlerConfigure.

As the LSI is very un-precise it makes sense that the timings are off.

I am not sure what it actually changes, did not dig too much.

By the way i am using STM32WLE5 IC.

[Connor48]

Hi, 

I have the same problem using the End_Node example, however I have had the Nucleo connected to the LoRaWAN network, it is just very intermittent in joining. I have changed LmHandlerSetSystemMaxRxError to (200) but this did not help.

I also cannot see any Join Request messages. Why might this be?

 

[pcmar__]

Hello Conno48! Have you found any solution for this? I have the same problem

[Connor48]

Hi @pcmar__ 

I have not found a solution!

I am using a Seeed Sense Cap M2 Indoor Gateway and I keep getting a "Time Sync Rejected" issue on the gateway log. I posted this in the Seeed Forum also but have not had a reply. 

Gateway Log:

Wed Dec 11 19:42:23 2024 daemon.info station[4605]: [S2E:VERB] RX 917.8MHz DR2 SF10/BW125 snr=13.2 rssi=-39 xtime=0x5500009B9C0931 - jreq MHdr=00 JoinEUI=101:101:101:101 DevEUI=80:e115:5ab:cfbd DevNonce=2 MIC=-585191918
Wed Dec 11 19:42:23 2024 daemon.info station[4605]: [SYN:INFO] MCU/SX130X drift stats: min: -1.4ppm q50: -2.4ppm q80: -5.7ppm max: -9.5ppm - threshold q90: -8.1ppm
Wed Dec 11 19:42:23 2024 daemon.info station[4605]: [SYN:INFO] Mean MCU drift vs SX130X#0: -2.5ppm
Wed Dec 11 19:42:38 2024 daemon.info station[4605]: [SYN:VERB] Time sync rejected: quality=981 threshold=168
Wed Dec 11 19:42:41 2024 daemon.info station[4605]: [SYN:VERB] Time sync rejected: quality=225 threshold=168
Wed Dec 11 19:43:03 2024 daemon.info station[4605]: {“state”:1,“temperature”:0,“rx_sum”:1,“report_time”:1733910183,“tx_sum”:0}
Wed Dec 11 19:43:03 2024 daemon.info station[4605]: [SYS:INFO] lora info statistics: rx:26 (+1), tx:0 (+0)
Wed Dec 11 19:43:03 2024 daemon.info station[4605]: [SYS:INFO] ubus: ubus -S call sensecap lora ‘{“rx_sum”:1,“tx_sum”:0,“report_time”:1733910183, “state”:1}’
Wed Dec 11 19:43:07 2024 daemon.info station[4605]: [SYN:INFO] MCU/SX130X drift stats: min: -1.4ppm q50: -2.4ppm q80: -6.7ppm max: -8.6ppm - threshold q90: -8.6ppm
Wed Dec 11 19:43:07 2024 daemon.info station[4605]: [SYN:INFO] Mean MCU drift vs SX130X#0: -2.8ppm
Wed Dec 11 19:43:19 2024 daemon.info station[4605]: [SYN:INFO] Time sync qualities: min=133 q90=168 max=981 (previous q90=168)
Wed Dec 11 19:43:23 2024 daemon.info station[4605]: [RAL:DEBU] [CRC FAIL] 917.200MHz -17.75/-110.5 SF10/BW125 (mod=16/dr=10/bw=4) xtick=9f303af5 (2670738165) 23 bytes: 000101010101010231BEEFA80515E1800008001FF9C149
Wed Dec 11 19:43:32 2024 daemon.info station[4605]: [SYN:VERB] Time sync rejected: quality=169 threshold=168
Wed Dec 11 19:43:38 2024 daemon.info station[4605]: [SYN:VERB] Time sync rejected: quality=227 threshold=168

STM32WL Nucleo:

APPLICATION_VERSION: V1.3.0
MW_LORAWAN_VERSION: V2.6.1
MW_RADIO_VERSION: V1.3.1
L2_SPEC_VERSION: V1.0.4
RP_SPEC_VERSION: V2-1.0.3

AppKey: xx

NwkKey: xx

AppSKey: xx

NwkSKey: xx

DevEUI: xx

AppEUI: xx

DevAddr: xx

0s041:TX on freq 916600000 Hz at DR 2
0s414:MAC txDone
5s398:RX_1 on freq 927500000 Hz at DR 10
5s449:IRQ_RX_TX_TIMEOUT
5s449:MAC rxTimeOut
6s410:RX_2 on freq 923300000 Hz at DR 8
6s476:IRQ_RX_TX_TIMEOUT
6s477:MAC rxTimeOut

= JOIN FAILED

10s048:TX on freq 917800000 Hz at DR 2
10s050:Payload:
10s421:MAC txDone
15s405:RX_1 on freq 926300000 Hz at DR 10
15s456:IRQ_RX_TX_TIMEOUT
15s456:MAC rxTimeOut
16s416:RX_2 on freq 923300000 Hz at DR 8
16s483:IRQ_RX_TX_TIMEOUT
16s484:MAC rxTimeOut