Device Does Not Boot Up
Reset the Digi Device/Terminal Server back to factory defaults and try again. All of the devices have a reset button. You will need to power cycle the Digi Device/Terminal Server while holding in the reset button. Continue holding in the reset button for about 60 seconds and then release. The device should now be set back to Factory Defaults. Since it generally takes a few minutes for the unit to reset, you may want to wait before attempting to access to the Digi Device/Terminal Server. If there is any LED activity, check to see if it is flashing a code sequence shown in the table below.
Power and LED activity:
Always check the power first. Use the following chart to interpret the LEDS:
Network Communication Issues
If you are unable to communicate with the Digi unit over the network, try the following:
1. Make sure you are not behind a firewall or running any third party firewall software on your PC.
2. Make sure Internet Connection Firewall is not enabled in Windows.
3. Make sure the web browser isn’t using proxy server and this has been disabled.
4. Ping the IP address:
Where ###.###.###.### represents the actual IP address assigned to the unit.
If you do not receive ping responses, please confirm the network settings on the unit match up with your network environment by logging in directly to one of the serial ports. This can be done by connecting a PC (with terminal emulation software such as Hyperterminal), or by attaching a dumb terminal. A crossover (null modem) cable will be necessary. Set the dip switches to EIA-232 communication for the port you will login to: 1-up; 2, 3, & 4-down. Configure your terminal or emulation software for the following communication settings:
• VT-100 emulation
• 9600 baud
• 8-bit characters
• 1 stop bit
• No parity
You may need to press [Enter] to see the login prompt. Login as root (default password: dbps) and issue the “set config” command to view current network settings. If you are applying a static IP address, make sure dhcp is set to off. Apply any other network settings needed in your environment such as, domain, gateway and name server information. A reboot may be required. After these settings are confirmed, try to ping from the Digi Device/Terminal Server root prompt (#>) to another network node and vice versa to see if the unit is now communicating on the network.
NOTE: Also verify the Ethernet cable is plugged in securely and is pinned appropriately.
The Link (LI) LED on the Digi Device/Terminal Server will indicate if the network is being detected.
5. If the unit responds to pings, next try to telnet to the unit:
You should see the login prompt from the unit. If not, power off the Digi unit and try the ping command again. This will rule out a possible duplicate IP address being assigned to the unit.
NOTE: Make sure in Windows Operating Systems that Internet Sharing Services is not turned on or you will be able to ping the unit, but not have telnet access to the Digi Device/Terminal Server.
Serial Port Communication Issues
Make sure that the PortServer/Digi One unit is configured correctly:
Review the port settings:
#> set port
Any port that is going to have a RealPort device attached, should have:
*dev - Needs to be set to rp or prn.
*auto – Needs to be set to off
NOTE: You can use the Web Interface to verify the device type as well.?
#> set flow
Any port that is going to have a RealPort device attached, should have all signals off except ixon and ixoff (which can be on or off) and altpin (which should be off for a 10 wire cable and on for anything else).
#> set auth
Will show settings like the following:
Ind IPaddr Mask RealPort Login Unrestricted
1 0.0.0.0 0.0.0.0 oooo-ooo -------- oooooooo
o-oooooo -------- oooooooo
RealPort should show "o" for all RealPort ports. The ports are indicated across in groups of eight -- In the example above, all ports are set correctly in the RealPort column except ports 5 and 10 (which are possibly being used for non-RealPort connections as indicated by the “-“ in position 5 and 10).
Check for stuck processes:
At the Digi Device/Terminal Server root command prompt type:
If a proccess (RealPort or otherwise) is running on the port, type:
?#> kill tty=[port_number]
If this does not work, unplug the serial device and reboot the Digi Device/Terminal Server.
Conducting a Loopback Test:
If the loopback test performed in the previous sections passed, but you are unable to communicate to your device, you will need to verify:
You are using the proper cabling:
PortServer TS, ConnectPort TS and ConnectPort LTS:
? 2. Altpin settings: When altpin is enabled, DCD becomes available on pin 1 of an 8-pin RJ-45 connector (set flow altpin=on range=(port_number).
3. Additionally, if you are unable to communicate with the individual ports on the Digi Device/Terminal Server, confirm the port dip switches are configured to match your peripheral devices communication protocol for RS-232 (1-up; 2, 3, & 4-down), RS-485 or RS-422.
Possible Buffer Overflow:
#> display port
If IFC or OFC are shown, refer to the following article:
RealPort Connectivity Issues
Make sure that the RealPort host can reach the Digi Device/Terminal Server:
Once who (see above) shows no processes on the port, from the host command line or telnet client, check connectivity to the 771 TCP port:
telnet [IP_of_digi_unit] 771
If the host cannot telnet to the 771 socket then RealPort won't connect to it. This would indicate that the IP address or the RealPort (771) socket is in use, being blocked or fire walled. If the connection succeeds, you can disconnect using <Ctrl> ] <Enter>, followed by typing quit at the telnet prompt.
Last updated: May 09, 2019