Skip to main content
4-Participant
December 16, 2025
Solved

Integration of Modbus RTU data in KepServer EX 6

  • December 16, 2025
  • 1 reply
  • 225 views

Dear Members,

I am new to KEPServerEX 6 and request expert guidance to configure Modbus RTU (RS-232) data in KEPServer, which I have been unable to achieve so far.

Current Challenge

At present, to bring RS-232 data into Modbus TCP/IP, I am using a protocol converter. However, this setup works only after running a Python script on the historian server that continuously sends ASCII commands (video attached) to read serial data and then pushes it back to the historian. Only then does the converter provide usable values for our Digital Data Visualization.

Pain Points

This approach is becoming unsustainable due to the following reasons:

  • The Python script must run 24×7

  • Any script failure results in complete data loss

  • Maintenance and troubleshooting are time-consuming

  • The solution is not reliable for long-term plant operations

What I Am Looking For

I want to directly configure the RS-232 / Modbus RTU device in KEPServerEX and expose the data as Modbus TCP/IP (or directly to the historian), without using any external code or scripts.

 

I have been struggling with this issue for the past 6 months. Although I have an active AMC, I have not yet received a workable solution.

 

If any expert here has successfully implemented a similar configuration or can guide me with the correct setup, drivers, or best practices in KEPServerEX, your support would be highly appreciated.

 

Thank you in advance for your help.

 

Best regards,
Sangram Patnaik

INDIA

Best answer by SlidingDownhill

I'm no expert by any measure, but I use UCON to pull serial (RS-485) data into the kepware datalogger, I'm sure you could use it to populate a series of static tags that you could then use to feed your historian. How your historian gets the data would need to be figured out but possibly ODBC?

I don't understand the need to move it to ModbusTCP.

1 reply

12-Amethyst
December 17, 2025

I'm no expert by any measure, but I use UCON to pull serial (RS-485) data into the kepware datalogger, I'm sure you could use it to populate a series of static tags that you could then use to feed your historian. How your historian gets the data would need to be figured out but possibly ODBC?

I don't understand the need to move it to ModbusTCP.