[Adam Gold]

@w3asa

Hi Jim – To get the linear correction, you should be able to make a calculated variable in .ino file and have that reported to MMW. It looks like there’s no code for calculated variables in the DRWI_CitSci.ino, but it is in the menu_a_la_carte.ino. Hope this helps!

[Adam Gold]

Hi Brian, I wasn’t able to get version 0.23.11 to work, but I think my issue is related to code for the Sodaq Ubee R410M modem that I’m using (and possibly PlatformIO). I do get a 504 sending error when running 0.22.6, though. Fortunately, I was able to get version 0.21.4 working great after I made a fresh PlatformIO project and manually installed 0.21.4

[Adam Gold]

Thanks, @srgdamiano! I think that the “CEREG” change helped with the registration issue. I’m still not able to get ModularSensors 0.23.16 up and running, though. Seems like another modem issue – these things are definitely finicky! I’ll reach out through the SARA R410M modem GitHub thread or email. Thanks again for your help!

[Adam Gold]

Interesting, thanks for the reply! It’s odd that bypass mode works for the Xbees because the Sodaq Ubee I think is always talking directly to the Ublox.

I don’t have the latest firmware update. I’ve gotten in touch with Ublox for help updating the firmware because it looks like some Hologram folks have had LTE-M issues that have been resolved by an update, although a Hologram engineer said that my issues likely weren’t related and asked me to make a new thread.

Have you had success updating any Sodaq Ubee firmware? I think my only option is using AT commands to update and so far that has been unsuccessful.

[Adam Gold]

You can do this remotely if you send data to ThingSpeak (already supported by ModularSensors). There are caps on how many ThingSpeak channels you can have and still have it be free (4 per account, I think), but you can make a ThingSpeak channel email or tweet at you when it meets certain conditions. Here’s a similar question about alarms from the Mayfly: https://www.envirodiy.org/topic/programming-mayfly-to-send-alerts/

Emailing from ThingSpeak involves using an IFTTT applet and some built-in ThingSpeak apps: https://www.mathworks.com/help/thingspeak/analyze-channel-data-to-send-email-notification-from-ifttt.html

Tweeting functionality is built in to ThingSpeak: https://thingspeak.com/apps

[Adam Gold]

