ICC OPC-PRT3, Инструкция по эксплуатации, Страница: 55 / 115

ICC
54
10.2.3 Connection Timeout Options
In the studio
’s Project panel, navigate to
OPC-PRT3
…Ethernet…EtherNet/IP Server
. The following
configuration options will determine the actions to be taken if the connection is abnormally terminated or
lost. While this feature provides an additional level of fail-safe functionality for those applications that
require it, there are several ramifications that must be understood prior to enabling this capability. Note
that a certain degree of caution must be exercised when using the timeout feature to avoid “nuisance”
timeouts from occurring.
Scanner Idle State Behavior
EtherNet/IP scanners
(such as PLCs) have the option of adding a “run/idle” header to all class 1 (I/O)
data packets sent to devices. This header is intended to signify when the scanner is in the
“running”
state or the
“idle” state. For example, an Allen Bradley ControlLogix PLC will set the run/idle header to
Idle when its
processor keyswitch is placed in the “PROG” position.
The Invoke Timeout on Scanner Idle State setting configures the behavior of the interface card when the
scanner sets the run/idle header to idle.
•
If the checkbox is not checked (default setting), then the driver will maintain the last consumed I/O
data values received from the scanner. For example, if the scanner commanded the inverter to run
prior to the run/idle header being set to Idle, then the inverter will continue to run.
•
If the checkbox is checked, then the driver will perform the Timeout Action .
Timeout Action
Select an action from the drop down menu:
“None”.................................. No effect. The inverter will continue to operate with the last available
settings.
“Apply Fail-safe Values” ....... Apply the fail-safe values as described in section 6.6.1.
“Fault Drive” ......................... The behavior will depend on the timeout conditions set by the inverter
(function codes o27 and o28), which may result in an Er5 fault. Refer to
section 3.2.
Enable Drive Fault Reset
This will clear the Er5 fault once communication is re-established. This option is only available if the
Timeout Action
is set to “Fault Drive”.
10.2.4 Generic Class 1 I/O Produced and Consumed Data Settings
The Produced Data Word and Consumed Data Word objects are only applicable when connecting to
assembly instances 100 and 150 (generic I/O), which is typically the case. The Produced Data Word
defines the structure of status data sent from the inverter back to the controller (T->O, target to
originator). The Consumed Data Word objects will define the structure of the command data sent from
the EtherNet/IP controller (for example, a ControlLogix PLC) to the inverter (O->T, originator to target).
These objects allow the creation of custom-
built I/O data. Up to 32 “command” function code values can
be sent to the inverter, and up to 32 “status” function code values can be sent back to the controller.
Therefore, up to 32 Produced and 32 Consumed Data Word objects can be created. If a consumed word
offset is not defined, that data will be ignored by the inverter. If a produce word offset is not defined, the
value will default to 0. The size of the actual I/O produced and consumed data is determined by the
client upon initial connection establishment. Since a data word utilizes 2 bytes, the size must be an even
number of bytes. The I/O data format is summarized in Table 21.
Description
This 32-character (max) field is strictly for user reference: it is not used at any time by the driver.
Produced Data Word Offset
The value from the associated inverter function code will populate this word offset of the produced data
that is to be sent to the client. It is recommend to start at word offset 0.
Consumed Data Word Offset
The consumed data received from the client at this word offset will contain the value to be written to the
associated inverter function code. It is recommend to start at word offset 0.