- HELP
The purpose of this program is to provide functional online
testing of the DHU11 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: internal loopback (default), external loopback with a
H325 connector and loopback from programmable modems. The DHU11 has
internal loopback on all lines.
- REQUIREMENTS
The following requirements must be met before the Diagnostic is
executed.
- HARDWARE
VAX processor(11/780,11/750,11/730,v8200,v8600) with minimum VMS
configuration.
1 to 8 M3105 DHU11 asynchronous interfaces
Associated cables
Connectors (H325 loopback connector(s) (optional))
Modem (optional)
Note:
If testing with modems in local modem loopback, do
not put the modem into loopback before the diagnostic
tells you to.
- SOFTWARE
VAX Diagnostic Supervisor rev 8.2 or later, 11/780=ESSAA, 11/750=ECSAA,
11/730=ENSAA, VAX8200=EBSAA or VAX8600=EDSAA must be resident in
memory. The Supervisor must first be loaded, and successive diagnostics
can then be loaded and run without re-loading the Supervisor.
VAX/VMS version V4.2 plus TXDRIVER.
- PREREQUISITES
- Hardcore fully tested
- Functional DW780, DW750, DW730, or BUA
- ATTACH_DHU11
The following is an example of how to attach the device to
be tested, and to load and run EVDAH:
$ ALL TXA0 ; Allocate all lines to be tested
$ ALL TXA1 ;
$ | |
$ RUN ESSAA ; For (11/780), Supervisor.
or
$ RUN ECSAA ; For (11/750)
or
$ RUN ENSAA ; For (11/730)
or
$ RUN EBSAA ; For VAX 8200
or
$ RUN EDSAA ; For VAX 8600
DIAGNOSTIC SUPERVISOR. ZZ-ECSAA-Y8.2 4-SEPT-1985 12:00:00.00
DS> ATT DW780 SBI DW0 3 4 ; For 11/780 Attach the UBA on the SBI
or
DS> ATT DW750 HUB DW0 ; For 11/750 testing
or
DS> ATT DW730 HUB DW0 ; For 11/730 testing
or
DS> ATT DWBUA HUB DW0 n 4 ; For v8200. n = node ID of BUA.
or
DS> ATT SBIA HUB SI0 ; For v8600 attach 1st SBI
DS> ATT DW780 SI0 DW0 3 4 ; Attach 1st SBI-UNIBUS adapter
DS> LOAD EVDAH ; Load the DHU11 diagnostic
DS> ATT DHU11 ; Attach the DHU11
DEVICE LINK? DW0 ; The option is linked to the UBA
DEVICE NAME? TXA ; The option named unit:
; (range=A-F)
CSR? 760000 ; The CSR address:
; (range=760000-777776)
VECTOR? 300 ; Vector address: (range=300-770)
BR? 5 ; BR Interrupt Level: (range=4-7)
DS> SEL TXA ; Select Unit Under Test
DS> START ; Start diagnostic execution
The program should now be running.
- OPTIONS
- LINES_TO_TEST
The following line will be displayed:
Lines to test [(ALL),REV,EVE,ODD,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15]
Various responses can be given:
ALL - Test all lines 0 - 15 in ascending order, default on <cr>.
REV - Test all lines 15 - 0 in descending order.
EVE - Test lines 0,2,4,6,8,10,12 and 14.
ODD - Test lines 1.3,5,7,9,11,13 and 15.
n - Any line number.
n,m - Any combination of line numbers, i.e 0,15,3,7,1.
They will be tested in the sequence entered.
Any invalid entry will display an error message:
?? Invalid response
Followed by a reprompt of the input request.
- BAUD_RATE
The following line will be displayed:
Baud Rate [(9600),50,75,110,134,150,300,600,1200,1800,2000,2400,4800,
7200,19200,38400]
Various responses can be given:
n - Value, or <cr> default speed of 9600.
Any invalid entry will display an error message:
?? Invalid response
Followed by a reprompt of the input request.
- LOOP_TYPE
The following line will be displayed:
Loop Type [(INTERNAL), MODEM, H325]
Various responses can be given:
INTERNAL - Internal loopback will be used in the test, default on <cr>.
MODEM - A Modem preset to Internal Loopback.
H325 - External loopback connect is to be used.
Any invalid entry will display an error message:
?? Invalid response
Followed by a reprompt of the input request.
- EVENT_FLAGS
Two event flags are used by this program to enable the operator to
inform the program of its loopback capabilities.
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.
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.
DS>SET EVENT 20 or SET EVENT 21
- TEST_DESC
- TEST_1
Test 1 - Per Line Internal Data Loopback Test
This test will be aborted if the device is not a DHU11.
Internal loopback mode is selected on lines requested to be tested and
a message transmitted. No operator setup is required for this test.
- ASSUMPTIONS
All hardware upto the device is working.
- TEST_STEPS
1. Verify this is a valid device for this test.
2. Check the Loopback mode selected.
3. Initialize any parameters needed.
4. Identify the line selected to be tested.
5. Enable internal loopback.
6. Purge type ahead buffer.
7. Set baud rate.
8. Write message string to device.
9. Read message back.
10. Verify <data sent> = <data received>.
11. Disable internal loopback.
12. Increment pointers and loop to (5) if necessary.
13. End.
- ERRORS
ERROR 01: NOT A DHU11
ERROR 02: INVALID LOOPBACK SELECTED
ERROR 03: SET MODE ERROR ENABLING LOCAL LOOPBACK
ERROR 04: SYSTEM ERROR TRYING TO PURGE TYPE-AHEAD BUFFER
ERROR 05: SET MODE ERROR, SETTING BAUD RATE
ERROR 06: SYSTEM ERROR ON WRITE
ERROR 07: SYSTEM ERROR ON READ
ERROR 08: DATA COMPARE ERROR
ERROR 09: SET MODE ERROR, DISABLING LOCAL LOOPBACK
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. Using the listing, together with R0 and IOSB information,
fault isolation can be achieved.
4. If isolation is not achieved proceed to level 2 diagnostic.
- TEST_2
Test 2 - DMA, Per Line Internal Data Loopback Test
This test will be aborted if the device is not a DHU11.
This test is to force the DHU11 driver to do a DMA transfer.
The DHU11 FIFO is 64 characters long, to force a DMA transmission
a character transfer greater than 64 characters will be performed.
Internal loopback mode is selected on lines requested to be tested and
a message transmitted. No operator setup is required for this test.
- ASSUMPTIONS
All hardware upto the device is working.
- TEST STEPS
1. Verify this is a valid device for this test.
2. Check the Loopback mode selected.
3. Initialize any parameters needed.
4. Identify the line selected to be tested.
5. Enable internal loopback.
6. Purge type ahead buffer.
7. Set baud rate.
8. Write message string to device.
9. Read message back.
10. Verify <data sent> = <data received>.
11. Disable internal loopback.
12. Increment pointers and loop to (5) if necessary.
13. End.
- ERRORS
ERROR 01: NOT A DHU11
ERROR 02: INVALID LOOPBACK SELECTED
ERROR 03: SET MODE ERROR ENABLING LOCAL LOOPBACK
ERROR 04: SYSTEM ERROR TRYING TO PURGE TYPE-AHEAD BUFFER
ERROR 05: SET MODE ERROR, SETTING BAUD RATE
ERROR 06: SYSTEM ERROR ON WRITE
ERROR 07: SYSTEM ERROR ON READ
ERROR 08: DATA COMPARE ERROR
ERROR 09: SET MODE ERROR, DISABLING LOCAL LOOPBACK
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. Using the listing, together with R0 and IOSB information,
fault isolation can be achieved.
4. If isolation is not achieved proceed to level 2 diagnostic.
- TEST_3
Test 3 - Multiple Line Internal Data Loopback Test
This test will be aborted if the device is not a DHU11.
This test is designed to identify interaction problems between lines
by the transmission of data on all selected lines in internal loopback
mode. No operator setup is required for this test.
- ASSUMPTIONS
All hardware upto the device is working.
- TEST STEPS
1. Verify this is a valid device for this test.
2. Check the Loopback mode selected.
3. Initialize any parameters needed.
4. Identify the line selected to be tested.
5. Enable internal loopback.
6. Purge type ahead buffer.
7. Set baud rate.
8. Write message string to device.
9. Increment pointers and loop to (5) if necessary.
10. Reset and initialize any parameters.
11. Read message back.
12. Verify <data sent> = <data received>.
13. Disable internal loopback.
14. Increment pointers and loop to (11) if necessary.
15. End.
- ERRORS
ERROR 01: NOT A DHU11
ERROR 02: INVALID LOOPBACK SELECTED
ERROR 03: SET MODE ERROR ENABLING LOCAL LOOPBACK
ERROR 04: SYSTEM ERROR TRYING TO PURGE TYPE-AHEAD BUFFER
ERROR 05: SET MODE ERROR, SETTING BAUD RATE
ERROR 06: SYSTEM ERROR ON WRITE
ERROR 07: SYSTEM ERROR ON READ
ERROR 08: DATA COMPARE ERROR
ERROR 09: SET MODE ERROR, DISABLING LOCAL LOOPBACK
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. Using the listing, together with R0 and IOSB information,
fault isolation can be achieved.
4. This diagnostic handles all lines at one time. The lines
identified with possible problems should be tested with
Test 1 and 2, to isolate the fault.
5. If isolation is not achieved proceed to level 2 diagnostic.
- TEST_4
Test 4 - Modem Signal Loopback Test
This test will be aborted if the device is not a DHU11 or the user
did not select external loopback with connector H325.
This test is designed to check the sending of modem signals looped
back via the H325 connector.
Note:
SET EVENT FLAG 20 For delay between lines for loopback connector.
SET EVENT FLAG 21 For delay between units.
- ASSUMPTIONS
All hardware upto the device is working.
- TEST STEPS
1. Verify this is a valid device for this test.
2. Check the Loopback mode selected.
3. Initialize any parameters needed.
4. Identify the line selected to be tested.
5. Set up expected transmit and receive modem signals.
6. Read event flag 20. If not then set (8).
7. Ask user to place connector on line.
8. Clear TX modem signals.
9. Read RX modem signals.
10. Test RX modem signals are cleared.
11. Set TX modem signals.
12. Read TX modem signals.
13. Verify correct RX modem signal(s) set.
14. Increment pointer for TX signals to test and loop to (8).
12. Increment pointers and loop to (4) if necessary.
13. End.
- ERRORS
ERROR 01: NOT A DHU11
ERROR 02: INVALID LOOPBACK SELECTED
ERROR 03: SET MODE ERROR, SETTING OR CLEARING MODEM SIGNALS
ERROR 04: SENSE MODE ERROR, READING MODEM SIGNALS
ERROR 05: MODEM SIGNALS FAILED TO CLEAR
ERROR 06: SET MODE ERROR, SETTING OR CLEARING MODEM SIGNALS
ERROR 07: SENSE MODE ERROR, READING MODEM SIGNALS
ERROR 08: TRANSMITTED DTR, EXPECTED DSR AND RING
<or> TRANSMITTED RTS, EXPECTED CARRIER AND CTS
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. Using the listing, together with R0 and IOSB information,
fault isolation can be achieved.
4. If isolation is not achieved proceed to level 2 diagnostic.
- TEST_5
Test 5 External Data Loopback Test
This test will be aborted if the device is not a DHU11.
Test data transmitted on a selected line is compared to data received
on that line. Any variance will be flagged. The user is required to
setup the hardware before execution of this test using loopback
connector H325. If a modem loopback is to be tested then manual
selection of this mode has to be performed on the modem.
Note:
SET EVENT FLAG 20 For delay between lines for loopback connector.
SET EVENT FLAG 21 For delay between units.
- ASSUMPTIONS
All hardware upto the device is working.
- TEST STEPS
1. Verify this is a valid device for this test.
2. Check the Loopback mode selected.
3. Initialize any parameters needed.
4. Identify the line selected to be tested.
5. Check event flag 20, if clear then (7).
6. Ask user to place connector on line or modem into local loopback.
7. Set baud rate.
8. Purge any type-ahead information.
9. Write message string to device.
10. Read message back.
11. Verify <data sent> = <data received>.
12. Increment pointers and loop to (5) if necessary.
13. End.
- ERRORS
ERROR 01: NOT A DHU11
ERROR 02: INVALID LOOPBACK SELECTED
ERROR 03: SET MODE ERROR, SETTING BAUD RATE
ERROR 04: SYSTEM ERROR TRYING TO PURGE TYPE-AHEAD BUFFER
ERROR 06: SYSTEM ERROR ON WRITE
ERROR 07: SYSTEM ERROR ON READ
ERROR 08: DATA COMPARE ERROR
- DEBUG
1. Using the listing, follow the test steps.
2. Identify the ERROR message printed with the table above.
3. Using the listing, together with R0 and IOSB information,
fault isolation can be achieved.
4. If isolation is not achieved proceed to level 2 diagnostic.
- ERROR_TYPES
The following are the types of errors that can be reported by this
program:
Data Compare Errors
IO Time Out Errors
IO Setup Errors
- DATA_COMPARE_ERRORS
These errors occur when data transmitted does not correspond to data
received. For example:
******** DHU11 16 LINE ASYNC MUX TEST - 2.1 ********
Pass 1, test 3, subtest 0 error 8 27-JAN-1984 12:22:15.12
Hard error while testing TXB: DATA COMPARE ERROR
FOR LINE: 0F
GOOD DATA= 58(X) , BAD DATA= 00(X)
GOOD MESSAGE: ...$A THE QUICK BROWN FOX JUMPED OVER THE LAZY DOG.......
BAD MESSAGE: ...$A THE QUICK BROWN FO. JUMPED OVER THE LAZY DOG.......
Note: The "." (dots) represent non-printable characters.
In the message the "X" character, hex 58, was transmitted but when
received a null character, hex 00, was detected.
- IO_TIME-OUT_ERRORS
These errors can occur when information has been requested and a time
limit placed on the reply. Normally seen when loopback on modems
is not set up correctly or wrong baud speed selected for modem.
For example:
******** DHU11 16 LINE ASYNC MUX TEST - 2.1 ********
Pass 1, test 3, subtest 0, error 4 27-JAN-1984 12:40:50.54
System fatal while testing TXA: SYSTEM ERROR ON READ
FOR LINE: 0A
IOSB = 0000022C(X)
%TIMEOUT, device timeout
R0 = 00000009(X)
- IO_SETUP_ERROR
When a test is selected a series of checks are performed to make
sure that the correct information has been entered. For example:
Are we testing a DHU11?
Has the correct Loopback been selected for this test?
If an error is detected a error message of the following type will
be displayed.
******** DHU11 16 LINE ASYNC MUX TEST - 2.1 ********
Pass 1, test 5,subtest 0, error 2, 27-JAN-1984 12:50:23.32
System fatal while testing TXA: INVALID LOOPBACK SELECTED
FOR LINE: 05
Note:
All lines which are going to be tested should be allocated before the
Diagnostic Supervisor is executed. Once the Diagnostic is running
and lines selected the baud rate is entered. This rate is constant
for all lines under test. The situation can arise, since the DHU11
has two speed groups, that a speed selected can be influenced by the
adjacent line owned by a user. This is due to the ports being Dual
UARTS. So if an error occurs on setup related to the setting of the
baud rates check the adjacent port usage. To overcome the problem
always allocate adjacent ports, ie. 0-1,2-3,...14-15.
- SUMMARY
This command will display the diagnostic programs execution history.
- DEVICE
The DHU11 option is an asynchronous multiplexer which provides 16
full-duplex asynchronous serial data channels on UNIBUS systems.
The option can be used in many applications. These include data
concentration, terminal interfacing and cluster controlling.
- FEATURES
o Sixteen full duplex asynchronous data channels.
o Large 256-entry First-In-First-Out, (FIFO), buffer for
received characters, dataset status changes and
diagnostic information.
o Non-Processor Request, (NPR), or programmed transfers on
transmit. Each channel has a 64-byte FIFO for output data.
o Delay-timer for the receive interrupt aids efficient use
of the received character FIFO.
o RS-423-A/V.10/X.26 and RS-232-C/V.28 compatible.
o Full-duplex point-to-point or auto-answer dial-up operation.
o Programmable split speed per line.
o Total module throughput of 15000 characters per second.
o Automatic flow control of transmitted and received data.
o Self-test and background monitor diagnostics.
o Programmable test facilities.
o Single hex-height module (M3105).
o All functions are programmable, except for device
address and vector selection, which are made by hardware
switches on the module.
Enough modem control is provided on all 16 channels to allow
auto-answer dial-up operation over the Public Switched Telephone
Network, (PSTN). Suitable modems to use this facility are the Bell
models 103, 113, 212, or equivalent. The DHU11 can also be used
for point-to-point operation over private lines. Modem control is
imlemented by software in the host.
The module provides NPR or programmed transfers from the host
system to the serial lines via 16 x 64-byte FIFO buffers (one per
channel). A common 256-character FIFO buffer is provided for data
received from the serial lines.
By using microcomputers the DHU11 releases the host system from many
of the data handling tasks.
One 8051 microcomputer controls NPR transmissions from the host
system to the DHU11. A second 8051 controls eight SC2681 Dual
Universal Asynchronous Receiver Transmitters, (DUARTs), which carry
out the serial/parallel and parallel/serial conversion of data.
The DHU11 carries ROM-based diagnostics which are executed
independently of the host. A full range of diagnostic programs is
also available for both PDP-11 and VAX-11 systems.
A green LED gives the GO/NO-GO status of the module. More detailed
diagnostic information is also made available to the host system
via the received character FIFO. Loopback test connectors, built
into each line distribution panel, are available for use with the
system-based diagnostics.
I/O addresses, interrupt vectors, and interrupt priority for the
module are selected on three Dual-In-Line, (DIL), switchpacks. All
other DHU11 functions and configurations are programmable.
To prevent data loss at high throughput levels, the DHU11 can be
programmed for automatic X-ON and X-OFF operation.
- PHYSICAL
o A single hex-height module, (M3105).
o Two 8-way distribution panels, (H3029).
o Four interconnecting cables, (BC05L-xx).
Figure 1-1 shows major features of the module. Its dimensions are
21.4 cm x 39.9 cm (8.41 inches x 15.69 inches). The module is
connected to the backplane via connectors A-F. J1-J4 are
connected to the communications lines via BC05L cables and
(H3029) distribution panels.
DIL switchpacks E173, E60 and E121, select the device address,
the interrupt vector and the interrupt level, respectively.
- QUICK
Not supported
- SECTIONS
Indicates which program section to execute.
The section named DEFAULT will executed Tests 1, 2 and 3.
DS>ST
The section named MANUAL will execute Tests 4 and 5.
DS>START/SEC=MANUAL
Operator intervention is required for Test 4 and 5.