Sara Damiano

Can you post your code? I can’t help much with the sleeping issue without seeing your code.

The issue with getting those 300mm values back from the sonar is an issue with the sensor/installation itself not the code. The sonar will report its blanking distance (300 or 500 depending on the model) anytime something is too close to it to get a real…[Read more]

Oops, I was just looking over again the code I gave you and realized there’s a mistake in line 41. The levelStatus should be the inverse of the modbus result since 0 is good. (bool levelStatus = !modbus.uint16FromRegister(0x03, 40042)) I corrected it above.

You should be able to copy that chunk of code and apply it to any variable you’re interested in. You can even grab multiple variables in the same query. In the example I typed up I grabbed all six registers for the date/time at once (with the getRegisters call) and then used the uint16FromFrame function to separate them into the component parts.…[Read more]

Correct.

The sequence of variables (and the order of the plots) is fixed.

When you delete a variable result, it’s gone forever. Any data you attempt to add to that result time series will disappear into the ether. Creating a new variable result generates a new UUID; you would have to reprogram your Mayfly to know about the change.

You can…[Read more]

It looks like you’re using the Arduino IDE. Managing multiple libraries for the Arduino IDE is NOT easy – it is quite a hassle. Have you installed all the libraries following the instructions here: https://github.com/EnviroDIY/Libraries#installing-libraries-in-the-arduinocc-ide? Have installed them more than one time? When you open your…[Read more]

Okay, this should get you pretty far.

#include <Arduino.h>
#include <AltSoftSerial.h>
#include <SensorModbusMaster.h>


// Create the stream instance
AltSoftSerial modbusSerial;
// OR, if AltSoftSerial isn't working consistently enough
// HardwareSerial modbusSerial = Serial1;

// Create the modbus instance
modbusMaster modbus;

// Setup…

[Read more]

I’ve only ever used a much older ISCO automated sampler and that only using its internal programming. This is something new to me; I’m skimming your manual. The Signature itself is obviously more powerful than the Mayfly. Are you just looking to use the Mayfly to report live data in order to avoid buying the ISCO supplied modem? Doing that…[Read more]

I’m sorryfor the confusion. The unit selected on MonitorMW should be the unit you are sending data in. The MonitorMW data portal never does any calcu lation of any type on the posted data, including unit conversions. If you select different units from those units sent in your post request, the website will simply be wrong. If you modify an…[Read more]

I don’t think you should have to be messing with eTree if you’re using ulmo. There’s a get_values function that returns a simple python dictionary: https://ulmo.readthedocs.io/en/latest/api.html#ulmo.cuahsi.wof.get_values The WSDL URL is https://monitormywatershed.org/wofpy/soap/cuahsi_1_1/.wsdl.

Have you found the ulmo library: https://github.com/ulmo-dev/ulmo It can parse the WaterML.

I believe it’s what Model My Watersehd and other tools we have are using. I haven’t actually used it myself, so I can’t help with it more than giving you the link.

There are some bugs with WOFpy right now; I think some had been fixed, but I don’t remember the current state. I know that even when it is working large data queries tend to crash browsers.

https://github.com/ODM2/ODM2DataSharingPortal/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+wofpy

Just a note on sending to ThingSpeak: there’s no free tier for anything but “personal use.” If you set your MathWorks/MatLab/ThingSpeak account up as anything else (even non-profit/educational) you only get 30 days free and have to pay beyond that, no matter how low your usage is.

If a new csv is being created, it’s almost certainly because the logger is restarting. It could be some irregularity in the power that’s causing the board to restart directly or it’s the watchdog. If you’re not specifically setting the file name, whenever the board attempts to talk to the SD card, it puts together the logger ID and the date and…[Read more]

The WoFpy endpoint is here: http://data.wikiwatershed.org/wofpy/

Right now there’s no ability to do units conversions in either ModularSensors or on Monitor My Watershed. Your only option in ModularSensors would be to create a calculated variable that did the units conversion.

On Monitor My Watershed, I think almost all of the temperature variables have the option of being in either C or F, but nearly…[Read more]

To turn on the “deep” debugging for the modem, add build flags “-DMS_DIGIXBEECELLULARTRANSPARENT_DEBUG” and “-DMS_DIGIXBEECELLULARTRANSPARENT_DEBUG_DEEP” for cellular or “-DMS_DIGIXBEEWIFI_DEBUG” and “-DMS_DIGIXBEEWIFI_DEBUG_DEEP”. Keep the publisher build flags set. You’d also have to change your serial monitor line endings to just a carriage…[Read more]

The only thing coming to mind right now is possible issues with the json or the content length header. If the length of the json doesn’t match up with the actual size of the json, the send would probably be rejected. (You’d get a 5xx I think.) Unfortunately the only way you’d see that 5xx or details on why the send failed would be to turn on…[Read more]

I’d completely forgotten about the filename issue, too. It’s definitely a “gotcha” that’s hard to catch.

Hm. Well, I’m stumped. I have issues all the time with the cellular, but not the Wifi.

I’m sorry; I’m going to throw a zillion questions at you again.

You’re using 4 separate Mayfly’s, right? (ie, you don’t have both the wifi and cellular XBee’s hooked up to the same Mayfly). You’re wifi is connected to “real” wifi, right? (ie, not a…[Read more]