[David Lutz]

Shannon,

This is very helpful! We’ve ordered a few XBee PRO S3B 900 modules but are having trouble getting them to communicate via the Mayfly script.

One thing we think may be a problem is whether or not we chose the ‘programmable’ version of the modules. I noticed that Scott had an issue with this in another post from earlier in the Spring, and that he just purchased non-programmable XBees and the situation resolved itself. I’m willing to just purchase those if that makes the difference, but figured it was worthwhile to ask you to see which versions of the 900 modules you had been using successfully.

One thing we’re also not convinced we are doing correctly is adding the proper libraries to the simple sketch you posted before (here). I don’t see any libraries in that and think that also may be an issue.

Do you have any suggestions?

Dave

[David Lutz]

Hi everyone,

Just an update here. Due to the issues with the CS-215, we ultimately decided to go with the Meter Group’s ATMOS-41. It worked seamlessly with the Mayfly and our script and we had no issues with addresses or voltages. Seeing that it was relatively similar in cost, it was an easy decision. This evades the answer to the question, so this won’t be of help to those looking for how to use a CS-215 they may have lying about, unfortunately.

Dave

[David Lutz]

Sara,

Just to loop back – we were in touch with Campbell and their suggestion was also along the lines of the 3.5V voltage requirement. In the meantime, we picked up a Meter Group (formerly Decagon) ATMOS-14 sensor which collects temp/RH/VP and it worked perfectly. Since we only had to install one, we just went with that.

We’ll try to figure this out this fall/winter and once we do, I’ll make sure to update this thread for others!

Dave

[David Lutz]

Hi Sara,

We spent several hours today trying to work with the CS-215. We did update and use the most recent library (1.3.1) but were still having issues with the two examples. For the address change example, all of the addresses were vacant, even though we had defined the sensor having an address previously using a CR1000 (Campbell) logger. The simple logger did not result in anything going to the serial – it said no sensors found and to check the physical connection.

One interesting twist – for a while we were adjusting the delays in the address change script with the original (1.0.1) library. Every time the code ran, the sensor appeared at an address and we were able to change the address. However, when the script continued and rescanned all the addresses, the sensor was identified in a different address than what we told it to be at. This makes me think that there is some particular mismatch between the timing and delays that the sensor requires when passing data back/forth using the SDI-12 protocol, and what is in the library that works with other sensors that are not 12 volts.

The only thing we can think of is that somewhere in the CS code for how a CS logger interacts with a CS-215 that gets the delays exactly right because Campbell knows the timing needed by that particular sensor. I’m not sure if it is possible to access that script and/or look in the manual to see if it is an issue with the specific sensor, but that is my guess. You may know where to look since you were involved in working with that library?

Here is the manual

Thanks for any advice or guidance you could provide,

Dave

[David Lutz]

Hi Sara,

Thank you for getting back to me. I’ll check the version of the library we have and will capture the serial output. We won’t be having a lab meeting until Tuesday so I will send it right after that. I noticed that there were updates last month so perhaps that will sort things out. In the meantime, thank you for helping!

Dave

[David Lutz]

Iris,

I’d be interested to hear what you find. Here in NH we have interest in sap flow measurements for projects in conjunction with the Proctor Maple Syrup Institute at UVM. Installing Mayfly-based networks could be really interesting to them.

Dave

[David Lutz]

The Grove connectors are currently a bit of a pain to procure. They are available on SeeedStudio and Amazon but my sense is that everything is back ordered. I’ve had to have them shipped from Hong Kong over the past few months.

[David Lutz]

I wanted to resurrect this particular thread because we have been running into the same issue that Chan had. However, I note that there is a new variant of the SDI12 library as of roughly 2 weeks ago (EnviroDIY_SDI12_PCINT3) and I am pretty sure that it is an updated version of the SDI12_mod that Shannon sent in response a few years back in this thread.

We are going to work on this because we are interested in having the Mayfly control several SDI-12 sensors in a remote field site using the RTC to put the logger to sleep in order to only collect measurements every hour.

I get the sense that that is what the water monitoring project around the Delaware River basin is doing, but it is tough to know without looking at the code. Our network will be in remote northern NH.

[David Lutz]

Hi Beth,

Yes of course! Just checked – we have 0.5b. Don’t know how I overlooked that!

Another quick question that you may/may not know – if you are connecting an external 12v power supply to the mayfly, what type of jack is needed to connect the power source to the Mayfly? Is that just a male JST jack? (pictured here: jack)

Thanks!!

[Author]

Posts