System variables - EtherNet/IP™ targets
Available for AXC F 2152 (from firmware release 2019.3), for AXC F 1152 and AXC F 3152 (all available firmware releases)
A PLCnext controller can be operated as slave device in an EtherNet/IP™ (short: EIP) network, provided that this functionality is available. As of now, the controller can only be used as a target, but not as an I/O controller.
Note: With EtherNet/IP™, different terms are used for the ends of a communication line. In the PLCnext Technology context, it is "target" and "controller". Show more terms in useShow more terms in use
| Terms for the end of a communication line which establishes an EtherNet/IP™ connection can be: | Terms for the end of a communication line which takes part in an EtherNet/IP™ connection can be: |
|
|
| Typically, this is a PLC (just not a PLCnext Control) but can also be a stand-alone HMI panel. | In this context, this would be a PLCnext Control, or other devices with PLCnext Technology. |
In PLCnext Engineer, the EtherNet/IP™-specific parameters are available under the Ethernet/IP category in the Settings editor of the controller. The parameters in the category represent the attributes of the EtherNet/IP™ Identity Object (contains device-related identity values). All parameters are read-only.
For communicating with the EtherNet/IP™ network, the PLCnext Technology controller provides the system variables listed below that you can use in your IEC 61131‑3 code.
Known for all firmware versions on all supported PLCnext Control devices:
If the firewall is activated via WBM, the operation of EtherNet/IP™ is no longer possible. This can be remedied by subsequently activating the ports:
- Incoming connections: port 44818
- Outgoing connections: port 2222
EtherNet/IP™ variables
| System variable | Type | Description |
| EIPD_INPUTS | EIPD_IO_ARRAY | Process input data array – consumed data. Memory area for the input process data that the PLCnext device (here as an EtherNet/IP™ target) receives from a higher-level EtherNet/IP™ controller. |
| └ [0] .. [127] | WORD | |
| EIPD_OUTPUTS | EIPD_IO_ARRAY | Process input data array – produced data. Memory area for the input process data that the PLCnext device (here as an EtherNet/IP™ target) sends to a higher-level EtherNet/IP™ controller. |
| └ [0] .. [127] | WORD | |
| EIPD_INPUTS_LENGTH | WORD | Process input data length that was configured for the EtherNet/IP™ target. Fixed at 256 bytes. |
| EIPD_OUTPUTS_LENGTH | WORD | Process output data length that was configured for the EtherNet/IP™ target. Fixed at 256 bytes. |
| EIPD_VALID_DATA_CYCLE | BOOL | The higher-level EtherNet/IP™ controller has established the connection. Indicates whether a connection exists, and cyclic data is being exchanged between the EtherNet/IP™ target and the higher-level EtherNet/IP™ controller, and whether the last frame received contained valid data. |
| EIPD_PEER_RUN | BOOL | Status of the higher-level EtherNet/IP™ controller. Indicates whether the higher-level EtherNet/IP™ controller is connected and actively running. The value is TRUE if the higher-level controller is in the RUN state, meaning the application logic on the controller is executed.Note: This flag is only valid with an established EtherNet/IP™ connection ( EIPD_VALID_DATA_CYCLE is TRUE). If EIPD_PEER_IDLE and EIPD_PEER_RUN both are FALSE, the remote controller does not send its state.
|
| EIPD_PEER_IDLE | BOOL | Status of the higher-level EtherNet/IP™ controller. Indicates whether the higher-level EtherNet/IP™ controller is connected but stopped. The value is TRUE if the higher-level controller is in the STOPPED state, meaning the application logic on the higher-level controller is not executed. Note: This flag is only valid with an established EtherNet/IP™ connection ( EIPD_VALID_DATA_CYCLE is TRUE).If EIPD_PEER_IDLE and EIPD_PEER_RUN both are FALSE, the remote controller does not send its state.
|