BlackDoor Duo
Engage Black
5.5 Can't communicate to BlackDoor Duo - Console Port
Cause: Baud Rate, Stop Bits, etc. set wrong on communication application
Solution: Ensure the communication software is congured for a xed, asynchronous data rate of
115200 bps, 1 stop bit, no parity, 8 bit xed and that the Flow control is set to none.
5.6 BlackDoor Duo O Net IP Interconnect Verication
In most applications BlackDoor Duo will be located on dierent IP networks and the interconnection
is through a routed connection. At each end of the routed connection the Tube's default router IP
address needs to be pointed to the rst router in the path to that remote IP subnet. Through an
SSH connection to an BlackDoor Duo it is possible to verify the ability of the unit to ping its local
default router and to ping the remote BlackDoor Duo. Note: the console port does not support the
Ping Command as it does not have an IP Address.
5.7 TCP/IP Connection
An IP Ping program is the best tool for troubleshooting TCP/IP connectivity. As a sanity check,
rst ensure you can ping the local router. If unsuccessful, go back to "Can't Communicate using
SSH with BlackDoor Duo"
5.8 Can't IP Ping Remote BlackDoor Duo
Cause: Ping workstation does not have Default Gateway (or Router) set. In the workstation's IP
conguration, alongside workstation's own IP address and subnet mask, you must provide the IP
address of the device (a router) to which all packets destined o the local net should be sent.
Cause: default router on the net, serving as Default Gateway for all net workstations, does not know
about the remote IP net where the remote BlackDoor Duo is located.
Solution: Under these circumstances, the two BlackDoor Duo units are on dierent networks or
subnets, the default gateway address must be congured.
5 TROUBLESHOOTING
Page 21