RAK7258 + RAK7200 - working distance less than 10 meters

Issue: NO signal between Lora Gateway 7248 and GPS tracker 7200 in a range over than 5, 10 meters

Setup: I did an OTAA Piaring of the rak 7200

LoRa® Server:

Details:
I’m living in France in an urban area in a 1 floor house, surrounded by houses mainly with 2 floors.


I’ve been walking outside between 15h10 and 16h30. Staying around 10 to 15 minutes on points 1 - 2 - 3 .

Duing that time the traker tried to send 10 dataset I think (fCnt values from 31 to 42) and all has been lost,
Connection between the tracker and the gateway came back when I enter back home. (I only have a link between the gateway and the tracker beeing at home. Outside I never succeed during 1 month I’m trying the devices)
Inside home I’ve no fix with GPS, only sometime when I put the tracker outside beside a window (accuracy is not so bad)

When I bought a 7248 gateway and a RAK7200 gps tracker for tests, I expectied to have really quite better performances. Surely not kilometers but a least hundreds fo meter.
And my assumption whas to buy an antena in order to reach my initial goal to get tracking signal in a range of 3 to 5 kilometers.

Do you think that it’s still possible? Or do i’ve to forget all.
I saw 5,8 ,12 or 15db antenas, but with a 5-10 meters wire to connect the antena to the gateway does it make sense?
If yes wich (kind) antena could really help me?
Which antena are you using to replace the 2db antena which is coming with de gateway?

Reading a lot of closed post here, I feel that I’m not alone with such issue.
I hope also that I did a missusage of the gateway and the tracker.
Or a bad configuration.
any suggestion is really welcome to make me feeling better with this material.

I also bought another tracker (Dragino). I’ve been able to pair it with the application (OTAA also), but I’m not able to finilize the configuration as I do not see any way to add the decoding for it.

I saw an old post ( almost 2 years) saying that it should come in a next release.
Is it still foreseen, or do I have to stick with only rak devices paired witha rak 7258 gateway.
How could I add decoding for a non rak device if it’s possible?

Many thanks for reading and for all answers that wil perhaps come :wink:

Regards

The antenna inside RAK7200 doesnt works fine, it is just a FPC but when we test it over a truck in a desert, it works fine. We configure it with no ACK (best effort) and the result was couple KMs withput LOS.

can you share us your AT config?
Matt

Thanks a lot for your so fast answer :wink:

That configuration?

If you mean something else I will share

Also about a better outdoor antena, which one would you advice?

Where is your gateway - inside, next to a window, in the centre of the building that is made of concrete & rebar?

Try on the window sill and then go outside with your tracker in your hand so that you can still see the window.

For tracking applications, ABP is better as it doesn’t rely on an initial OTAA join.

HI,

The walls are made with bricks (~40, 60 cm).
The gateway is on the backside of the house, 1rst floor, on the bottom nearby a window.

You can see the yellow mark on the picture (on the grey roof), and around the “houses” have a 2nd floor (brick walls)

image
Do you think it could be better if I try to move the gateway 8 meters on the right to the front window where I put the green mark?
There the rak7200 gps tracker sometime get agps fix when I let it ouyside on the border of the window.

I will also try to change the setup to ABP.
Can I keep the current address, or do I’ve to change it?

Would an outdoor antena help?
Which kind?

For the moment, it is a “test location”. The final destination of the gateway is some kilometers away in a less dense zone.


My goal is to make it working here at home on my test location in order to be able to cover a range of 2-3 kilometers with an antena.

I’ve done these changes:
On the tracker side

at+set_config=lora:app_key:88A…
OK

at+set_config=lora:dev_addr:02000002
OK

at+set_config=lora:nwks_key:bbcd…
OK

at+set_config=lora:apps_key:f3eac…
OK

