Sara Damiano

I don’t know whether the data is lost or not. I’ll look into it.

Monitor My Watershed’s visualizations were down for a while, but should now be fixed. We don’t currently have a specific page to go to to check the website status.

Can you try again? There was a hot-fix yesterday that caused trouble, but it was reverted this morning. The download is working for me right now.

Why did you decide to keep the power to your shield/Atlas sensors on all of the time?

As of a few years ago, the Skywire were _NOT_ compatible with the Mayfly. They use the XBee footprint, but they’ve re-arranged some of the pins so that it won’t work with the Mayfly – 0.5 or 1.x. At the time, each Skywire variant used slightly different pin-outs so you couldn’t even exchange between them directly.

I don’t know of any other…[Read more]

Oh, your right, that’s from the break. I’m not sure about the power line.

100ms

@w3asa Did you look at this example: https://github.com/EnviroDIY/ModularSensors/tree/master/examples/DRWI_Mayfly1. I think it’s almost exactly what you want.

To close the jumper on the Mayfly, you need a soldering iron. If you don’t have access to one of those, you might need to go back to the trinket.

You could also order a replacement pendant logger from Onset: https://www.onsetcomp.com/products/data-loggers/ua-003-64

I don’t know if the Mayfly is powerful enough for any of the SSL libraries, but you shouldn’t need one. The SIM7080G itself can handle the layers of secure connection. The Mayfly should only need to tell it to use the secure connection. Look in the examples for secure connections in the TinyGSM library. Essentially all you need to do is call TinyGs…[Read more]

Unfortunately, there’s not a way currently to change the data level from provisional.

It’s been a long time since I played with the Atlas sensors, but from my notes, power cycling them can cause the whole logger to crash. If you want to power down Atlas sensors between readings, you need an I2C isolator.  See the warning here: https://envirodiy.github.io/ModularSensors/group__atlas__group.html.  The simple logging program should p…[Read more]

The maximum transmission unit (MTU) for TCP is 1500 bytes. That’s why your transmissions over that size are failing. The commands TinyGSM uses for the SIM7080G are too low-level to break it up; you’ll need to do that yourself or submit a PR for TinyGSM. The XBee commands are higher level;  it does the break-up for you.

My first guess for the…[Read more]

The ModularSensors library is running the SDI-12 sensors in “concurrent” mode and the modbus communication only happens when initiated by the logger.  So the two sensors really should not be trying to talk to the logger at the same time.  ModularSensors first asks each sensor to start taking a reading, then goes back and asks each one for its r…[Read more]

I also responded on GitHub (https://github.com/EnviroDIY/SensorModbusMaster/issues/25), but the endian-ness of your sensor simulator is not compatible. You simulator seems to be sending CDAB mixed-endian.  SensorModbusMaster only supports ABCD or DCBA.

The WoFpy end-point should be usable.  Can you give an example URL that you’re trying?

Are you setting up a system to regularly poll Monitor My Watershed?  If this is something you plan do to automatically and frequently, please email help@monitormywatershed.org so we can talk directly with to make sure you’re using the most efficient endpoint possible.

Can you explain what issues you’re having?

Are you trying to use the library or to modify it?  The instructions you linked are for making changes to the library itself.

There’s an example of using an Arduino as an SDI-12 slave in the Arduino SDI-12 library.

The a-la-carte example isn’t usable as written any more. It got to be too big so I filled it up ugly pre-processor conditionals and snippet markers to use for continuous integration and documentation.

There are virtual functions all over the library, which definitely are eating up memory. I think almost the entire inheritance chain for sensors,…[Read more]

If the communication works sporadically, it’s more likely to be an electrical issue than a code issue.  Coding issues *usually* cause it to not work at all.

The -9999 is the library’s value for a failed reading.  When you get in in SDI-12, it most often means the sensor didn’t respond or the response was garbled.  Because the Mayfly’s voltage (a…[Read more]