DIAG EXT[ernal] [ Troubleshooting Terminal, Printer, and Serial Device Connections ] MPE/iX 5.0 Documentation
Troubleshooting Terminal, Printer, and Serial Device Connections
DIAG EXT[ernal]
Determines if a specific port is functioning properly , including the
connector. Sends data out and reads it immediately, verifying that the
data received is exactly what was sent.
Security level: 2.
Syntax
________________________________________________________________________
| |
| |
|EXT[ERNAL] dtcnum,cardnum,portnum |
________________________________________________________________________
Parameters
dtcnum
The number TermDSM associates with a particular DTC. The DTC command
lists each DTC with its assigned number. This list is also printed when
you make a mistake while typing in a DTC number.
cardnum
Number of the interface card within the DTC to which the device is
connected. The cards are numbered from zero beginning at the bottom of
the DTC.
Range: 0 - 5
portnum
Number of the port on the interface card. As you face the back of the
DTC, the ports are numbered from zero beginning at the left of the board.
Range: 0 - 7 for direct connections.
0 - 5 for modem connections.
Description
When this subcommand is entered, the following question is displayed on
the terminal:
Do you want to stop looping if an error is found
(yes/no)?
If the answer is yes, the series of loopback tests will stop if an error
is encountered. For example, you specified you want the loopback test to
run 10 times and an error is encountered in the third test. If you
answered yes to the above question, the remaining seven tests will not be
run. If you answered no, all 10 loopback tests will be executed
regardless of the results of each test. The following is then printed on
the terminal:
Please put a loopback hood on the Port, before
answering the "How many times?" question. (TDSM 113)
How many times do you want to repeat this operation?
At this time, go to the DTC and connect a loopback hood to the port.
Then return and enter how many times you want to run this diagnostic
function. Enter a number between 1 and 65535. The following is then
displayed:
Type CONTROL_Y to stop the looping.
Any time that you want to stop the diagnostic, press CTRL-Y. The
diagnostics prompt will be printed and you will be allowed to enter
another subcommand.
If TermDSM knows that this test has failed, an error message will be
printed listing the reason for the failure and how many milliseconds the
test ran before failing.
The diagnostics prompt will be printed and you will be allowed to enter
another subcommand.
Example
(diagnostics)
SElftest # (DTC Selftest)
PRint #,#,# (Print to specified port)
Internal #,#,# (Internal loopback on specified port)
EXTernal #,#,# (Loopback through hood on specified port)
Terminal #,#,# (Write and read to terminal on that port)
(carriage return to exit) ?EXT 3,2,5
Do you want to stop looping if an error is found (yes/no)? y
Please put a loopback hood on the Port, before answering the
"How many times?" question. (TDSM 113)
How many times do you want to repeat this operation? 5
Type CONTROL_Y to stop the looping. Read timeout (no data came back).
Time = 16950 msec. If External loopback, check loopback hood.
If Terminal loopback, check connections, terminal configuration, etc.
(TDSM 229)
The test passed 0 times and failed 1 time.
(diagnostics)
SElftest # (DTC Selftest)
PRint #,#,# (Print to specified port)
Internal #,#,# (Internal loopback on specified port)
EXTernal #,#,# (Loopback through hood on specified port)
Terminal #,#,# (Write and read to terminal on that port)
(carriage return to exit) ?
The example External Port subcommand should execute four internal
loopback tests on the sixth port of the third card of DTC number three.
(Remember that ports and cards are numbered starting with zero.) Note
that when the first loopback fails, the other four are not executed
because stop on error was requested. If the loopback connector is on the
correct port, attached correctly, this error indicates the port is
defective. Verify the proper attachment of the loopback hood and run the
test again. If you do not have a loopback connector, the internal
loopback test or terminal test (for supported devices) can be run
instead.
MPE/iX 5.0 Documentation