at+get_config=lora:status
OK Work Mode: LoRaWAN
Region: EU868
Send_interval: 300s
Auto send status: true.
Send_interval work at sleep
Join_mode: ABP
DevAddr: 02000002
AppsKey: F3EA…
NwksKey: BBC…
Class: A
Joined Network:false
IsConfirm: unconfirm
AdrEnable: true
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 869525000, RX2_CHANNEL_DR:0
RX_WINDOW_DURATION: 3000ms
RECEIVE_DELAY_1: 1000ms
RECEIVE_DELAY_2: 2000ms
JOIN_ACCEPT_DELAY_1: 5000ms
JOIN_ACCEPT_DELAY_2: 6000ms
Current Datarate: 3
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 663
DownLinkCounter: 10

at+get_config=lora:channel
OK *0,on,868100000,0,5; *1,on,868300000,0,5; *2,on,868500000,0,5; 3,off,0,0,0; 4,off,0,0,0; 5,off,0,0,0; 6,off,0,0,0; 7,off,0,0,0; *8,on,868300000,6,6; *9,on,868800000,7,7; *10,on,867500000,0,5; *11,on,867700000,0,5; *12,on,867900000,0,5; 13,off,0,0,0; 14,off,0,0,0; 15,off,0,0,0
ABP:
DevAddr: 02000002
AppsKey: F3EA…
NwksKey: BBCD…
[LoRa]:Joined Successed!

on the Gateway

The tracker is linked with the gateway,

but since, the gateway is totaly unstable.
I can use the web app for 10, 40 seconds and I’m back to the connexion panel where I’ve to enter my credentials.

What did I do so wrong that all is broken.
Or is there no link with what I did to link the tracker on ABP mode??

Below is what I see in the system log now, but it doesn’t ring a bell on my side!

