top - download
⟦44c0d9e65⟧ Wang Wps File
Length: 11909 (0x2e85)
Types: Wang Wps File
Notes: TDX Dev.Config.PSP
Names: »2622A «
Derivation
└─⟦5f5ac081b⟧ Bits:30006138 8" Wang WCS floppy, CR 0236A
└─ ⟦this⟧ »2622A «
WangText
…0e……05……0d……86…1
…02…
…02…
…02…
…02…FIX/3232/PSP/0034
…02…HV/820920…02……02…
TDX DEVICE
CONFIGURATION
PRODUCT
SPECIFICATION…02……02…FK
7809
LIST OF CONTENTS Page
1. SCOPE 1
2. APPLICABLE DOCUMENTS 1
3. FUNCTIONAL DESCRIPTION 2
3.1 Overview 2
3.1.1 External Interfaces 3
3.1.2 Processing 6
3.2 Submodule Description 14
3.2.1 LTUX-S Version 14
3.2.2 LTUX-M Version 16
4. Preparation for delivery 19
1. S̲C̲O̲P̲E̲
The TDX Device Configuration Submodule is used in the LTUX-S and LTUX-M for opening and closing
subdevices. Further parameters for programming the V24 line interfaces can be loaded to the
LTUX via this submodule.
2. A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
1. FIKS TDX SYSTEM DESIGN SPECIFICATION
FIX/3131/DSP/0011.
2. LTUX-S F/W Product Spec.
CSD-MIC/220/PSP/0012
3. LTUX-M F/W Product Specification.
CSD-MIC/230/PSP/0017
4. LTUX-S SYSTEM FIRMWARE
USERS MANUAL
CSD-MIC/220/USM/0006
5. LTUX-M SYSTEM FIRMWARE
USERS MANUAL
CSD-MIC/230/USM/0005
3. F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
3.1 O̲v̲e̲r̲v̲i̲e̲w̲
The log-lines which are connecting hosts with subdevice No. 0 in the LTUX's are reserved
for the TDX-Device Configuration Protocol.
The protocol includes 3 commands for opening, closing subdevices and for loading an SIO parameter
block.
The decision, whether or not to accept an incoming command, is left to the user. (Not implemented
in the LTUX-M version).
If the user accepts the open or close command, a Command Handler in the LTUX-System Software
is called to execute one or more of the following commands:
Code: Command:
00H Stop outputter
01H Stop inputter
02H Close channel
03H Open channel
05H SET OUTG.RESET MODE
06H Adjust Receive timer
07H Adjust Send timer
08H Start inputter
09H Input permit
0AH Input Not permit
0BH Start outputter
For each command received by an LTUX a command response shall be sent back to the device
that issued the command.
3.1.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
C̲o̲m̲m̲a̲n̲d̲ ̲P̲a̲c̲k̲e̲t̲ ̲F̲o̲r̲m̲a̲t̲
The commands are formatted as follows
CMD DST PAR1 PAR2
Max. 16 bytes
CMD: A one byte code indicating the type of command
DST: Destination code:
7 4 3 0
JACK NO. when CMD= LOAD SIO BLOCK
SUBDEVICE NO. when CMD= OPEN OR
CLOSE
PAR1, PAR2: Parameters, depending on the type of command
C̲o̲m̲m̲a̲n̲d̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲ ̲P̲a̲c̲k̲e̲t̲ ̲F̲o̲r̲m̲a̲t̲
To each command issued from CR80 to an LTUX a response is returned to the CR80 to tell whether
the command was successfully completed or not.
Layout:
CMD COMPL. PROGRAM
RESP. CODE REF.
CMD RESP.: Command Response Code (20H is chosen)
COMPL.CODE: Completion Code
PROGRAM REF: A program address reference (2 bytes).
Completion Code: 00H indicates successful completion. All other codes indicate unsuccessful
completion:
Completion Code:01H-0FH indicates unsuccessfull completion after a call of the Command Handler
in the LTUX-system software.
Completion Code:10H-1FH indicates unsuccesful completion after a call of a subroutine in
the LTUX application software.
A code indicating a unsuccessful completion is followed by a program address reference (2
bytes in the Command response packet).
Completion Code:20H indicates that a illegal command has been received.
Fig. 3.1.1
Completion Codes:
From LTUX-System Software
01H stop outputter not executed
02H stop inputter - -
03H close channel - -
04H open channel - -
05H reserved
06H start outputter - -
07H adjust rec. timer not executed
08H adjust send - - -
09H start inputter - -
0AH Input Permit - -
0BH Input Not Permit - -
From LTUX-Application Software
10H open subdevice not executed
11H close - - -
12H SIO Parameter Block rejected
20H Illegal command received
3.1.2 P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲
The TDX-System Configuration Protocol takes care of
o Open specified subdevice
o Close specified subdevice
o Load SIO-parameter Block to specified V24 line
After power-up the Configuration Protocol is initialized.
The subdevice No. 0 is opened during initialization with the correct device number, which
is read from the DIL-switch, and the inputter-routine is started.
The LTUX is then ready for receiving the following configuration frames from the host:
O̲p̲e̲n̲ ̲s̲p̲e̲c̲i̲f̲i̲e̲d̲ ̲S̲u̲b̲d̲e̲v̲i̲c̲e̲
To open a subdevice the host must send a configuration frame with Command Code = 01H to the
LTUX.
The Configuration frame is formatted as shown on fig. 3.1.2.
C̲l̲o̲s̲e̲ ̲s̲p̲e̲c̲i̲f̲i̲e̲d̲ ̲S̲u̲b̲d̲e̲v̲i̲c̲e̲
To close a subdevice the host must send a configuration frame with Command Code = 02H to
the LTUX.
The Configuration frame is formatted as shown on fig. 3.1.2.
L̲o̲a̲d̲ ̲S̲I̲O̲-̲B̲l̲o̲c̲k̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲
A line handler is programmed from an application program in the host by sending a configuration
frame with Command Code = 03H to the LTUX. The frame is formatted as shon on fig. 3.1.2
M̲0̲:̲
B̲i̲t̲ ̲3̲-̲0̲ ̲ ̲F̲r̲e̲q̲.̲A̲s̲y̲n̲c̲.̲(̲b̲i̲t̲/̲s̲e̲c̲)̲ ̲ ̲F̲r̲e̲q̲.̲S̲y̲n̲c̲.̲(̲b̲i̲t̲/̲s̲e̲c̲)̲
0000 50 300
0001 75 600
0010 100 1200
0011 110 2400
0100 150 4800
0101 165 9600
0110 200 19200
0111 300 32000
1000 600 48000
1001 1200 64000
1010 2400
1011 4800
1100 9600
1101 19200
B̲i̲t̲ ̲7̲-̲4̲
0000
M̲1̲:̲ Reserved
M̲2̲:̲ Not used
Fig. 3.1.3
M̲3̲:̲
B̲i̲t̲ ̲5̲-̲0̲
000000
B̲i̲t̲ ̲7̲-̲6̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲R̲e̲c̲e̲i̲v̲e̲ ̲f̲o̲r̲m̲a̲t̲
00 5 bits/char
01 7 bits/char
10 6 bits/char
11 8 bits/char
M̲4̲:̲
B̲i̲t̲ ̲1̲-̲0̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲P̲a̲r̲i̲t̲y̲-̲m̲o̲d̲e̲
00 no parity
01 odd parity
10 no parity
11 even parity
B̲i̲t̲ ̲3̲-̲2̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲F̲r̲a̲m̲e̲-̲m̲o̲d̲e̲
00 Sync. mode
01 1 stop bit/char
10 1 1/2 stop bit/char
11 2 stop bit/char
B̲i̲t̲ ̲5̲-̲4̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲y̲n̲c̲-̲m̲o̲d̲e̲
00 8 bit programmed sync
01 16 bit programmed sync
10 SDLC
11 External sync
B̲i̲t̲ ̲7̲-̲6̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲C̲l̲o̲c̲k̲-̲m̲o̲d̲e̲
00 Data rate x 1 = clock rate
01 Data rate x 16 = clock rate
10 Data rate x 32 = clock rate
11 Data rate x 64 = clock rate
M̲5̲:̲
B̲i̲t̲ ̲4̲-̲0̲
00000
B̲i̲t̲ ̲6̲-̲5̲ ̲ ̲ ̲ ̲T̲r̲a̲n̲s̲m̲i̲t̲ ̲f̲o̲r̲m̲a̲t̲
00 5 bits/char
01 7 bits/char
10 6 bits/char
11 8 bits/char
B̲i̲t̲ ̲7̲
0
M̲6̲:̲
B̲i̲t̲ ̲7̲-̲0̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Sync char/address field. This field is programmed to contain the transmit sync character
in the Monosync mode, the first eight bits of a 16-bit sync character in the Bisync mode,
or a transmit sync character in the External Sync mode. In the SDLC mode, it is programmed
to contain the secondary address field used to compare against the address field of the SDLC
frame.
M̲7̲
B̲i̲t̲ ̲7̲-̲0̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Sync char/flag character field. This field is programmed to contain the receive sync character
in the Monosync mode, a second byte (last eight bits) of a 16-bit sync character in the Bisync
mode, or a flag character (01111110) in the SDLC mode. M7 is not used in the External Sync.
mode.
The TDX Device Configuration Protocol hands over an incoming request by calling one of three
user defined subroutines. The subroutine entry point is fetched from a user defined branch
table, UBTAB.
UBTAB: ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
0…0f…OPEN…0e…
1 ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
2…0f…CLOSE…0e…
3 ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
4…0f…SIO BLOCK…0e…
5 ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
O̲P̲E̲N̲ ̲S̲u̲b̲d̲e̲v̲i̲c̲e̲,̲ ̲s̲u̲b̲r̲o̲u̲t̲i̲n̲e̲
DESCRIP: The routine receives an incoming OPEN request from the TDX-Device Configuration
Protocol and decides if the request shall be accepted or rejected. Further the
routine may include user defined actions.
ENTRY: SUBDEVICE NO. in reg. C (bit 4-7)
EXIT: CY - flag = 0 - Request not accepted
CY - flag = 1 - Request accepted
IF CY = 0, Reg A holdes a Completion
Code and Reg DE holds a Program
address reference.
C̲L̲O̲S̲E̲ ̲S̲u̲b̲d̲e̲v̲i̲c̲e̲,̲ ̲s̲u̲b̲r̲o̲u̲t̲i̲n̲e̲
DESCRIP: The routine receives an incoming CLOSE request from the TDX-Device Configuration
Protocol and decides if the request shall be accepted or rejected. Further the
routine may include user defined actions.
ENTRY: SUBDEVICE No. in reg. C (bit 4-7)
EXIT: CY - flag = 0 - Request not accepted
CY - flag = 1 - Request accepted
IF CY = 0, Reg A holds a Completion
Code and Reg DE holds a Program
address reference.
R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲I̲O̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲B̲l̲o̲c̲k̲,̲ ̲s̲u̲b̲r̲o̲u̲t̲i̲n̲e̲
DESCRIP: The routine decides if an incoming SIO parameter block shall be accepted or rejected.
If accepted, the block is fetched and handed over to the user. Further the routine
may incluyde user defined actions.
ENTRY: V24 Jack No. in reg. C
Pointer to start of SIO block in reg. pair DE
EXIT: CY - flag = 0 - SIO block not accepted
CY - flag = 1 - SIO block accepted
If CY = 0, Reg A holds a Completion
Code and Reg DE holds a
program address reference.
3.2 S̲u̲b̲m̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The configuration submodule differs in the LTUX-S and LTUX-M.
3.2.1 L̲T̲U̲X̲-̲S̲ ̲V̲e̲r̲s̲i̲o̲n̲
In the LTUX-S the submodule is implemented as a process, which shall be created and scheduled
by the operating system in the standard LTUX-S S/W.
This process has its own stack (15 levels deep) and the entry point is the label: "DCINIT".
During processing the command "OPEN SUBDEVICE" following calls to the TDX Protocol are performed:
1) Adjust Receive Timer
2) Adjust Send Timer
3) Input Permit
4) Start Inputter
5) Start Outputter
6) Open Channel
During "Closing Subdevice" the following call is performed: 1) close channel.
3.2.2 L̲T̲U̲X̲-̲M̲ ̲V̲e̲r̲s̲i̲o̲n̲
In the LTUX-M the submodule is implemented as two subroutines:
1) DCMINI: THis subroutine shall be called 1 time during initialisation of the entire LTUX-M
2) DCM: Which shall be called regularly.
During "open and close subdevice" the same calls are performed to the TDX protocol as described
in LTUX-S version.
NOTE: In the LTUX-M version the decision for the user to accept the incoming commands are not implemented.
4. P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲ ̲F̲O̲R̲ ̲D̲E̲L̲I̲V̲E̲R̲Y̲
The submodules can be found in the following files:
LTSDCS: FIXSYS (LTUX-S)
LTMDCS: FIXSYS (LTUX-M)
The submodules are further located in the FIXLIB:FIXSYS as relocatable modules, which can
be linked to the other modules by calling FIXLIB:FIXSYS during linking.
