[James_NZ]

METER replied:

I am so sorry. That error means that there is some kind of error with the calibration of the sensor. I will have one of my colleagues reach out to you with a return material authorization (RMA)  to have that instrument brought in to have the issue fixed. 

James

 

[James_NZ]

Hi all,

Just an update.  I uploaded ‘d_simple_logger’ to see what is coming directly from the sensor.  It seems that the sensor itself is producing the -9992 values, rather than it being created somehow by the Mayfly.

I have contacted METER and they are looking into it.  I suspect the sensor is faulty.

James

[James_NZ]

Hi Shannon,

Thanks for your reply, and apologies for not replying sooner.  My replies to your message are in bold:

1. Do you have one of the Meter ZSC bluetooth interfaces for setting and checking Meter Group sensors? They’re really handy testing and troubleshooting things like their CTD sensors, and for changing the SDI12 address.  – No I only have spare Mayfly boards to test this device.
2. It would be important to know whether it’s the sensor that is reporting -9992 or if it’s what the Mayfly is saying. – I suspect there is some confusion between the data coming back from the sensor the -9999 code programmed in Modular sensors.  It seems strange that the temperature sensor works fine but not the others. 
3. Do you only get that value when the sensor is plugged in to the Mayfly?  Does the Mayfly report -9999 for all 3 parameters when no sensor is connected? – Yes I get -9999 when no sensors are attached.
4. Are you running a logging sketch or a simple test sketch? – I am running a logging sketch.  This sketch works perfectly for my other 9 sites. I will upload ‘d_simple_logger’ when I am next at the site to determine the raw information from the sensor.
5. You could also try putting the SDI-12 address back to ‘0’ and then power the sensor and watch the serial DDI string it prints out, thus bypassing the SDI-12 libraries all together, which again can help determine if it’s a sensor issue or a Mayfly library issue. – Is there a sketch I could use for this, or is it as simple as setting the sensor power as ‘high’ and reading the output? 
6. You should also disconnect all other external sensors from the Mayfly when troubleshooting communication issues because we’ve seen several instances of a CTD sensor losing partial or total communication with a Mayfly while a malfunctioning OBS-3 turbidity sensor was also connected to the Mayfly on another port. – Yes I have removed the turbidity sensor and still end up with -9992 values. 

Thanks again for your help and I look forward to your replies.

James

 

[James_NZ]

@sofija I am using mayflies for my PhD research as well.  I’m really interested to hear what you are doing with them, and can also provide some advice on how to get equipment.

[James_NZ]

Hi @shicks and  @srgdamiano.  You’re not going to believe it but the addition of the build flag below has fixed my problem, at least for the Gen2 sensors.

-D MS_SDI12_NON_CONCURRENT

1	-D MS_SDI12_NON_CONCURRENT

I am certain it is this build flag and not the voltage pin (previously set to 5v) because I uploaded my script prior to switching the voltage pin over and it suddenly sprang into life.  I have subsequently changed the pin over to 3.3v for good measure.

I will keep you updated.

James

[James_NZ]

@shicks, would you mind publishing your Y-511a +  Gen 2 Hydros21 CTD code so I can ensure I haven’t done anything wrong on that front?

Thanks in advance.

James

 

[James_NZ]

Thank you both for your reply.  Okay, so it seems that I may be barking up the wrong tree with that one.  I will try Sara’s build flag to see if that works, but I’m not holding my breath.

I have my SDI12 jumper pins for the CTS set on 5v.  Could this be the problem?  For some reason I couldn’t get the Gen1 CTD’s to work at 3.3v, but they worked at 5v so I set them all as that.

FYI, I am using the modbus wing-shield here:

https://github.com/EnviroDIY/Mayfly-Modbus-Wing/tree/master/Modbus-Mayfly_WingShield

Thanks again for your help.

James

 

 

 

[James_NZ]

I’m also still very interested in these wings.  The Pololu 12v Step-up voltage regulator has been discontinued and I’m struggling to build new wings.
<h1 id=”page_title”></h1>

[James_NZ]

Hi @shicks (and thanks @neilh20),

Thanks for that.  I am using a Yosemitech Y511-A with a Hydros CTD (Gen 1).  My code is fairly similar to yours.  I notice that you use pin 22 to power the Y511 (line 145) where I have ‘-1’.  I also don’t see the line ‘<span class=”crayon-i”>AltSoftSerial</span> <span class=”crayon-v”>altSoftSerial</span><span class=”crayon-sy”>(</span><span class=”crayon-cn”>6</span><span class=”crayon-sy”>,</span><span class=”crayon-cn”>5</span><span class=”crayon-sy”>)</span><span class=”crayon-sy”>;'</span> in my code.  Do you think this could be causing the problem?

FYI, more information (and my current code) can be found in this post:

https://www.envirodiy.org/topic/hydros-ctd-10-regularly-dropping-out-9999/

Since posting the topic above I have attached ferrite collars to no avail and inspected all sensors and cables for damage (which there is none).  I have also switched the TTL-RS-485 board on the MODBUS wing with another (working) TTL-RS-485, which also doesn’t solve the problem.  I can get a perfect CTD record by removing the MODBUS wing.  The strange thing is that I have 6 other sites with identical code that work perfectly.

I would love to solve this issue without having to install a secondary board.

James

 

 

 

 

[James_NZ]

Hi Neil,

I would only need 5 at this stage.  I would connect it to my Yosemitech turbidity sensors and potentially Yosemitech pH sensors as well.

Regards,

James

 

[Author]

Posts