Modbus communications on Keller CTD Sensor

Tagged: Modbus Keller

This topic has 2 replies, 2 voices, and was last updated 2023-05-31 at 2:59 PM by dan@wachusett.

Viewing 2 reply threads

Author

Posts

2023-05-16 at 9:00 AM #17818

dan@wachusett

Participant

Hello,

I am looking for some help troubleshooting modbus communications on a Keller CTD sensor. I am running the very basic KellerTest sketch on a Mayfly 0.5b board with a RS-485 half shield adapter board. I turned on debugging to get some extra information.

The Modbus slave address is returning a value of 253… it should be 1. However, there is a note in a different script (KellerModbus.cpp) that says this function is not yet working (line 40). I have not tried the function setSlaveID, as this also has a note saying it is not yet tested.
When main loop function runs I am only getting a value returned for TOB1 = -1.9626 (Temperature), but it is obviously not correct.
The other register read requests return overflow values.
All responses are not coming from the correct modbus slave (according to the debugging checks)

Here are my register read requests:

    waterPressureBar = modbus.float32FromRegister(0x03,  0x0108);
    Serial.print("Pressure (bar): ");
    Serial.println(waterPressureBar, 6);

    waterTempertureC = modbus.float32FromRegister(0x03,  0x0102);
    Serial.print("Temperature (C): ");
    Serial.println(waterTempertureC, 4);

    waterSpCondMScm = modbus.float32FromRegister(0x03,  0x010C);
    Serial.print("Specific Conductance (mS/cm): ");
    Serial.println(waterSpCondMScm, 4);

waterPressureBar = modbus.float32FromRegister(0x03, 0x0108);

Serial.print("Pressure (bar): ");

Serial.println(waterPressureBar, 6);

waterTempertureC = modbus.float32FromRegister(0x03, 0x0102);

Serial.print("Temperature (C): ");

Serial.println(waterTempertureC, 4);

waterSpCondMScm = modbus.float32FromRegister(0x03, 0x010C);

Serial.print("Specific Conductance (mS/cm): ");

Serial.println(waterSpCondMScm, 4);

Here is some of the output when it runs:

16:20:59.925 -> Raw Request >>> {0x01, 0x03, 0x01, 0x08, 0x00, 0x02, 0x44, 0x35}
16:20:59.925 -> Raw Response (8 bytes) <<< {0x7F, 0x7E, 0x7F, 0xEF, 0xFB, 0x77, 0x95, 0x00}
16:20:59.925 -> Response is not from the correct modbus slave!
16:20:59.971 -> Pressure (bar): ovf

16:21:00.437 -> Raw Request >>> {0x01, 0x03, 0x01, 0x02, 0x00, 0x02, 0x64, 0x37}
16:21:00.483 -> Raw Response (8 bytes) <<< {0x7F, 0x7E, 0x7F, 0xBF, 0xFB, 0x37, 0x91, 0x00}
16:21:00.483 -> Response is not from the correct modbus slave!
16:21:00.530 -> Temperature (C): -1.9626

16:20:59.925 -> Raw Request >>> {0x01, 0x03, 0x01, 0x08, 0x00, 0x02, 0x44, 0x35}

16:20:59.925 -> Raw Response (8 bytes) <<< {0x7F, 0x7E, 0x7F, 0xEF, 0xFB, 0x77, 0x95, 0x00}

16:20:59.925 -> Response is not from the correct modbus slave!

16:20:59.971 -> Pressure (bar): ovf

16:21:00.437 -> Raw Request >>> {0x01, 0x03, 0x01, 0x02, 0x00, 0x02, 0x64, 0x37}

16:21:00.483 -> Raw Response (8 bytes) <<< {0x7F, 0x7E, 0x7F, 0xBF, 0xFB, 0x37, 0x91, 0x00}

16:21:00.483 -> Response is not from the correct modbus slave!

16:21:00.530 -> Temperature (C): -1.9626

This is my first time ever working with modbus communication on my Mayfly so I am rather lost at what to do next in my troubleshooting efforts. If anyone has experience with Modbus communications or any of the Keller sensors, I would greatly appreciate any insight into what might be going on here and how to address it. I also contacted tech support at Keller, but thus far the only thing that I have learned is that the device address should be 1. I’ve attached the Keller documentation with the modbus protocols for my sensor. This is where I found the register addresses.

Thanks for your help!

Dan

Attachments:

Communication-Protocol-X-Line-V3.7.pdf

2023-05-26 at 4:01 PM #17846
neilh20
Participant
@dan-wachusett Gosh just seeing this – seems like you got that Keller CTD.

Just wondering did you follow the advice given from https://www.envirodiy.org/topic/keller-ctd-sensor/#post-16332

Partly its decoding the layers of software. The keller protocol is used to access the Keller CTD map. I find it most helpful to compare and trace how different keller instruments are handled by the enviroDIY keller. If you only have one Keller Instrument on your line, then you are getting a response from that instrument – you may need to interpret the data that is coming back and find a path to getting working readings.
2023-05-31 at 2:59 PM #17856
dan@wachusett
Participant
@neilh20

Yes, I did get the Keller CTD. We had the budget and I was able to get an extra Hydros21 to deploy while figure out the Keller CTD. It took me a while to get the parts for the Modbus Wing shield and then build it, but I finally got them and had time to do it… so now I am in the thick of it.

I did follow instructions from the post you mentioned. I have begun doing what you suggest as well… parsing out the raw requests and responses to see what is happening. This may take me quite a while to figure out since I am new to all of this.

I’ll probably post some follow-up questions for the community once I can unravel some of the information that I am getting back from the sensor.

Thanks,
Dan