Uncommitted Changes - Allen-Bradley Micro830 Manual

Rockwell Automation Publication 2080-UM002K-EN-E - March 2019
ATTENTION: Use extreme caution when you use Run Mode Change.
Mistakes can injure personnel and damage equipment. Before using Run
Mode Change:
·
assess how machinery will respond to the changes.
·
notify all personnel about the changes.
A new global variable __SYSVA_PROJ_INCOMPLETE has been added to
indicate when Run Mode Changes are being made. This can be used to notify
personnel on the HMI that there are uncommitted changes in the controller.
Bit Definitions of Global Variable – __SYSVA_PROJ_INCOMPLETE
Bit Definition
0 Set when the Run Mode Change process starts.
Cleared once the Run Mode Change is written permanently to the controller
(completion of Accept or Undo).
This bit can be used to warn operators that a run mode change is in progress and
that there are uncommitted changes in the controller.
1 Set if an error occurred while saving the changes to flash or an integrity check failed
during Run Mode Change.
Cleared on the next successful Run Mode change.
When you perform a Test Logic Change, the value of the variable is changed from
zero to one. After you choose to accept or undo the changes, the value of the
variable is reset to zero.
When a Test Logic is performed, or undoing changes after the Test Logic
IMPORTANT
is completed, any active communication instructions will be aborted
while the changes are downloaded to the controller.

Uncommitted Changes

Uncommitted changes are changes made in RMC that have not been accepted or
undone after a Test Logic Change has been performed.
If the controller power loses power while there are uncommitted changes, you
will not be able to re-enter RMC upon reconnection. You can choose to re-
download the project to keep the changes, or upload if the uncommitted changes
are not wanted.
If you choose to upload a project with uncommitted changes from the controller,
you cannot enter RMC until you have done a full download.
About Your Controller Chapter 2
13