Activity

I’ve created a low cost monitoring console using a Raspberry Pi and FTDI cable. This allows a release debug OUTPUT to be monitored just as if it was on the console and compared to https://monitormywatershed.org/

https://github.com/neilh10/ModularSensors/wiki/Test-monitoring-host

There’s not a direct replacement for that sensor, meaning one with the same operating specs and output.  There are some alternatives, but most are significantly more expensive, or require different interface hardware (like the Yosemitech sensors), or Turner Cyclops sensors (but require user calibration).  Unless you need a turbidity sensor i…[Read more]

Thanks , can you suggest alternate of any other company having almost same specs

Campbell Scientific discontinued the OBB3+ sensor about a year ago.  They have new turbidity sensor models in development, but I’ll let them make the announcement about when it will be ready.

#jsterling, I am looking for OBS3+ for my pilot project , went to campbell site but it shows discontinued. Can any support to provide source for OBS3+ or its alternate model

Ok, I see. Thanks so much for taking the time to provide all these details – very helpful!

Best,
Matt

Trout Unlimited

No, the Meter Group sensor will not work with Modular Sensors if its address is set to ‘0’.  When it’s set to ‘0’, the data string is not in proper SDI12 delimeted format and Modular Sensors won’t be able to see anything.  Plus, the only way to get it to take multiple readings would be to turn the sensor power off and back on each time you want t…[Read more]

Shannon, thanks for those additional details!!!

Matt, from what I read in Shannon’s description, keeping the address set to ‘0’ might result in you only taking 1 measurement for averaging, even if you asked for 6.

Thank you both for those details!

So to be clear: if I have only 1 SDI-12 sensor on the bus, and it’s at address 0, it should work properly with ModularSensors, even if I’m averaging 6 readings and collecting conductivity, temp, and depth each time. Is that correct?

Meter Group sensors that use SDI12 protocol (like the Hydros 21) come from the factory with a default SDI12 address of ‘0’.  Their sensors are programmed to output a serial data string containing the current measurement upon powerup if the address is set to ‘0’.  Meter Group’s dataloggers all talk to their sensors like this.  You can see it in ac…[Read more]

Matt, my understanding is that the warning to not use address “0” came from a Meter/Decagon integration manual and from real-world experience. If I’m not mistaken, some sensor manufacturers reserve the “0” address for all sensors to use all the time, even when their address has been changed. This allows for a back-door to poll a line for all the…[Read more]

Thanks Anthony. That warning is pretty clear. But I wonder why that’s a constraint.

It looks like “0” is a valid address according to the SDI-12 spec, and Meter supports it. Perhaps there’s something in ModularSensors that doesn’t like it. Scanning through the code, I don’t see anything right off.

Matt

Matt, unfortunately, I’m nearly sure that it has to be changed.

See the warning in: https://envirodiy.github.io/ModularSensors/group__sensor__hydros21.html#sensor_hydros21_ctor

Thanks for the input, ~ Yup that is what did it for interfacing with the LT500.  I brought in each change from Dec 1st till I found it

Doesn’t make a lot of sense to me why that impacts the protocol, but in dealing with a bug, the first stage is Detection, 2nd stage is Isolation, 3rd stage is Fixing it.

The Isolation in this case took a couple…[Read more]

I’d put it in the power up, since it’s supposed to happen right away and setting the pin is nearly instant and won’t slow down other things powering up.

I added 10 extra ms of wake time in v2.1.3.  You can revert everything back to the original by adding a second argument of 0 to your send command functions.