Troubleshooting
RS-232 Mode Troubleshooting Tips
Table 3-11 RS-232 Mode Tips
|
|
|
CannotSymptomestablish | PossibleUsing straightCausesthrough | CorrectiveUse a Null ModemActionscable |
communication |
| |
| Null Modem cable |
|
| Loose cables | Ensure that the cables are securely connected to |
|
| the computer and the power supply. |
| Baud rate mismatch | Select a baud rate that matches the instruments |
|
| settings. See “Baud Rate Selection” on page 2– |
|
| 18 for details changing this setting. |
| Trying to communicate via | Most computers have two COM ports, COM1 |
| the wrong COM port | and COM2, so ensure you have selected the |
|
| correct COM port. |
| The interface card is | Reconfigure the interface card for |
| configured for Ethernet | communications. See “Configuring for Ethernet |
| communications | or |
|
|
|
| ||
Table |
| |
|
|
|
|
|
|
InstrumentSymptomnot | PossibleThe unit isCausesin local mode | CorrectivePut the unit intoActionsremote mode by sending the |
responding to new |
| command REN ON. |
user settings |
|
|
|
|
|
The output is | The output is off | Send the command OUT ON |
displaying zero |
|
|
volts and zero amps, | The output has tripped due | the condition that has caused the fault, |
but the setpoints are | to an OVP, or foldback | and send the command RST |
protection event |
| |
|
|
|