MBTCP Protocol PLX32-EIP-MBTCP-UA ♦ Multi-Protocol Gateway
User Manual
Page 100 of 156 ProSoft Technology, Inc.
March 8, 2018
6.3 Network Diagnostics
6.3.1 MBTCP PCB Diagnostics
The best way to troubleshoot the MBTCP 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 30).
The following table summarizes the status information available in PCB for the
MBTCP driver:
Configuration settings for Server Connections.
Status of the Server Connections. Displays a summary of the
requests, responses, and errors.
Configuration settings for Client [x] Connections.
Status information for Client [x] commands. Displays a
summary of all the errors resulting from Client [x] commands.
Configuration for the Client [x] Modbus command list.
Modbus Cmd
Errors (Decimal)
Current error codes for each command on the Client [x]
command list in decimal number format. A zero means there is
currently no error for the command.
Current error codes for each command on the Client [x]
command list in hexadecimal number format. A zero means
there is currently no error for the command.
6.3.2 MBTCP Status Data in Upper Memory
The MBTCP driver has an associated status data area located in the PLX32-EIP-
MBTCP-UA’s upper memory. The Data Map functionality of the PLX32-EIP-
MBTCP-UA can be used to map this data into the normal user data range of the
PLX32-EIP-MBTCP-UA’s database.
Note that all the status values are initialized to zero (0) at power-up, cold boot
and during warm boot.
MBTCP Server Status Data
The following table lists the addresses in upper memory where the PLX32-EIP-
MBTCP-UA stores status data for MBTCP servers: