[Shannon Hicks]

The UUIDs for the various parameters are generated by the MonitorMyWatershed website.  When you created the site for your particular station, you had to manually add whatever parameters you were interested in receiving from the Mayfly logger.  It looks like you added the 3 parameters for the Hydros21 and one turbidity parameter for the OBS3 sensor.  The old OBS3 turbidity sensors have two analog outputs, one low range and one high range (there’s more about this in the Monitoring Station Manual).  So you’ll need to log in to MonitorMyWatershed, go to your station details, then hit the Manage Sensors button and then add the additional parameters, starting with another OBS3 turbidity value.  Then you’ll need to add the parameters from the Mayfly itself, which are battery voltage, ds3231 temperature (Mayfly board temp that’s sometimes helpful for diagnostics), and the EnviroDIY LTEbee sim7080 signal percent.  All 3 of those parameters can be found on MMW dropdown menu under the sensor manufacturer name of EnviroDIY.

[Shannon Hicks]

Did you download the libraries.zip file correctly from this page carefully following the instructions in the Readme:  https://github.com/EnviroDIY/Libraries

and then confirm that all 42 folders are in your Arduino/libraries folder (not nested into a sub-folder called “Arduino/libraries/libraries”) and that the folders contain actual files are are not empty?  You also have to restart the Arduino IDE if you unzip the files into the Libraries folder while the IDE is running.

[Shannon Hicks]

The example code for a CTD/OBS3/SIM7080 station can be found here:  https://github.com/EnviroDIY/ModularSensors/tree/master/examples/DRWI_SIM7080LTE

The only changes you’ll have to make is to enter the turbidity sensor calibration information in the correct place (lines 157 to 186), give the logger a unique name in line 59, and enter your UUID from MonitorMyWatershed in the section lines 220-238 (making sure that the order of the parameters in the UUIDs match the order of the variables in lines 194-201).  If your UUIDs from the website are in a different order than the code, then rearrange the variables in lines 194-201 to match the order of the UUIDs.  DO NOT rearrange the order of the UUIDs in lines 194-201.

If you’re using a provider other than Hologram, you’ll need to change the APN as listed in line 106.  And make sure the SDI12 channel of your CTD sensor has been change to something other than ‘0’ (we usually use ‘1’ which is why it’s set to 1 in line 146.)  And make sure the jumper next to the Aux Analog Grove Jacks is set to 5v (the middle position) in order to power the analog OBS3 sensors with the appropriate 5v excitation voltage.

[Shannon Hicks]

It’s likely that you deleted something important and that’s why the code isn’t working properly.  What sensors are you trying to use with your logger?

[Shannon Hicks]

There’s a list of sensors currently supported by the ModularSensors libraries listed on the Github repo for ModularSensors:  https://github.com/EnviroDIY/ModularSensors?tab=readme-ov-file#supported-sensors-

[Shannon Hicks]

Rather than create a new forum post for this issue, I’ll just add to this thread from last summer.

Today (January 22, 2024) there has been a widespread nationwide (USA) cellular network outage that has been affecting users of all the major wireless carriers, including the ones used by Hologram (the company that most of the EnviroDIY stations use).   The network has been down for about 5 hours, so logger stations aren’t able to connect to MonitorMyWatershed to upload their data.  There’s nothing that stations owners can do until the outage is resolved by the phone companies.  Once everything is back online, station owners could retrieve the memory card from their stations if they wanted to see any data that was recorded to the memory cards but wasn’t transmitted to the website.

[Shannon Hicks]

We’d need more information in order to troubleshoot your problem.  Are you using an EnviroDIY Mayfly board, and if so what hardware version do you have?  What cell or wifi board are you using?  What Arduino sketch are you using on the board and are you using it mostly as-is, or did you rewrite any part of it or the supporting libraries?

[Shannon Hicks]

I found a schematic in your github repo, my suggestion would be to power everything external to the Mayfly with its own beefy power source, especially the relay bank.  It looks like you’re currently using the main 3.3v regulator of the Mayfly to power the relays and maybe some other things, which is probably what’s causing the brownout.  There’s a secondary 3.3v regulator that powers the SWITCHED_3V output (and the switched 5v and 12v circuits too), so that would be a better source for external devices (just leave pin D22 high all the time to leave the switched power outputs constantly on).  Most big external loads on the Mayfly should be connected to the switched outputs in order to provide a more stable voltage for the processor and other vital on-board circuitry.  Also, all of that power the Mayfly is providing to itself and all the peripherals has to run through the bq24074 charge controller, which handles all the power going into the Mayfly from either a battery or USB power (and also back out to the battery for charging), and sometimes it doesn’t like surges from motors and other heavy instantaneous loads.  So try powering that relay bank (and any other load) from an external source (making sure to tie all the grounds together for common reference) and see if that corrects your brownout issue.

[Shannon Hicks]

What version of the Mayfly board are you using?  And how are you powering the Mayfly?  Is the Mayfly providing the power for the sensor and vacuum pump too, or is that from a different source?

[Shannon Hicks]

You could also try putting an ammeter in line with the main battery (with no solar or USB connected) to monitor the current of the board during use.  When it’s sleeping, you should see a current of about 0.6mA  for your configuration.  If you measure a sleeping current above 1mA, then something is probably wrong, either the board isn’t properly sleeping, or something is drawing more power than it should.  Have you tried swapping or kist removing the microSD card?  Some cards brands use more power in a sleeping Mayfly than others.  And sometimes old cards that once were good will start to go bad and use more power than normal.  And on rare occasions, the pins of the microSD card socket (either the optional vertical or the horizontal on-board socket) will get bent and allow for a phantom current draw.  So monitoring the sleeping Mayfly current with no memory card can be a useful tool to locate the source of the issue, as well as removing any external sensors and the cell board, all one at a time, to locate anything using an unusual amount of power during idle or sleep mode.

[Author]

Posts