LDS01 rxTimeOut

End Devices (Nodes) Dragino
1

Hi, I don’t have much experience with TTN installations. I bought a TTIG gateway mod.TBMH100 on RS and registered it without major problems on TTN. I connected it to my wiFi and on the TTN console it is connected. I also bought Lorawan Dragino LDS01 Door Sensors. As soon as I turn them on I see them on the Traffic section of the Panel of my gateway. Now I would like to route these messages to a mqtt server but how should I proceed? First I guess I have to register the individual LDS devices in the device section as well. I created an application and registered a device, but the status of the device is never seen.

If I look at the sensor log I see:
[3322] DRAGINO LDS01 Device
[3324] Frequency Band: EU868 v1.3
[3327] OTAA
[3328] DevEui = A840XXXXXXXX9816
[3331] class type A
[3332] intra freq mode

[3336] ***** UpLinkCounter = 0 *****
[3347] TX on freq 868300000 Hz at DR 5
[3357] Start to Join, method 1, nb_trials: 48
[3421] txDone
[8407] RX on freq 868300000 Hz at DR 5
[8442] rxTimeOut
[9414] RX on freq 869525000 Hz at DR 3
[9457] rxTimeOut

[10358] ***** UpLinkCounter = 0 *****
[10362] TX on freq 868300000 Hz at DR 5
[10436] txDone
[15423] RX on freq 868300000 Hz at DR 5
[15458] rxTimeOut
[16429] RX on freq 869525000 Hz at DR 3
[16472] rxTimeOut

But what am I wrong? Maybe they are not compatible? Thanks for the help you can give me.

2

Did you read the manual?
I suggest to look at page 7 and 8 .

1 Like
3

Excellent, that means data is flowing to TTN. It also means you are using TTN V2 as TTIG does display gateway traffic in V3.

The most common error with these devices is typing errors in the DevEUI, AppEUI or AppKey. Please check these carefully (8 and B are often an issue).

Did you issue any commands to the sensor to change settings? Because for the join phase the second RX window (the one at 869525000 Hz) should use DR0, not DR3.

This combination should work fine.

4

Thanks so much. I reread the manual. I didn’t realize that I had to re-enter the KEY APP as well. Thanks now it’s better …

[3370]DRAGINO LDS01 Device
[3372]Frequency Band: EU868 v1.3
[3375]OTAA
[3376]DevEui= A840417361829816
[3379]class type A
[3381]freq mode intra

[3385]***** UpLinkCounter= 0 *****
[3395]TX on freq 868100000 Hz at DR 5
[3405]Start to Join, method 1, nb_trials:48
[3469]txDone
[8456]RX on freq 868100000 Hz at DR 5
[8540]rxDone
+CJOIN:OK
[8550]Joined

[8637]***** UpLinkCounter= 0 *****
[8641]TX on freq 867500000 Hz at DR 0
[10136]txDone
[11163]RX on freq 867500000 Hz at DR 0
[11370]rxTimeOut
[12129]RX on freq 869525000 Hz at DR 3
[12302]rxDone

OK+SENT:01
[12311]receive data: rssi = -41, snr = 10, datarate = 3

OK+RECV:00,00,00

5

Thanks. I still have a TimeOut rx. What parameters should I change exactly?

6

You don’t need to change anything as the sensor is working according to your logs. RX timeouts are normal for LoRaWAN, you should only receive data very infrequently, LoRaWAN is an uplink mostly protocol.

7

Thanks so much. With these objects (Gateway and sensors) could I also upgrade to V3 with The Things Stack? But do I have to remove these gateway and device registrations or can I leave these and register them on Things Stack too?

8

You can leave your gateway untouched at the moment.
As far as i know you can not migrate the TTIG by yourself to TTSv3.
You can already migrate your application and sensors to TTSv3.
The Traffic will be forwared through your v2 gateway to the v3 Stack.

Be aware that other users reported some issues with RX windows and a workaround:

As long as you have a console access to the LDS01 you can have an eye on this issue.

I am unsure if it is necessary and safe to delete your application and sensor from v2 Console.
But i am sure:
Do not delete your Gateway from v2 Console!

1 Like
9

thanks!