Thread Content
What parameters are related to the DCS programming cycle? Is it the reaction time of the DCS’s own control software, or the length of the programming?
From the user’s perspective, it is the scanning cycle set within the program; from the manufacturer’s perspective, it refers to the CPU’s processing speed, storage capacity, and redundancy features
It’s related to the program settings; it depends on what you intend to use and what kind of program you set up. :):):):)
The reaction speed of DCS systems from different manufacturers varies, and the programming control sequences are also different. In other words, the reaction cycle depends on the product manufactured by each manufacturer
I’m not sure what you mean by the programmed cycle time. In Siemens systems, it’s possible to choose the scanning interval of the program, that is, the execution cycle. For example, if the scanning cycle is 1 second, it means the program will be executed once per second; your program will only respond if the signal changes over a period of more than 1 second.
In other words, it’s related to the program’s set cycle, right?
Both the computing speed of the DCS control card and the length of the program itself have an impact; generally, DCS systems provide several scanning cycles for the user to choose from.
That must also be related to the signal control and feedback time when transmitting to the DCS
Firstly, the fastest achievable cycle is related to the system itself. Imported ones are fast, while domestic ones are a bit slower. Then it can be set to a slower speed.
Both Zhongkong and LS seem to have a response time of 500 milliseconds. Well, achieving 1 millisecond doesn’t seem to make much difference; no matter how fast the signal is, it’s only when the actual action takes place that something is completed. High-speed control is where this speed really matters