Sara Damiano

Have you tried using the -D MS_SDI12_NON_CONCURRENT build flag: https://envirodiy.github.io/ModularSensors/group__sdi12__group.html.  Some SDI-12 sensors don’t properly support the concurrent mode that ModularSensors uses by default.  That could by why they work individually, but not all together.

I finally dug into this.  As I commented on GitHub, I think this loss must be related to a server update or hotfix.  The server did get the data, so it might be recoverable. I doubt it’s related to the older issue.

If you can create a POST request, you can get data to Monitor My Watershed.  There’s information about the POST format here:

https://github.com/ODM2/ODM2DataSharingPortal/blob/main/doc/example_rest_requests.md

I’m sorry; I’m stumped. There’s something wrong with the way the battery voltage is being read. But I don’t understand what. As soon as I turn on the debugging for it.. it works. It also works if I upgrade to the current ModularSensors master branch. But I cannot figure out for the life of me what change makes it work.

So my two suggestions to…[Read more]

I’m looking into it. I would have said “of course they should work together” but I’d never tried it, so I hooked it up and tried it out. And I got the same result as you. I haven’t figured it out yet, though.

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…[Read more]

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 line dataLogger.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…[Read more]

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

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]