Standalone DDT Data Structure for M580 CPUs

Introduction

This topic describes the Control Expert Device DDT tab for an M580 CPU in a local rack. A derived data type (DDT) is a set of elements with the same type (ARRAY) or with different types (structure).

NOTE: The device DDT type supported by a standalone M580 CPU depends on its firmware version, and can be T_BMEP58_ECPU, T_BMEP58_ECPU_EXT, T_BMEP58_ECPU_EXT2, or T_BMEP58_ECPUPRP_EXT.

Access the Device DDT Tab

Access the device DDT for the CPU in Control Expert:

Step	Action
1	Open a Control Expert project that includes an M580 CPU in the configuration.
2	Rebuild the project ( Build > Rebuild All Project .)
3	Open the Data Editor in the Control Expert Project Browser (Tools > Data Editor).
4	Select the Device DDT checkbox.
5	Expand (+) the Device DDT in the Name column.

You can add this variable to an Animation Table to read the status and set the object control bit.

NOTE: The red arrow and lock icons in the Device DDT table indicate that the variable name was auto-generated by Control Expert based on the configuration of the communication module, local slave, or distributed device. The variable name cannot be edited.

Input and Output Freshness

This table describes the inputs and outputs that are associated with EtherNet/IP or Modbus devices:

Name	Description
Freshness	This is a global bit: 1: All input objects below (Freshness_1 , Freshness_2 , etc.) for the associated device are true ( 1) and provide up-to-date data. 0: One or more inputs (below) is not connected and does not provide up-to-date data.
Freshness_1	This bit represents individual input objects for the connection: 1: The input object is connected and provides up-to-date data. 0: The input object is not connected and does not provide up-to-date data.
Freshness_2	This bit represents an individual input object for the device: 1: The input object is true (1 ) and provides up-to-date data. 0: The input object is not connected (0 ) and does not provide up-to-date data.
Freshness_3
...
(available)	The rows after the Freshness data are organized in groups of Inputs and Outputs that have user-defined names. The number of input and output rows depends on the number of input and output requests configured for a particular device.

Parameters

Use the Control Expert Device DDT tab to configure parameters for the CPU RIO head on the local rack:

Parameter		Description
Implicit device DDT	Name	the default name of the device DDT
Implicit device DDT	Type	module type (uneditable)
Goto details		link to the DDT data editor screen

Standalone Configuration

These tables describe the fields in the implicit device DDT type that is used with the CPU RIO communication server in standalone configurations using Unity Pro 10.0 or later and M580 CPU version 2.01 or later.

NOTE:

Unity Pro is the former name of Control Expert for version 13.1 or earlier.

Input Parameters

The following tables describe the input parameters in the device DDT for the CPU.

ETH_STATUS (WORD):

Name	Type	Bit	Description
PORT1_LINK	BOOL	0	0 = ETH 1 link is down.
PORT1_LINK	BOOL	0	1 = ETH 1 link is up.
PORT2_LINK	BOOL	1	0 = ETH 2 link is down.
PORT2_LINK	BOOL	1	1 = ETH 2 link is up.
PORT3_LINK	BOOL	2	0 = ETH 3 link is down.
PORT3_LINK	BOOL	2	1 = ETH 3 link is up.
ETH_BKP_PORT_LINK	BOOL	3	0 = Ethernet backplane link is down.
ETH_BKP_PORT_LINK	BOOL	3	1 = Ethernet backplane link is up.
REDUNDANCY_STATUS (see the note below.)	BOOL	5	0 = Redundant path is not available.
REDUNDANCY_STATUS (see the note below.)	BOOL	5	1 = Redundant path is available.
SCANNER_OK	BOOL	6	0 = Scanner is not present.
SCANNER_OK	BOOL	6	1 = Scanner is present.
GLOBAL_STATUS	BOOL	7	0 = At least one service is not operating normally. NOTE: Refer to the footnotes for `SERVICE_STATUS` and `SERVICE_STATUS2`, below, to identify the services that set `GLOBAL STATUS` to 0.
GLOBAL_STATUS	BOOL	7	1 = All services are operating normally.
NETWORK_HEALTH	BOOL	8	0 = A potential network broadcast storm is detected. NOTE: Check your wiring and your CPU and BMENOC0301/11 configurations.
NETWORK_HEALTH	BOOL	8	1 = A network broadcast storm is not detected.
NOTE: You can monitor breaks in the RIO main ring by diagnosing the REDUNDANCY_STATUS bits in the CPU module device DDT. The system detects and reports in this bit a main ring cable break that persists for at least 5 seconds. REDUNDANCY_STATUS bit value: 0: The cable is broken or the device is stopped. 1: The loop is present and healthy.

NOTICE

UNEXPECTED EQUIPMENT BEHAVIOR

Confirm that each module has a unique IP address. Duplicate IP addresses can cause unpredictable module/network behavior.

Failure to follow these instructions can result in equipment damage.

SERVICE_STATUS (WORD):

