RAK7200 node, GPS tracker

Ricardo · March 23, 2020, 9:45am

the network server and gateway is our own implemented version. In this stage I’m not interested in the network server at all to unmarshall and decrypt any packet according to the keys and device address for any high-level application.

The issue here is a very low-level one in the network stack: Our own custom gateway receives LoRa packets and prints out the bytes received (even if not decrypt using NwksKey and forward to an Application Server, we really don’t care about that right now) from other trackers (SEMTECH SX1272 for instance) but not from the RAK7200 tracker. By sharing the same RF parameters shouldn’t I be receiving any LoRa packet in any way in our gateway’s LoRA transceiver or am I missing something here ?

leopold · March 23, 2020, 10:05am

Hi @Ricardo
In that case you should confirm the frequency list of RAK7200 with “at+get_config=lora:channel”,
then see if the supported frequency points of the gateway match the frequency points that 7200 has turned on.

focigod705 · March 25, 2020, 5:41pm

@leopold @Fomi

Do you know how to get the additional two digits of GPS data into The Things Network with the decoder? The decoder only shows 4 decimal places but the raw data in the serial port tool shows 6 decimal places.

TTN DATA
“gps”: {
“altitude”: “393.5m”,
“latitude”: “44.9833°”,
“longitude”: “-89.6449°”
},

DECODER SCRIPT
case 0x0188:// GPS
var gps = {};
gps.latitude = (parseTriple(str.substring(4, 10), 16) * 0.0001).toFixed(4) + “°”;
gps.longitude = (parseTriple(str.substring(10, 16), 16) * 0.0001).toFixed(4) + “°”;
gps.altitude = (parseTriple(str.substring(16, 22), 16) * 0.01).toFixed(1) + “m”;
myObj.gps = gps;
str = str.substring(22);
break;

JeroenKl · March 25, 2020, 7:10pm

@focigod705

With AT command:
at+set_config=device:gps_format:X
X means: <0: LPP format which is only 4 decimal digits accuracy>
<1: 6 decimal digits accuracy>

BR,
Jeroen

focigod705 · March 25, 2020, 7:54pm

Hi @JeroenKl,

I tried sending the command and found the following result.

at+set_config=device:gps_format:1
The AT Command is invalid.

Any other suggestions? Thanks for your help.

Is this AT command an update in the latest firmware? I am currently on 3.1.0.10.

Fomi · March 26, 2020, 2:33am

Hi @focigod705,

Which version firmware are you using?
I think it may be a lower version so that this AT command can’t be used.
You can download the latest firmware and the bootloader here:
https://downloads.rakwireless.com/en/LoRa/RAK7200-Tracker/Firmware/
Then flash them into your RAK7200 according to the document:
https://doc.rakwireless.com/rak7200-lora-tracker/burning-the-bootloader
https://doc.rakwireless.com/rak7200-lora-tracker/upgrading-the-firmware

focigod705 · March 26, 2020, 2:44am

Thanks @JeroenKl and @Fomi. After updating the firmware I was able to send the command. Thank you both.

focigod705 · March 26, 2020, 2:48am

@Fomi, will I need to adjust the payload decoder for TTN?

Fomi · March 26, 2020, 3:33am

Hi @focigod705,

Yes, we’re making another decoder for TTN now.

Fomi · March 26, 2020, 3:41am

you can use

github.com

RAKWireless/RUI_LoRa_node_payload_decoder/blob/master/RUISensorDataDecoder_for_TTN.js

// ttn application function to decode uplink data.
// Decode decodes an array of bytes into an object.
//  - port contains the LoRaWAN fPort number
//  - bytes is an array of bytes, e.g. [225, 230, 255, 0]
// The function must return an object
// for RAK, return {
//                     "DecodeDataHex": {} // RAK5205 sensor data in Hex format
//                     "DecodeDataObj": {} // RAK5205 sensor data object.
//                 }
// The function prototype cannot be modified.
function Decoder(bytes, port) {
  var decoded = {"DecodeDataHex": {}, "DecodeDataObj": {}};
  var hexString=bin2HexStr(bytes);
  decoded.DecodeDataHex = hexString;
  decoded.DecodeDataObj = rakSensorDataDecode(hexString);

  return decoded;
}

// convert array of bytes to hex string.

This file has been truncated. show original

for 4 digits precision gps data.

If you increased the precision(6 digits), you should use

github.com

RAKWireless/RUI_LoRa_node_payload_decoder/blob/master/RUISensorDataDecoder_GPS6digitPrecison_for_TTN.js

