
FUNCTION CODE CONFIGURATION
FUNCTION CODES
WBPEEUI240759A0
4 - 3
The EDI module is able to support fast scan rates of 125 milli-
seconds. The performance is primarily dependent on the load
of the PLC:
•
Size of message packets.
•
Synchronous or asynchronous operations.
•
Frequency of data requests.
•
Whether or not the file being written is being shared.
•
Implementation of ladder logic on the PLC.
•
Network load.
•
Programming software on-line and off-line.
The performance measured using HP9000/745 computer run-
ning Interchange software and a PLC-5E handled approxi-
mately 50 to 54 transactions per second for synchronous read
and write operations and 57 to 63 transactions per second for
asynchronous read and write operations.
It is recommended to keep the total number of requests made
to the PLC at 50 to 60 maximum. To stay within this threshold,
much care should be taken in configuring the function codes.
The following guidelines should be observed to configure the
function codes for optimum performance:
•
All points must be grouped in contiguous order with little
or no addressing gaps between logically grouped points.
•
Fast scan rates should only be selected for points critical to
the interface. Again, these points must be grouped in con-
tiguous order with little or no addressing gaps between log-
ically grouped points.
•
Use the aperiodic or periodic options to determine the most
efficient means of sending data to the PLC (refer to
EDI Performance
NOTES:
1.
The performance data provided in this section is based on the
EDI module using Allen Bradley interface protocol.
2.
All performance is based on the EDI module and PLCs operat-
ing on a dedicated Ethernet network.
The following information should be considered when configur-
ing function codes to obtain maximum performance from the
EDI module.
•
The EDI module is capable of generating messages (i.e.,
request, replies, acknowledgments, etc.) at a typical rate of
one message every four to five milliseconds.