- HELP
This product is part of the diagnostic package for the DMB32. It
provides the ability to test the Asynchronous 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 Asynchronous interfaces, 1 to 64 units(maximum)
o Associated cables - BC22D for local terminals or BC22E for
remote terminals
o 12-15336-00 (or H325) single line loopback connector
(optional)
o Modem with loopback (optional)
- SOFTWARE
o VAX/VMS V4.4 or later operating system
o VAX Diagnostic Supervisor (VDS) V10.0
o EVDAJ.EXE - VAX Online diagnostic for DMB32 async lines
o EVDAJ.HLP - VAX Online help for the EVDAJ 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 - TXa 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 TXa 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 TXa 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
EVDAJ diagnostic program is divided into three sections which can be
selected via the /SECTIONS qualifier on the VDS START command. The
sections are as follows:
o Default : no loopback connector required
o External : 12-15336-00 single line loopback required
o Modem : modem with loopback capability required
- DEFAULT
This section contains tests 1,2 and 3. The tests are run in internal
loopback, no loopback connectors are needed.
Example: DS> START or
DS> START/SECTION=DEFAULT
- EXTERNAL
This section contains tests 1,2,3,4 and 5. Tests 1-3 are run in
internal loopback mode and tests 4 and 5 in normal mode. The single
line 12-15336-00 external loopback connector is needed to run this
section.
Example: DS> START/SECTION=EXTERNAL
- MODEM
This section contains tests 1,2,3 and 5. Tests 1-3 are run in
internal loopback mode and test 5 in normal mode. A modem with local
loopback capability is needed to run 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
Event flag 20 functions in tests 4 and 5 only. When the flag is set
the program halts before each channel is tested. This allows the
operator to :
o move the loopback connector to the channel to be tested next
OR
o move the modem (in local loopback), to the channel to be
tested next.
Example: DS> SET EVENT 20
Event flag 21 functions in all tests. When the flag is set the
program halts before each DMB32 is tested, allowing loopbacks or
modems to be connected.
Example: DS> SET EVENT 21
- OPTIONS
The following questions will be asked on start up
LINES TO TEST
BAUD RATE
- LINES_TO_TEST
You will be asked to identify the lines on the UUT(Unit Under Test) to
be tested.
Lines to test [(ALL), REVERSE, EVEN, ODD, 0,1,2..,6,7]
This question can take one of the the following responses:
o ALL - All 8 lines on the unit under test will be accessed
(default).
o ODD - Odd numbered lines only will be tested (lines 1,3,5,7).
o EVEN - Even numbered lines only will be tested (lines
0,2,4,6).
o REVERSE - All 8 lines tested in reverse order.
o n - Only the line specified will be tested.
o n,m,p - Combinations of lines selected within the unit under
test.
NOTE : The lines will be tested in the order specified.
- BAUD_RATE
The user will be asked to identify the Baud rate to be used during
testing.
Baud Rate [(9600), 75, 110, 134, 150, 300, 600, 1200, 1800, 2000,
2400, 4800, 19200]
- TESTS
This diagnostic contains the following tests.
- TEST_1
The internal loopback test transmits a single character on lines that
you specify. No operator setup is required for this test. The test
attempts to cause single character mode transmission from the DMB32.
This test is contained in ALL sections
- STEPS
1. Initialise any parameters needed.
2. Identify the line selected to be tested.
3. Enable internal loopback.
4. Purge type ahead buffer.
5. Set baud rate.
6. Write message string to device.
7. Read message back.
8. Verify <data sent> = <data received>.
9. Disable internal loopback.
10. Increment pointers and loop to (2) if necessary.
11. End.
- ERRORS
ERROR 01: ERROR ON SET_MODE QIO, WHEN ENABLING LOCAL LOOPBACK
ERROR 02: ERROR ON READ QIO, WHEN PURGING TYPE-AHEAD BUFFER
ERROR 03: ERROR ON SET_MODE QIO, WHEN SETTING BAUD RATE
ERROR 04: ERROR ON WRITE QIO
ERROR 05: ERROR ON READ QIO
ERROR 06: DATA COMPARISON ERROR
ERROR 07: ERROR ON SET_MODE QIO, WHEN DISABLING LOCAL LOOPBACK
ERROR 100: SYSTEM ERROR ON $GETDVI SYSTEM SERVICE
ERROR 101: ERROR ON SET_MODE QIO, WHEN SETTING BAUD RATE,
POSSIBLE CONFLICTING BAUD GROUP ON ADJACENT LINE
ERROR 103: TIMEOUT WAITING FOR WRITE QIO TO COMPLETE
- 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 3 diagnostic.
- TEST_2
This test attempts to force the DMB32 driver to do a DMA transfer
by transmitting a long message (greater than 64 bytes in length).
For each line specified by the user, the following is performed
on each line in turn :
o Set the line into internal loopback
o Transmit a message
No operator setup is required for this test.
This test is contained in ALL sections
- STEPS
1. Initialise any parameters needed.
2. Identify the line selected to be tested.
3. Enable internal loopback.
4. Purge type ahead buffer.
5. Set baud rate.
6. Write message string to device.
7. Read message back.
8. Verify <data sent> = <data received>.
9. Disable internal loopback.
10. Increment pointers and loop to (2) if necessary.
11. End.
- ERRORS
ERROR 01: ERROR ON SET_MODE QIO, WHEN ENABLING LOCAL LOOPBACK
ERROR 02: ERROR ON READ QIO, WHEN PURGING TYPE-AHEAD BUFFER
ERROR 03: ERROR ON SET_MODE QIO, WHEN SETTING BAUD RATE
ERROR 04: ERROR ON WRITE QIO
ERROR 05: ERROR ON READ QIO
ERROR 06: DATA COMPARISON ERROR
ERROR 07: ERROR ON SET_MODE QIO, WHEN DISABLING LOCAL LOOPBACK
ERROR 100: SYSTEM ERROR ON $GETDVI SYSTEM SERVICE
ERROR 101: ERROR ON SET_MODE QIO, WHEN SETTING BAUD RATE,
POSSIBLE CONFLICTING BAUD GROUP ON ADJACENT LINE
ERROR 103: TIMEOUT WAITING FOR WRITE QIO TO COMPLETE
- 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 3 diagnostic.
- TEST_3
This test identifies interaction problems between lines. This is
done by transmitting data on all the user selected lines in internal
loopback mode. On completion of this, the transmitted data is then
read back and verified. No operator setup is required for this test.
In this test each line will be tested once only, even though it may
have been specified more than once during the Lines To Test question.
This test is contained in ALL sections
- STEPS
1. Initialise any parameters needed.
2. Identify the line selected to be tested.
3. Enable internal loopback.
4. Purge type ahead buffer.
5. Set baud rate.
6. Increment pointers and loop to (2) if necessary.
7. Reset and initialise any parameters.
8. Write message string to device.
9. Increment pointers and loop to (8) if necessary.
10. Reset and initialise 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: ERROR ON SET_MODE QIO, WHEN ENABLING LOCAL LOOPBACK
ERROR 02: ERROR ON READ QIO, WHEN PURGING TYPE-AHEAD BUFFER
ERROR 03: ERROR ON SET_MODE QIO, WHEN SETTING BAUD RATE
ERROR 04: ERROR ON WRITE QIO
ERROR 05: ERROR ON READ QIO
ERROR 06: DATA COMPARISON ERROR
ERROR 07: ERROR ON SET_MODE QIO, WHEN DISABLING LOCAL LOOPBACK
ERROR 100: SYSTEM ERROR ON $GETDVI SYSTEM SERVICE
ERROR 101: ERROR ON SET_MODE QIO, WHEN SETTING BAUD RATE,
POSSIBLE CONFLICTING BAUD GROUP ON ADJACENT LINE
ERROR 103: TIMEOUT WAITING FOR WRITE QIO TO COMPLETE
- 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 3 diagnostic.
- TEST_4
This test checks the sending of modem signals looped back via
the 12-15336-00 loopback connector.
This test is contained in the EXTERNAL section only.
NOTES:
SET EVENT FLAG 20 For delay between lines for loopback connector.
SET EVENT FLAG 21 For delay between units.
- STEPS
1. Initialise any parameters needed.
2. Identify the line selected to be tested.
3. Read event flag 20. If not then set (5).
4. Ask user to place connector on line.
5. Set TX modem signals.
6. Read modem signals.
7. Verify RX modem signals are correct.
8. Increment pointer for TX signals to test and loop to (5).
9. Increment pointers and loop to (2) if necessary.
10. End.
- ERRORS
ERROR 01: SET MODE ERROR, SETTING OR CLEARING MODEM SIGNALS
ERROR 02: SENSE MODE ERROR, READING MODEM SIGNALS
ERROR 03: TRANSMITTED DTR, EXPECTED DSR AND RING
<or> TRANSMITTED RTS, EXPECTED CARRIER AND CTS
<or> MODEM SIGNALS FAILED TO CLEAR
- 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 3 diagnostic.
- TEST_5
Test data transmitted on a selected line is compared to data received
on that line. Any variance will be reported. The user is required
to setup the hardware before execution of this test using loopback
connector 12-15335-00. If a modem loopback is to be tested then
manual selection of this mode has to be performed on the modem.
This test is contained in sections EXTERNAL and MODEM
NOTES:
SET EVENT FLAG 20 For delay between lines for loopback connector.
SET EVENT FLAG 21 For delay between units.
- STEPS
1. Initialise any parameters needed.
2. Identify the line selected to be tested.
3. Check event flag 20, if clear then (5).
4. Ask user to place connector on line
or switch modem into local loopback.
5. Purge any type-ahead information.
6. Set baud rate.
7. Write message string to device.
8. Read message back.
9. Verify <data sent> = <data received>.
10. Increment pointers and loop to (3) if necessary.
11. End.
- ERRORS
ERROR 01: ERROR ON SET_MODE QIO, WHEN SETTING BAUD RATE
ERROR 02: ERROR ON READ QIO, WHEN PURGING TYPE-AHEAD BUFFER
ERROR 03: ERROR ON WRITE QIO
ERROR 04: ERROR ON READ QIO
ERROR 05: DATA COMPARISON ERROR
ERROR 100: SYSTEM ERROR ON $GETDVI SYSTEM SERVICE
ERROR 101: ERROR ON SET_MODE QIO, WHEN SETTING BAUD RATE,
POSSIBLE CONFLICTING BAUD GROUP ON ADJACENT LINE
ERROR 103: TIMEOUT WAITING FOR WRITE QIO TO COMPLETE
- 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 3 diagnostic.