2021-05-11 16:47:23 UTC

Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: ### [UPSTREAM] ###
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # RF packets received by concentrator: 0
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # CRC_OK: 0.00, CRC_FAIL: 0.00, NO_CRC: 0.00
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # RF packets forwarded: 0 (0 bytes)
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # PUSH_DATA datagrams sent: 1 (135 bytes)
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # PUSH_DATA acknowledged: 100.00
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: ### [DOWNSTREAM] ###
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # PULL_DATA sent: 6 (100.00 acknowledged)
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # RF packets sent to concentrator: 0 (0 bytes)
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # TX errors: 0
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # BEACON queued: 0
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # BEACON sent so far: 0
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # BEACON rejected: 0
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: ### [JIT] ###
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # SX1301/SX1302 time (PPS): 1443801143, offset us 0
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: ### [GPS] ###
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: # GPS sync is disabled
Tue May 11 18:47:23 2021 user.notice lora_pkt_fwd[1657]: ##### END #####
Tue May 11 18:47:24 2021 kern.info quectel-CM[4349]: requestRegistrationState2 MCC: 208, MNC: 20, PS: Detached, DataCap: UNKNOW
Tue May 11 18:47:24 2021 kern.info quectel-CM[4349]: Dail Failed 30
Tue May 11 18:47:29 2021 kern.info quectel-CM[4349]: requestRegistrationState2 MCC: 208, MNC: 20, PS: Detached, DataCap: UNKNOW
Tue May 11 18:47:29 2021 kern.info quectel-CM[4349]: Dail Failed 31
Tue May 11 18:47:34 2021 kern.info quectel-CM[4349]: requestRegistrationState2 MCC: 208, MNC: 20, PS: Detached, DataCap: UNKNOW
Tue May 11 18:47:34 2021 kern.info quectel-CM[4349]: Dail Failed 32
Tue May 11 18:47:39 2021 kern.info quectel-CM[4349]: requestRegistrationState2 MCC: 208, MNC: 20, PS: Detached, DataCap: UNKNOW
Tue May 11 18:47:39 2021 kern.info quectel-CM[4349]: Dail Failed 33
Tue May 11 18:47:39 2021 kern.info quectel-CM[4349]: QmiWwanThread exit
Tue May 11 18:47:39 2021 kern.info quectel-CM[4349]: main exit
Tue May 11 18:47:41 2021 kern.info quectel-CM[5859]: WCDMA<E_QConnectManager_Linux&Android_V1.1.38
Tue May 11 18:47:41 2021 kern.info quectel-CM[5859]: /usr/sbin/quectel profile[1] = (null)/(null)/(null)/0, pincode = (null)
Tue May 11 18:47:41 2021 user.notice root: echo 1 > /sys/class/gpio/gpio2/value
Tue May 11 18:47:42 2021 kern.info kernel: [10094.280000] usb 1-1: USB disconnect, device number 54
Tue May 11 18:47:42 2021 kern.info kernel: [10094.290000] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
Tue May 11 18:47:42 2021 kern.info kernel: [10094.310000] option 1-1:1.0: device disconnected
Tue May 11 18:47:42 2021 kern.info kernel: [10094.320000] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
Tue May 11 18:47:42 2021 kern.info kernel: [10094.330000] option 1-1:1.1: device disconnected
Tue May 11 18:47:42 2021 kern.info kernel: [10094.340000] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
Tue May 11 18:47:42 2021 kern.info kernel: [10094.360000] option 1-1:1.2: device disconnected
Tue May 11 18:47:42 2021 kern.info kernel: [10094.370000] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
Tue May 11 18:47:42 2021 kern.info kernel: [10094.380000] option 1-1:1.3: device disconnected
Tue May 11 18:47:42 2021 kern.info kernel: [10094.420000] qmi_wwan 1-1:1.4 wwan0: unregister ‘qmi_wwan’ usb-101c0000.ehci-1, WWAN/QMI device
Tue May 11 18:47:42 2021 daemon.notice netifd: Network device ‘wwan0’ link is down
Tue May 11 18:47:42 2021 daemon.notice netifd: Interface ‘wwan’ has link connectivity loss
Tue May 11 18:47:42 2021 daemon.notice netifd: wwan (4675): Read error: Network is down, reopening socket
Tue May 11 18:47:42 2021 daemon.notice netifd: Interface ‘wwan’ is disabled
Tue May 11 18:47:42 2021 daemon.notice netifd: wwan (4675): udhcpc: bind: No such device
Tue May 11 18:47:42 2021 user.notice root: echo 0 > /sys/class/gpio/gpio2/value
Tue May 11 18:47:53 2021 user.notice lora_pkt_fwd[1657]:

2021-05-11 16:47:53 UTC

Thanks to Valimir’s help Ive been able to see again the GUI

I did a first test, still with OTAA some days ago.

and today I did another.being configured in ABP.
I can’t really say that it is better.
From the gateway on the fisrt floor, window open, I walked from home (yellow mark) to marks 1, 2, 3, 4 5, staying 7,8 minutes on each location.

On locatoin 2 I was able to see the antena of the gateway.
From other points, the window was visble or at least the white frame around.
I never got any gps fix in 1 hour outside, and just got link with the gateway on marks 1 and 2.
So no more than 30 meters which is quite low!

For me there are too much lost packets

Could really an extranal antena help?
Or which setup would improve the working distance?

Is there someone using the 7200 GPS device?
For me it’s seems that it is not working in an urban area?

Regards

@Flip ,

An external antenna will definitely help with the LoRa Range, however the GPS should work independently in a way. You said no GPS coordinates, what is the GPS tiomeout you have set, what about the transmission interval?

Regards
Vladislav

Hi Vladimir,

Which antena could you advice in order to cover a radius range between 2 and 3 kms in a not so dense urban region like on the pictures above (if such a coverage makes sense - I heard about 10km for lora … but perhaps only in very best conditions?)

According to what I remember, I set 5 minutes for interval transmission and let default 100 secs for gps timeout.

But in order to be sure, below are my device feedback from the RAK Serial tool:

