- HELP
EVDMF is a level 2R diagnostic intended to aid in the maintenance and
installation of M8206/M8201 communication link. This program
is DCLT (Data Communication Link Test) Compatible.
- ATTACH
A sample of attaching a M8206/M8201 on a VAX 11/780:
ATT DW780 SBI DW0 3 4 ; Attaches the UBA to the SBI
ATT KMSYG DW0 YGx 760100 300 5 ; Attach YGx (x=A,B,..) to UBA
SELECT YGx ; Select the attached M8206/M8201.
Only the first M8206/M8201 will be tested as the VAX end of the
communication link.
- SECTIONS
There is only one section to EVDMF, which is run every time a START is
typed.
- DEVICE
EVDMF supports DCLT testing of M8206/M8201 link. The
VAX M8206/M8201 DCLT program is capable of exercising a VAX to PDP-11
M8206/M8201 link.
- EVENT
This DCLT program uses only one event flag:
Event Flag 1 Clear The M8206/M8201 is run in full
duplex mode
Set The M8206/M8201 is run in half
duplex mode. Initialized to half duplex
mode in the DVINIT subroutine after a
DS> START.
- QUICK
This DCLT program does not implement the QUICK feature. Execution
mode is specified at the time of the DCLT Run Command
- SUMMARY
The Summary command will cause EVDMF to do the same as a DCLT Print;
Optionally prints the DDCMP Error counters provided by the M8206/M8201
driver and prints the DCLT Event Log which contains the last 45 events
that occurred and the information associated with each event.
- DCLT
DCLT is the acronym for Data Communications Link Test. The DCLT
project is a group of programs aimed at detecting failures in
the modems, communication link, or computer equipment. The goal
of DCLT programs is to test the link, not the communciations
equipment. Therefore, it would be wise to run the diagnostics
specific to the device before attempting to test the link.
- YGDRIVER
To install the VAX/VMS device driver for the M8206/M8201, use the
following command sequence:
$ MCR SYSGEN
SYSGEN> CONNECT YGx/ADA=UBx/CSR=%O76xxxx/VEC=%Oxxx/NUMVEC=2/DRIVER=YGDRIVER
SYSGEN> EXIT
- SYSGEN
YGx - is the generic name for the M8206/M8201 and x is the controller
letter. The letter A is used for the first one, B for the second,
etc.
UBx - is the Unibus Adapter number that the device is connected to.
it should be 0 for the first UBA, 1 for the second UBA, etc.
CSR - is the Unibus address for this controller. %O tells the software
that the number is an octal value.
VEC - is the interrupt vector for the device. %O tells software that the
number is an octal value
NUMVEC - is the number of interrupt vectors used by the device. This
one uses two, one for commands to device, one for information
from the device.
DRIVER - is the name of the VAX/VMS Device Driver for this device. The
software will assume that the driver is in SYS$SYSROOT:[SYSEXE]
if specified as the example shows. If it is not in that
directory, then let the software know which disk and directory
the driver is located in. i.e. if the driver was in the
directory DBA1:[SYSMAINT], then use
.../DRIVER=DBA1:[SYSMAINT]
- PROBLEMS
Once you are finished, use the show device command to check the state of
the device. i.e.
$ SHO DEV YGA
If the resulting text says the device is online, then go ahead and use the
diagnsostic. If it is offline, it probably means that Unibus Timeouts occur
when accessing the device at the address you specified. Check the following:
a) The address you connected the device at is the correct address
b) You did not forget the %O (not %0) before entering the address
c) That the M8206 passes the diagnostic EVDXA without errors
If you still have problems, then your guess is as good as mine.
If you get the vector wrong, interrupts will never be delivered to
the VAX/VMS driver and the diagostic will get I/O timeout errors.
Use the same procedure to verify the vector as used to verify the
address.
- COMMANDS
Once a DCLT program is started, the initialization code is executed.
After that a DCLT prompt will appear at which time the operator can
enter any of the DCLT Message, Run, or Statistical Commands.
- CLEAR
Format: Clear list where list is Transmitlist or Expectlist
for example: C T
- SET
Format: SEt list=type/Size=n/Copy=m
where list is Transmitlist or Expectlist
where type is Ones,Zeroes,Ccitt,Itep,1alt
0alt, or " A-Z 0-9"
for example SE T=CC/S=25/C=5 ; which puts 6 CCITT messages on the
; transmit list
- SHOW
Format: SHow list where list is Transmitlist or Expectlist
- RUN
Format: Run Mode=type/switch(es)
where type is Active,Passive,TRansmit,Receive,
TAlk,Listen, or Downlineload
where /switches is any one or combination of:
/Status,/Check,/Echo,/Pass=n
/NOStatus,/NOCheck,/NOEcho,
/Loop=Internal or Cable
- EXIT
Returns program execution to the DS> command level
- PRINT
Optionally prints the DDCMP Error counters provided by the M8206/M8201 driver
and prints the DCLT Event Log which contains the last 45 events that
occurred and the information associated with each event.
- SCRIPT
Indirect command files can contain commands appropriate to the DCLT>
or DS> command level and are invoked by a "@file-spec" at the DS> level.
a sample command file may look something like:
DS> START
DCLT> SET TRANSMIT=CCITT/SIZE=25/COPY=5
DCLT> SET EXPECT=CCITT/SIZE=25/COPY=5
DCLT> RUN MODE=ACTIVE/LOOP=INT/STATUS/PASS=3