BB2-7030 User Guide – Rev. 1.0
Page 64
18.
Trouble
Shooting
Connection problems between the BB2-7030 and other devices when using any of the Client
features of the BB2-7030 will be indicated by reliability codes for each local object mapped to a
remote device. Check these codes against the legend at the bottom of the object data pages.
Modbus devices will return exception codes if the request was received by the Modbus device
but rejected because a register number was out of range, etc. Check the message counts. If total
messages count is increasing right along with exception count, one or more client maps are
configured incorrectly. If the no-response count is incrementing, the remote device is simply not
responding. The status code on the TCP devices page may provide further information.
Routing problems are the most difficult to trouble shoot, and there is no easy recommendation
for fixing routing problems. Using Wireshark to see what is on the network is highly
recommended.
MS/TP does not tolerate any errors in configuration. If adding the BB2-7030 to an MS/TP
network appears to bring down the MS/TP network, first of all wait a short time. When a new
device is inserted in the token ring, it will take a little bit of time to get re-synchronized. But if
the network does not come back up, recheck configuration settings. Incorrect baud rate will kill
the network completely. Incorrect max master setting, or duplicate mac address or device
instance, will cause intermittent operation at best. Also, be sure the EIA-485 wiring is “clean”,
and that the BB2-7030 is not on a long “stub” off the main network. Recheck wiring polarity as
well if adding the BB2-7030 took the network down.