Thread Content
The existing VOC detection data is connected to the control system via MODEBUS and 485; the data type is real numbers, and the data length is one word. The processing method involves handling the data on a word-by-word basis, with the high and low bits reversed. Data can indeed be collected, but since it comes from separate instruments that transmit the data to the control system, it isn’t the actual values. The manufacturer only provides us with some MODBUS parameters, address tables, and information regarding the instrument’s range. How can I convert this data into actual values? I have never done communication before; I earnestly ask for detailed guidance
Ultimately, the problem lies with the VOC instrument; it is necessary to contact the manufacturer of this instrument to obtain the manual or communication protocols before data conversion can be carried out. The read data can be converted to the desired format directly here in the control panel. The premise remains the same as before: it is necessary to be able to understand what information the instruments are transmitting. As for configuring communication, it is relatively more complicated. It’s not clear when expressed in two sentences.
The first three values have had their highs and lows reversed, and the difference from the actual values is minimal; for the subsequent values, after they were reversed, the manufacturer said that the range values need to be used in the calculations. But how exactly should those values be applied? The manufacturer said that they had always just given those instructions, and that it was up to us to develop the algorithms ourselves – they had never done it before. Now we want to know how to incorporate these values into the calculation range Also: Is this something that DCS configuration personnel must know?
:victory: Find the manufacturer
To work with communication, one needs to understand the methods of communication, whether they are standard or non-standard protocols, the baud rate, device addresses, register addresses, and data types.
You can try to first convert the read uint to a float type, then perform the conversion based on the range by dividing by the range value and adding the lower limit of that range. The actual measured value is of floating-point type; if a sfloat type is required, it needs to be converted again. You should be able to get what you want. I think you said that three numbers have been read and are correct. Then the communication is normal with no issues. It’s just a conversion of the graphical programming configuration on the DCS side. Let’s look at a few cases.
Refer to \"Application of Interconnection of Multiple Control Systems in Water-Coal Slurry Plants\" – all communications are the same.
I want to know right now how to convert the range. The manufacturer says we should know how to do it, but I really have no idea; I’ve never dealt with communication before