Introduction

The T_U_ANA_SIS_IN_4 device derived data type (DDDT) is the interface between the BMXSAI0410 analog input module and the application running in the CPU. The T_U_ANA_SIS_IN_4 DDDT incorporates the data types T_SAFE_COM_DBG_IN and T_U_ANA_SIS_CH_IN.

All of these structures are described, below.

T_U_ANA_SIS_IN_4 DDDT Structure

The T_U_ANA_SIS_IN_4 DDDT structure includes the following elements:

Element

Data Type

Description

Access

MOD_HEALTH1

BOOL

  • 1: The module is operating correctly.

  • 0: The module is not operating correctly.

RO

SAFE_COM_STS1

BOOL

  • 1: Module communication is valid.

  • 0: Module communication is not valid.

RO

S_COM_DBG

T_SAFE_COM_DBG_IN

Safe communication debug structure.

RO

CONF_LOCKED

BOOL

  • 1: Module configuration is locked.

  • 0: Module configuration is not locked.

RO

CH_IN

ARRAY[0...3] of T_U_ANA_SIS_CH_IN

Array of structure of channel.

MUID2

ARRAY[0...3] of DWORD

Module unique ID (auto-assigned by Control Expert)

RO

RESERVED

ARRAY[0...9] of INT

1. When the SAFE task on CPU is not in running mode, the data exchanged between the CPU and the module are not updated and MOD_HEALTH and SAFE_COM_STS are set to 0.

2. This auto-generated value can be changed by executing the Build > Renew Ids & Rebuild All command in the Control Expert main menu.

T_SAFE_COM_DBG_IN Structure

The T_SAFE_COM_DBG_IN structure includes the following elements:

Element

Data Type

Description

Access1

S_COM_EST

BOOL

  • 1: Communication with the module is established.

  • 0: Communication with the module is not established or corrupted.

RO

M_NTP_SYNC

BOOL

With CPU firmware 3.10 or earlier:

  • 1: The module is synchronized with the NTP server.

  • 0: The module is not synchronized with the NTP server.

NOTE: With CPU firmware 3.20 or later, the value is always 1.

RO

CPU_NTP_SYNC

BOOL

With CPU firmware 3.10 or earlier:

  • 1: The CPU is synchronized with the NTP server.

  • 0: The CPU is not synchronized with the NTP server.

NOTE: With CPU firmware 3.20 or later, the value is always 1.

RO

CHECKSUM

BYTE

Communication frame checksum.

RO

COM_DELAY

UINT

Communication delay between two values received by the module:

  • 1...65534: The time, in ms, since the last communication was received by the CPU from the module.

  • 65535: The CPU did not receive a communication from the module.

RO

COM_TO

UINT

Communication time-out value for communications coming from the module.

NOTE: You may want to edit this read/write value to equal or exceed the actual communication time for the module (for example, in a remote RIO drop).

R/W

STS_MS_IN

UINT

Safe timestamp value for the fraction of a second, to the nearest ms, of the data received from the module.

RO

S_NTP_MS

UINT

Safe time value for the fraction of a second, to the nearest ms, for the current cycle.

RO

STS_S_IN

UDINT

Safe timestamp value in seconds of the data received from the module.

RO

S_NTP_S

UDINT

Safe time value in seconds for the current cycle.

RO

CRC_IN

UDINT

CRC value for data received from the module.

RO

T_U_ANA_SIS_CH_IN Structure

The T_U_ANA_SIS_CH_IN structure includes the following elements:

Element

Data Type

Description

Access

FCT_TYPE

WORD

  • 1: The channel is enabled.

  • 0: The channel is not enabled.

RO

CH_HEALTH1

BOOL

  • 1: The channel is operational.

  • 0: An error has been detected on the channel, which is not operational.

Formula:

CH_HEALTH = not (OOR or IC) and SAFE_COM_STS

RO

VALUE

INT

Analog input value.

Formula:

VALUE = if (SAFE_COM_STS and not (IC)) then READ_VALUE else 0

RO

OOR

BOOL

  • 1: The channel input current value is out of range, either:

    • <3.75 mA

    • >20.75 mA

  • 0: The channel input current value is not out of range.

RO

IC

BOOL

  • 1: Invalid channel detected by the module.

  • 0: The channel is declared internally operational by the module.

RO

1. When the SAFE task on CPU is not in running mode, the data exchanged between the CPU and the module are not updated and CH_HEALTH is set to 0.