[Matt Barney]

Hi Neil,

Thanks for sharing your experience. It’s unclear to me the intent of the Switched 3V3 jumper on the Mayfly I2C port; it appears that it cannot be used in the Switched position with peripherals that pull up the I2C lines (which most seem to do) because the Wire library locks up.

I’m also doing some testing with power consumption and hope to share those results here soon.

Best,
Matt

[Matt Barney]

Thanks @srgdamiano — and thanks so much for announcing the release here on the forum and sharing links to the release notes!

Until somewhat recently, I didn’t fully grasp the connection between a ModularSensors GitHub release number and the version number in the PlatformIO library registry. To clarify for others who may be new to these software ecosystems, when EnviroDIY developers (usually Sara) tag a new release in the GitHub library, they also update the version number in the ModularSensors manifest (its library.json file) and add that new, versioned release to the PlatformIO library registry. This way, when we developers load code onto a Mayfly and we specify, for example:

lib_deps = EnviroDIY_ModularSensors@0.28.01

1	lib_deps = EnviroDIY_ModularSensors@0.28.01

…then we know exactly which version of ModularSensors we’re developing against, and can consult its release notes on GitHub.

(Please correct me if I’ve got any of this wrong!)

Understanding these tools, and the versioning mechanisms in use, is critical for those of us with a large and growing number Mayfly stations deployed. This way, we can always know precisely what code, including MS and all its dependencies, is running on each station in the field. This becomes vital when investigating a problem with one of our stations: Which version of code is it running? Do any of my other stations run that same code, and are they exhibiting the same behavior?

Thanks for all your efforts!

Matt

Trout Unlimited

[Matt Barney]

Ah, perfect – thanks Sara!

[Matt Barney]

Hi @heather, Thanks for following up. All looks good to me!

Matt

[Matt Barney]

I was curious whether opening Developer Tools (in Chrome) would show any insight to this problem. To my surprise, the Add Sensor button worked while I had DT open! One time I had to refresh the page while DT was open in order to get the Add Sensor dialog to display. Might be a workaround until the problem gets fixed.

[Matt Barney]

This issue is fixed in the latest PIO dev version. Details can be found in the PIO issue thread.

Matt

[Matt Barney]

I can recommend the Mayfly Hardware page, along with the Features and Jumper Settings links found there.

As far as reading and writing to the various pins in code, I’d suggest the Mayfly Software page, and particularly the LearnEnviroDIY link there, which is a series of detailed tutorials to get you started.

Good luck,

Matt

[Matt Barney]

Thanks. I have a couple of protoshields now, as well as some 2×10 male headers, so I’ve got options to work with!

Matt

[Matt Barney]

Interesting -thanks Neil. I may try that fuel gauge as well.

Matt

[Matt Barney]

It would be interesting to see if the anomalies in sync with periods when the Mayfly’s battery voltage is peaking, i.e., during maximum solar input.

It sounds like you have the sensor on a separate circuit from the Mayfly. If that’s the case, should the grounds tied together between these two circuits? I’m not an electrical engineer, so I don’t know – just throwing it out there.

Matt

[Author]

Posts