Based on the list of supported sensors (https://github.com/EnviroDIY/ModularSensors), it looks like a Yosemitech DO sensor is another option.

[Adam Gold]

You might want to check out Atlas Scientific DO sensors (https://www.atlas-scientific.com/product_pages/kits/do_kit.html). They are galvanic probes that are cheap and fairly accurate (+- 0.05 mg/l), but they do require a fair bit of effort to piece together. You would need the DO kit (previous link, $280), an isolated carrier board ($40, https://www.atlas-scientific.com/product_pages/components/single_carrier_iso.html), and an extension cable where the connection to the probe needs to be waterproofed with CoaxSeal ($17,https://www.atlas-scientific.com/product_pages/components/bnc_10.html). You then would need to figure out how to connect the carrier board to the Mayfly. We are starting to use them for our project, and we’ve created our own carrier board to hold 3 sensor chips rather than use their carrier boards (https://github.com/acgold/Atlas-Scientific-Carrier-Board). They work with the ModularSensors library (in I2C mode), and the data sheets from Atlas Scientific are great (https://www.atlas-scientific.com/_files/_datasheets/_circuit/DO_EZO_Datasheet.pdf?)

[Adam Gold]

I’m having a similar problem with the LTE-M Xbee3 that folks in this forum have already described, but slightly different. I have the same hardware as Cal and Brian, but I have a Taoglas LTE-M/NB-IoT antenna. Using the menu_a_la_carte.ino from Modular Sensors, the modem will throw a lot of “NO RESPONSE” messages while trying to synchronize with NIST, and the cell signal strength and % will be displayed as -105 and 12 when written to the SD card. It is getting a good amount of signal when I connect the modem to XCTU with an XBEE explorer-type board, but it takes a few minutes to connect. I tried using some simple code with AT commands that was posted in the “Trouble Initializing XBEE LTE-M” forum to wake it up and reset defaults, but it only responds about half of the time to the “+++” commands and never responds to AT commands with StreamDebugger.

I switched from using the main branch of Modular Sensors to the develop branch, but I got the same kind of response. I then changed up some of the “timeout” values in “TinyGSMXbee.h” and got this response:

Sending data to data.envirodiy.org
08:54:25.650 -> POST /api/data-stream/ HTTP/1.1
08:54:25.650 -> Host: data.envirodiy.org
08:54:25.650 -> TOKEN: [my token]
08:54:25.650 -> Content-Length: 402
08:54:25.650 -> Content-Type: application/json
08:54:25.650 ->
08:54:25.650 -> {“sampling_feature”: [my sampling feature]}
08:54:25.650 ->
08:55:17.649 -> — Response Code —
08:55:17.649 -> 504

I could see that the modem was trying because the Hologram Dashboard showed activity, but my values for cell strength were all zero. I modified some code in EnviroDIYPublisher::sendData to try and increase the waiting time for a response from the data portal:

start_timer = millis(); while ((millis() - start_timer) < 50000L && _outClient->available() < 12) //default 10000L {delay(100);} //default 10

1 2 3

start_timer = millis();         while ((millis() - start_timer) < 50000L && _outClient->available() < 12) //default 10000L         {delay(100);} //default 10

After this change, I got a similar response, but there are no “NO RESPONSE” codes, a “Bad timestamp, not setting clock.” message, and my data were sent to the portal once. Every time after that initial upload to the data portal, I will get a 504 response code. The cell strength and % were still reported as zero even when it uploaded to the data portal. Output showing initial successful upload:

Setting up sleep mode on the XBee.
08:46:28.963 -> [2797] ### Modem: Digi XBee3™ Cellular LTE-M
08:46:29.308 -> Attempting to synchronize RTC with NIST
08:46:29.308 -> This may take up to two minutes!
08:47:06.473 -> Bad timestamp, not setting clock.
08:48:01.713 -> ——————————————
08:48:18.506 -> Successfully connected to SD Card with card/slave select on pin 12
08:48:18.540 ->
08:48:18.540 -> \/—- Line Saved to SD Card —-\/
08:48:18.540 -> 2019-02-01 08:48:00,2,-9999,11025,4.761,30.25,0,0
08:48:18.574 ->
08:48:18.574 ->
08:48:26.027 ->
08:48:26.027 -> Sending data to data.envirodiy.org
08:48:42.099 -> POST /api/data-stream/ HTTP/1.1
08:48:42.099 -> Host: data.envirodiy.org
08:48:42.099 -> TOKEN: [My Token]
08:48:42.099 -> Content-Length: 402
08:48:42.099 -> Content-Type: application/json
08:48:42.099 ->
08:48:42.099 -> {“sampling_feature”:[My sampling features]}
08:48:42.099 ->
08:48:45.941 -> — Response Code —
08:48:45.941 -> 201

Does anyone have code that consistently works with the LTE-M Xbee3 or suggestions on how to proceed? I am hoping to have a total of 10 stations that each have an LTE cell modem so they will work for a long time, and I don’t want to invest in the LTE-M Xbee3s if they’re not dependable. Are there other LTE cell modems that are known to work easily with a Mayfly like the Digi 4G LTE Xbee or the Digi 4G LTE-Cat1 Xbee3?

[Adam Gold]

@w3asa Hi Jim, I figured I’d address the Atlas Scientific code question in this forum. I sent a pull request to the Modular Sensors library on GitHub yesterday with some messy code that I got to work with temperature, EC, and DO Atlas sensors using I2C, and it looks like @srgdamiano already made a new branch of the Modular Sensors library called “atlas” that includes cleaned up versions of the code. I can get to it now using PlatformIO by changing the “lib_deps” section of my “platform.ini” file to this:

lib_deps = ; EnviroDIY_ModularSensors ; ^^ Use this when working from an official release of the library https://github.com/EnviroDIY/ModularSensors.git#atlas ; ^^ Use this when if you want to pull from the develop branch

1 2 3 4 5

lib_deps = ;    EnviroDIY_ModularSensors ;  ^^ Use this when working from an official release of the library     https://github.com/EnviroDIY/ModularSensors.git#atlas ;  ^^ Use this when if you want to pull from the develop branch

I’m definitely interested in seeing the code that you’re using as well as your set up in Great Marsh and any tips that you’ve learned while deploying the sensors!

[Adam Gold]

Thanks for adding those to the portal. Those are the only ones that I plan on using.

[Author]

Posts