// ttn application function to decode uplink data.
// Decode decodes an array of bytes into an object.
//  - port contains the LoRaWAN fPort number
//  - bytes is an array of bytes, e.g. [225, 230, 255, 0]
// The function must return an object
// for RAK, return {
//                     "DecodeDataHex": {} // RAK5205 sensor data in Hex format
//                     "DecodeDataObj": {} // RAK5205 sensor data object.
//                 }
// The function prototype cannot be modified.
function Decoder(bytes, port) {
  var decoded = {"DecodeDataHex": {}, "DecodeDataObj": {}};
  var hexString=bin2HexStr(bytes);
  decoded.DecodeDataHex = hexString;
  decoded.DecodeDataObj = rakSensorDataDecode(hexString);

  return decoded;
}

// convert array of bytes to hex string.

This file has been truncated. show original

focigod705 · March 26, 2020, 4:12am

Wonderful. Thank you very much.

JeroenKl · March 27, 2020, 7:19pm

Hi @Fomi,

Can we expect a RUI based firmware soon?

BR,

Jeroen

JeroenKl · April 12, 2020, 7:24pm

Hi @Fomi,

Can we expect a RUI based firmware soon?

BR,

Jeroen

Fomi · April 13, 2020, 1:58am

Oh @JeroenKl,

I’m really sorry for late reply, especially your last post because i just see it…

About the new firmware for RAK7200 based one RUI, i’m afraid it will not be released soon.
Recently, my team are working on RAK modules linke RAK811, RAK4200, RAK4270, RAK4600, …
We want to focus on imporving these modules firstly (the first step), then improving RAK products like RAK7200 based on these modules’s new firmware (the second step). This is a re-optimized work.
Now, we are at the end of the first step, and the second step will start at the beginnig of the next month.

jazbond · April 24, 2020, 8:35pm

Hi Jeroen,
Waiting to buy a lot of trackers 7200 for my job. Seems to be a lot of bugs in the firmware. You have test it since a few months I have seen that. Could you please contact me at jazbond at gmail to discuss if you agree and give me your advice in private
Best
Jason

stephenb · May 21, 2020, 11:36am

@Fomi - I have been following this thread since Aug 2019. I would like to use this tracker if the internal antenna issue has been resolved. Have you an ETA of the new updated antenna being made available for sale? Thanks!

JeroenKl · May 24, 2020, 1:43pm

Hi Stefan,

I’ve got a 7200 tracker with the new internal antenna and works fine.
Of course is my 7200 with a tweaked external anttenna performing a little bit better, but that’s logical.

BR, Jeroen

stephenb · May 24, 2020, 1:55pm

Thanks @JeroenKl - I think I’ll use an external one.

mvcorrea · October 26, 2020, 5:58am

Hi there, anyway to visually detect the problematic antenna?
Just received the tracker, with latest firmware, only able to talk to GW if its around 40 meters!
Any help please!?

Board Core:  S76G_B
MCU:  STM32L073RZ
LoRa chip:  SX1276
----
Please Configurate parameters within 30 seconds ...
at+get_config=lora:status
OK Work Mode: LoRaWAN
Region: AU915
Send_interval: 180s
Auto send status: true.
Send_interval work at sleep
Join_mode: OTAA
DevEui: AC1F09FFFE003XXX
AppEui: 70B3D57ED0036XXX
AppKey: AC1F09FFFE00375AAC1F09FFFXXXXXX
Class: A
Joined Network:false
IsConfirm: unconfirm
AdrEnable: false
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 0, RX2_CHANNEL_DR:0
RX_WINDOW_DURATION: 0ms
RECEIVE_DELAY_1: 0ms
RECEIVE_DELAY_2: 0ms
JOIN_ACCEPT_DELAY_1: 0ms
JOIN_ACCEPT_DELAY_2: 0ms
Current Datarate: 0
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 0
DownLinkCounter: 0
lorasend_interval: 180s
MPU9250 Init OK
GPS Init OK
Initialization OK,Current work_mode:LoRaWAN, join_mode:OTAA, Class: A
gps_timeout: 100s
Configuration OK!
OTAA Join Start...
[LoRa]:Joined Successed!
Start Search Satellite(about 100 seconds) ...

in picture, circle radius is around 150 meters
Screen Shot 2020-10-26 at 03.04.15
and the antenna version/picture

nmcc · October 26, 2020, 11:14am

If you’ve opened the box up, you may want to very carefully unplug the uFl connection and try a different antenna to compare & contrast.