Name	Type	Bit	Description
RSTP_SERVICE¹	BOOL	0	0 = RSTP service is not operating normally.
RSTP_SERVICE¹	BOOL	0	1 = RSTP service is operating normally or disabled.
PORT502_SERVICE¹	BOOL	2	0 = Port 502 service is not operating normally.
PORT502_SERVICE¹	BOOL	2	1 = Port 502 service is operating normally or disabled.
SNMP_SERVICE¹	BOOL	3	0 = SNMP service is not operating normally.
SNMP_SERVICE¹	BOOL	3	1 = SNMP service is operating normally or disabled.
MAIN_IP_ADDRESS_STATUS	BOOL	4	0 = The main IP address is a duplicate or unassigned.
MAIN_IP_ADDRESS_STATUS	BOOL	4	1 = The main IP address is unique and valid.
ETH_BKP_FAILURE	BOOL	5	0 = Ethernet backplane hardware is not operating properly.
ETH_BKP_FAILURE	BOOL	5	1 = Ethernet backplane hardware is operating properly.
ETH_BKP_ERROR	BOOL	6	0 = Ethernet backplane error detected.
ETH_BKP_ERROR	BOOL	6	1 = Ethernet backplane is operating properly.
EIP_SCANNER¹	BOOL	7	0 = Service not operating normally.
EIP_SCANNER¹	BOOL	7	1 = Service operating normally.
MODBUS_SCANNER¹	BOOL	8	0 = Service not operating normally.
MODBUS_SCANNER¹	BOOL	8	1 = Service operating normally.
NTP_SERVER^1,²	BOOL	9	0 = SNTP server not operating normally.
NTP_SERVER^1,²	BOOL	9	1 = SNTP server operating normally.
SNTP_CLIENT^1,²	BOOL	10	0 = Service not operating normally.
SNTP_CLIENT^1,²	BOOL	10	1 = Service operating normally.
WEB_SERVER¹	BOOL	11	0 = Service not operating normally.
WEB_SERVER¹	BOOL	11	1 = Service operating normally.
FIRMWARE_UPGRADE	BOOL	12	0 = Service not operating normally.
FIRMWARE_UPGRADE	BOOL	12	1 = Service operating normally.
FTP	BOOL	13	0 = Service not operating normally.
FTP	BOOL	13	1 = Service operating normally.
FDR_SERVER¹	BOOL	14	0 = Service not operating normally.
FDR_SERVER¹	BOOL	14	1 = Service operating normally.
EIP_ADAPTER¹	BOOL	15	0 = EIP adapter (server) service not operating normally.
EIP_ADAPTER¹	BOOL	15	1 = EIP adapter (server) service operating normally.
1. When this service is set to 0, `GLOBAL_STATUS` is also set to 0. 2. Only for firmware earlier than version 4.01.

SERVICE_STATUS2 (WORD):

Name	Type	Bit	Description
A_B_IP_ADDRESS_STATUS	BOOL	0	0 = Duplicate IP or no IP address assigned.
A_B_IP_ADDRESS_STATUS	BOOL	0	1 = IP addresses (A/B status) correctly assigned.
LLDP_SERVICE¹	BOOL	1	0 = LLDP service is not operating normally.
LLDP_SERVICE¹	BOOL	1	1 = LLDP service is operating normally or disabled.
EVENT_LOG_STATUS	BOOL	2	0 = Event log service is not operating normally.
EVENT_LOG_STATUS	BOOL	2	1 = Event log service is operating normally or is disabled.
LOG_SERVER_NOT_REACHABLE	BOOL	3	1 = No acknowledgment received from the syslog server.
LOG_SERVER_NOT_REACHABLE	BOOL	3	0 = Acknowledgment received from the syslog server
CSIO_SCANNER (CIP Safety PAC)	BOOL	4	0 = At least one CIP Safety connection is not operating normally.
CSIO_SCANNER (CIP Safety PAC)	BOOL	4	1 = All CIP Safety I/O devices are operating normally.
NTP_SYNC	BOOL	5	1= Server Only mode..
NTP_SYNC	BOOL	5	0 = Not Server Only mode.
NTP_SERVICE	BOOL	6	0 = NTP Daemon status = down.
NTP_SERVICE	BOOL	6	1 = NTP Daemon status = active.
NTP_QUALITY_WARNING	BOOL	7	1= Quality of the clock out of the range defined in the configuration.
NTP_QUALITY_WARNING	BOOL	7	0 = Clock quality within defined configuration range.
(reserved)	–	8–15	(reserved)
1. When this service is set to 0, `GLOBAL_STATUS` is also set to 0.

ETH_PORT_1_2_STATUS (BYTE):

Name	Type	Description
Ethernet ports function and RSTP role coded on 2 bits	Bits 1...0	0: ETH 1 disabled
		1: ETH 1 access port
		2: ETH 1 port mirroring
		3: ETH 1 device network port
	Bits 3...2	reserved (0)
	Bits 5...4	0: ETH 2 disabled
		1: ETH 2 access port
		2: ETH 2 port mirroring
		3: ETH 2 device network port
	Bits 7...6	0: ETH 2 alternate RSTP port
		1: ETH 2 backup RSTP port
		2: ETH 2 designated RSTP port
		3: ETH 2 root RSTP port

