Communication configuration issues with the ECS100 central control unit
Thread Content
This post was last edited by Amber Heart 01 on 2018-1-15 at 10:20. The data has now been read in, but I don’t know how to convert it. Could someone please take a look and analyze it, showing me the approach? The point table and configuration are as follows; only the relevant part needs to be highlighted in the point table, and some individual parameters are not required either. So the total number of elements in the configuration is 26
What was communicated over? Convert to what. Does ECS display it? Custom half-precision is used to display instantaneous values, while floating-point values need to be divided by the range before being converted to half-precision for computation. Compensation is generally performed in floating-point format, and then converted to half-floating-point for display.
For 485 communication, parse the data to match the values 13-40 in the point table respectively
According to the configuration instructions, it is necessary to use the Modbus_IMG protocol to call the relevant module in order to read the content. What version do you have of ADVAntrol? Check the documentation for that module and give it a try.
There’s no need to do this; it’s too troublesome. The main issue lies in the parsing of the communication configuration data in the DCS system. I understand what you’re saying
The explanation is not easy to understand; it seems that the data has been passed over, but it can’t be accessed, or maybe it wasn’t passed over at all
This post was last edited by IndustryMan on 2018-1-16 09:18. OP, do you not know how to configure it? Did you read the data, but it’s inaccurate and doesn’t match? I haven’t used the central control software, but it seems that the communication address for your substation is 1, the Modbus function code is 3, while the communication addresses specified by Excel are 37001–37026. The data type is floating-point, with each piece of data occupying two registers. If you are unable to read the data correctly, try changing the parameter 7001 in the intermediate module to 7000. If you don’t know how to read the data, please refer to the software’s help documentation.
The data is available, but I don’t know how to parse it. The communication module has been set up, but the data parsing part hasn’t been completed yet
I’ll give it a try; what you said makes a lot of sense. Thank you