- HELP
EVDOC LEVEL III DIAGNOSTIC
TESTS THE ASYNCHRONOUS FUNCTIONALITY OF THE CPI32-A
!!! WARNING !!!
The H3026 wrap cable should always be installed and the T1 link
disconnected to run this diagnostic.
!!! NOTE !!!
If the level II and level III diagnostics run without error and
users still cannot get onto the CPI check the help information on
the T1 link and PBX parameters. Type HELP EVDOC PBX
- DEVICE
The CPI32-A is a tri-port, twenty-four channel, asynchronous
multiplexer. The CPI32-A simulates three DMF32s. This diagnostic,
EVDOC, is designed to functionally verify all three ports. This
is a VAX Level III diagnostic which runs under the Diagnostic
Supervisor.
- ATTACH
The following is an example of how to attach the device to
be tested, and to load and run EVDOC (answers to hardware questions
are typed in octal) :
NOTE: The unibus address is a function of the switch pack on the
CPI32 board. The vector is in floating space and is not set
until the vector is written into the first csr.
$ RUN ESSAA ; FOR (11/780)
or
$ RUN ECSAA ; FOR (11/750)
or
$ RUN ENCAA ; FOR (11/730) START SUPERVISOR
DIAGNOSTIC SUPERVISOR. ZZ-ENSAA-6.8-YYY 8-FEB-1982 09:40:14.80
DS> ATT DW780 SBI DW0 3 4 ; FOR VAX/780 ATTACH THE UBA ON THE SBI
or
DS> ATT DW750 HUB DW0 ; FOR VAX/750 TESTING
or
DS> ATT DW730 HUB DW0 ; FOR VAX/730 TESTING
DS> LOAD EVDOC.EXE ;LOAD THE CPI32A DIAGNOSTIC
DS> ATT CPI32A ;ATTACH THE CPI32A
DEVICE LINK? DW0 ;THE OPTION IS LINKED TO THE UBA
DEVICE NAME? TXA ;THE OPTION IS NAMED UNIT #1
; (RANGE=A-F)
CSR? 760340 ;THE CSR ADRS IS 760340
; (RANGE=760000-777776)
VECTOR? 300 ;VECTOR ADRS IS 300 (RANGE=300-776)
BR? 5 ;BR INTERRUPT LEVEL IS 5 (RANGE=4-7)
ACTIVE LINES? 77777777 ;ALL LINES 0-7 WILL BE TESTED
;(OCTAL BIT MAP OF DESIRED LINES TO
;TEST, BIT0 = LINE 0,
; BIT1 = LINE 1, ETC. -
; RANGE = 0-77777777)
BAUD RATE? 9600 ; BAUD RATE THAT CAN BE SELECTED ARE:
; ARE, 50, 75, 110, 135, 150, 300, -
; 600, 1200, 1800, 2000, 2400, 3600, -
; 4800, 7200, 9600, 19200
WRAP TYPE? H3026 ; WRAP TYPE IS
; H3026 = SINGLE LINE WRAP AT
; DISTRIBUTION PANEL
UNIBUS INIT JUMPER? YES ; JUMPER ON CPI32 BOARD WHICH INHIBITS
; UNIBUS INITS
DS> SELECT TXA ; SELECT DEVICE TO BE RUN.
DS> START
THE DIAGNOSTIC SHOULD NOW BE RUNNING
!!! NOTE !!!
If the level II and level III diagnostics run without error and
users still cannot get onto the CPI check the help information on
the T1 link and PBX parameters. Type HELP EVDOC PBX
- SECTIONS
There is one section, DEFAULT. The default section includes all tests.
- DEFAULT
The default section will includes all tests.
- WRAP_TYPE
Test 31 requires an H3026 single line external wrap connector.
If the diagnostic is run without the H3026 it will error on Test 31.
- REQUIREMENTS
The base SYSTEM and UBA must be functional.
- RUNTIME
EVDOC runtime with trace set, is approximately 3 minutes.
With the quick flag set, runtime is approximately 2 minutes.
For more information on the QUICK FLAG, type HELP EVDOC QUICK_FLAG
- QUICK_FLAG
Testing is restricted to one port during a quick verify pass.
Additionally, tests 28 and 29 are run against only one line.
EVDOC runtime; QUICK FLAG CLEAR is approximately 3 minutes.
QUICK FLAG SET is approximately 2 minutes.
Test which are not run with quick flag set are;
TEST 31: RX _& TX Modem Signal
TEST 32: Parity LED Test
- PBX
The following information is not needed to run the diagnostics
however it is intended to aid in finding a missmatch between the
CPI32-A and the PBX after both diagnostics have run without error.
Parameters vary with PBX vendor however some general information is
usefull. If a connection cannot be made from a terminal connected to
the PBX vendors data access module (DAM) thru the PBX to the VMS system
verify that parameters on the VMS system are correct. Look at the
help section on parameters. Then check with PBX personnel to insure
that the PBX parameters are set correctly.
HELP EVDOC PBX ALARM ;T1 trunk is declared out of service?
HELP EVDOC PBX PARAMETERS ;Are parameters set correctly?
- ALARM
The quality of the link between the CPI and the PBX is monitored by the
PBX. If frame (the 193rd bit of the T1 frame follows a pattern) loss is
detected by the PBX it records it as a framming error (RED ALARM).
After some number of frame losses the PBX may declare the T1 link out
of service. The number of frame losses before out of service is a
setable parameter at the PBX. INSURE THAT THIS PARAMETER IS SET HIGH.
A UNIBUS init or power failure for example cause a frame loss. The
following activities at the CPI will cause a frame loss to be seen
at the PBX:
o The booting of a 730 system causes 5 bus inits to the CPI.
o The switching of the UETP switch on the distributation panel.
One each time it is turned on and the UETP is started.
o Starting the level II diagnostic. Every time the cleanup code
is done followed by the init code.
o Most test in the level III diagnostic will cause atleast 1
framming error. This is why the level III is run with the
loopback connector in and the T1 link disconnected.
- PARAMETERS
Inorder for communication to occur between the host VMS system and a
terminal thru the CPI parameters must be set in several places. Verify
that parameters have been set in the following places.
o Parameters in the terminal match parameters in the Data
Access Module.
o The Data Access Module is understood to be a data connection
at the PBX.
o The T1 trunk is understood to be a data trunk at the PBX.
o The phone # associated at the PBX with the T1 link agrees
with the one being used.
o The set term commands have been executed on the VMS system.
o The set term commands should look like;
SET TERM TXxx:/MODEM/HANG/NOBROAD/NOAUTOBAUD/SPEED=xxxx/PERM
o The level II diagnostic ran correctly insures the device is
sysgen connected to the driver correctly.