Forum Replies Created
-
AuthorPosts
-
The LTE Bee (and WiFi) can change IP addresses at any time.
The WiFi bee is actively being supported. It’s what I test with on my desk. Switching back and forth between WiFi and LTE is fairly simple. But you should still do some LTE testing on your desk before moving to the field.
If you’re using a Mayfly, I’d go with the WiFi Bee. It plugs right in. Any other shield would require jumper wires or other connections.
You need to set the sampling feature UUID for the logger. If you have an EnviroDIYPublisher, this happens automatically, but without the publisher, you need to add it.
So after you set the logger pins in line 283 (
dataLogger.setLoggerPins()
), add the linedataLogger.setSamplingFeatureUUID(samplingFeature);
I’m sorry I haven’t responded yet. I’ll try to look into this tomorrow.
The radio XBee’s *cannot* be used directly with the logAndPublishData functions. That only works for XBees that have a direct internet connection.
You would have to set up your radio using the Digi software and then write your loop function, which would print your json or csv string out over the serial port for the radio to hear.
The processor on the Mayfly isn’t clocked fast enough for reliable two-way communication at 115200. It’s pretty reliable at talking at that speed (ie, to the serial monitor), but when listening at that speed, it drops and garbles too many characters to be usable.
I don’t know why you had problems compiling the sketch. It compiles and runs for me with both debugging definitions.
The reason initialization is failing is the baud rate. I wrote that example for someone with a new ESP32 bee. In the example, the baud for the modem is first set at 115200, which is what an ESP32 will use at factory defaults. The modem is woken, and the communication is tested at the set baud; if (when) that fails, it tries to reset the baud rate to 9600 and then saves that baud to the ESP32’s flash. Because the slow baud is saved to flash, the initial communication will fail after running the script the first time because the Mayfly is still trying at 115200, but the ESP’s already down to 9600. You can fix it by setting the modemBaud to 9600 in the first place, but remember that that won’t work with a new ESP32 bee. Even if you don’t change the baud, the two should sync after the first attempt at initialization when the Mayfly retries at the slower baud.
Are you singned in as the same user for both sites? Right now, a user can only be associated with a single organization.
I think the bests solution would be to create a new “module” (h/cpp) for the Teros 12.
We’re actively working on getting funding to further develop an efficient data access API.
I have a jupyter notebook showing how I get data here: https://gist.github.com/SRGDamia1/d5bf4b651756a19a6df1a653b9493a6e
-
AuthorPosts