RAK2245 Pi HAT + Dragino LHT65 & TTN uplink problem

LPWAN Developer Gateways / Concentrators RAK2245 / RAK2243
1

Hi to all,
I need your help

Issue: RAK2245 PI HAT no uplink traffic

TTN screen_
TTN screen_1341×598 55.9 KB

Setup:

  • RAK2245 Pi HAT as gateway
  • DRAGINO LHT65 as lorawan end node EU868

Server:

  • TTN as network server

Details:

  1. RAK2245 is correctly connected with TTN

    RAK2245 as gateway
    RAK2245 as gateway1347×584 73.6 KB

  2. LHT65 correctly join network and send uplink
    Dragino LHT65 Device
    Image Version: v1.6

LoRaWan Stack: DR-LWS-003
Frequency Band: EU868
DevEui= A8 40 41 00 01 81 DC 05
Enter Password to Active AT Commands

JOINED

[953]***** UpLinkCounter= 0 *****
[954]TX on freq 868300000 Hz at DR 0
[2440]txDone
[3470]RX on freq 868300000 Hz at DR 0
[3670]rxTimeOut
[4435]RX on freq 869525000 Hz at DR 3
[4475]rxTimeOut

[48372]***** UpLinkCounter= 1 *****
[48373]TX on freq 867700000 Hz at DR 0
[49859]txDone
[50889]RX on freq 867700000 Hz at DR 0
[51089]rxTimeOut
[51854]RX on freq 869525000 Hz at DR 3
[51894]rxTimeOut

[60953]***** UpLinkCounter= 2 *****

[60954]TX on freq 867900000 Hz at DR 0
[62441]txDone
[63471]RX on freq 867900000 Hz at DR 0

[63671]rxTimeOut
[64436]RX on freq 869525000 Hz at DR 3
[64476]rxTimeOut

[120953]***** UpLinkCounter= 3 *****
[120954]TX on freq 867500000 Hz at DR 0
[122441]txDone
[123471]RX on freq 867500000 Hz at DR 0
[123671]rxTimeOut
[124436]RX on freq 869525000 Hz at DR 3
[124476]rxTimeOut

[180953]***** UpLinkCounter= 4 *****
[180954]TX on freq 867700000 Hz at DR 0
[182441]txDone
[183471]RX on freq 867700000 Hz at DR 0
[183671]rxTimeOut
[184436]RX on freq 869525000 Hz at DR 3
[184476]rxTimeOut

[240953]***** UpLinkCounter= 5 *****
[240954]TX on freq 867100000 Hz at DR 0
[242441]txDone
[243471]RX on freq 867100000 Hz at DR 0
[243671]rxTimeOut
[244436]RX on freq 869525000 Hz at DR 3
[244476]rxTimeOut

Please see below ./lora_pkt_fwd command

lora_pkt_fwd_1
lora_pkt_fwd_1751×698 231 KB

lora_pkt_fwd_2
lora_pkt_fwd_2745×669 112 KB

lora_pkt_fwd_3
lora_pkt_fwd_3754×673 131 KB

lora_pkt_fwd_4
lora_pkt_fwd_4758×681 101 KB

See below util_tx_test command result

util_tx_test
util_tx_test747×671 156 KB

thank you very much for help and sorry for my English

2

This is more a TTN question - as you say, the gateway is showing connected.

The data / traffic pages only show entries as they happen - they do not show historic data* and if you navigate away from the page for long enough or log out, it will be blank again when you go back.

  • If you have the FREE data storage integration turned on, it will pickup a few lines of historic data, bit random as to how many entries it shows.

So, add the data storage integration so you can start saving your data, go to the data page so you can see it and then get your Dragino device to send an uplink.

You can also have the traffic page open for the gateway - same rules, you only see it as it comes in.

3

Thank you very much for your help

So I’m going to do integration
I am keeping you in touch

4

Your packet forwader logs indicate you are getting CRC error packets, but not in that instant any valid ones.

Watch the packet forwarder logs longer; if you only see CRC error you need to figure out why. One the other hand, if you are getting valid packets at the concentrator, then the CRC errors are probably due to non-LoRa traffic falsely tripping the start of packet detection.

It may be premature to look at “data integration” or similar until you know that the gateway is receiving valid LoRa packets, as valid LoRaWAN packets can only be contained in valid LoRa ones, and so far your logs show only LoRa packets which have errors.

5

I had note that.
What could be the possible causes of these CRC_ERROR 100% that concern now all packets sent?

6

I’d first try to figure out if they are time correlated to your transmission attempts.

I believe you can modify the packet forwarder configuration file, or failing that the source code itself to pass on (and potentially print) packets with errors, then you could see if they bear any resemblance to what you were sending, in terms for frequency, SF, or timing (remember the raw packet will be encrypted, not the cleartext application one)

Also try to get several meters distance between the node and gateway; being too close can cause false reception on other channels, and possibly in an extreme case only garbled reception without any good reception on the true channel.

7

Actually I’ll put distance between the dragino and the gateway They were too close and I’ll see the lora_pkt_fwd after

8

CRC_ERROR persists with distances between gateway and node.

In what way do I need to change the packet forwarder configuration files to test?

9

Look at this part of the code and try the json key that would control it, also consider modifyin the source to print out more in the log in the case it controls:

10

Thanks I’ll try it now

11

Hi all
I think of something that could be the cause of the problem There are a lot of 890MHz GSM2 transmitter next to us Can be interference that alter the lorawan signal

13

This seems to have nothing to do with the topic of this thread.

Please create a new one. Explain exactly:

  1. What device you are using

  2. What you are trying to accomplish

  3. Why you are using “stone software tools” and not some more ordinary means of doing this