PLX3x Series ♦ Multi-Protocol Gateways
MBS Protocol
User Manual
ProSoft Technology, Inc.
Page 127 of 215
January 25, 2018
7.3
MBS Diagnostics
7.3.1 MBS PCB Diagnostics
The best way to troubleshoot the MBS driver is to use ProSoft Configuration
Builder to access the diagnostic capabilities of the gateway through the Ethernet
debug port. For instructions on how to access the diagnostics, see Diagnostics
and Troubleshooting (page 31).
The following table summarizes the status information available in PCB for the
MBS driver:
Connection Type
Submenu Item
Description
MBS Port [x]
Config
Configuration settings for MBS Port [x].
Comm Status
Status information for MBS Port [x] commands. Displays a
summary of all the errors resulting from MBS Port [x]
commands.
Slave Status
Current poll status of each slave device on MBS Port [x].
Modbus Cmds
Configuration for the MBS Port [x] Modbus command list.
Modbus Cmd
Errors (Decimal)
Current error codes for each command on the MBS Port [x]
command list in decimal number format. A zero means
there is currently no error for the command.
Modbus Cmd
Errors (Hex)
Current error codes for each command on the MBS Port [x]
command list in hexadecimal number format. A zero
means there is currently no error for the command.
7.3.2 MBS Status Data in Upper Memory
Each Modbus port has an associated status data area located in the gateway’s
upper memory. The Data Map functionality of the gateway can be used to map
this data into the normal user data range of the gateway’s database. See
Mapping Data in Module Memory (page 24).
General Modbus Error and Status Data
The following table lists the starting addresses in upper memory where the
gateway writes general error and status data for each Modbus master or slave
port. Note that all the status values are initialized to zero (0) at power-up, cold
boot and during warm boot.
Modbus Port
Starting Address
1
4400
2*
4800
3*
5200
4*
5600
*Status data for Ports 2 through 4 is only present in 4-port PLX3x gateways.