Wake up .
GPS Init OK
Start Search Satellite(about 100 seconds) …
FAIL.The Satellite signal not found!
Battery Voltage = 3.548 V
Acceleration(g) of X,Y,Z:
0.09,0.56,0.81
Gyro(degress/s) of X,Y,Z:
0.71,1.74,0.70
Magnetometer(uT) of X,Y,Z:
73.50,5.25,-29.70

>>at+get_config=lora:status
OK
Work Mode: LoRaWAN
Region: EU868
Send_interval: 300s
Auto send status: true.
Send_interval work at sleep
Join_mode: ABP
DevAddr: 02000002
AppsKey: F3EA…
NwksKey: BBCD…
Class: A
Joined Network:true
IsConfirm: unconfirm
AdrEnable: true
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 869525000, RX2_CHANNEL_DR:0
RX_WINDOW_DURATION: 3000ms
RECEIVE_DELAY_1: 1000ms
RECEIVE_DELAY_2: 2000ms
JOIN_ACCEPT_DELAY_1: 5000ms
JOIN_ACCEPT_DELAY_2: 6000ms
Current Datarate: 0
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 1488
DownLinkCounter: 19

>>at+get_config=lora:channel
OK
*0,on,868100000,0,5;
*1,on,868300000,0,5;
*2,on,868500000,0,5;
3,off,0,0,0;
4,off,0,0,0;
5,off,0,0,0;
6,off,0,0,0;
7,off,0,0,0;
*8,on,868300000,6,6;
*9,on,868800000,7,7;
*10,on,867500000,0,5;
*11,on,867700000,0,5;
*12,on,867900000,0,5;
13,off,0,0,0;
14,off,0,0,0;
15,off,0,0,0

These parameters are perhaps radio parameters? (some values seems to be my regional radio frequency, but others are quite fuzzy :wink: )

What do mean the stars before some numbers like 0, 1,2,8,…?

Regards

@Flip ,

Ok maybe start by turning ADR off:
at+set_config=lora:adr:0

Seems like the channels are a bit messed up, maybe do a little adjustment:
at+set_config=lora:ch_mask:8:0
at+set_config=lora:ch_mask:8:0
at+set_config=lora:ch_mask:3:1
at+set_config=lora:ch_mask:4:1

Adjust the GPS time:
at+set_config=device:gps_timeout:120

Give it a test and see what packets arrive.

Regards
Vladislav

One thing to check is that the antenna on the gateway is in OK.

The SMA connectors have a very slender centre pin that can easily get out of alignment - if it doesn’t connect properly it’s like not having an antenna at all.

Also, worth checking that the U.FL connector inside the tracker is firmly connected and you aren’t carrying it in a tin box.

Hi Valdimir,

TRhank’s a lot for your answer.
You wrote 2 times:
at+set_config=lora:ch_mask:8:0

Do I’ve really to apply that commande twice?

Thans a lot also Nick.

I will check the antena on the gateway and also open the tracker to chack the antena

Regards

@Flip ,

It was a typo, should have been:
at+set_config=lora:ch_mask:9:0

Regards
Vladislav

HI,

Last Sunday I applied your proposal

Wake up .
GPS Init OK
Start Search Satellite(about 120 seconds) …

at+set_config=device:gps_timeout:120
OK

at+set_config=lora:ch_mask:9:0
OK

at+set_config=lora:ch_mask:8:0
OK

at+set_config=lora:ch_mask:3:1
OK

at+set_config=lora:ch_mask:4:1
OK

And got the following conf:

