- HELP
EVDCA VAX SYNCHRONOUS LINK DIAGNOSTIC
This diagnostic will not run if the local node is connected to
DECNET. The logical link with DECNET must be terminated, type
'HELP EVDCA DECNET' for more information.
- DECNET
This diagnostic will not run while there exist a logical
link to DECNET. The operational state of the link
must be terminated in the following manner.
$MCR NCP
NCP> SET CIRCUIT DMC-n STATE OFF
NCP> SET LINE DMC-n STATE OFF
NCP> CLEAR CIRCUIT DMC-n
All circuit parameters (Y, N): Y
NCP> CLEAR LINE DMC-n
All line parameters (Y, N): Y
NCP> ^Z
- DEVICE
The VAX Synchronous Link Diagnostic (EVDCA) will provide an on-line
mechanism for determining the quality of a synchronous data commu-
nications link. The term 'link' meaning that set of hardware/software
functionality required to establish synchronous data communication.
This link will be self contained in one computer system for the first
three test sections (maintenance wrap, cable wrap, and modem wrap).
This program is for DMC11, DMR11 and DUP11.
- ATTACH
DS> ATTACH DW780 SBI DW0 3 4 ; Attaches UBA to 11/780.
or
DS> ATTACH DW750 CMI DW0 ; Attaches UBA to 11/750.
or
DS> ATTACH DW730 CMI DW0 ; Attaches UBA to 11/730.
DS> ATTACH DUP11 DW0 XWA0 760050 300 5 ; Attaches device to UBA if
; connected to DUP11.
DS> ATTACH DMC11 DW0 XMA0 760100 310 5 ; Attaches device to UBA if
; connected to DMC11.
DS> ATTACH DMC11 DW0 XMB0 760110 320 5 ; Attaches device to UBA if
; connected to DMC11.
DS> ATTACH DMR11 DW0 XMC0 760120 330 5 ; Attaches device to UBA if
; connected to DMR11.
DS> SELECT XWA0,XMA0,XMB0,XMC0
- SECTIONS
EVDCA consists of the following tests:
1. Test 1: Maintenance Wrap Test
2. Test 2: Cable Wrap Test (DMC,DMR ONLY)
3. Test 3: Modem Wrap Test (Must have a modem for DUP11)
4. Test 4: System Wrap - Sender (DMC11,DMR11 only)
5. Test 5: System Wrap - Receiver (DMC11,DMR11 only)
- MAINTENANCE WRAP
This section is the default section. It will utilize the internal
loopback capability of the unit under test. The data received will be
compared with the data pattern that was transmitted. The internal
clock of the communications device will be used.
- CABLE WRAP
This section will transfer data in a configuration which utilizes a
test connector (H325 or equivalent). All received data will be
compared against the transmitted data pattern. The clock will be
supplied by the communications device.
There are several possible operator induced errors which may occur
while running the cable wrap section. For the DMC11-AR,
be sure that there is a turn around connector (H325 or equivalent)
connected to the cable(BC05). For the DMC11-AL ensure that the
coaxial test connector (DEC P/N 12-12528) is in stalled. For the
DMC11-AR, be sure that switch #8 on switch pack #1 of the M8201 line
unit is on to enable the DMC internal clock. For the DMC11 these
problems will indicate a QIO timeout.
- MODEM WRAP
In this section data will be transferred via a modem. The test will
run full duplex since the modem can not buffer data. The clock
will be provided by the modem. Data transfer will be the same as
in maintenance and cable wrap, except that the clocking will be done
by the modem. The data checking will also be the same as in the
previous two sections.
However there are certain key points to remember when attempting to
affect modem loopback. Analog loopback creates a direct path from the
transmit line to the receive line on the analog or channel side of the
modem. Some modems such as the Bell 208/212 series provide an analog
loop switch which connects the transmit and receive analog circuits,
for other modems this connection may have to be created manually by
correct jumpering at the analog terminal on the modem. It should be
noted that on those modems which provide an analog test switch there
is the additional concern over whether this switch causes Data Set
Ready(DSR) to be deascerted by the modem (this is a feature in most
Bell modems). The DMC11 hardware requires DSR before transmission can
take place and so if DSR is not present a QIO timeout will result.
Digital loopback is implemented at the remote modem and is either
switch selectable (Bell 208/212 series), or must be implemented via a
jumpered connector on those modems which do not support this feature.
On certain modems Digital loopback also requires changing the clock
source to external. See Field Service Support for details on the
jumpering required to support either analog or digital loopback on
those modems where this feature is not directly supported.
Please note that for DUP11, an turnaround connector is not enough.
There has to be a modem since that is the only thing that is going
to provide a clock on the line. The driver supports internal loopback,
but none of the external loopback modes.
- SYSTEM_WRAP_SENDER
(DMC11,DMR11 only).
This test will be the master for the system to system loop test. This
test runs in conjunction with Section DTR which is the slave or
receive section of the system to system loop. Each system must run a
copy of EVDCA with the master system started in section DTS and
the slave system started in section DTR. The master system will init-
iate the transfer after which each system will sequence through each
size for each pattern. There will be four transfer sizes (16, 64,512,
1000 bytes) and five bit patterns ( all 0's, all 1's, floating 1's,
floating 0's, and the CCITT 511 bit pattern). Data transfer will be
repeated until all transfer sizes and all bit patterns have been
exhausted. The data will be compared to check that the data
transmitted was the same as the data that was received. Any errors
(system errors, device errors, data compare errors, and hard errors)
will be reported and non-fatal errors will be updated for the summary.
Fatal errors (system and device) will cause the program to abort.
- SYSTEM_WRAP_RECEIVE
(DMC11, DMR11 only)
This test will be the slave for the system to system loop test. This
test runs in conjunction with Section DTS which is the master or
transmit section of the system to system loop. Each system must run a
copy of EVDCA with the master system started in section DTS and the
slave system started in section DTR. The master system will initiate
the transfer after which each system will sequence through each size
for each pattern. There will be four transfer sizes (16, 64, 512,
1000 bytes) and five bit patterns ( all 0's, all 1's, floating 1's,
floating 0's, and the CCITT 511 bit pattern). Data transfer will be
repeated until all transfer sizes and all bit patterns have been
exhausted. The data will be compared to check that the data
transmitted was the same as the data that was received. Any errors
(system errors, device errors, data compare errors, and hard errors)
will be reported and non-fatal errors will be updated for the summary.
Fatal errors (system and device) will cause the program to abort.
- EVENT-FLAGS
NONE
- QUICK
- SUMMARY
This section prints out the total number of hard errors that occurred
during a transmit and the hard errors that occurred during a receive.
It also prints out the number of data compare errors (the number of
bytes that were not received as they were sent). The last item to be
printed in the summary section is the total number of bytes
transferred.
If the unit under test is a DMC11 or DMR11, the DDCMP error counters
are also reported.
These error counters are:
The number of NAK's received -- no buffer available
The number of NAK's received -- bad header BCC
The number of NAK's received -- bad data BCC
The number of NAK's sent -- no buffer available
The number of NAK's sent -- bad header BCC
The number of NAK's sent -- bad data BCC
The number of REPs sent
The number of REPs received
- REQUIREMENTS
HARDWARE REQUIREMENTS
1 VAX CPU
256 kb memory
1 Unibus adaptor (or equivalent)
1 DMC11 or
1 DMR11 or
1 DUP11
1 H325 Turnaround connector (or equivalent)
1 12-12528 Turnaround connector (or equivalent)
SOFTWARE REQUIREMENTS
The VAX Diagnostic Supervisor (E*SAA - Version 5.0 or later) must be
loaded. The standard VMS drivers for the communications device(s) to be
tested must be present(XMDRIVER.EXE for the DMC11,DMR11 and XWDRIVER.EXE
for the DUP11).
- PREREQUISITES
This diagnostic is a link test and as such does not support detailed
testing of the communications option at the hardware level. To verify
correct hardware operation of the Synchronous communications options the
appropriate Level 3 repair tests should be run. These Level 3 tests are
as follows:
EVDXA - COMM IOP Diagnostic (DMC11)
EVDBA - Line Unit Diagnostic (M8201,M8202)
EVDBB - DMC11 Stand Alone Exerciser
- HISTORY
June 15 1979 - First submission - Version 1.0
August 15 1979 - Second submission - Version 1.1
Added system wrap tests 4 and 5
October 25 1982 - Third submission - Version 2.0
Allowed the use of the mnemnonic "DMR".
August 1984
major rev change to indicate compile and link under V.4 VAX/VMS
added logical DIAGLIB: to diag.l32 declaration
modified transmit routines to allow ^c intervention in case of
timeout without having to wait 60 seconds for ^c ack. Change
consisted of:
- issuing QIO instead of QIOW
- executing $DS_BREAK while waiting for xmit and rcv event
flags to set
- cancelling i/o and timer in cleanup section
- issuing a shutdown qio in cleanup section
removed section definitions with no tests in them
modified DTR test to transmit received data with no data check
added code in DTR and DTS tests to shutdown controller after
patterns have been transmitted
modified the ast parameter print routine to handle new info