Skip to main content
12-Amethyst
November 7, 2025
Solved

No way to read a undefined floating point value through KEPServerEX?

  • November 7, 2025
  • 1 reply
  • 689 views

When using drivers with HMI applications like InTouch or Ignition, the tag in its database could have address modifiers or simply the tag type to let the Modbus driver know that you're looking for a floating point that is using more than one register.

 

It appears that there's no way to accomplish the same thing when using KEPServerEX. Instead of a Modbus driver specifically written for Intouch or Ignition HMI applications.

The only option is to manually create tags inside of KEPServerEX and then read those from the HMI? 

Best answer by Tanquen

I was using slave and poll tools from: https://www.modbustools.com/
This added to the confusion and complexity because I could only run it for 10 minutes. I'm sure there's a setting in the tool but I figured the default would work, but to read the value correctly I did need to change the data encoding `First Word Low` option to be disabled.

There was also an issue with getting the simulator and KEPServerEX and Ignition all talking within the 10 minute window. The other day I wasn't seeing any value using `@float` but this morning I believed I was doing the same exact thing and then all the sudden I could see a value but it was still a little off.
124 vs 125.25
`First Word Low` Option fixed that but I don't know way it was `0` all day yesterday. 

 

1 reply

16-Pearl
November 11, 2025

Hello,

 

Are you looking to define tags directly in the client instead of creating them in KEPServerEX?

 

If yes, you can use dynamic tag addressing to retrieve data in the client without defining tags in the Kepware server. Here is an article that clarifies the difference between static and dynamic tags.

CS278481 - Differences between static and dynamic Tags in KEPServerEX / ThingWorx Kepware Server

 

Thanks

 

 

Tanquen12-AmethystAuthor
12-Amethyst
November 11, 2025

Yes, we were hoping to reference Modbus TCP/IP values without having to define tags inside KEPServerEX, but it looks like if we want a floating point that uses two registers there's no way to do this without creating a point inside KEPServerEX. Drivers provided by the HMI manufacturers normally have a way to do this.

That article kind of makes it look like you can with the data type modifier ?

Article - CS278481
  • Most OPC clients allow users to specify the data type as part of the request when registering a link for a specific data item. The data type specified by the OPC client is used if it is supported by the communications driver. The @[Data Type] modifier can be useful when ensuring that a communications driver interprets a piece of data exactly as needed