- HELP
EVDAF
THE PURPOSE OF EVDAF IS TO PROVIDE FUNCTIONAL ONLINE
TESTING OF THE DMZ32 LOGIC THROUGH USE OF THE VAX/VMS DRIVER.
THIS PROGRAM IS A LEVEL 2R DIAGNOSTIC AND CAN RUN ONLY WITH
THE VAX/VMS OPERATING SYSTEM AND THE DIAGNOSTIC SUPERVISOR.
VARIOUS WAYS OF LOOPING BACK DATA ARE MADE AVAILABLE TO THE
USER, THEY INCLUDE:
o INTERNAL LOOPBACK
o EXTERNAL LOOPBACK WITH AN H3248 LOOPBACK CONNECTOR
o EXTERNAL LOOPBACK WITH ANY OTHER TYPE PER-LINE LOOPBACK
METHOD
THE INTERNAL LOOPBACK METHOD IS THE DEFAULT. EXTERNAL METHOD
ENABLES THE USER TO ACTIVELY LOOP BACK DATA WITH A CABLE
LOOPBACK CONNECTOR OR BY ENABLING A MODEM WITH THE LOOP BACK
FEATURE.
- PRIVILEGES
$ ! THE FIELD SERVICE ACCOUNT UNDER VMS 4.0 DOESN'T COME UP
$ ! WITH REQUIRED PRIVILEGES. SO YOU MUST SET PRIVILEGES.
$ ! PRIVILEGES NEEDED TO RUN DIAGNOSTICS.
$ !
$ SET PROC/PRIV=(CMKRNL,DIAGNOSE,EXQUOTA,LOG_IO,OPER,PHY_IO,CMEXEC)
- DEVICE
The DMZ32 is a 24 line asynchronous multiplexer consisting of the
hex unibus module (M8398), a high speed(1.544mbps)T1 link, and a
remote distribution panel(H3014). The distribution panel is
available with or with modem control.
- REQUIREMENTS
HARDWARE
o DW780, DW750, DW730, or DWBUA fully tested with no errors
occurring
o VAX Processor with at least the minimum VMS configuration
o M8398 unibus hex modules
o H3014 distribution panel
o H3248 Single line Turnaround Connector
o Modem (optional)
NOTE: THIS DIAGNOSTIC SUPPORTS FULL DUPLEX LINKS ONLY.
SOFTWARE
This program is a level 2R diagnostic and can run only
with the VAX/VMS Operating System version 4.0, latest DMZ32
driver and the VAX Diagnostic Supervisor version 7.0 or later.
The VAX Diagnostic Supervisor version 7.0 or later
must be resident in memory. This diagnostic may be loaded and
started after the supervisior is running.
- ATTACHING
ATTACH & RUN SEQUENCE
Because the DMZ32 architecture is very similar to the DMF32, many
programming similarities exist. In fact, the DMZ32 appears very
much like the async portions of three DMF32's. CSR's (control/
status registers) and vectors will appear as if there were three
DMF32's on the UBA (UNIBUS adapter).
The program treats each octet selected as though it were a
separate device. For example:
o If you select TXA only, the first 8 lines (Octet) of the DMZ32
can be tested & only those lines.
o If you select TXA & TXB, the program can test TXA (Lines 0-7),
then it starts over and can then test TXB(Lines 0-7). It
treats the two octets as though there were two devices and
therfore runs twice.
o If TXA,TXB, & TXC are selected, the program will test TXA first,
then TXB, and finally TXC.
NOTE:
This diagnostic shares a common P-table with the Level 3
diagnostic.
The input for CSR, VECTOR and BR prompts are irrelevant in a
level 2r diagnostic. This merely satisfies the prompt request
and has no effect on running the program. All I/O is done via
VMS system services.
When running the Level 2R diagnostic, the user should enter "0"
for the Level 3 Only - Test Lines. This merely satisfies the
prompt request and has no effect on running the program. See
comments for "Test Lines" below.
$ RUN ENSAA ; START SUPERVISOR (11/780/82/85=ESSAA,
; 11/750 = ECSAA, 11/725/30=ENSAA,
; 8200/8300 = EBSAA)
DIAGNOSTIC SUPERVISOR. ZZ-ENSAA-7.0-YYY 9-OCT-1984 09:40:14.80
DS> ATT DW780 SBI DW0 3 4 ; ATTACH THE UBA ON THE SBI, VAX/780
OR
DS> ATT DW750 HUB DW0 ; FOR VAX/750 TESTING
OR
DS> ATT DW730 HUB DW0 ; FOR VAX/730 TESTING
OR
DS> ATT DWBUA HUB DW0 node 4 ; FOR THE VAX 8200/8300 TESTING (where node
; is the DWBUA VAXBI node ID
DS> LOAD EVDAF ; LOAD THE DIAGNOSTIC
DS> ATT DMZ32 ; ATTACH THE 1ST OCTET
DEVICE LINK? DW0 ; THE OPTION IS LINKED TO THE UBA
DEVICE NAME? TXA ; THE OPTION IS NAMED TXA
CSR? 760440 ; THE CSR ADRS IS 760440
; (RANGE=760000-777776)
VECTOR? 400 ; VECTOR ADRS (RANGE=300-776)
BR? 5 ; BR INTERRUPT LEVEL IS 5 (RANGE=5-6)
TEST LINES (OCTET 0) ? 377 ; LINES 0-7 IN OCTET 0 WILL BE TESTED
; (OCTAL BIT MAP OF DESIRED LINES TO
; TEST, BIT0 = LINE 0,
; BIT1 = LINE 1, ETC. -
; RANGE = 000-377)
; EXAMPLE: TEST LINES? 123
; TEST LINES SIX,FOUR ONE AND ZERO
LEVEL 3 ONLY - TEST LINES (OCTET 1) ? 0 ; Applies only to Level 3
LEVEL 3 ONLY - TEST LINES (OCTET 2) ? 0 ; Applies only to Level 3
BAUD RATE? 9600 ; BAUD RATES THAT CAN BE SELECT
; ARE: 50, 75, 110, 135, 150, 300, -
; 600, 1200, 1800, 2000, 2400, -
; 4800, 9600, 19200
LOOPBACK TYPE? 4 ; LOOPBACK TYPES ARE:
; 4 = LOCAL LINE (EIA)(INTERNAL LOOPBACK)
; 5 = H3248 TURNAROUND
; 7 = LOCAL MODEM IN ANALOG LOOP
; 8 = LOCAL MODEM (PROGRAMMABLE LOOPBACK)
MODEM CONTROL? YES ; DOES THE DEVICE HAVE MODEM CONTROL, YES
; OR NO.
DS> ATT DMZ32 ; ATTACH THE 2ND OCTET
DEVICE LINK? DW0 ; THE OPTION IS LINKED TO THE UBA
DEVICE NAME? TXB ; THE OPTION IS NAMED TXB
CSR? 760440 ; CSR ADDRESS
; (RANGE=760000-777776)
VECTOR? 400 ; VECTOR ADRS (RANGE=300-776)
BR? 5 ; BR INTERRUPT LEVEL IS 5 (RANGE=5-6)
TEST LINES (OCTET 0)? 377
LEVEL 3 ONLY - TEST LINES (OCTET 1) ? 0 ; Applies only to Level 3
LEVEL 3 ONLY - TEST LINES (OCTET 2) ? 0 ; Applies only to Level 3
BAUD RATE? 9600
LOOPBACK TYPE? 4
MODEM CONTROL? YES
DS> ATT DMZ32 ; ATTACH THE 3RD OCTET
DEVICE LINK? DW0 ; THE OPTION IS LINKED TO THE UBA
DEVICE NAME? TXC ; THE OPTION IS NAMED TXC
CSR? 760440 ; THE CSR ADRS IS 760440
; (RANGE=760000-777776)
VECTOR? 400 ; VECTOR ADRS IS 420 (RANGE=300-776)
BR? 5 ; BR INTERRUPT LEVEL IS 5 (RANGE=5-6)
TEST LINES (OCTET 0)? 377
LEVEL 3 ONLY - TEST LINES (OCTET 1) ? 0 ; Applies only to Level 3
LEVEL 3 ONLY - TEST LINES (OCTET 2) ? 0 ; Applies only to Level 3
BAUD RATE? 9600
LOOPBACK TYPE? 4
MODEM CONTROL? YES
DS> SEL TXA ; SELECTS LINES 0-7 (OCTET0)
DS> SEL TXB ; SELECTS LINES 8-15 (OCTET1)
DS> SEL TXC ; SELECTS LINES 16-23 (OCTET2)
DS> START
The program should now be running.
- EVENT_FLAGS
TWO EVENT FLAGS ARE USED BY THIS PROGRAM.
SET EVENT FLAG 20
TO SUSPEND PROGRAM EXECUTION BETWEEN TESTING OF EACH LINE ON A UNIT
SO THAT THE OPERATOR CAN INSERT LOOPBACK ON A LINE BEING TESTED, THE
OPERATOR SHOULD SET EVENT FLAG 20. THE PROGRAM WILL INFORM THE USER
AS TO WHICH LINE IS CURRENTLY CONSIDERED FOR TESTING SO THAT THE
CONNECTOR CAN BE PLACED ON THAT LINE.
SET EVENT FLAG 21
PROGRAM EXECUTION CAN ALSO BE SUSPENDED BETWEEN TESTING OF UNITS, SO
LOOPBACK CAN BE PROVIDED ON PER-UNIT. TO DO THIS SET EVENT FLAG 21.
TO SET EVENT FLAGS, TYPE: SET EVENT 20 or SET EVENT 21
- SECTIONS
There is only 1 section to this diagnostic:
o Default Section - contains 4 tests.
- TEST1
Test 1 - Single Line Internal EIA Data Loopback <Default>
Internal loopback mode is employed and a message is sent, one line
at a time, on all lines selected. The transmitted message is:
<177><177>$A THE QUICK BROWN FOX JUMPED OVER THE LAZY DOG. <15><12>
<177<177<177<177><0>
No operator setup is required for this test.
NOTE: The EIA internal loopback is the only internal loopback currently
supported by the DMZ32 VMS driver.
TEST STEPS:
1) Test if this line has been selected to test
2) Enable internal loopback
3) Purge type-ahead buffer
4) Set baud rate
5) Write message string to device under test
6) Read message back and verify data
7) Disable internal loopback
8) Point to new line and loop to 2
9) End
ERRORS:
ERROR 01: QIO request failed to be queued
ERROR 02: QIO failed while set internal loopback
ERROR 03: QIO failed while purging type ahead buffer
ERROR 04: QIO failed while setting baud rate
ERROR 05: QIO failed while writing message
ERROR 06: QIO failed reading back message string
ERROR 07: Message string doesn't match transmitted message string
ERROR 08: QIO failed while disabling internal loopback
- TEST2
Test 2 - Single Line Internal Data Loopback Test (DMA)
<Default>
The following test will transfer a 70 character message. This
message is used to force the DMZ32 driver to perform a DMA transfer.
The VMS terminal driver defaults to a 80 character typeahead buffer with
a minimum DMA character transfer of 64 characters. This means that
the number of characters transfered must be between 64 - 80 characters;
the character size chosen was 70.
TTY_DMASIZE (64 Char) < MESSAGE SENT (70 Char) < TTY_TYPAHDSZ (80 Char)
Internal loopback mode is employed and a message is sent, one line
at a time, on all lines selected. The transmitted message is:
<177><177>$A THE QUICK BROWN FOX JUMPED OVER THE LAZY DOG. <15><12>
<177<177<177<177><0>
No operator setup is required for this test.
NOTE: The EIA internal loopback is the only internal loopback currently
supported by the DMZ32 VMS driver.
TEST STEPS:
1) Test if this line has been selected to test
2) Set internal loopback
3) Purge type ahead buffer
4) Set baud rate
5) Write message string to device under test
6) Read message back and verify data
7) Disable internal loopback
8) Point to a new line and loop to 2
9) End
ERRORS:
ERROR 01: QIO request failed to be queued
ERROR 02: QIO failed while set internal loopback
ERROR 03: QIO failed while purging type ahead buffer
ERROR 04: QIO failed while setting baud rate
ERROR 05: QIO failed while writing message
ERROR 06: QIO failed reading back message string
ERROR 07: Message string doesn't match transmitted message string
ERROR 08: QIO failed while disabling internal loopback
- TEST3
Test 3 - Modem Signals Loopback <H3248>
This test will verify the DMZ modem signals and will be executed if
the loopback type 5 was selected in the supervisor attach sequence,
and if modem control is available. Only those modem signals supported
by the VMS ttdriver can be tested.
SET EVENT FLAG 20 If you want a delay between lines to allow manual
intervention to move the loopback connector.
SET EVENT FLAG 21 For delay between units.
TEST STEPS:
1) If looptype <> 5 or there is no modem control then abort.
2) Set up message address block pointer and transmit and receive
modem signal pointer for device under test
3) Read event flags, see if operator wants a delay between lines
to allow manual intervention to move the loopback connector.
4) Clear Modem signals
5) Verify Modem signals are cleared
6) Set transmit modem signal
7) Read receive modem signals
8) Verify that correct modem signals are set
9) Loop to 3 until all modem signals that can be set manually
are tested
12) End
ERRORS:
ERROR 01: QIO failed while clearing modem signals
ERROR 02: QIO failed while reading modem signals
ERROR 03: Modem signals didn't clear
ERROR 04: QIO failed while setting transmit modem signals
ERROR 05: QIO failed while reading modem signals
ERROR 06: Receive modem signals not correctly
- TEST4
Test 4 - External Data Loopback Test
This test will verify the data and modem signal on an external data
path. The path can be the single line turnaround connector (H3248), the
local modem in analog loopback, or local modem placed in analog loopback
via software.
In this test, data transmitted on a user selected line is compared
to the data received on that line. Any differences are reported. The
user is required to set up the hardware. If a H3248 loopback connector
is used, it must be put in place. If LOCAL_MODEM loopback is employed,
the modem must be manually placed in analog loopback.
A message is sent, one line at a time, on all lines selected. The
message is the following:
<177><177>$A THE QUICK BROWN FOX JUMPED OVER THE LAZY DOG. <15><12>
<177<177<177<177><0>
SET EVENT FLAG 20 If you want a delay between lines to allow manual
intervention to move the loopback connector.
SET EVENT FLAG 21: For delay between units.
TEST STEPS:
1) If loopback = 4 then abort
2) Test if this line has been selected to test
3) Set baud rate
4) If loopback type = 8 then set USERTX bit
5) Wait for signals to settle
6) Purge type ahead buffer
7) Write message string to device under test
8) Read message back and verify data
9) Point to a new line and loop to 2
10) End
ERRORS:
ERROR 01: QIO failed while setting baud rate
ERROR 02: QIO failed while set external loop back
ERROR 03: QIO failed while purging type ahead buffer
ERROR 04: QIO failed while writing message
ERROR 05: QIO failed reading back message string
ERROR 06: Message string doesn't match transmitted message string
- ERROR
- DATA
THE FOLLOWING IS AN EXAMPLE OF A DATA COMPARE ERROR TYPEOUT:
***** EVDAF DMZ32 FUNCTIONAL DIAG - 1.0 *********
PASS 1 TEST 3 SUBTEST 0 ERROR 5 09-OCT-1983 11:20:30.84
HARD ERROR WHILE TESTING TTA: DATA COMPARE ERROR
FOR LINE: 000
GOOD DATA = 101 , BAD DAT = 102
GOOD MESSAGE: ..$A THE QUICK BROWN FOX JUMPED OVER THE LAZY DOG..
BAD MESSAGE: ..$B THE QUICK BROWN FOX JUMPED OVER THE LAZY DOG..
NOTE: THE "." (DOTS) REPRESENT NON-PRINTABLE CHARACTERS.
- TIME-OUT
THE FOLLOWING IS AN EXAMPLE OF AN IO TIME OUT ERROR:
******** EVDAF DMZ32 FUNCTIONAL DIAG - 1.0 **********
PASS 1 TEST 3 SUBTEST 0 ERROR 4 09-OCT-1983 11:12:30.97
SYSTEM FATAL WHILE TESTING TTA: QIOW READ TIMED OUT,NO MESSAGE
RECEIVED FOR LINE: 000
THIS ERROR INDICATES THAT WE WERE ABLE TO SUCCESSFULLY TRANSMIT A
MESSAGE, HOWEVER, NO MESSAGE WAS RETURN TO THE DIAGNOSTIC. THIS
USUALLY INDICATES THAT A LINE WAS NOT SUCCESSFULLY LOOPED BACK.
- SETUP
THE FOLLOWING IS AN EXAMPLE OF AN IO SETUP ERROR:
******** EVDAF DMZ32 FUNCTIONAL DIAG - 1.0 **********
PASS 0 INITIALIZATION SECTION ERROR 2 09-OCT-1983 11:12:30.97
SYSTEM FATAL WHILE TESTING TTA: * LINE ALLOCATED TO ANOTHER PROCESS *
FOR LINE: 000
THIS ERROR INDICATES THAT ANOTHER USER HAS CONTROL OVER THIS LINE
AND THE DIAGNOSTIC IS UNABLE TO ALLOCATE IT. YOU MUST VERIFY THAT
YOU SPECIFIED THE CORRECT LINE FOR THE TEST, AND THEN TAKE CONTROL
OF THE LINES.
OCCASIONALLY, DURING THE PROCESS OF PUTTING ON LOOPBACK CONNECTORS,
YOU MAY ACCIDENTLY SEND INFORMATION TO VMS THROUGH THE LINE. VMS
COULD INTERPRET IT AS A USER ATTEMPTING TO LOG IN. IN THIS CASE,
VMS WILL HOLD THIS LINE AND YOU WILL BE UNABLE TO TEST IT.
THIS CONDITION COULD ALSO OCCUR IF YOU ^Y (CONTROL-Y) OUT OF THIS
DIAGNOSTIC WHILE IT IS RUNNING. TO GET OUT OF THIS SITUATION,
DISCONNECT THE LOOPBACK FOR 5 SECONDS, THEN REPLACE IT.