Instruction manual

3-14 / Service ControlWaveLP
This will prevent the boot project from running and places the unit into diagnostic
mode. To test COM1 using the WINDIAG program, it must not otherwise be in use
and CPU Switch SW4-8 must be set OFF. Connection to a PC requires the use of
an RS-232 “Null Modem” cable (see Figure 2-5).
COM2: From the factory, COM2 defaults to 9600 baud, 8-bits, no parity, 1 stop bit,
BSAP/ControlWave Designer protocol operation. To test COM2 using the WIN-
DIAG program, it must not otherwise be in use and CPU Switch SW4-8 must be
set OFF. It is recommended that an RS-232 “Null Modem” cable be connected
between COM2 and the PC (typically COM1) (see Figure 2-5).
COM3: When set for RS-232 or RS-485 operation, COM3 defaults to 9600 baud, 8-bits, no
parity, 1 stop bit, BSAP/ControlWave Designer protocol operation. To test COM3
using the WINDIAG program, it must not otherwise be in use and CPU Switch
SW4-8 must be set OFF.
If RS-485 communications is required an RS-485 cable can be assembled using the
connections provided in Table 2-5.
COM4: From the factory COM4 defaults to 9600 baud, 8-bits, no parity, 1 stop bit,
BSAP/ControlWave Designer protocol operation. To test COM4 using the WIN-
DIAG program, it must not otherwise be in use and CPU Switch SW4-8 must be
set OFF. In lieu of the use of COM2, an RS-232 “Null Modem” cable can be
connected between COM4 and the PC (typically COM1) (see Figure 2-5).
COM5 From the factory COM5 defaults to 9600 baud, 8-bits, no parity, 1 stop bit,
BSAP/ControlWave Designer protocol operation. To test COM5 using the WIN-
DIAG program, it must not otherwise be in use and CPU Switch SW4-8 must be
set OFF. An RS-232 “Null Modem” cable can be connected between COM5 and the
PC (typically COM1) (see Figure 2-5).
To use the WINDIAG program place any critical process (associated with the
ControlWaveLP unit in question) under manual control. WINDIAG cannot be run while
the ControlWaveLP application is running. Set the CPU Board Switche SW4-8 to the OFF
position. Perform steps 1 through 6 below.
1. Start the OpenBSI NetView Program. A menu similar to Figure 3-10 will appear.
2. To start the WINDIAG program, go to the Start Program’s menu, select OpenBSI Tools,
then select Utilities Programs and then select Diagnostics.
3. Once WINDIAG has been entered, the Main Diagnostics Menu of Figure 3-11 will
appear.
4. Select the module to be tested. Enter any prompted parameters (slot #, etc.). WINDIAG
will perform the diagnostics and display pass/fail results.
5. After all diagnostic testing has been performed, exit the WINDIAG program and then
exit the NetView Program if there aren’t any other ControlWaveLP units to be tested.
When you close the NetView program you will be prompted as to whether or not you
want to close the OpenBSI program; select Yes.