RAK 7200 reporting only stationary

Issue: RAK 7200 can’t send packets to TTN while moving

Setup: RAK7200 connecting to MikroTik LoRa8 GW

Server: ttn eu

Details: I started to measure LoRa coverage in my region with RAK 7200 tracker. Sadly - when I’m very close to my gateway (like 1000 meters) everything is OK. But when I drive further from it I can see traffic on my TTN app only when I stop (or slow down to 20km/h or so). What can be the issue?

Hi @rolfo,
Is this a 1km line of sight?
Could you provide some downlinks from TTN so we can see the SNR and RSSI values?
Also the response of “at+get_config=lora:status” to check if there are any problems with the node’s configuration.
The node should be with a disabled ADR function.
Also, the speed that you are moving with may be the problem.

There are issues with the way that radio propagates & reflects that can cause uplinks to be scrambled just enough they fail CRC.

Or words to that effect, I can’t find the original post where it was discussed.

Given allowed message intervals on TTN, driving is probably not a good way to do mapping, at least unless you have something like a mountaintop gateway overlooking a large flat area as in more typical circumstances a car would have you moving between coverage and non-coverage too quickly for packets spaced as widely in time as required to be able to capture.

You might start by walking or riding a bike.

1 Like


Work Mode: LoRaWAN
Region: EU868
Send_interval: 30s
Auto send status: true.
Send_interval work at no sleep
Join_mode: OTAA
Class: A
Joined Network:true
IsConfirm: unconfirm
AdrEnable: false
EnableRepeaterSupport: false
Current Datarate: 5
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 6162
DownLinkCounter: 0

I doesn’t matter if it is line of sight or no. ADR is disabled. So to conclude - can you confirm that the speed can be issue?

The problem is not the speed itself. As @cstratton said the problem may be that you are moving between areas with coverage and areas with no coverage too quickly, due to the speed. The effect is that the node dont have enough time in the coverage zone so the whole packet to be captured.

It actually matters. If you have a complete line of sight for the full test field that will eliminate the possibility for the node to move too fast from coverage to non-coverage areas.
Try to take a walk with the node on the same road and see if the problem remains.


I do have the same issue as Arthur.
I do have 3 devices and they only report position when they are stationary. While moving, they still comunicate and are able to send the position, but position is always on the static one. Start or stop of the movement.
Doesnt matter, if I walk… Bicycle or by car.


So I been playing around with RAK7200 with Helium network. The data is transmited and well decoded.
The only problem is, I can only get position, when the device is stationary. While moving, I can see the device can send data into the network ( so is not a problem into coverage) , but no position.
Do you Guys are able to get position, while moving with the device?

Hi @Carlos1,
I suspect that the GPS timeout is too little and it is not enough to fix GPS coordinates.
Can you give me the devise status using this command:

Best Regards,

===============Device Status List================
Board Core: S76G_B
LoRa chip: SX1276

Battery Voltage = 4.72 V
Support Gps:true
gps_timeout: 100s
gps_format:standard LPP format
No signal with Satellite.

MPU9250 sensor:
Acceleration(g) of X,Y,Z:
Gyro(degress/s) of X,Y,Z:
Magnetometer(uT) of X,Y,Z:

So, it is 100S currently