RAK7200 node, GPS tracker

[JeroenKl (Jeroen)]

Latest testfirmware 3.1.0.7.T outside placed.
GPS timeout=100sec

• RAK development team: advice to check first if the GPS has a real fix with minimal sat’s before sending Lora data.
• Also advice to introduce an option to put the tracker NOT into sleep mode during movement (>3km/h speed), works great with my TTGO-T-Beam

[JeroenKl (Jeroen)]

No movement, GPS timeout=100 sec, clear sky view, Cayenne result:

[cstratton (Chris)]

Enjoy your vacation in Banff, it’s really beautiful

[pe1mew (Remko Welling)]

Hi, Yesterday I walked around a gateway with two trackers: TTGO T-Beam and the RAK7200. Both ware in the same backpack.

This is the route logged by the TTGO T-Beam:

The RAK7200 was NEVER heard on this track!.

Before I left I verified that the RAK7200 was working. I extended GPS search time to 2 minutes to have a fix and location.

[Fomi (Fomi Tong)]

Maybe we should compile a firmware which will not sleep all time.
Just for testing GPS position.

[velev (Todor Velev)]

Around 5 km driving, data sent - 60 seconds, GPS timeout 60 seconds.

Cayenne is also back

[JeroenKl (Jeroen)]

Dear @velev,

I’m not sure what you want to tell with your update. The majority reports issues.
Today, arround 2x 27km driving (by car), NO GPS fix with 100seconds time-out.

You are testing it with a RAK5205 instead of a 7200. Also you have a temp/hum sensor which the 7200 doesn’t have.
To be honest, it is not the same as the 7200 so if you want to share your experiences, please use at least the same device.

[JeroenKl (Jeroen)]

Dear @fomi,
Yes please, and even better make at as an AT command option.
sleep, no-sleep

[Fomi (Fomi Tong)]

OK, will do it ASAP.

[HansRak (Hans)]

Dear RAK people,

As an owner of your new RAK7200 I must, unfortunatelly, confirm most or even all above mentioned issues and I am counting on RAK to solve these problems soon. Furthermore I wonder why Todor has placed the image of the RAK7205 Cayenne overview as Jeroen also noted.

Kind regards, Hans.

[Fomi (Fomi Tong)]

Hi all,

We’ve compiled a firmware for RAK7200. In this version, you can set whether RAK7200 will go to sleep after sending a packet.
Please download it from here:
https://github.com/RAKWireless/Update-File/blob/master/RUI_RAK7200_V3.1.0.7.T1.bin

The AT command is this one:

In this version firmware, you can use this AT command and set X to 2 which means RAK7200 will send packet every Y seconds too, but after sending, RAK7200 will not go to sleep.
For example, “at+set_config=lora:send_interval:2:10” means RAK7200 will wait for 10 seconds after sending a packet without sleep, then it will prepare another packet for sending.

BTW, we’ve add the LEDs function in this version too.
Please try to test with this firmware.

[HansRak (Hans)]

Hi Fomi,

Thanks for the new version! Just wanted to test your new firmware but updating went wrong with the LoRaButton Upgrade Tool. Not sure what I am doing wrong now and I did not discover any update problems before using the same setup and PC.

After pressing the Upgrade Tool start button it shows “Open Serial Port” and a few seconds later “Time out error, Please click STOP to restart operation”. The port connection should not be the problem, this because the Serial Port Tool works and shows firmware version 3.1.0.7 with command “at+version”. Pressing the reset button as suggested bij Todor Velev (RAK7200, updater tool and firmware) did no work in my case.

Any solution?

Best regards, Hans.

[velev (Todor Velev)]

Hi @HansRak
Do you try to put RAK7200 in boot mode?
at+set_config=device:boot
Disconnect from RAK Serial Port Tool and then update with RAK LoRaButton Upgrade Tool.

[HansRak (Hans)]

Hi,

My mistake, I was not fully awake yet Problem solved, thanks for your quick response! Now updating and testing later today.

Best regards, Hans.

[JeroenKl (Jeroen)]

Currently under test. Curious!

First impression:

• Charge LED and TX LED are working
• at+set_config=lora:send_interval:2:10 works great. TX Interval is 10sec + packet_ready-time = approx 25 sec.
  
• Magneto sensor accoring to LPP standard, not fixed yet:
  {
  “accelerometer_3”: {
  “x”: -0.006,
  “y”: 0.003,
  “z”: 0.95
  },
  “analog_in_10”: -33.45, <<<<<
  “analog_in_11”: 3.15, <<<<<
  “analog_in_8”: 3.82,
  “analog_in_9”: 44.25, <<<<<
  “gps_1”: {
  “altitude”: 7,
  “latitude”: xx.2657,
  “longitude”: xx.1832
  },
  “gyrometer_5”: {
  “x”: -0.03,
  “y”: -1.31,
  “z”: -0.02
  }
  }

-TTN mapper, without physical tracker movement, clear sky view:

NOT ok

During car-driving:
Not too bad!

BR,

Jeroen

[leopold (wang)]

Hi,@ JeroenKl
Do you have the document about LPP standard? We find the LPP document support Cayenne no Magneto sensor.

[JeroenKl (Jeroen)]

Hi @wang,

I’ll check for you, but should it not be in between as MagnetometerID is 3314?

So the LPP ID is 114?

Cayenne accepts somehow Magnetometers:

Data types for Cayenne MQTT API

I’ll search further, but will be later today due to work.

BR,

Jeroenkl

[JeroenKl (Jeroen)]

Hi @Fomi,

I think there is something wrong with the GPS, data, clock regarding the Longitude variable.
Only this variable is sometimes sending wrong data:

What can we do about it?

Checking the TTN console I indeed see this variable ‘hopping’.

BR,

Jeroenkl

[leopold (wang)]

Hi,@JeroenKl
If I set LPP ID is 114(0x72),all sensor data can’t decode by LPP format.So I think Cayenne don’t suppot magnetometers.

[leopold (wang)]

Yes,we found that Longitude variable indeed have abnormal numerical.we will verify it.