The mandatory intermediate variables in Tricon TS3000 have been changed!
Thread Content
In the control system of a certain air separation unit, Tricon TS3000 (1131: 4.1.420), due to an engineering oversight, an unused intermediate variable (a boolean value) was forced to “0” in order to render it ineffective. Yet, a communication point in the DCS continued to write new values to it at regular intervals (as a 1 signal). Logically, a value that has been forced should not be able to be changed, but in practice this “change” did take effect! ! Who can answer this? ? Thank you. (Asked the experts at Congisun; no answer available.:@)
4.1.420 – that’s a very old version; the project must be from before 2006, right? It seems that intermediate variables cannot be forced; only the tagname that serves as the source can be forced. Could you take a screenshot and show it?
At that time, people from Kangjisen came and said they had never seen it before and couldn’t explain it. But it is indeed an intermediate variable, and it has indeed been “rewritten”. It is a logic for clock synchronization.
This year, an expert from Conixen confirmed that communication points can still be changed even after they have been forced!
There’s no need to look; it’s already been confirmed that even if the communication point is forced, the data can still be written there! Confirmed!
If it’s not a communication point, then it shouldn’t be possible, right? Can’t you solve this problem of yours then?
To get back to the point, if it weren’t a communication point, there would be no need to discuss it here.