rxTimeOut when trying to communicate with gateway

End Devices (Nodes)
1

Hi there,

Intro

I have a Dragino gateway (LPS8) and I am trying to make my Nucleo board (P-NUCLEO-LRWAN1) connect, using the default end-node code from STM32CubeExpansion_LRWAN_V2.0.0.

I keep getting rxTimeOut, and I am unsure why, perhaps I missed setting up something.

The questions

I tried changing the duty cycle from 10 to 30s, and OTAA to ABP. Neither seemed to help.

Does anyone know what it could be? I presume this is not expected behaviour, as I found a flag for rxDone in the code.

I think I might have missed some set up? Or is the gateway refusing to communicate?

Logs

Gateway setup

Gateway is connected to the TTN.

Logread RxTxJson

Sun Apr 25 08:49:29 2021 daemon.info lora_pkt_fwd[31113]: RXTX~ {"rxpk":[{"tmst":2880334028,"time":"2021-04-25T08:49:29.267227Z","chan":0,"rfch":1,"freq":868.100000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":9.2,"rssi":-53,"size":23,"data":"AAEBAQEBAQEBGGk2czAwMDk7iI5NlR8="}]}
Sun Apr 25 08:49:39 2021 daemon.info lora_pkt_fwd[31113]: RXTX~ {"rxpk":[{"tmst":2890379492,"time":"2021-04-25T08:49:39.311460Z","chan":1,"rfch":1,"freq":868.300000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":10.5,"rssi":-47,"size":23,"data":"AAEBAQEBAQEBGGk2czAwMDmvWkUJKEQ="}]}

FreqINFO:

Gateway Channels frequency
---------------------------------------
chan_multSF_0
Lora MAC, 125kHz, all SF, 868.1 MHz
---------------------------------------
chan_multSF_2
Lora MAC, 125kHz, all SF, 868.5 MHz

Logread REPORT:

Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ ################## Report at: 2021-04-25 09:55:40 UTC ##################
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ ### [UPSTREAM] ###
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # RF packets received by concentrator: 3
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # RF packets forwarded: 3 (69 bytes)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # PUSH_DATA datagrams sent: 3 (733 bytes)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # PUSH_DATA acknowledged: 100.00%
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ ### [DOWNSTREAM] ###
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # PULL_DATA sent: 1 (100.00% acknowledged)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # RF packets sent to concentrator: 0 (0 bytes)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # TX errors: 0
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # TX rejected (collision packet): 0.00% (req:96, rej:0)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # TX rejected (collision beacon): 0.00% (req:96, rej:0)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # TX rejected (too late): 0.00% (req:96, rej:0)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # TX rejected (too early): 39.58% (req:96, rej:38)
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # BEACON queued: 0
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # BEACON sent so far: 0
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # BEACON rejected: 0
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ ### [PPS] ###
Sun Apr 25 09:55:40 2021 daemon.info lora_pkt_fwd[31113]: REPORT~ # SX1301 time (PPS): 2534747127

The terminal

for OTAA

APP_VERSION:        V1.0.0
MW_LORAWAN_VERSION: V2.2.1
MW_RADIO_VERSION:   V0.0.1
###### OTAA ######
###### AppKey:  2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C
###### NwkKey:  2B 7E 15 16 28 AE D2 A6 AB F7 15 88 09 CF 4F 3C
###### 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:  39-30-30-30-73-36-69-18
###### AppEui:  01-01-01-01-01-01-01-01
0s057:TX on freq 868100000 Hz at DR 0
1s581:MAC txDone
6s613:RX_1 on freq 868100000 Hz at DR 0
6s812:MAC rxTimeOut
7s613:RX_2 on freq 869525000 Hz at DR 0
7s812:MAC rxTimeOut

###### = JOIN FAILED
10s099:temp= 24
10s100:VDDA= 254

When Changed to ABP

###### = JOINED = ABP ======================
30s056:temp= 25
30s057:VDDA= 254
30s060:TX on freq 868500000 Hz at DR 0
30s068:SEND REQUEST
31s715:MAC txDone
32s748:RX_1 on freq 868500000 Hz at DR 0
32s947:MAC rxTimeOut
33s748:RX_2 on freq 869525000 Hz at DR 0
33s947:MAC rxTimeOut

###### ========== MCPS-Confirm =============
60s056:temp= 25
60s057:VDDA= 254
2

No. This is perfectly normal. LoRaWAN does not send data to a device unless there is an urgent need (sending data back does not scale as a gateway can only transmit one packet at a time and at that time it is not receiving anything, at all other times it might be receiving up to 8 transmissions)
The message basically means: “I’ve listened for incoming data at the agreed times and didn’t get any”. Perfect. If you would be receiving data on every transmit you would be breaking the TTN Fair Access Policy anyway, that allows for just 10 packets to a node a day, including acknowledgements.

The gateway log shows data has been received and forwarded to TTN which indicates things are fine too.

In the TTN console do you see any activity in the devices data page? If the DevEUI, AppEUI and AppKey match you should see a join (ligtning symbol). Given the lack of response to the join request one of these might not be matching. You can take a look at the gateway traffic page as well and check it lists two join symbols.

Looking at the signal strength you might need to move you node further away from the gateway. Make sure there is at least 4 meters and preferably a wall between the two.

1 Like
3

Sorry for the late reply, I thought I sent this already. Thank you very much for your reply, it helped a bunch with my investigation.

Oh thank you, just now I realized I can check the gateway in the console.

I will probably have to configure the device into the console right?

So I see it in the gateway:
image

I persume for TTN to recognize it, I will have to register the end node as an application (and make sure application ID in the page matches the one in my device)

image
image1035×120 3.28 KB

4

Yes! Probably helpful to you if you read:

Read all of: https://www.thethingsnetwork.org/docs/lorawan/
The devices section of: https://www.thethingsnetwork.org/docs/devices/
The gateways section of: https://www.thethingsnetwork.org/docs/gateways/
The network section of: https://www.thethingsnetwork.org/docs/network/
The applications and API sections of: https://www.thethingsnetwork.org/docs/applications/

1 Like
5

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.