Details of the IODDTs Explicit Exchange Objects of Types T_COM_MB_BMX and T_COM_MB_BMX_CONF_EXT
(Original Document)
About us
At a Glance
This part presents the explicit exchange objects of the IODDTs of types T_COM_MB_BMX and T_COM_MB_BMX_CONF_EXT that are applicable to Modbus serial and differ in terms of configuration objects availability. It includes the word type objects whose bits have a specific meaning. These objects are described in detail below.
In this part, the IODDT_VAR1 variable is of the T_COM_STS_GEN type.
Observations
In general, the meaning of the bits is given for bit status 1. In specific cases, each bit status is explained.
Not all bits are used.
Explicit Exchange Execution Flags: EXCH_STS
The following table shows the meanings of the exchange control bits of the EXCH_STS channel (%MWr.m.c.0):
Standard symbol
Type
Access
Meaning
Address
STS_IN_PROGR
BOOL
R
Reading of channel status words in progress.
%MWr.m.c.0.0
CMD_IN_PROGR
BOOL
R
Command parameter exchange in progress.
%MWr.m.c.0.1
ADJ_IN_PROGR
BOOL
R
Adjustment parameter exchange in progress (not applicable to the BMX NOM 0200 module).
%MWr.m.c.0.2
Explicit Exchange Report: EXCH_RPT
The table below presents the various meanings of the EXCH_RPT exchange report bits (%MWr.m.c.1):
Standard symbol
Type
Access
Meaning
Address
STS_ERR
BOOL
R
Detected read error for channel status words.
%MWr.m.c.1.0
CMD_ERR
BOOL
R
Anomaly during command parameter exchange.
%MWr.m.c.1.1
ADJ_ERR
BOOL
R
Anomaly while exchanging adjustment parameters (not applicable to the BMX NOM 0200 module).
%MWr.m.c.1.2
Standard Channel Detected Faults: CH_FLT
The following table explains the various meanings of the CH_FLT status word bits (%MWr.m.c.2):
Standard symbol
Type
Access
Meaning
Address
NO_DEVICE
BOOL
R
No devices are working on the channel.
%MWr.m.c.2.0
ONE_DEVICE_FLT
BOOL
R
A device on the channel is inoperating.
%MWr.m.c.2.1
BLK
BOOL
R
Terminal block is not connected.
%MWr.m.c.2.2
TO_ERR
BOOL
R
Time out overtaken (analysis needed).
%MWr.m.c.2.3
INTERNAL_FLT
BOOL
R
Internal detected error or channel self-testing.
%MWr.m.c.2.4
CONF_FLT
BOOL
R
Different hardware and software configurations.
%MWr.m.c.2.5
COM_FLT
BOOL
R
Communication analysis needed with the channel.
%MWr.m.c.2.6
APPLI_FLT
BOOL
R
Application detected error (adjustment or configuration error).
%MWr.m.c.2.7
Reading is performed by the READ_STS instruction (IODDT_VAR1).
Specific channel status: %MWr.m.c.3
The table below shows the various meanings of the bits of the PROTOCOL channel status word (%MWr.m.c.3):
Standard symbol
Type
Access
Meaning
Address
PROTOCOL
INT
R
Byte 0 = 16#06 for Modbus Master mode.
Byte 0 = 16#07 for Modbus Slave mode.
Byte 0 = 16#03 for Character mode.
%MWr.m.c.3
Reading is performed by the READ_STS (IODDT_VAR1) instruction.
Channel command: %MWr.m.c.24
The table below shows the various meanings of the bits of the CONTROL (%MWr.m.c.24) word:
Standard symbol
Type
Access
Meaning
Address
DTR_ON
BOOL
R/W
Set the Data Terminal Ready signal.
%MWr.m.c.24.8
DTR_OFF
BOOL
R/W
Reset the Data Terminal Ready signal.
%MWr.m.c.24.9
TO_MODBUS_MASTER
BOOL
R/W
Change from Character mode or Modbus Slave mode to Modbus Master mode.
%MWr.m.c.24.12
TO_MODBUS_SLAVE
BOOL
R/W
Change from Character mode or Modbus Master mode to Modbus Slave mode.
%MWr.m.c.24.13
TO_CHAR_MODE
BOOL
R/W
Change from Modbus to Character Mode.
%MWr.m.c.24.14
The command is carried out with the WRITE_CMD (IODDT_VAR1) instruction.
For further information about how to change protocols, you can refer to protocol changes.
External Configuration Objects of Type T_COM_MB_BMX_CONF_EXT: %MWr.m.c.24.7 and %MWr.m.c.25
The table below shows the meaning of the CONTROL (%MWr.m.c.24.7) bit and of the CONTROL_DATA (%MWr.m.c.25) word that are specifically intended for the BMX NOM 0200 module programming:
Standard symbol
Type
Access
Meaning
Address
SAVE_SLAVE_ADDR
BOOL
R/W
Save the control data into the FLASH memory
%MWr.m.c.24.7
SLAVE_ADDR
INT
R/W
Modbus slave address to store in the FLASH memory, from 0 to 248 (0 for Master).
NOTE: Be aware that this functionality is optional and there is no reason to use it intensively. As the technology involved is a FLASH, it may damage the chip.
%MWr.m.c.25