Rockwell Automation 283A ArmorStart with ArmorPoint Backplane - Getting Started - Manual (Page 21)

Publication 283A-QS001C-EN-P - July 2006
21
Triggering a System Wide Read
Once the system configuration has been done, a System Wide Read must be
initiated. The logic to trigger both a System Wide Read and Write is
contained in a subroutine called Handle_All_Armor. The rungs are shown
below for reference.
Figure 18 Handle_All_Armor Rungs
To trigger the system wide read, the contact Read_All_Condition_Here
needs to be energized in the ladder logic. This can be done through
additional logic or simply by energizing the bit, on-line, in the
RSLogix™5000 software, Controller Tag monitor screen. The
Read_All_Condition_Here is handled as a one shot inside the logic, but
should be de-energized at a later time. This is so a system wide read is not
triggered after every Logix power cycle or for each transition from Program
to RUN mode. When the read finishes successfully, the
Read_All_System_Done_Flag bit energizes in the logic. However, if an
error occurs during the read, the Read_All_System_Error_Flag bit
energizes and the error will be logged into the structure called
Error_Report.
Triggering a System Wide Write
Once a successful System Wide Read has been initiated and the
Read_All_System_Done_Flag bit is energized, a System Wide Write can
be triggered. To trigger the system wide write, the contact
Write_All_Condition_Here needs to be energized in the ladder logic. This
can be done through additional logic or simply by energizing the bit on-line,
in the RSLogix5000 software, Controller Tag monitor screen. The
Write_All_Condition_Here is handled as a one shot inside the logic, but
should be de-energized at a later time. This is so a System Wide Write is not
triggered after every Logix power cycle or for each transition from Program
to RUN mode. When the write finishes successfully, the
Write_All_System_Done_Flag bit energizes in the logic. If an error occurs
during the write, the Write_All_System_Error_Flag bit energizes and the
error will be logged into the structure called Error_Report.