Activity

Hey! Sorry for the late response but I tried running a few of the different ModularSensor versions, and it seemed that v0.36.0 works for DRWI_7080LTE!

I initially started with v0.37.0 and v0.34.0, but those had issues with the libraries working together, naming issues, etc.

v0.35.0 was able to compile but recorded -9999 values for both the…[Read more]

If you’re having trouble getting all the libraries to work happily together, you could try downloading all of the ModularSensors dependency libraries from the release files on github:https://github.com/EnviroDIY/ModularSensors/releases

You can scroll down that page and find the zip file at the bottom of each release summary (under the “Assets”…[Read more]

Are the 3 solder jumpers on the back of your 6-pin screw terminal board soldered properly?  We noticed a few of them came from the factory with no solder on them, so I soldered them in the “Default” position before shipping them out, but there’s a chance yours might have been missed.  You can also try closing solder jumper SJ25 on the back of t…[Read more]

kwolfe:

So far I haven’t been able to get the turbidity sensor to show up in b_address_change, but a little while ago I did run the DRWI_SIM7080LTE sketch using the clarivue (before I muddled up my libraries), and the clarivue was recording and sending data over even though, at that time, it ALSO never showed up on b_address_change. So perhaps it…[Read more]

Did you get your turbidity sensor issue resolved? We are having an issue with out ClariVue turbidity sensor not being recognized by the Mayfly board. Running b_address_change.ino doesn’t find any sensors. Our Hydros 21 continues to to work. We have our 6-pin multipurpose screw terminal wired as shown in Shannon’s pic. We have the jumper set to…[Read more]

Thank you! After replacing my current libraries folder with a more recent version from the github, I got the Hydros 21 to show up, but not the Clarivue even after moving the white pin to S1. Also, now when trying to upload DRWI_SIM7080LTE, I’m getting compilation errors like “EnviroDIY_ModularSensors/src/LoggerModem.h:46:10: fatal error:…[Read more]

The b_address_change sketch you attached looks like an older version, it doesn’t match the latest example you can find on our Github: https://github.com/EnviroDIY/Arduino-SDI-12

So make sure you’re using the latest Arduino-SDI-12 library files (download that directory from Github and replace whatever is currently in that folder on your PC.  And…[Read more]

Oh also forgot to mention that I’m fairly certain I’ve switched the meter hydros 21 factory address away from 0 in the past.

Using ModularSensors doesn’t necessarily require the sensors to be directly connected to the Mayfly.  They could be, but they don’t have to be. In the case of a lot of inexpensive sensors sold as breakout boards, the Mayfly connects and talks directly to the sensor, but most of the not-bare-circuit sensors have black-box layers between the raw…[Read more]

Ok great, thank you for taking a look. Yes I2C is too short range for the applications I have in mind, but I have some experience with RS485 so that sounds like a good option.

I’m not very familiar with your ecosystem, but would using ModularSensors require the Mayfly to be connected directly to the sensor? So if my sensors are natively I2C, I…[Read more]

I spent some time skimming your GitHub code for your device.  If your logger is using a simple serial protocol to communicate with your GUI controller, it should also be able to communicate with the Mayfly (with or without Modular Sensors) in the same way if you expose the Serial (or AltSoftSerial) pins.

ModularSensors already supports the MS5803…[Read more]

We don’t have any set requirements for connection.  The Mayfly can communicate with almost anything that could communicate with an Arduino-style device.  Many users opt to user our ModularSensors library to run their loggers, but that library supports many protocols.

SDI-12 devices are very common in the environmental sensing field, so we have a…[Read more]