Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
it depends on what is changed, if the varlist is changed the cpu must stop
if only a variable is changed the cpu does not need a stop but i would recommend it.
if program is changed the cpu must stop even if inside a library there is a change.
If cpu is not allowed to stop you will have to write your program complete and good in one go.
remember the retain vars etc.
If process is that critical use another method like two plc next to each other with a changeover.
it is called redundant.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using Codesys not from long time... but still not clear 100% when CPU need to go to stop in order to update a program:
-if I "rebuild all " project--> STOP
-when I "build" (F11) ? (usually not..)--> NOT STOP
-when "moving" project from one pc to another?-->??
other-->?
I mean, what is the rule for that? (in some process a CPU going to stop to update the program is not acceptable...)
Regards
it depends on what is changed, if the varlist is changed the cpu must stop
if only a variable is changed the cpu does not need a stop but i would recommend it.
if program is changed the cpu must stop even if inside a library there is a change.
If cpu is not allowed to stop you will have to write your program complete and good in one go.
remember the retain vars etc.
If process is that critical use another method like two plc next to each other with a changeover.
it is called redundant.