RAK7200 node, GPS tracker

[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.

[Fomi (Fomi Tong)]

Hi all,

We’ve modified the source code to fix the issue of Longitude avariable, and i think it mai be fixed now according to our testing.

Please try to test in your location using this firmware:
https://github.com/RAKWireless/Update-File/blob/master/RUI_RAK7200_V3.1.0.7.T3.bin

[Joolz2k1]

GPS was a bit too far east on the earlier firmware. I’ve managed to get a good hit on my house now Thanks!

[JeroenKl (Jeroen)]

Thanks @fomi,

The downloaded firmware T3, is after flashing named: RAK7200 version:3.1.0.7.T2
Currently under test.

BR,

Jeroen

[JeroenKl (Jeroen)]

Hi @leopold ,

Are you sure as the TTN console is not Cayenne. Cayenne will only use the LPP data forwarded from TTN server.
First LPP need to support it, I’ll investigate and get back to you asap.

regards,

Jeroen

[pe1mew (Remko Welling)]

Hi, Some testing toady here with T1 version. There is progress as I can see!
here is the same route today by the same two trackers I used last sunday:

Reference tracker:

RAK7200 tracker:

I will now program T3 version.

[HansRak (Hans)]

Hi Fomi,

Below the device status in Serial Port Tool with your latest firmware:

• version 3.1.0.7.T2 (T2, not T3 as .bin filename)

• LPS22HD sensor is closed or not found

The MPU9250 sensor (indoor and stable on my desktop):

• Acceleration(g) of X,Y,Z: 0.02,0.07,0.99

• Gyro(degress/s) of X,Y,Z: -1.61,0.45,0.71

• Magnetometer(uT) of X,Y,Z: 28.65,52.95,55.05

The indoor GPS position is accurate (The Netherlands) and pretty constant over time. Altitude value is constant but wrong, this is a common problem with all GPS modules I have tested so far.

Best regards, Hans.

[jchonig (Jeffrey Honig)]

One nit is that V3.1.0.7.T3 identifies as T2 in at+version.

The GPS data is now reporting and correct.

A feature request would be a GPS tracking mode where the device would send a packet every X seconds if the GPS position has not changed more than a given distance. If it did change it would send a packet every Y seconds. This would be useful when trying to provide data to ttnmapper.org.

[HansRak (Hans)]

Hi Jeffrey,

Like the idea but constant checking distance changes (or speed) will drain the battery I’m afraid.

Best regards, Hans.

[JeroenKl (Jeroen)]

I should say, as already provided some posts ago:

wake up> check previous GPS coordinates > movement? >

• Yes> transmit data and store/save coordinates for next check > sleep
• No > sleep

as an addition, after 30 min of no movement, transmit data once

[jchonig (Jeffrey Honig)]

I would envision sending a packet every 600 seconds unless the position changes, then send every minute. That won’t be much different than sending a packet once a minute.

[jchonig (Jeffrey Honig)]

Sending a position every 5 minutes if you are not moving vs every minute if you are not shouldn’t be significanly different change over sending a position every minute.

[JeroenKl (Jeroen)]

…or make it AT configurable as it depens how you want to use the tracker.
I do not need an update if there is no movement but like to have it in 30 min to know if the tracker is alive and to know the battery status.

[jchonig (Jeffrey Honig)]

Agreed, sorry I didn’t explicitly say this should be a configurable mode. It would be great for ttnmapper.org, but less useful for other things.

[JeroenKl (Jeroen)]

Dear @fomi,

For me there is no difference with regards the GPX fix. This is the data from the tracker, no movement, clear sky:

and TTN mapper:

It needs further investigations.

BR,

Jeroen