at+get_config=lora:status
OK Work Mode: LoRaWAN
Region: EU868
Send_interval: 300s
Auto send status: true.
Send_interval work at sleep
Join_mode: ABP
DevAddr: 02000002
AppsKey: F3EAC080342AE409D738A8DDB8BE9E59
NwksKey: BBCDD875CBAF37B57B45B92925D425CB
Class: A
Joined Network:true
IsConfirm: unconfirm
AdrEnable: true
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 869525000, RX2_CHANNEL_DR:0
RX_WINDOW_DURATION: 3000ms
RECEIVE_DELAY_1: 1000ms
RECEIVE_DELAY_2: 2000ms
JOIN_ACCEPT_DELAY_1: 5000ms
JOIN_ACCEPT_DELAY_2: 6000ms
Current Datarate: 0
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 1698
DownLinkCounter: 19

at+get_config=lora:channel
OK
*0,on,868100000,0,5;
*1,on,868300000,0,5;
*2,on,868500000,0,5;
*3,on,0,0,0;
*4,on,0,0,0;
5,off,0,0,0;
6,off,0,0,0;
7,off,0,0,0;
8,off,868300000,6,6;
9,off,868800000,7,7;
*10,on,867500000,0,5;
*11,on,867700000,0,5;
*12,on,867900000,0,5;
13,off,0,0,0;
14,off,0,0,0;
15,off,0,0,0

But at the end I don’t really see any changes
I’ve still a lot of lost packet, even when the tracker is close to the gateway

As proposed I checked the sma connection on the gateway.
I removed it and fix it again as much as possible.

I checked the tracker

When I’ve a global look on the devices, the gateway is loosing almost 36% of the packets, which is I think too much (and most of the time the tracket is around 50 cm from the gateway!)

Compared to the other tracker (whose sending frequence is its default one - not yet customized) there is a big difference a there is no lost packets


but only 22 uplinks

For the moment as I don’t know how I could decode its payload on the gateway, I’ve not done more customization.
But if someone knows if it’s possible to add some decoding function on the gateway, I wil try to follow the instructions for implementing de decoding function of that non-rak tracker.

Regards

Hei,

It might be it is too close, sometimes this leads to issues. Try going 10 meters away and observing again, though I doubt this is it. I would replace the antenna with an external one, perhaps a gluestick monopole.
Is the other tracker another RAK7200.
Sorry might be repeating myself, but it has been some time since the discussion started.

Regards
Vladislav

Hi Vladimir,

Don’t worry you’re so kind to help me.
It’s not an issue to repeat things, you’re welcome and as I start to become old I’m used to repeat myself (or perhaps it’s absolutely normal with childs and wife :wink: )

The other tracker is a Dragino LGT-92 LoRaWAN GPS Tracker with 9-axis accelerometer-LGT92 with its red alert button I wanted to use.

About an external antena, which one would you advice?
That mikrotik (1m) for which I saw good ratings MikroTik Routers and Wireless - Products: Antenna kit for LoRa®
or a RAK one like that one 80cm: Fiber Glass Antenna | LoRa High Gain Antenna | Long Range Frequency Antenna – RAKwireless Store

I’ve moved the tracker on another window sill, 5 meter away from the gateway,
I will see if it there are changes.

Regards

Hei,

I was thinking something a lot more portable:

Together with one of these:

Should be less bulky than the outdoor antennas, but still pretty good.

Regards
Vladislav

Thanks Vladimir,

I will buy those 2 accessories that are quite affordable and see the benefit.

Otherwise, about connecting the other tracker (the Dragino one) do you know how to decode it’s payload.
I don’t find any tab for that like in “normal” ChirpStack server.

Or does it mean that the only way is to install a ChirpStack server (on a rpi?) beside the gateway and forward all payloads to it whic will perform the decoding?

Regards

Hei,

There is no custom payload functionality available. Only option is Cayenne LPP.
So for your Dragion you would have to do post processing beyond the gateway I suppose. Perhaps use the HTTP integration to send it to an end point or the MQTT Global integration to a broker.
The RAK7200 should work with the Cayenned payload format, no problem.

Regards
Vladislav

HI,

Thanks a lot.
I will investigate and try either to turn the payload in Cayenne LPP format, or install a MQTT broker somwhere in order to get the raw payload and work with it

Regards