13.2.3 Debugging a Modbus Slave application
If configuration for Modbus Slave is set up, handler for protocol will start automatically.
If
configuration is missing or contains errors, protocol will not start. It is done intentionally to decrease
unnecessary memory usage.
Table 19: Modbus Slave command line debugging options
Option
Description
h [ –help ]
Display help information
V [ –version ]
Show version
d<debug level>
Set debugging level
c [ –config ]
Config path
r [ –raw ]
Show raw telegram data
f [ –frame ]
Show frame data
s [ –serial ]
Show serial port data
–tcp
Show tcp packets
–ascii
Show ASCII messages
–rtu
Show RTU messages
e [ –redis ]
Show redis debug information
R [ –readyfile ]
Ready notification file
If Modbus Slave does not work properly (e.g. no communication between devices, data is corrupted,
etc.), a user can launch a debug session from command line interface and find out why link is not
functioning properly. To launch a debugging session, a user should stop modbusslave process
and run modbusslave command with respective flags as in Table 19.
102
Содержание WCC Lite
Страница 1: ...ELSETA WCC Lite User manual Elseta 2020 04 07 Doc version 1 4 0 HW version 1 2 FW version 1 4 0...
Страница 62: ...8 5 9 Reboot This reboots the operating system of the device 62...
Страница 78: ...General DHCP settings Resolve and hosts files settings TFTP server settings 78...
Страница 155: ...Figure 37 Screen showing existing user groups Figure 38 Screen for user group editing 154...
