Anthony Aufdenkampe

Check out this repo: https://github.com/EnviroDIY/Trigger

This example sketch shows how it would be used in combination with the ModularSensors library: https://github.com/EnviroDIY/Trigger/blob/master/examples/simple_logging/simple_logging.ino

It’s old, so some components are probably outdated, but it’s generally what you’re looking for.

@james-dareboprc-govt-nz, those power issues you came across on GitHub (regarding getting the brush to spin and wondering about setting the spin rate) were quite old (2017?) when we first started using YosemiTech sensors and early in my knowledge of DIY electronics. The short-story is that once we figured out that we needed to add a capacitor…[Read more]

James, I’m glad to see that you’re using our DIY Mayfly-Modbus-Wing. Yes, soldering the DIY windshield is required. I had thought you were discussing soldering an RS485 adapter directly to the Mayfly. My bad for misunderstanding!

From my perspective, there is not “problem” with the YosemiTech Y511 turbidity brush running every time the sensor…[Read more]

James, I really like all the YosemiTech sensors I’ve used, and I’ve facilitated the purchase of approximately ~150 or more for various organizations. The Y511 turbidity sensor with wiper is the most common we use, and everyone is very satisfied with it.

I’ve been working with a water utility, and after doing a careful comparison with their other…[Read more]

James, by the way, I would suggest that you NOT solder anything to the wing headers. Our two options just plug into them and can be removed anytime, just like an Arduino shield.

James, we’ve been playing with hardware designed for this for quite some time (as a subfolder in our SensorModbusMaster repo), and just recently spun our commits/designs into it’s own Mayfly-Modbus-Wing repo. Have you seen this?

Our solder-your own DIY version is described here: https://github.com/EnviroDIY/Mayfly-Modbus-Wing/tree/master/Modbus-Ma…[Read more]

Hi All,

Good news! We completed the fix to issue #3 “Sparkline” plots and CSV downloads not functioning.

As expected, most of the data that looked to be missing is now showing up in the “Sparkline” plots, in the data table views, and in the CSV downloads.

One disappointing discovery is that the #2 Networking (Domain Name System) issues laste…[Read more]

@mbarney & @neilh20, the CSV downloads are not an effective way of accessing data gaps, because that mechanism relies on the same corrupted catalog crosswalk that underlies the problem with the sparkline plots.

There are really only two ways for you to assess data gaps:

• Keep a record of server response codes from RESTful POST requests, from…

[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]

Shannon, thanks for those additional details!!!

Matt, from what I read in Shannon’s description, keeping the address set to ‘0’ might result in you only taking 1 measurement for averaging, even if you asked for 6.

Matt, my understanding is that the warning to not use address “0” came from a Meter/Decagon integration manual and from real-world experience. If I’m not mistaken, some sensor manufacturers reserve the “0” address for all sensors to use all the time, even when their address has been changed. This allows for a back-door to poll a line for all the…[Read more]

Matt, unfortunately, I’m nearly sure that it has to be changed.

See the warning in: https://envirodiy.github.io/ModularSensors/group__sensor__hydros21.html#sensor_hydros21_ctor

I recently had this problem too!

The solution was to type:

lib_deps = envirodiy/EnviroDIY_ModularSensors@0.28.1

So, drop the “0”. Everything worked well, and it properly fetched v0.28.01.

I’m not sure why Sara added that 0 to this version, but I suspect is was for a reason, but unfortunately the PlatformIO library registry doesn’t like having…[Read more]

@brianjastram, I’m glad to hear that replacing the cable with a shorter length worked!

@shicks, that’s great to hear that you have a bunch of tipping buckets connected directly to the Mayfly. Could you share that code with us? Is it integrated with ModularSensors? It would be very valuable to do that.

I can’t remember all the reasons for developing the TippingBucketRainCounter device application for the Pro Trinket. I do remember…[Read more]

@brianjastram, I think my colleagues in Washington DC have experienced a similar problem to yours, and after a bunch of troubleshooting, we figured out that it was due to electromagnetic interference in the analog signal line from the tipping bucket to the counting device. They had used unshielded cable and also had some unshielded connectors on…[Read more]

Matt, LoRa is a big leap beyond the Xbee 900 MHz self-meshing and local network stuff.

Shannon set up an Xbee 900 MHz network for us in 2012, which I think is still in use. Short story is that 1 km range is max and bandwidth is low for standard HTTP Post requests.

LoRa is much longer range (5-10 miles or more) and lower power. It does this with…[Read more]

Dale, I’m not familiar at all with the Semtech SX1272MB2DAS Shield LoRa radio module.

I am, however, quite familiar with the MultiTech mDotTM LoRa radio modules, which come with an XBee interface that plugs right into the Mayfly and works without any trouble. My colleagues at LimnoTech’s Ann Arbor office have been using them successfully in the…[Read more]

Neil & Matt, thanks for that very good news from your testing!

I’m really glad to hear that everything seems to be working well again!!!

We think we found and fixed the major issue with slowness and 502/504 Gateway errors that have been increasing since this spring!

Please let us know if you see any slowdowns from the web-browser or gateway errors from devices trying to post data, just in case there’s yet another issue we didn’t notice.

@tslawecki , @htaolimno and Lim…[Read more]