Table 3.3 msg write table locations, File data values – Rockwell Automation 1403-NENET Ethernet Communication Card Installation Instructions User Manual
Page 64
![background image](/manuals/578454/64/background.png)
Publication 1403-IN005A-EN-P
C-4 Sample Ladder Listing
Sequencer input file N10 contains a list of the block transfers required to
complete the active mode. The contents of N10 are copied from N11 for
Configuration mode, N12 for Setpoint mode and N13 for Run mode during
each mode’s initialization.
The reset word for the sequencer is N10:1. The first word in the rotation of the
sequencer N10:1. The value in N10:0 must be the same as that in N10:1. This
means N11:0 must equal N11:1, N12:0 must equal N12:1 and N13:0 must
equal N13:1. The size of file N10 is equal to the size of the largest sequencer
input file. For configuration and setpoint modes, this size will always be 2. In
Run mode the size depends on the number of block transfers to be performed.
The sequencer length may be expanded or reduced for run mode. It is
imperative that the corresponding file that serves as the source of the
sequencer’s input file, N13, must be modified accordingly.
File Data Values
Prior to running the sample ladder, each of the three sequencer initialization
files need to be loaded with the numbers that correspond to each mode’s block
transfer sequence. The following is a list of each mode’s initialization file and
the required/possible numbers to be stored in each. The first value of a block
Table 3.3 MSG Write Table Locations
Data File Address
(Control/Data)
Data File Size
Description
N54/N84
23
Command
N55/N85
45
Device Configuration
N56/N86
21
Setpoint
IMPORTANT
“Device Configuration” data must be placed in file N:85
and “Setpoint” data must be placed in file N:86. Failure to
place data in these files results in the ladder failing to
sequence through the respective modes.
IMPORTANT
Failure to modify the length of file N13 for a modification
of the run mode sequencer size results in improper
operation of the run mode block transfer ladder and
possible FAULT of the processor due to invalid indirect
offsets.