Forum Replies Created
-
AuthorPosts
-
DaveG, since you inherited a monitoring station from a previous owner, you didn’t get the full training we give station owners when we teach a workshop and/or install a station for them. I would suggest looking through all of our EnviroDIY Monitoring Station Manual since we thoroughly document all of the information about station assembly, installation, and maintenance. In particular, Section 8 – Monitoring Station Management addresses all of the common issues related to ongoing maintenance and support for a station, including links to quick guides for performing quality control and sensors calibration checks. There’s also 8 additional sections of appendices in the manual, with sample plots of data with explanations for the most common issues.
But for the quick answers to your questions above:
Battery voltage: the nominal voltage of the lipo battery is 3.7v. When fully charged, it will go up to around 4.2v, and can go as low as 3.55v. Below that, the logger code will prevent the sensors and cell modem from coming on in order to keep the battery from going below 3.5 v. Stations with a bad or dying battery will usually still operate on sunny days but will then stop at night, so that sort of data pattern would indicate that a new battery is required, but it sounds like your station’s battery is fine, and so is your solar panel. Occasionally the solar panels or their cables will degrade, causing the station to stop charging properly.
We usually program our loggers to transmit Mayfly board temperature (and now board humidity on v1.0 and above) so that it is some diagnostic info about the board conditions, along with battery voltage and the cellular signal strength. While the Pelican case looks like it’s an insulated box because of the foam, it definitely is not. Temperatures inside the case at night or in the shade are essentially the same as the surrounding air temperature, with a little attenuation because of the transfer of heat between the inside of the case and outside. And during the daytime if there’s direct sunlight on the case, board temperatures can get much hotter than the actual air temperature. We use the light colored tan or silver cases to prevent excess heating by the sun, and also because they visually blend in to the environment better. So in summary, you can’t really use the Mayfly board temperature as an accurate air temperature measurement, it’s only an indication of the temperature extremes the circuit board is seeing inside the case. The Mayfly circuit board can theoretically handle the standard industrial operation range of -40C to 85C (-40F to 185F), so it is unlikely your station will exceed those values. However, it is the lithium battery pack that suffers performance and lifespan issues at either of those temperature extremes so anyone planning to operate their station in the hot desert or the cold arctic might want to keep an eye on the lipo battery performance after a year or more. I’ve got stations here in Pennsylvania that have been deployed for 6 or 7 years with the same Lipo battery and logger board and have been operating continuously with no issues. The bigger killer of circuit boards and battery packs is humidity. Condensation will collect on the battery pack and logger board if there’s humid air in the Pelican case, and that condensation causes corrosion that can kill a Mayfly or battery pack. We recommend putting a desiccant pack inside the case of stations that have a tendency for humidity and condensation inside the case.
The conductivity range you mentioned seems about right for baseflow in your part of PA, however every stream and watershed is different, so you’ll want to take supplement measurements with a separate handheld conductivity meter to determine if the sensor is reading normally. There’s no way to recalibrate the sensor, it simply takes a reading and report it to the Mayfly board. The only time the reading is inaccurate is if the sensor is fouled or damaged. Fouling can occur on the electrodes of the CTD sensor that will affect the accuracy of the reading, but over-zealous cleaning of the CTD sensor could result in damage to the pressure measurement sensor that’s located right next to the electrodes, so extreme care should be taken when cleaning the CTD sensor. See section 8 of the Station Manual for more information about cleaning the sensor, and read the manufacturer’s manual (link available on that page, you have Hydros 21 Gen1 version) to learn more about how the sensor operates. The water depth is measured in millimeters of water above the pressure-sensing part of the sensor. That disk is about 15mm from the bottom of the sensor housing (on Gen 1 version). There’s a cutaway diagram in the Hydros 21 manual showing the location of the sensor components, and there’s also great information information in the quick guides (both the Maintenance Quick Guide and also in the QC Quick Guide) that can be found in section 8 of the EnviroDIY Manual.
The turbidity sensor on your station is an optical sensor (OBS3+) that can “see” about 16 inches into the water, so anything that is within that distance will affect the readings. Things like grass, sticks, fish, rocks, etc will cause the sensor to report a higher turbidity value than is actual, so you’ll need to investigate the area of influence around your sensor to see if there’s anything near the sensor in the direction that the sensor window is pointing. Sometimes mounting the sensors too close to the bottom of the stream will result in a constant reading that’s higher than normal, but if you’re seeing varying readings, my guess would be something loose nearby that’s waving in the current and causing the noise, or possibly fish activity. That particular sensor model was discontinued a few years ago by the manufacturer and has been replace by one with a much shorter measurement area, so shallow streams or cluttered channels will be much easier to monitor with the newer sensor (ClariVUE 10). Your turbidity sensor can’t be calibrated either, so the only way to know it’s working properly is to visually check that the sensor window is clean (refer to the Quick Guides for info about that) and check that you get a low reading when the water is clear. You can kick up some sediment around the sensor right at the time of measurement (every 5 minutes) to simulate high turbidity and then check that the sensor reported a higher value. You can also place your hand about one inch from the sensor window (while under the water) and you should get the max turbidity reading (around 250NTU on low scale and 1000NTU on high scale).
And as Neil mentioned, the CR1220 battery on the Mayfly board is there to keep the onboard clock synchronized. Your station is old enough that the backup battery might be getting low if the Mayfly was stored without the main Lipo battery connected for awhile. Is your station transmitting data to our website, or is it only reporting to the memory card? Does the timestamp on the data card appear accurate? For cellular-equipped stations, the logger contacts the internet time server upon initial startup to synchronize the clock, however your station is old enough that it might not have that feature, and of course it only works if you’ve got an active cellular data plan and a functioning cellular module. I think you’ve got an older 2G model which may not even have coverage in most places nowadays.
Are you saying you’ve got a bad cable or a bad Mayfly? Have you tried a different USB-C cable? The pins in USB-C connectors and cables are extremely small and are easy to fail. And when the pins in a cable’s connector get bent or damaged, we’ve seen them inflict damage on brand-new boards, so I’d suggest trying a new cable or two.
Matt, you are correct that it appears the solar panel was connected to the spare LipoBatt JST socket on the Mayfly, which causes the board to see those high levels during the day. The voltage regulator on the Mayfly can theoretically be damaged if you put more than 6.5v into the board via the LipoBatt jack, so they should definitely fix that as soon as possible. The big question is whether this damaged the regulator on the Mayfly or the battery pack. Once the panel is back on the correct SOLAR jack, you can look at the station data after a day or two and determine if things are behaving normally or not.
For the record, the JST jacks on the Mayfly have always been a little confusing, since there are 3 of them; only one is to be used by the solar panel, and the other two are for the Lipo battery, but only one battery can be attached at a time. This is a holdover from previous Mayfly designs where accessory boards like the older cellular bees require a separate power jumper to get power directly from the Lipo. Now that we’ve got our own LTE cell boards that don’t require that jumper, we’re moving towards only having one JST jack for the Lipo and removing the JST jack for the solar panel, which is why I added the new black quick-connector on the Mayfly v1.0. But since there are so many existing stations in the field with the existing configurations for solar and cellular, I didn’t want to totally remove those extra JST sockets on the Mayfly just yet.
If you’d like to prevent future people from accidentally connecting the solar panel to the spare Lipo jack, I’d suggest cutting one of the Lipo jacks off. To do this, make sure the Mayfly is completely unpowered with nothing connected (no solar, no battery, no USB). Use needle-nose pliers to pull up on the plastic housing of one of the JST jacks and it’ll pop off pretty easily. Now use a small pair of diagonal cutters to snip off the 2 pins flush with the circuit board. Now you’ve only got one Lipo jack on the Mayfly, and if you really want to prevent errors, remove the SOLAR JST jack from your Mayfly using the same technique, then cut off the JST plug from the solar panel wire and use the black quick-connect socket instead. One is included with all Monitoring Station Kits sold in the EnviroDIY shop, otherwise they can be purchased separately from places like Digikey: https://www.digikey.com/en/products/detail/phoenix-contact/1778832/2625556
@aufdenkampe, do you have any information about why certain sites are having this issue of their map marker being gray even though they’re still sending live data, or the issue of sensors not being able to be deleted from sites?
The dipswitches are mainly there to let people know their board is working during initial testing or desktop deployments. Anytime a board is deployed in the field as a “sleeping” station, power savings are important during the sleep period. So I put the dipswitches on the new versions of the Mayfly to allow people to deactivated the LEDs. The dipswitch for the green LED only cuts power to the green LED and nothing else, but it will save you about 2 mA. The orange LED is only on if power is being supplied through the USB jack, like when connected to a computer or when powering from the USB jack like what that converter will do. Whenever the USB jack is powered and the USB dipswitch is on, the LED is on plus the USB converter chip, which draws some not-insignificant power, so turning off the USB dipswitch will save power and prevent the USB converter from being on constantly. However, you’ll just have to remember to turn that dipswitch on again in the future if you ever decide to reprogram that Mayfly or want to connect to the Serial Monitor to see some output.
There’s a description of the dipswitches and all the new circuitry on the Mayfly Hardware Details page.
Powering the Mayfly v1.0 and v1.1 from the solar jack only would not be recommended because the power input circuit was not designed to operate that way. The most electrically efficient way is to use the 12v-to-5v converter and connect it to the USB-C jack and then deactivate the USB interface circuitry with the dip switch as explained above. The Mayfly will not operate properly if you only provide power to the solar jack with no 3.7v Lipo connected to the LIPOBATT jack.
That’s great, I’m glad it worked. Based on your screenshot, I can tell that your station is running a sketch that I programmed onto that Mayfly board in March of 2018. It’ll still work if you’re using the same CTD and turbidity sensor it originally had on it, and it will save data to the memory card every 5 minutes. It had the ability to transmit data to our older database system using a 2G cell modem, but those modems are no longer available and that database has been replaced with Monitor My Watershed. The RTC clock on the Mayfly may still be correct if the CR1220 battery is still good, but it might not if the station has been in storage awhile without a main lipo battery. That clock would have been set in 2018 to Eastern Standard Time, so it will appear to be one hour off from the current local time now. Nowadays we program all our RTC clocks to GMT time instead, to be compatible with the MMW database. If you end up needing to reprogram your Mayfly at some point in the future but still want to keep using that OBS3+ turbidity sensor, you’ll need the sensor’s 6 calibration coefficients from the calibration sheet that it was originally shipped with, which we still have in our records. You can send me an email at mayfly@envirodiy.org and I can provide those numbers to you so you can put them into the new logger sketch.
And for reference, here’s a better picture of how I soldered the right-angle header pins onto my CP2104 board.
Attachments:
As stated on the Details and Spec page, the Mayfly v1.1 can only source about 100mA from the 12v output, so if your motor draws 400mA, you’ll need to power the motor directly from your 12v source and not from the Mayfly.
That is correct, the Mayfly v1.0 and 1.1 boards do not have a separate external power input for 4v to 12v sources like the v0.5b boards. This is because the main voltage regulator on the v0.5b board that accepted that wide range of voltage was discontinued by the manufacturer, and the new voltage regulator doesn’t accept that high of an input voltage. However the tradeoff is that the new regulators have double the current output (1 Amp instead of 500 mA).
To power a Mayfly v1.0 or v1.1 board from a 12v battery, I’d suggest a 12v-to-5v power adapter with a USB-C plug on the end, and just plug it into the Mayfly’s USB port, and preferably one with a low quiescent power draw so that it doesn’t waste too much power on the dropdown. I think a few people on the forum here have recently mentioned adapters that they’ve had either good or bad results with. Something like this might work, but I haven’t test this exact model so performance results with a Mayfly aren’t guaranteed. You should also turn off the dip switch (after programming and when you’re ready for deployment) for the USB LED because it’ll save several mA of current for the LED and about 10mA of current for the CP2102 USB adapter chip that is powered anytime the Mayfly v1.0 or v1.1 is powered by a USB cable.
The other improvement of the new Mayfly boards when paired with the new sim7080 LTE cell boards is that these cell boards no longer require a direct connection to a 3.7v lipo battery like the Digi LTE boards did with the custom adapter board. Those older setups were harder to power from a 12v battery because you still needed to provide a separate Lipo battery for powering the LTE board. Now with the new sim7080 LTE cell boards, everything can be powered from just the 5v USB connector with no external lipo necessary.
The Adafruit CP2104 Friend has the correct 6-pin layout to work perfectly with the FTDI interface header on all Mayfly versions. The attached photo shows one connected to a Mayfly 1.0 but you can connect it to the Mayfly v0.5b the exact same way. Give that a try and see if you’re able to communicate with the Mayfly board. If not, it’s possible the corrosion on the board is the cause of your problems. If that’s the case, you could try cleaning the corrosion off using acetone or 91% isopropyl alcohol and an old toothbrush. But if the corrosion caused a part on the board to be damaged when it was powered up, then it’s like unsalvageable. The Mayfly v.05b boards have been discontinued as have the v1.0 boards, but the v1.1 boards will hopefully be listed as single items on Amazon sometime soon, but I don’t know the date yet.
-
AuthorPosts