I have been using 0.1.3 for a number of months. Today I upgraded to 0.1.6 but when I attempt to compile with the 0.1.6 version, I get a number of errors of the “lib/LIS3DH/LIS3DH.h:20:2: ‘int16_t’ does not name a type”. I am using firmware 0.6.0 and the web development environment.
My code have #include “Particle.h” and #include "math.h"
The first line of my .ino is // This #include statement was automatically added by the Particle IDE.
I released version AssetTrackerRK 0.1.7 that uses an updated version of the LIS3DH library with a LIS3DH.h that includes Particle.h so you won’t get that error if you don’t include Particle.h before LIS3DH.h.
Thank you.
When I upgraded to 0.1.6, the library manger inserted the:
// This #include statement was automatically added by the Particle IDE. #include <AssetTrackerRK.h>
as the first two lines in my code before the #include "Particle.h"
be well
I’ve been having trouble with AssetTracker on my Electron Asset tracker, so I’m trying rickkas’s upgrade.
I’ve pulled the libraries from those available in the WebIDE list.
I’m getting a compile error: ‘AssetTrackerRK’ does not name a type, is there a parameter that should be in the constructor?
#include "Particle.h"
// This #include statement was automatically added by the Particle IDE.
#include <LIS3DH.h>
// This #include statement was automatically added by the Particle IDE.
#include <AssetTrackerRK.h>
// Port of TinyGPS for the Particle AssetTracker
// https://github.com/mikalhart/TinyGPSPlus
//#include "TinyGPS++.h"
AssetTrackerRK t = AssetTrackerRK();
int transmittingData = 1;
void setup() {
t.begin();
t.gpsOn();
t.updateGPS();
Particle.function("tmode", transmitMode);
Particle.function("batt", batteryStatus);
Particle.function("gps", gpsPublish);
}
void loop() {
t.updateGPS();
delay(5000);
}
It did not however fix my GPS problem. Both AssetTracker.h and AssetTrackerRK.h are doing the same thing. I have 3 GPS boards, all three do the same thing. Any time I try to use the GPS I get a flashing LED: 10 fast cyan flashes, one long white, one (or 2) quick green… repeat.
When this happens I loose communication and have to go to safe mode. If I take the GPS out, everything else works fine.
The problem appears to be in the physical Particle itself.
A new out-of-the-box Particle works correctly with the same firmware that isn’t working on the prototype I was having trouble with. (example code with AssetTrackerRK.h library for both Particles)
I will put in a support ticket as you suggest as soon as I can take a video.