Sara Damiano

@w3asa Did you look at this example: https://github.com/EnviroDIY/ModularSensors/tree/master/examples/DRWI_Mayfly1. I think it’s almost exactly what you want.

To close the jumper on the Mayfly, you need a soldering iron. If you don’t have access to one of those, you might need to go back to the trinket.

You could also order a replacement pendant logger from Onset: https://www.onsetcomp.com/products/data-loggers/ua-003-64

I don’t know if the Mayfly is powerful enough for any of the SSL libraries, but you shouldn’t need one. The SIM7080G itself can handle the layers of secure connection. The Mayfly should only need to tell it to use the secure connection. Look in the examples for secure connections in the TinyGSM library. Essentially all you need to do is call TinyGs…[Read more]

Unfortunately, there’s not a way currently to change the data level from provisional.

It’s been a long time since I played with the Atlas sensors, but from my notes, power cycling them can cause the whole logger to crash. If you want to power down Atlas sensors between readings, you need an I2C isolator.  See the warning here: https://envirodiy.github.io/ModularSensors/group__atlas__group.html.  The simple logging program should p…[Read more]

The maximum transmission unit (MTU) for TCP is 1500 bytes. That’s why your transmissions over that size are failing. The commands TinyGSM uses for the SIM7080G are too low-level to break it up; you’ll need to do that yourself or submit a PR for TinyGSM. The XBee commands are higher level;  it does the break-up for you.

My first guess for the…[Read more]

The ModularSensors library is running the SDI-12 sensors in “concurrent” mode and the modbus communication only happens when initiated by the logger.  So the two sensors really should not be trying to talk to the logger at the same time.  ModularSensors first asks each sensor to start taking a reading, then goes back and asks each one for its r…[Read more]

I also responded on GitHub (https://github.com/EnviroDIY/SensorModbusMaster/issues/25), but the endian-ness of your sensor simulator is not compatible. You simulator seems to be sending CDAB mixed-endian.  SensorModbusMaster only supports ABCD or DCBA.

The WoFpy end-point should be usable.  Can you give an example URL that you’re trying?

Are you setting up a system to regularly poll Monitor My Watershed?  If this is something you plan do to automatically and frequently, please email help@monitormywatershed.org so we can talk directly with to make sure you’re using the most efficient endpoint possible.

Can you explain what issues you’re having?

Are you trying to use the library or to modify it?  The instructions you linked are for making changes to the library itself.

There’s an example of using an Arduino as an SDI-12 slave in the Arduino SDI-12 library.

The a-la-carte example isn’t usable as written any more. It got to be too big so I filled it up ugly pre-processor conditionals and snippet markers to use for continuous integration and documentation.

There are virtual functions all over the library, which definitely are eating up memory. I think almost the entire inheritance chain for sensors,…[Read more]

If the communication works sporadically, it’s more likely to be an electrical issue than a code issue.  Coding issues *usually* cause it to not work at all.

The -9999 is the library’s value for a failed reading.  When you get in in SDI-12, it most often means the sensor didn’t respond or the response was garbled.  Because the Mayfly’s voltage (a…[Read more]

The instructions for manual installation on the https://www.arduino.cc/en/Guide/Libraries are telling you how to find the right location to put the unzipped folder.  Once you have the right folder, you cut and past the files.  That’s it.

To update libraries, the easiest way is to delete everything in the library folder and re-download.

Can you c…[Read more]

Changing the address via the Yosemitech library is not hard.  I would strongly recommend you do that rather than mess with two adapters and two serial lines.  No matter what, I’m positive that the default addresses are not 0x04 or 0x0B as you have them coded.  Those are just my favorite addresses for them.

If you really want two separate co…[Read more]

There’s no enable pin broken out, so it must have automatic flow control.  That’s what you want.  This one, right:  https://www.amazon.com/ALMOCN-Adapter-Module-Converter-Indicator/dp/B09998FY4X?th=1

You said:

Currently the RS485 wires connected to the Y510-B into the mayfly are as follows: GND to GND, RXD to D11, TXD to D8, and VCC to sv5.

If th…[Read more]

Sorry, I coded up the ThingSpeak publisher ages ago only to prove to myself that I could get an MQTT publisher working. I’ve never used it beyond that. I don’t have a paid account so after the trial period I was locked out and I’m not willing to do much testing on an account tied to my personal email.

Anyway, the code for ThingSpeak is in the…[Read more]

AltSoftSerial only works on pins 5 and 6. That’s why there’s no place in the code to declare the Tx and Rx pins. It’s strictly limited to those two.
<div dir=”auto”></div>
<div dir=”auto”>Is there a reason you have the two sensors on separate RS485 adapters and power supplies? I’m fairly certain that the two sensors operate on the same supply…[Read more]

It’s been a while since I’ve used Atom.  Are you sure the program is compiling without errors and actually being uploaded?  If there are errors in the build, it won’t actually be uploaded.

Done.  Sorry for the delay.  Let me know if you have any issues adding a sensor.