D
TRICONEX documentation gives a warning that "Online changes should be avoided as an error in application might cause unpredicatable behaviour or a trip". Has anyone had any experience of tripping caused during download change process? not because of human error in application but because of the download change process itself? If we remove existing tags connected to a AND gate, and connect this gate to new memory tags (whose state is defined in a different program), what will be the state of those tags/& output of AND gate during the download change process? Will they go to a zero state first assuming that before the download change their state was High? or will they stay high throughout the process?
Are there any other risks associated with download change command provided that sufficient scan surplus is available?
Are there any other risks associated with download change command provided that sufficient scan surplus is available?
