When the cable is unplugged for the network interface, why does the receive carrier loss (RCL) bit in the status register or the pin of the LIU or SCT occasionally report an incorrect status?
A5. It is unlikely that the device actually reports the RCL status incorrectly. The most common cause of this problem is that a noise/signal source is coupling into the receive-side interface (the RTIP and RRING pins). The following are suggestions to verify that noise/signal coupling is the problem and what can be done to solve the problem. • Set the equalizer gain limit (EGL) of the device to the lower of the two settings (i.e., if the two choices are -43dB and -15dB, choose the -15dB setting). This will allow the LIU to remove low-level signals that may be causing the device to report the RCL status incorrectly. If this solves the problem, then the EGL bit can be left at this setting for future operation. However, if long-haul operation is required by the system, another suggestion should be considered. • Set the transmitter power-down (TPD) of the device to turn off the transmitter. This will prevent the transmitted signal from coupling into the receiver. If this solves the problem
Related Questions
- When the cable is unplugged for the network interface, why does the receive carrier loss (RCL) bit in the status register or the pin of the LIU or SCT occasionally report an incorrect status?
- Why does the ethernet hostid disappear when the network cable is unplugged?
- Why doesn cURL return an error when the network cable is unplugged?
