IP
•
Tube E
2
Duo
Engage Communication Inc.
6.5
Can’t communicate to IP
•
Tube E
2
Duo - Console Port
Cause: Baud Rate, Stop Bits, etc. set wrong on communication application
Solution: Ensure the communication software is configured for a fixed, asynchronous data rate of
115200 bps, 1 stop bit, no parity, 8 bit fixed and that the Flow control is set to none.
6.6
IP
•
Tube E
2
Duo Off Net IP Interconnect Verification
In most applications IP
•
Tube E
2
Duo will be located on different 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 first router in the path to that remote IP subnet. Through an
SSH connection to an IP
•
Tube E
2
Duo it is possible to verify the ability of the unit to ping its local
default router and to ping the remote IP
•
Tube E
2
Duo. Note: the console port does not support
the Ping Command as it does not have an IP Address.
6.7
TCP/IP Connection
An IP Ping program is the best tool for troubleshooting TCP/IP connectivity. As a sanity check,
first ensure you can ping the local router. If unsuccessful, go back to ”Can’t Communicate using
SSH with IP
•
Tube E
2
Duo”
6.8
Can’t IP Ping Remote IP
•
Tube E
2
Duo
Cause: Ping workstation does not have Default Gateway (or Router) set. In the workstation’s IP
configuration, 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 off 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 IP
•
Tube E
2
Duo is located.
Solution: Under these circumstances, the two IP
•
Tube E
2
Duo units are on different networks or
subnets, the
default gateway
address must be configured.
6
TROUBLESHOOTING
Page 19