ETH_PORT_3_BKP_STATUS (BYTE):

Name	Bit	Description
Ethernet ports function and RSTP role coded on 2 bits	Bits 1...0	0: ETH 3 disabled
		1: ETH 3 access port
		2: ETH 3 port mirroring
		3: ETH 3 device network port
	Bits 3...2	0: ETH 3 alternate RSTP port
		1: ETH 3 backup RSTP port
		2: ETH 3 designated RSTP port
		3: ETH 3 root RSTP port
	Bits 5...4	0: The Ethernet backplane port is disabled.
	Bits 5...4	1: The Ethernet backplane port is enabled to support Ethernet communications.
	Bits 7...6	reserved (0)

FDR_USAGE:

Type	Type	Description
FDR_USAGE	BYTE	% of FDR server usage

NTP_WITHIN:

Type	Type	Description
NTP_WITHIN	UINT	Estimated accuracy of the clock in milliseconds.

NTP_NB_SERVER_CONNECTED:

Type	Type	Description
NTP_SERVER_CONNECTED	UINT	Number of servers connected.

IN_PACKETS (UINT):

Type	Bit	Description
UINT	0-7	number of packets received on the interface (internal ports)

IN_ERRORS (UINT):

Type	Bit	Description
UINT	0-7	number of inbound packets that contain detected errors

OUT_PACKETS (UINT):

Type	Bit	Description
UINT	0-7	number of packets sent on the interface (internal ports)

OUT_ERRORS (UINT):

Type	Bit	Description
UINT	0-7	number of outbound packets that contain detected errors

CONF_SIG (UDINT):

Type	Bit	Description
UDINT	0-15	Signatures of all files on local module FDR server

Output Parameters

Although the complete Hot Standby Device DDT is not exchanged from the primary CPU to the standby CPU, these fields are transferred: DROP_CTRL; RIO_CTRL; DIO_CTRL

These tables describe those output parameters:

DROP_CTRL:

Name	Type	Rank	Description
DROP_CTRL	BOOL	1...32 or 1...64	1 bit per RIO drop (up to 32 or 64 depending on the CPU firmware version)

Name

Type

Rank

Description

DROP_CTRL

BOOL

1...32

1...64

1 bit per RIO drop (up to 32 or 64 depending on the CPU firmware version)

RIO_CTRL:

Name	Type	Rank	Description
RIO_CTRL	BOOL	257...384	1 bit per RIO (up to 128)

DIO_CTRL:

Name	Type	Rank	Description
DIO_CTRL	BOOL	513...640	1 bit per DIO (up to 128)

CSIO_HEALTH:

Name	Type	Rank	Description
CSIO_HEALTH (safety)	BOOL	769...896	CSIO health bits (1 bit per DIO up to 68 CSIOs)

SERVICE_CMD (WORD):

Name	Bit	Rank	Description
NTP_ENABLE	BOOL	0	0: Stop the NTP daemon.
NTP_ENABLE	BOOL	0	1: Start the NTP daemon.

RED_PRP_DROP_SWAP:

Name	Type	Rank	Description
RED_PRP_DROP_SWAP	BOOL	1...64	1 bit per PRP drop (up to 64). A swap is only possible for the PRP drop managed by BMECRA31310(H) adapter modules in redundant mode.

Device Health Status

Although the complete Hot Standby Device DDT is not exchanged from the primary CPU to the standby CPU, these fields are transferred: DROP_HEALTH; RIO_HEALTH; LS_HEALTH; DIO_HEALTH

This table describes the health of the devices that are scanned by the module. The data is presented as an array of boolean:

Parameter	Type	Health status of ...
DROP_HEALTH	ARRAY [1...32] of BOOL or ARRAY [1...64] of BOOL	One array element corresponds to one X80 drop managed by a BMXCRA••••• or BMECRA••••• adapter module (up to a maximum of 32 or 64 depending on the CPU firmware version).
RIO_HEALTH	ARRAY [257...384] of BOOL	RIO devices: One array element corresponds to one RIO device (up to a maximum of 128 RIO devices).
LS_HEALTH	ARRAY [1...3] of BOOL	local slaves: One array element corresponds to one local slave (up to a maximum of three local slaves).
DIO_HEALTH	ARRAY [513...640] of BOOL	DIO devices: One array element corresponds to one DIO device (up to a maximum of 128 DIO devices).
CSIO_HEALTH (CIP Safety PAC)	ARRAY [769...896] of BOOL	CSIO devices: One array element corresponds to one CSIO device (up to a maximum of 128 CSIO devices).

Values:

1 (true): A device is healthy. The input data from the device is received within the pre-configured health timeout.
0 (false): A device is not healthy. The input data from the device is not received within the pre-configured health timeout.