You are viewing an article about an obsolete product. Information on this page is provided as-is and not supported.

EtherLite LED indicator information

When troubleshooting a Digi EtherLite, one of the key indicators of the EtherLite's status are the LEDs on the unit's front panel.

The LINK LED is an indicator of whether or not the EtherLite has a physical network connection. If LINK LED is lit, the unit believes it has a good connection to the network. If LINK LED is not lit, the first thing to check is the cabling between the EtherLite unit and the LAN hub/switch. Check to make sure both ends of the network cable are securely connected and that a standard (not back to back) network cable is in use. If the cable is securely connected on both ends and the LINK LED is still not lit, replace the network cable with a known-working one from a PC currently on the network, just to verify it isn't the cable.  Alternately, an Ethernet crossover-cable could be used to connect the Etherlite directly to the Ethernet port of a Unix or Windows Server, as long as the server itself has a static IP.

The ON LED serves several purposes. If the ON LED does not light at all, the power supply is likely defective. If you have a spare, known-working EtherLite power supply, try using it instead.  If the ON LED is lit solid immediately after power is applied, this might also be an indicator that the power supply is defective or that the EtherLite's internal code has been corrupted. Either of these conditions will require that the EtherLite be sent in for repair.

If the ON LED has a fast, steady flicker, this indicates that the EtherLite is waiting to be served an IP address. If an IP address is stored on the unit, the LED will flicker briefly and then turn solid. The same behavior will be observed if the EtherLite is being served an IP address from a bootp or DHCP server, though it may take a bit longer to turn solid than a unit which has a stored IP address.

Occasionally, the ON LED might not behave in any of the ways described above, but instead blinks a "code" or pattern which keeps repeating. This is typically an indicator that the EtherLite's internal OS is corrupted, and the unit will need to be sent in for repair.

The only user-serviceable codes are:

64 - should be resolved when a user updates the firmware and driver for the EtherLite
67 - indicates that the EtherLite is being served an IP address that is already in use on the network
68 - the EtherLite has no IP address

For reference purposes, here is a list of all EtherLite blink codes:

11 - Self test failure (not generated form)
12 - Bad blink code passed to itself
13 - Fatal test RAS opcode
14 - Bad flow control mode in process_special
15 - Impossible else clause in process_special
16 - Dma on Null buf in dma_out
17 - Dma length zero in dma_out
21 - trap routine called
22 - Memory sizing error in init_bufs
23 - Not enough bufs in init_bufs
24 - Out of buffers in get_buf
25 - Impossible return point in xfer_to_scsi
26 - Impossible return point in xfer_from_scsi
27 - Buffer timer interrupt SLHdbt_idle handler called unexpectedly
30 - Rom or eprom failure
31 - Baud bank error in hwXXXX.c
32 - Bad register in call to wr_scc_reg in hwXXXX.c
33 - Bad register in call to rd_scc_reg in hwXXXX.c
34 - Xmit incomplete in slh.c 35 - Stuck SCC in slh.c
36 - Unexpected interrupt
37 - Abort got duplicated
41 - Sync free_buf had buffer type or already free
42 - SLMsm bad state transition
43 - Bad sync transmit status
44 - Frame too short
45 - Prep_buf: bad type
46 - Get_mesg: cnt short
47 - get_data: bp NULL or cnt short
51 - Switch default in do_sync
52 - Unit number out of range
53 - Unit not initd
54 - Bad cmd in do_scsi
55 - Bad cmd in proc_sync_buf
56 - Bad cmd in proc_bounced_buf
57 - SLMput_data: cnt too big
61 - SLMtrap
62 - SLMWrapUP: recv_frm NULL
63 - SLCtrap
64 - TXQ Overflow
65 - QUARTs failed init
67 - Duplicate IP Address
68 - Ethernet address not configured

Last updated: Jun 05, 2019

Recently Viewed

No recently viewed articles

Did you find this article helpful?