Output of modbus master logs (fl0, modbus_m), Output of modbus master logs (fl0, modbus_m) -25 – Yokogawa Standalone MW100 User Manual
Page 75
2-25
IM MW100-17E
Response
1
2
3
App
App
Index
Output of Modbus Master Logs (FL0, MODBUS_M)
• Output using the FL command.
• Modbus master information logs are output.
Syntax
EACRLF
yy/mo/dd_hh:mm:ss_xxx_mmm...mCRLF
.........................................
ENCRLF
yy
Year (00 to 99)
mo
Month (01 to 12)
dd
Day (01 to 31)
hh
Hour (00 to 23)
mm
Minute (00 to 59)
ss
Seconds (00 to 59)
xxx
Command number (001 to 100, ---)
mmm...m Command status
_
Blank
Example
EA
99/05/11 12:20:30 --- START
99/05/11 12:20:31 001 CONNECTING
99/05/11 12:20:32 001 VALID
EN
List of Character Codes Showing Modbus Master Command Statuses
The table below also includes character codes that are only used by either the
Modbus master or Modbus client.
Command
Meaning
Status
SKIP
Command not set
INVALID
Cannot execute command
NO_DATA
Data could not yet be acquired
VALID
Data successfully acquired
STALE
Data became old (acquisition error)
WAITING
Server/slave communication recovery waiting
CLOSED
Connection with server/slave closed
RESOLVING
Establishing connection with server/slave (address being resolved)
CONNECTING Establishing connection with server/slave (requesting connection)
UNREACH
Failed to connect to server/slave (not found)
TIMEDOUT
Failed to connect to server/slave (time out occurred)
BROKEN
Response message damaged (CRC error)
ERROR
Response message was an error message
BAD_SLAVE
Slave address of response message invalid (does not match command)
BAD_FC
Response message function code invalid (does not match command)
BAD_ADDR
Response message address invalid (does not match command)
BAD_NUM
Response message register invalid (does not match command)
BAD_CNT
Number of response message registers invalid (does not match command)
BAD_DATA
Conversion of response message data failed
2.2 ASCII Output