- HELP
This product is part of the diagnostic package for the DMB32. It
provides the ability to test the Synchronous portion of the DMB32
device while other users are active on the system. This is a level 2R
diagnostic and can run only with VMS V4.4 or greater and the VAX
Diagnostic Supervisor.
- REQUIREMENTS
The following requirements must be met (unless marked as optional)
before this diagnostic is executed.
- HARDWARE
o VAX Host with a VAXBI interface with the minimum
configuration required to run VMS
o DMB32 Synchronous interfaces, 1 to 64(maximum) units
o Associated cables
Adapter Cables :
V.35 17-01112-01
RS423 17-01111-01
V.24 17-01110-01
X.21 17-01109-01 * See note below *
RS422 17-01108-01
Sync Modem Cables :
RS232 BC22-F
RS422/RS423 BC55-D
V35 BC17-E
o H3196 - balanced 50-way connector (optional)
o H3195 - unbalanced 50-way connector (optional)
o H3250 - V.35 single line loopback (optional)
o H3248 - V.24 single line loopback (optional)
o H3198 - RS422, RS423 single line loopback (optional)
o Modem with loopback (optional)
NOTE 1
The X.21 adapter cable 17-01109-01 is only supported if a special
adapter cable is connected between it and the distribution panel.
When this special adapter cable is attached, the X.21 cable will be
reported as an RS422 cable.
NOTE 2
Any adapter cables or loopback connectors other than those listed
above are not supported by this diagnostic and may cause errors to
be reported if used.
- SOFTWARE
o VAX/VMS V4.4 or later operating system
o VAX Diagnostic Supervisor (VDS) V10.0
o VAX/VMS DMB32 Synchronous Port Device Driver
o EVDAL.EXE - VAX Online diagnostic for DMB32 sync line
o EVDAL.HLP - VAX Online help for the EVDAL diagnostic
- ATTACH
The following information must be included in the Hardware Parameter
Table, Ptable:
o Device Type - DMB32.
o Device Link - VAXBI interface.
o Device Name - SIa where a is a character for the unit under
test.
o VAXBI Node number - VAXBI Node number of unit under test.
This information will have to be entered by the user, for each unit
under test. An example of this is using the attach command:
DS> ATTACH DMB32 HUB SIa 3
^ ^ ^ ^ ^
| | | | |
| | | | +--------- VAXBI Node number HEX (range 0 - F)
| | | +----------- Generic Name (Range A - Z)
| | +---------------- Linked to VAXBI if this is the main
| | system bus, else link to the NBIB
| +--------------------- Device to be attached
+---------------------------- ATTACH command
NOTE: In cases where the VAXBI is itself attached to another bus, the
VAXBI adapter must be attached first, for example on a VAX8800
the attach would be :-
DS> ATTACH NBIA HUB NBIAn n ! Where n is 0 or 1
DS> ATTACH NBIB NBIAn NBIBm m p ! Where m is 0 or 1 and p is 0 to F
DS> ATTACH DMB32 NBIBn SIa 3
In this example n, m and p are dependent on machine configuration.
For further information refer to the appropriate manual for the
specific machine.
- SECTIONS
EVDAL diagnostic program is divided into three sections which can be
selected via the /SECTION qualifier on the VDS START command.
The sections are as follows:
o DEFAULT - no loopback connector required
o EXTERNAL - external loopback connector required
o MODEM - modem with loopback capability required
- DEFAULT
This section contains tests 1, 2 and 3. The Sync port is set to
internal loopback and no operator setup is required for this section.
Example: DS> START or
DS> START/SECTION=DEFAULT
- EXTERNAL
Tests 1, 2, 3, and 4 are included in this section. The tests are run
in normal mode, therefore an external loopback must be connected. To
run this section you must fit to the distribution panel either of the
following:
o one of the two 50-way external loopback connectors H3196 or
H3195
o the appropriate loopback connector via the associated adapter
cable
This diagnostic will issue an informational message on the first pass
describing which loopback connector the board has identified.
The following loopback connectors are supported:
o H3196 - Balanced 50-way connector
o H3195 - Unbalanced 50-way connector
o H3250 - V.35 (Cable 17-01112-01)
o H3248 - V.24 (Cable 17-01110-01)
o H3198 - RS422(Cable 17-01108-01), RS423(Cable
17-01111-01)
NOTE
In order to get full coverage of the board, this
diagnostic must be run with BOTH of the 50-way
loopback connectors H3196 and H3195.
Example: DS> START/SECTION=EXTERNAL
- MODEM
Tests 1, 2 and 3 are included in this section, the Sync port is set to
normal operation. The Modem must be set into loopback mode manually
when running this section.
Example: DS> START/SECTION=MODEM
- DEVICE
The DMB32 is a synchronous/asynchronous VAXBI multiplexer that
provides an interface for eight asynchronous serial data
communications channels, one synchronous line and one line printer.
- QUICK
Not implemented
- EVENT
If you set Event Flag 21 and have selected External or Modem section,
the diagnostic will prompt you to fit one of the loopback connectors
onto the Sync line of the device currently under test. The diagnostic
will then wait for your confirmation that the connector is fitted
before continuing execution.
For example to set the event flag:
DS> SET EVENT 21
On execution of the diagnostic, it will then prompt:
Put Modem into local loopback or fit loopback connector on unit _SIA
Type <Y><CR> when ready
- SUMMARY_REPORT
The summary report code, displays the DECNET datalink layer counters
stored for each device tested. Please refer to the DIGITAL Network
Architecture, DDCMP Functional Specification for a description of the
counters and associated messages.
A summary report is automatically displayed after completion of a
start command. The summary report can be redisplayed by the command :
DS> SUMMARY
The display can be disabled by the command :
DS> SET FLAG IES
Some counters have associated messages if an error occurs. Examples
of both types follow :
Example 1
UNIT NAME: _SIA0
SUMMARY - DDCMP COUNTERS
Data Bytes Transmitted 7600
Data Bytes Received 7600
Data Blocks Trans 20
Data Blocks Recvd 20
Data Errors Inbound 0
Data Errors Outbound 0
Remote Buffer Errors 0
Local Buffer Errors 0
.
.
.
Example 2
UNIT NAME: _SIA0
SUMMARY - DDCMP COUNTERS
Data Bytes Transmitted 7600
Data Bytes Received 7600
Data Blocks Trans 20
Data Blocks Recvd 20
Data Errors Inbound 2 including :
NAKs sent, REP response
NAKs sent, data field block check error
Data Errors Outbound 2
NAKs received, header block check error
NAKs received, REP response
Remote Buffer Errors 0
Local Buffer Errors 0
.
.
.
- TESTS
This diagnostic contains the following tests.
- TEST_1
DDCMP protocol is used during this test. If the Default
section is selected then the data is looped back internally
otherwise the DMB32 is set to no loopback and so requires
the data to be looped back externally.
There are four transfer sizes, (16,64,512,1000 bytes)
and five data patterns, ( all 0's, all 1's, floating 1's,
floating 0's, and incrementing bytes from 0 to 255).
If the 50-way Balanced loopback connector H3196 is fitted and the
External section is being run, then the code in this test will be
run twice, once without V.35 set and once with V.35 set.
This test will be performed on all lines selected (for devices
with more than one Sync port).
NOTES:
SET EVENT FLAG 21 for delay between units to fit the loopback
connector if running External or Modem sections.
- STEPS
1. Establish the Condition handler.
2. Initialise test parameters.
3. Build the Configuration buffer for DDCMP and the
Loop type.
4. Initialise loop parameters.
5. Identify the line to be tested.
6. Shutdown the Controller.
7. Set up the DMB32 as a Controller.
8. Startup the Controller circuit.
9. Startup the Tributary circuit.
10. Enable Attention ASTs.
11. Sense Loopback connector if necessary.
12. Set V.35 or V.11 operation if external loop and H3196
connector.
13. Initialise loop parameters.
14. Identify the pattern to be transmitted.
15. Initialise loop parameters.
16. Identify the size to transmit.
17. Issue a Read QIO.
18. Issue a Write QIO.
19. Verify <data sent> = <data received>.
20. Increment pointers and loop to (16) if necessary.
21. Increment pointers and loop to (14) if necessary.
22. Increment pointers and loop to (12) if necessary.
23. Read the DECNET Datalink Layer counters and update the
stored values.
24. Shutdown the Controller and Tributary circuit.
25. Increment pointers and loop to (5) if necessary.
26. End.
- ERRORS
ERROR 01: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 02: ERROR OCCURRED ON DEVICE SHUTDOWN
ERROR 03: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 04: ERROR OCCURRED ON DEVICE START-UP
ERROR 05: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 06: ERROR OCCURRED ON TRIBUTARY START-UP
ERROR 07: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 08: ERROR OCCURRED ENABLING ATTENTION AST
ERROR 09: SYSTEM SERVICE ERROR ON SETCHAR QIO
ERROR 10: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 11: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 12: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 13: SYSTEM SERVICE ERROR ON READ QIO
ERROR 14: ERROR ON $SETIMR SYSTEM SERVICE
ERROR 15: SYSTEM SERVICE ERROR ON WRITE QIO
ERROR 16: TIME-OUT OCCURRED ON WRITE QIO
ERROR 17: ERROR OCCURRED DURING WRITE OPERATION
ERROR 18: ERROR OCCURRED DURING READ OPERATION
ERROR 19: DATA COMPARISON ERROR
ERROR 20: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 21: ERROR OCCURRED ON DEVICE SHUTDOWN
ERROR 100: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 101: ERROR OCCURRED ENABLING ATTENTION AST
ERROR 102: FATAL ATTENTION AST OCCURRED
ERROR 103: DEVICE CANNOT DETECT THE
PRESENCE OF A CABLE OR LOOPBACK CONNECTOR
ERROR 104: THE CABLE OR LOOPBACK CONNECTOR ON THIS DEVICE IS
NOT SUPPORTED BY THIS DIAGNOSTIC PLEASE CONSULT
THE HELP FILE FOR A LIST OF SUPPORTED CABLES AND
LOOPBACKS
ERROR 105: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 106: ERROR OCCURRED DURING READING DECNET DATALINK
LAYER COUNTERS.
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. If the error message printed is a SYSTEM SERVICE error then
examine the printed status message.
CHECK (according to status message) :
o If you have the required privileges (see DMB32 users guide).
o If the synchronous device is already allocated.
o If the synchronous driver is correctly installed (see the
DMB32 Synchronous Drivers Manual).
o If device is offline. Note if the device was booted without
the cable connected to the synchronous port the device will
be offline.
4. If errors 2, 4, 6, 8, 21, 101 or 106 then check the IO
status byte for more information (refer to the DMB32
Synchronous Drivers Manual - the IOSB). If not helpful
then proceed to the level 3 diagnostic (EVDAK).
5. If error 14 then check all quotas.
6. If errors 16, 17, 18, or 19 then
If external mode check the connected modem, cable
and/or loopback, if still not OK then run this
diagnostic in internal mode.
If in internal mode then goto the level 3 diagnostic
(EVDAK).
7. If error 102 then check the associated printed status
message. Likely problem is the connected modem went from
online to an offline state. Try proceeding to the level 3
diagnostic(EVDAK).
8. If errors 103 or 104 then check correct cable is actually
connected. If correct then goto the level 3 diagnostic
(EVDAK).
- TEST_2
BISYNC protocol is used during this test. If the Default
section is selected then the data is looped back internally
otherwise the DMB32 is set to no loopback and so requires
the data to be looped back externally.
There are four transfer sizes, (1000,512,64,16 bytes)
and five data patterns, ( all 0's, all 1's, floating 1's,
floating 0's, and incrementing bytes from 0 to 255).
If the 50-way Balanced loopback connector H3196 is fitted and the
External section is being run, then the code in this test will be
run twice, once without V.35 set and once with V.35 set.
This test will be performed on all lines selected (for devices
with more than one Sync port).
NOTES:
SET EVENT FLAG 21 for delay between units to fit the loopback
connector if running External or Modem sections.
- STEPS
1. Establish the Condition handler.
2. Initialise test parameters.
3. Build the Configuration buffer for BISYNC and the Loop
type.
4. Initialise loop parameters.
5. Identify the line to be tested.
6. Shutdown the Controller.
7. Set up the DMB32 as a Controller.
8. Startup the Controller circuit.
9. Sense the loopback connector if necessary
10. Set V.35 or V.11 operation if external loop and H3196
connector
11. Initialise loop parameters.
12. Identify the pattern to be transmitted.
13. Initialise loop parameters.
14. Identify the size to transmit.
15. Frame the data buffer.
16. Issue a Read QIO.
17. Issue a Write QIO.
18. Verify <data sent> = <data received>.
19. Increment pointers and loop to (14) if necessary.
20. Increment pointers and loop to (12) if necessary.
21. Increment pointers and loop to (10) if necessary.
22. Shutdown the Controller and Tributary circuit.
23. Increment pointers and loop to (5) if necessary.
24. End
- ERRORS
ERROR 01: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 02: ERROR OCCURRED ON DEVICE SHUTDOWN
ERROR 03: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 04: ERROR OCCURRED ON DEVICE START-UP
ERROR 05: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 06: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 07: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 08: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 09: SYSTEM SERVICE ERROR ON READ QIO
ERROR 10: ERROR ON $SETIMR SYSTEM SERVICE
ERROR 11: SYSTEM SERVICE ERROR ON WRITE QIO
ERROR 12: TIME-OUT OCCURRED ON WRITE QIO
ERROR 13: ERROR OCCURRED DURING WRITE OPERATION
ERROR 14: ERROR OCCURRED DURING READ OPERATION
ERROR 15: DATA COMPARISON ERROR
ERROR 16: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 17: ERROR OCCURRED ON DEVICE SHUTDOWN
ERROR 103: DEVICE CANNOT DETECT THE
PRESENCE OF A CABLE OR LOOPBACK CONNECTOR
ERROR 104: THE CABLE OR LOOPBACK CONNECTOR ON THIS DEVICE IS
NOT SUPPORTED BY THIS DIAGNOSTIC PLEASE CONSULT
THE HELP FILE FOR A LIST OF SUPPORTED CABLES AND
LOOPBACKS
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. If the error message printed is a SYSTEM SERVICE error then
examine the printed status message.
CHECK (according to status message) :
o If you have the required privileges (see DMB32 users guide).
o If the synchronous device is already allocated.
o If the synchronous driver is correctly installed (see the
DMB32 Synchronous Drivers Manual).
o If device is offline. Note if the device was booted without
the cable connected to the synchronous port the device will
be offline.
4. If errors 2, 4, or 17 then check the IO status byte for more
information (refer to the DMB32 Synchronous Drivers Manual -
the IOSB). If not helpful then proceed to the level 3
diagnostic (EVDAK).
5. If error 10 then check all quotas.
6. If errors 12, 13, 14, or 15 then
If external mode check the connected modem, cable
and/or loopback, if still not OK then run this
diagnostic in internal mode.
If in internal mode then goto the level 3 diagnostic
(EVDAK).
7. If errors 103 or 104 then check correct cable is actually
connected. If correct then proceed to the level 3
diagnostic (EVDAK).
- TEST_3
HDLC protocol is used during this test. If the Default
section is selected then the data is looped back internally
otherwise the DMB32 is set to no loopback and so requires
the data to be looped back externally.
There are four transfer sizes, (16,64,512,1000 bytes)
and five data patterns, ( all 0's, all 1's, floating 1's,
floating 0's, and incrementing bytes from 0 to 255). These
patterns will be repeated for NRZI and non-NRZI coding.
If the 50-way Balanced loopback connector H3196 is fitted and the
External section is being run, then the code in this test will be
run twice, once without V.35 set and once with V.35 set.
This test will be performed on all lines selected (for devices
with more than one Sync port).
NOTES:
SET EVENT FLAG 21 for delay between units to fit the loopback
connector if running External or Modem sections.
- STEPS
1. Establish the Condition handler.
2. Initialise test parameters.
3. Build the Configuration buffer for HDLC and the Loop
type.
4. Select NRZI or non-NRZI coding.
5. Initialise loop parameters.
6. Identify the line to be tested.
7. Shutdown the Controller
8. Set up the DMB32 as a Controller.
9. Startup the Controller circuit.
10. Sense the loopback connector type if necessary
11. Set V.35 or V.11 operation if external loop and H3196
connector
12. Initialise loop parameters.
13. Identify the pattern to be transmitted.
14. Initialise loop parameters.
15. Identify the size to transmit.
16. Issue a Read QIO.
17. Issue a Write QIO.
18. Verify <data sent> = <data received>.
19. Increment pointers and loop to (15) if necessary.
20. Increment pointers and loop to (13) if necessary.
21. Increment pointers and loop to (11) if necessary.
22. Read the DECNET Datalink Layer counters and update the
stored values.
23. Shutdown the Controller and Tributary circuit.
24. Increment pointers and loop to (6) if necessary.
25. Increment pointers and loop to (4) if necessary.
26. End.
- ERRORS
ERROR 01: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 02: ERROR OCCURRED ON DEVICE SHUTDOWN
ERROR 03: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 04: ERROR OCCURRED ON DEVICE START-UP
ERROR 05: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 06: SYSTEM SERVICE ERROR ON SET_CHAR QIO
ERROR 07: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 08: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 09: SYSTEM SERVICE ERROR ON READ QIO
ERROR 10: ERROR ON $SETIMR SYSTEM SERVICE
ERROR 11: SYSTEM SERVICE ERROR ON WRITE QIO
ERROR 12: TIME-OUT OCCURRED ON WRITE QIO
ERROR 13: ERROR OCCURRED DURING WRITE OPERATION
ERROR 14: ERROR ON $SETIMR SYSTEM SERVICE
ERROR 15: TIME-OUT OCCURRED ON READ QIO
ERROR 16: ERROR OCCURRED DURING READ OPERATION
ERROR 17: RECEIVED DATA ERROR
ERROR 18: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 19: ERROR OCCURRED ON DEVICE SHUTDOWN
ERROR 103: DEVICE CANNOT DETECT THE
PRESENCE OF A CABLE OR LOOPBACK CONNECTOR
ERROR 104: THE CABLE OR LOOPBACK CONNECTOR ON THIS DEVICE IS
NOT SUPPORTED BY THIS DIAGNOSTIC PLEASE CONSULT
THE HELP FILE FOR A LIST OF SUPPORTED CABLES AND
LOOPBACKS
ERROR 105: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 106: ERROR OCCURRED DURING READING DECNET DATALINK
LAYER COUNTERS.
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. If the error message printed is a SYSTEM SERVICE error then
examine the printed status message.
CHECK (according to status message) :
o If you have the required privileges (see DMB32 users guide).
o If the synchronous device is already allocated.
o If the synchronous driver is correctly installed (see the
DMB32 Synchronous Drivers Manual).
o If device is offline. Note if the device was booted without
the cable connected to the synchronous port the device will
be offline.
4. If errors 2, 4, 19 or 106 then check the IO status byte
for more information (refer to the DMB32 Synchronous
Drivers Manual - the IOSB). If not helpful then proceed
to the level 3 diagnostic (EVDAK).
5. If errors 10 or 14 then check all quotas.
6. If errors 12, 13, 15, 16 or 17 then
If external mode check the connected modem, cable
and/or loopback, if still not OK then run this
diagnostic in internal mode.
If in internal mode then goto the level 3 diagnostic
(EVDAK).
7. If errors 103 or 104 then check correct cable is actually
connected. If correct then proceed to the level 3
diagnostic (EVDAK).
- TEST_4
This test will check that the Modem signals can be looped back
correctly. One of the external loopback connectors must be fitted
for this test to run correctly.
The modem signals which are tested are dependent upon which cable or
loopback connector the board detects as being fitted.
This test will be performed on all lines selected (for devices
with more than one Sync port).
NOTES:
SET EVENT FLAG 21 for delay between units to fit the loopback
connector.
- STEPS
1. Establish the Condition handler.
2. Initialise test parameters.
3. Build the Configuration buffer for HDLC and external
loop.
4. Initialise loop parameters.
5. Identify the line to be tested.
6. Shutdown the Controller.
7. Set up the DMB32 as a Controller.
8. Startup the Controller circuit.
9. Sense loopback connector if necessary.
10. Initialise loop parameters.
11. Set Transmit modem signals.
12. Read Received modem signals.
13. Clear unwanted modem signals.
14. Verify correct modem signals received.
15. Loop to (11) if necessary
16. Shutdown the Controller and Tributary circuit.
17. Increment pointers and loop to (6) if necessary.
18. End.
- ERRORS
ERROR 01: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 02: ERROR OCCURRED ON DEVICE SHUTDOWN
ERROR 03: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 04: ERROR OCCURRED ON DEVICE START-UP
ERROR 05: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 06: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 07: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 08: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 09: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 10: SYSTEM SERVICE ERROR ON SENSE_MODE QIO
ERROR 11: MODEM SIGNAL ERROR
ERROR 12: SYSTEM SERVICE ERROR ON SET_MODE QIO
ERROR 13: ERROR OCCURRED ON DEVICE SHUTDOWN
ERROR 103: DEVICE CANNOT DETECT THE
PRESENCE OF A CABLE OR LOOPBACK CONNECTOR
ERROR 104: THE CABLE OR LOOPBACK CONNECTOR ON THIS DEVICE IS
NOT SUPPORTED BY THIS DIAGNOSTIC PLEASE CONSULT
THE HELP FILE FOR A LIST OF SUPPORTED CABLES AND
LOOPBACKS
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. If the error message printed is a SYSTEM SERVICE error then
examine the printed status message.
CHECK (according to status message) :
o If you have the required privileges (see DMB32 users guide).
o If the synchronous device is already allocated.
o If the synchronous driver is correctly installed (see the
DMB32 Synchronous Drivers Manual).
o If device is offline. Note if the device was booted without
the cable connected to the synchronous port the device will
be offline.
4. If errors 2, 4, or 13 then check the IO status byte for
more information (refer to the DMB32 Synchronous Drivers
Manual - the IOSB). If not helpful then proceed to the
level 3 diagnostic (EVDAK).
6. If error 11 then
If external mode check the connected cable and/or
loopback,
if still not OK then run this
diagnostic in internal mode.
If in internal mode then proceed to the level 3
diagnostic (EVDAK).
7. If errors 103 or 104 then check correct cable is actually
connected. If correct then proceed to the level 3
diagnostic (EVDAK).