Activity

@fisherba – Thanks for sharing this! I’ll be very interested to learn what Meter tells you.

I see what you mean on their product page: “When used with the ZL6 data logger, you won’t require an additional sensor for measuring—and referencing—barometric pressure.”

However, both the sensor manual and the Integrator Guide in the Downloads secti…[Read more]

I’ve been seeing gaps, lost data as well.

Checking this morning there has been no gaps in my test site

UTC 2021-05-12 11:45   or PDT    2021-05-12 3:45

Do note that the specifications says accuracy  0.5% of 10,000m or +/-5mm. This  implies that you want to keep it at a constant (20C?) while sitting in the bucket, and even then the apparent water level can wander up  +5mm  or down -5mm and still be within specification.    If the temperature changes then the accuracy specification doesn’t apply…[Read more]

Are you using a sensor with bare wires at the end, or with the molded stereo plug?  Is it a red cable or a black cable?  We’ve bought hundreds of CTD-10 and now the Hydros 21 sensors (only the name changed when the company changed from Decagon to Meter, and there was no design change).  Every one we’ve ever used has a small Gore-Tex sleeve ab…[Read more]

There’s an example sketch in the Modular Sensors GitHub Repository with a calculated variable correction for water temperature (really it’s density, so it’s called rho and density in the sketch) that uses data from a temperature sensor. The same sketch has a calculated barometric…[Read more]

Thanks @aufdenkampe – really appreciate that update, and all of the hard work by you and the team to fix and document these issues!

Note that the lost data appears to extend beyond May 7th, with very large data gaps each day from the 8th through 12th. The images attached below show these data gaps for 3 of our sites, with the UTC timestamp when…[Read more]

Hi All,

Our apologies for the several sets of bugs on the Monitor My Watershed / EnviroDIY / ODM2DataSharingPortal.

The short story is we have had 3 sets of issues in the last two weeks:

1.  Browse window not mapping sites or populating filter pane #496
   • Fixed! No loss of data.
2. Networking (Domain Name System) issues
   • Fixed!
   • Hours of…

[Read more]

We are also seeing the data gaps that I believe @thomas-schanandore and @movingplaid have reported above across all 3 of the stations that I’ve checked.

In particular, there are large gaps (9- to 24-hours) every day since at least May 5th, followed by data resuming at 12:30UTC across every station. This suggests that something is failing on the…[Read more]

Sometimes there is no easy answers. I recently went to presentation that included this analysis for

https://creeklands.org/wp-content/uploads/2021/02/CLC-Micro-Flows-2020.pdf

So partly what range of flow are you looking for and what accuracy.

Some features of MMW are still down due to some complex server issues.  They’re still working on it but haven’t given a specific date when everything might return to normal.

Hi All,

Just checking in to see if there is any news about the status of MMW. I haven’t been able to find relevant issues in the ODM2 Github site, so thought I’d share here what we’re seeing on MMW:

• The big Download Sensor Data button returns a Server Error (500).
• No sparkline plots are displayed.
• The 3 buttons for each variable are…

[Read more]

The database still has some issues with sparkline plots and a few other things.  The team is still working on it but don’t have an estimate on when things will be back to 100% functional again.

I am seeing what I think @thomas-schanandore is seeing as well.
MMW is saying that many sites have not been updated (ex. May 6, 2021, 3:50 p.m. (UTC-05:00) (12 hours, 55 minutes ago).

Last night I could not manually upload my data and this morning I receive a Server Error (500) when trying to log in

I believe this is the same issue that was reported here? If so, it should mostly be resolved. The browse sites feature is now working; the sparkline plots (panels) are not working but should be soon. Note that only data display was affected; Monitor My Watershed continued to collect the data. Here is the GitHub issue if you’d like more details.

We just got the sensor and haven’t done any comparison tests alongside the Gen 1 sensor to see if there’s a difference, so I can’t comment yet on anything data-wise, we just know that there’s not a communication issue with the Mayfly now that we’ve adjusted the timing of the commands in our library.