[Shannon Hicks]

You can ignore the warnings to the serial monitor about the UUIDs if you never intend to send data to MMW.  The warnings are just there to help people in case they were using the generic ones when they didn’t intend to.  But since that’s what you want to do, it’s okay to ignore the warning.

[Shannon Hicks]

When you register a site on Monitor My Watershed you can set it up with various sensor parameters, and once you’ve got all of them entered on the website, you click the “View Token UUID List” button at the top of your site page and you’ll get a list of all the UUIDs in the exact format and order in which you need to paste them into your sketch.  If you’re not planning to transmit data to Monitor My Watershed or upload the file manually, then it’s okay to leave them as generic, non-unique UUIDs, but since you’ve got a unique registration token and sampling feature listed in your posted sketch, then I assume you’re intending to send data to MMW.

[Shannon Hicks]

Yes, the server was restarted this morning and service returned to normal, however all stations will be missing about 11 hours of data from earlier today.

[Shannon Hicks]

Yes, we’re aware of if and the data team has been notified.  No estimate on when it will be back up yet.

[Shannon Hicks]

There was a very small adjustment made several months ago to the delay time between commands to make communication with the Meter Group Gen 2 CTD sensor a little more reliable.  I don’t remember the exact date, but the latest release of ModularSensors definitely works with them.

[Shannon Hicks]

I’m not familiar with that module, but the specs say that its default baud rate is 115200, so you should set your “modemBaud” rate in the sketch to match that, so something like:

const int32_t modemBaud = 115200;

1	const int32_t modemBaud   = 115200;

Was that the value you changed in your sketch?  Because it’s set at 9600 in the example you attached.  Have you successfully communicated with the LoRa module by itself, outside of the Mayfly, by using just a basic bee carrier board?

[Shannon Hicks]

The current estimate is that we’ll receive a big shipment in about a month, so early August we’ll be able to restock the shop and Amazon.  The worsening electronics supply shortage caused me to have to make some changes to the Mayfly design based on component availability, and that delayed the fabrication of new boards until we could fully test everything.  I’ll post more information about the upcoming changes and improvements to the board and our new accessories in a few weeks.

[Shannon Hicks]

The entire electronics industry is facing growing supply issues that started last year.  I’ve been aware of the issue since early this year and started planning accordingly, so we shouldn’t have any supply issues with our custom EnviroDIY products.  But industry experts and suppliers are saying that components and products from companies like Digi will be difficult or impossible to find until next year sometime.  This is going to cause major supply shortages and price increases in every electronic device that needs to be built.  If you think you’ll need anything in the next year, I’d recommend you buy them now while you still can.  In the meantime, we’re awaiting a new production order of Mayfly boards and accessories, including some new items.  I’ll make a full blog post in a few weeks when we’re ready to release everything since these forum threads can sometimes get buried, and I think EnviroDIY members will be interested in all the new updates.

[Shannon Hicks]

I successfully used that sensor with a Mayfly v0.5 board with no problem.  If you’re powering the sensor with a separate 12v battery, do the Mayfly and the 12v battery share a common ground?  The white wire from the sensor is the SDI-12 data line, which should go to pin 7 , as you stated in Line 93.  It’s fine to use a separate battery to provide the 12v power to the sensor (red wire), but you need to make sure the Ground pin of the Mayfly is connected to that external battery, and the ground line of the sensor (black) is connected to the external battery as well.  I assume you used the sensor’s two RS485 wires (green & blue) to connect to some sort of modbus-to-PC adapter so you could use their software to change the SDI-12 channel number?  For future reference, you can use the Mayfly to change that channel number using the example “b_address_change” sketch included in our SDI-12 library.  Once you’ve deployed your sensor and don’t need to access the RS485 wires anymore, make sure you cover the bare ends of the green and blue wire and don’t let them touch anything on the Mayfly board or other pins in your logger enclosure.

I would also suggest removing line 172, because it’s going to reprogram the RTC time every time the board is turned on or restarted to whatever time you’re written in line 34.  If you’ve got a CR1220 coin cell battery in the Mayfly’s battery holder, there’s no reason to set the clock more than once.  It’s best to set the clock in a sketch all by itself, then verify that it’s synchronized, then upload any other sketch you want and the clock will keep the correct time for several years, until either the CR1220 dies or is removed.

[Shannon Hicks]

I’d have to see the rest of your sketch to know what you’re trying to accomplish with the 5v output.  If you put the CTD sensor on the D4-5 jack, and move the jumper to constant 3.3v, then the SDI12 power pin part of the code doesn’t really matter, but that kind of stuff gets declared early in sketch, usually in the setup function.  The bigger problem will be if you’re trying to keep a 5v output line powered after you take a reading and the logger goes to sleep, because normally the logger shuts down all the pins before going to sleep between readings.

[Author]

Posts