top - download
⟦4edf3956d⟧ Wang Wps File
Length: 21139 (0x5293)
Types: Wang Wps File
Notes: CPS/TCN/031
Names: »1315A «
Derivation
└─⟦71faab506⟧ Bits:30006051 8" Wang WCS floppy, CR 0079A
└─ ⟦this⟧ »1315A «
WangText
…0d……00……00……00……00…F…0a……00……00…F…0b…F…0c…F…00…F…05…E…0a…E…0e…E…0f…E…86…1 …02… …02… …02…
…02…CPS/TCN/031
…02…SRA/821109…02……02…#
CAMPS LTUX-S V24 INTERFACES
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1. GENERAL................................. 4
2. INTERFACES.............................. 5
2.1 LTUX-S TO VDU........................ 5
2.2 LTUX-S TO MSP........................ 8
2.3 LTUX-S TO OCR........................ 11
2.4 LTUX-S TO PTP/PTR.................... 14
2.4.1 ELECTRICAL INTERFACE............. 14
2.4.2 DATA TRANSFER.................... 15
2.5 LTUX-S TO TRC/POINT-TO-POINT......... 19
2.6 LTUX-S TO STATISTICAL MUX. 1......... 21
2.7 LTUX-S TO STATISTICAL MUX. 2......... 24
3. REMOTE SITE CONNECTIONS................. 27
1̲ ̲G̲E̲N̲E̲R̲A̲L̲
This TCN presents the currently existing CAMPS LTUX-S
V24 interfaces. The purpose of this presentation is
to establish:
1. the relevant V24 interface signals
2. how to interpret the V24 interface control
signals
Interface types to be described are:
LTUX-S to VDU, opto (sec. 2.1)
LTUX-S to MSP, opto (sec. 2.2)
LTUX-S to OCR (sec. 2.3)
LTUX-S to PTP/PTR (sec. 2.4)
LTUX-S to TRC/Point-to-point (sec. 2.5)
LTUX-S to Statistical Mux. 1 (sec. 2.6)
LTUX-S to Statistical Mux. 2 (sec. 2.7)
To complete the picture of CAMPS terminal connections
chapter 3 goes through connections between the Statistical
Multiplexer and the different terminals on the remote
site.
It should be noted that the LTUX-S V24 controlsignal
input circuit 109, as described in the TCM CSD-MIC/005/TCM/0009,
has been interchanged with circuit 107 for the CAMPS
application (This has LTUX-S software impact i.e. the
AUTO ENABLES function cannot be used when initializing
the SIO. The D̲S̲R̲ (SIO input D̲C̲D̲) and C̲T̲S̲ (SIO input
C̲T̲S̲) should be read from SIO register 0 and acted upon
as described in the following).
2̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
2.1 L̲T̲U̲X̲-̲S̲ ̲T̲O̲ ̲V̲D̲U̲
This interfacetype requires the following V24 circuits
(ref. fig. 2.1-1):
102 : Signal ground
103 : Transmitted data (TXD)
104 : Received data (RXD)
105 : Request To Send (RTS)
106 : Clear To Send (CTS)
107 : Data Set Ready (DSR)
108.2: Data Terminal Ready (DTR)
N̲o̲t̲e̲:̲ ̲A̲l̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲c̲i̲r̲c̲u̲i̲t̲s̲ ̲a̲r̲e̲ ̲d̲e̲s̲c̲r̲i̲b̲e̲d̲ ̲a̲s̲ ̲s̲e̲e̲n̲
̲f̲r̲o̲m̲ t̲h̲e̲ ̲L̲T̲U̲X̲-̲S̲ ̲u̲n̲l̲e̲s̲s̲ ̲o̲t̲h̲e̲r̲w̲i̲s̲e̲ ̲i̲n̲d̲i̲c̲a̲t̲e̲d̲.̲
The LTUX-S turns …08…ON…08… D̲T̲R̲ and R̲T̲S̲ whenever it is ready
to operate.
As long as D̲S̲R̲ (activated by the VDU) is …08…OFF…08… no data
must be transmitted on T̲X̲D̲.
When the LTUX-S has data to be transmitted on T̲X̲D̲ it
must for each character to be transmitted verify that
both D̲S̲R̲ and C̲T̲S̲ is …08…ON…08…. This indicates that both the
link to the VDU (C̲T̲S̲) and the VDU (D̲S̲R̲) is ready to
operate.
If the optolink fails during transmission this is indicated
by C̲T̲S̲ going …08…OFF…08…. Detecting this the LTUX-S must stop
transmitting data. The occurrence of C̲T̲S̲ …08…OFF…08… and R̲T̲S̲
…08…ON…08… shall be interpreted as an error condition and reported
accordingly.
D̲S̲R̲ going …08…OFF…08… is caused by:
1) Link error outside the optolink
2) Flowcontrol activated by the VDU
3) VDU power off
As seen from this D̲S̲R̲ going …08…OFF…08… provides no exact errorinformation.
A software timer would in most of the cases separate
condition 2 from 1 and 3 which are error conditions
to be reported.
Error conditions 1 and 3 are separated as follows:
Cond. 1 Cond. 3
D̲S̲R̲ …08…OFF…08… …08…OFF…08…
C̲T̲S̲ …08…ON…08… …08…OFF…08…
The VDU exercises flowcontrol via D̲S̲R̲ (VDU circuit
D̲T̲R̲) as described in Minutes Of Meetings 810706 between
Delta Data and CRAS. Whenever the free input buffer
space is below 100 characters D̲S̲R̲ is turned …08…OFF…08…. When
the free inputbuffer space exceeds 100 characters D̲S̲R̲
is turned …08…ON…08… again.
Fig. 2.1-1
L̲T̲U̲X̲-̲S̲/̲V̲D̲U̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
2.2 L̲T̲U̲X̲-̲S̲ ̲T̲O̲ ̲M̲S̲P̲
This interfacetype requires the following V24 circuits
(ref. fig. 2.2-1):
102 : Signal ground
103 : Transmitted data (TXD)
104 : Received data (RXD)
105 : Request To Send (RTS)
106 : Clear To Send (CTS)
107 : Data Set Ready (DSR)
108.2: Data Terminal Ready (DTR)
N̲o̲t̲e̲:̲ ̲A̲l̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲c̲i̲r̲c̲u̲i̲t̲s̲ ̲a̲r̲e̲ ̲d̲e̲s̲c̲r̲i̲b̲e̲d̲ ̲a̲s̲ ̲s̲e̲e̲n̲
̲f̲r̲o̲m̲ t̲h̲e̲ ̲L̲T̲U̲X̲-̲S̲ ̲u̲n̲l̲e̲s̲s̲ ̲o̲t̲h̲e̲r̲w̲i̲s̲e̲ ̲i̲n̲d̲i̲c̲a̲t̲e̲d̲.̲
The LTUX-S turns …08…ON…08… D̲T̲R̲ and R̲T̲S̲ whenever it is ready
to operate.
As long as D̲S̲R̲ (activated by the MSP) is …08…OFF…08… no data
must be transmitted on T̲X̲D̲.
When the LTUX-S has data to be transmitted on T̲X̲D̲ it
must for each character to be transmitted verify that
both D̲S̲R̲ and C̲T̲S̲ is …08…ON…08…. This indicates that both the
link to the MSP (C̲T̲S̲) and the MSP (D̲S̲R̲) is ready to
operate.
If the optolink fails during transmission this is indicated
by C̲T̲S̲ going …08…OFF…08…. Detecting this the LTUX-S must stop
transmitting data. The occurrence of C̲T̲S̲ …08…OFF…08… and R̲T̲S̲
…08…ON…08… shall be interpreted as an error condition and reported
accordingly.
D̲S̲R̲ going …08…OFF…08… is caused by:
1) Link error outside the optolink
2) Flowcontrol activated by the MSP
3) MSP power off
As seen from this D̲S̲R̲ going …08…OFF…08… provides no exact errorinformation.
A software timer would in most of the cases separate
condition 2 from 1 and 3 which are error conditions
to be reported.
Error conditions 1 and 3 are separated as follows:
Cond. 1 Cond. 3
D̲S̲R̲ …08…OFF…08… …08…OFF…08…
C̲T̲S̲ …08…ON…08… …08…OFF…08…
The following statements are valid for the current
issue of the MSP:
The MSP exercises flowcontrol via D̲S̲R̲ (MSP circuit
D̲T̲R̲). Whenever the free inputbuffer space is below
10 characters the D̲S̲R̲ is turned …08…OFF…08…. When the free
inputbuffer space is above 20% of buffer capacity
D̲S̲R̲ is turned …08…ON…08… again.
If the MSP detects a …08…paper out…08… condition, a status
message is transmitted to the LTUX-S. Printing
is stopped and when the bufferoverflow described
above arises D̲S̲R̲ is turned …08…OFF…08…. The combination
of D̲S̲R̲ …08…OFF…08… and the …08…paper out…08… status message enables
the LTUX-S to detect that D̲S̲R̲ is …08…OFF…08… due to MSP
…08…paper out…08… and report accordingly.
The status message format is described in TRACOR
document number T-81-AU-9835-U …08…Status Signal Specification
for Christian Rovsing Program…08….
Fig. 2.2-1
L̲T̲U̲X̲-̲S̲/̲M̲S̲P̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
2.3 L̲T̲U̲X̲-̲S̲ ̲T̲O̲ ̲O̲C̲R̲
This interfacetype requires the following V24 circuits
(ref. fig. 2.3-1):
102 : Signal ground
103 : Transmitted data (TXD)
104 : Received data (RXD)
105 : Request To Send (RTS)
106 : Clear To Send (CTS)
107 : Data Set Ready (DSR)
108.2: Data Terminal Ready (DTR)
N̲o̲t̲e̲:̲ ̲A̲l̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲c̲i̲r̲c̲u̲i̲t̲s̲ ̲a̲r̲e̲ ̲d̲e̲s̲c̲r̲i̲b̲e̲d̲ ̲a̲s̲ ̲s̲e̲e̲n̲
̲f̲r̲o̲m̲ t̲h̲e̲ ̲L̲T̲U̲X̲-̲S̲ ̲u̲n̲l̲e̲s̲s̲ ̲o̲t̲h̲e̲r̲w̲i̲s̲e̲ ̲i̲n̲d̲i̲c̲a̲t̲e̲d̲.̲
The LTUX-S turns …08…ON…08… D̲T̲R̲ and R̲T̲S̲ whenever it is ready
to operate.
As long as D̲S̲R̲ (activated by the OCR) is …08…OFF…08… no data
must be transmitted on T̲X̲D̲.
If the LTUX-S has data to be transmitted on T̲X̲D̲ it
must for each character to be transmitted verify that
both D̲S̲R̲ and C̲T̲S̲ is …08…ON. This indicates that both the
link to the OCR (C̲T̲S̲) and the OCR (D̲S̲R̲) is ready to
operate. The link verified doesn…08…t go beyond the V28(L/L)
adapter, meaning that the C̲T̲S̲ is generated by a loop
in the V28(L/L) adapter based on R̲T̲S̲.
If the link fails during transmission this is indicated
by C̲T̲S̲ going …08…OFF…08…. Detecting this the LTUX-S must stop
transmitting data. The occurrence of C̲T̲S̲ …08…OFF…08… and R̲T̲S̲
…08…ON…08… shall be interpreted as an error condition and reported
accordingly.
D̲S̲R̲ going …08…OFF…08… is caused by:
1) Link error outside the L/L adapter
2) OCR power off
This condition shall be interpreted as an error and
reported accordingly.
The LTUX-S can, if necessary, stop dataflow from the
OCR by turning R̲T̲S̲ …08…OFF…08….
Fig. 2.3-1
L̲T̲U̲X̲-̲S̲/̲O̲C̲R̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
2.4 L̲T̲U̲X̲-̲S̲ ̲T̲O̲ ̲P̲T̲P̲/̲P̲T̲R̲
2.4.1 E̲L̲E̲C̲T̲R̲I̲C̲A̲L̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
This interfacetype requires the following V24 circuits
(ref. fig. 2.3-1):
102 : Signal ground
103 : Transmitted data (TXD)
104 : Received data (RXD)
105 : Request To Send (RTS)
106 : Clear To Send (CTS)
107 : Data Set Ready (DSR)
108.2: Data Terminal Ready (DTR)
N̲o̲t̲e̲:̲ ̲A̲l̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲c̲i̲r̲c̲u̲i̲t̲s̲ ̲a̲r̲e̲ ̲d̲e̲s̲c̲r̲i̲b̲e̲d̲ ̲a̲s̲ ̲s̲e̲e̲n̲
̲f̲r̲o̲m̲ t̲h̲e̲ ̲L̲T̲U̲X̲-̲S̲ ̲u̲n̲l̲e̲s̲s̲ ̲o̲t̲h̲e̲r̲w̲i̲s̲e̲ ̲i̲n̲d̲i̲c̲a̲t̲e̲d̲.̲
The LTUX-S turns …08…ON…08… D̲T̲R̲ and R̲T̲S̲ whenever it is ready
to operate.
As long as D̲S̲R̲ (activated by the PTP/PTR) is …08…OFF…08… no
data must be transmitted on T̲X̲D̲.
If the LTUX-S has data to be transmitted on T̲X̲D̲ it
must for each character to be transmitted verify that
both D̲S̲R̲ and C̲T̲S̲ is …08…ON. This indicates that both the
link to the PTP/PTR (C̲T̲S̲) and the PTP/PTR (D̲S̲R̲) is
ready to operate. The link verified doesn…08…t go beyond
the V28(L/L) adapter, meaning that the C̲T̲S̲ is generated
by a loop in the V28(L/L) adapter based on R̲T̲S̲.
If the R̲T̲S̲-C̲T̲S̲ link fails during transmission this
is indicated by C̲T̲S̲ going …08…OFF…08…. Detecting this the LTUX-S
must stop transmitting data. The occurrence of C̲T̲S̲
…08…OFF…08… and R̲T̲S̲ …08…ON…08… shall be interpreted as an error condition
and reported accordingly.
D̲S̲R̲ going …08…OFF…08… is caused by:
1) Link error outside the L/L adapter.
2) Flowcontrol activated by the PTP/PTR.
3) PTP/PTR power off.
4) PTP/PTR front door opened.
As seen from this D̲S̲R̲ going …08…OFF…08… provides no exact errorinformation.
A software timer would in most of the cases separate
condition 2 from 1, 3 and 4 which are special conditions
to be reported.
The PTP/PTR exercises flowcontrol via D̲S̲R̲ (PTP/PTR
circuit D̲T̲R̲). Whenever the PTP is not ready to punch
D̲S̲R̲ is turned …08…OFF…08….
2.4.2 D̲A̲T̲A̲ ̲T̲R̲A̲N̲S̲F̲E̲R̲
Data is exchanged between the LTUX-S and CR80 in ASCII
(ITA no. 5) 7 bit format.
If the PTP/PTR requires 7 bit ASCII code no conversion
of data will be necessary, and data from/to CR80 to/from
the PTP/PTR are forwarded unchanged.
On the other hand if the PTP requires 5 bit Baudot
code (ITA no. 2) ASCII characters from CR80 to the
PTP/PTR has to be converted to Baudot characters and
Baudot characters received from the PTR has to be converted
to ASCII 7 bit before transmitted to CR80 (Note that
it is necessary to outmask bits 6 and 7 when receiving
Baudot coded messages from the PTR because the USART
still operates in 7 bit, even parity mode).
Conversion is performed according to table 2.4.2-1
which shows the ASCII characters and their Baudot binary
equivalent.
As shown in the table each Baudot binary character
has to possible ASCII translations (with the exception
of: Carriage return (#02), Line feed (#08) and Space
(#04)). The left ASCII column is used if the last executed
(received/transmitted) controlcode was a 'Lettershift'
(#1F), and the right column is used if the last executed
controlcode was a 'Figureshift' (#1B).
Fig. 2.4-1
L̲T̲U̲X̲-̲S̲/̲P̲T̲P̲-̲P̲T̲R̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
E.g:
1) The ASCII string 'ABC0123' (#41 #42 #43 #30 #31
#32 #33) is converted to Baudot 5 bit code as follows
(refer to table 2.4.2-1):
#1F ('Lettershift') #18 #13 #0E #1B ('Figureshift')
#0D #1D #19 #10
2) The Baudot coded string #18 #13 #0E #1B ('Figureshift')
#0D #1D #19 #10 is converted to ASCII as follows
(since no controlcode preceedes the string it has
two possible ASCII conversions, refer to table
2.4.2-1):
a) '-?:0123' if the latest executed controlcode
prior to reception/transmission of the string
was a 'Figureshift'.
b) 'ABC0123' if the latest executed controlcode
prior to reception/transmission of the string
was a 'Lettershift'.
Example 2 shows the necessity of keeping track with
the controlcodes executed.
Practical hints:
To get the punch mechanism 'up to speed' 32 'nul' characters
shall preceede any message transmitted to the PTP.
Each complete message transmitted to the PTP shall
be terminated with 145 'nul' characters to bring all
punched paper out of the punch mechanism.
Baudot ASCII Character allocation
̲elements ̲L̲e̲t̲t̲e̲r̲s̲ ̲F̲i̲g̲u̲r̲e̲s̲
MSB LSB
1 1 0 0 0 A -
1 0 0 1 1 B ?
0 1 1 1 0 C :
1 0 0 1 0 D WRU
1 0 0 0 0 E 3
1 0 1 1 0 F
0 1 0 1 1 G
0 0 1 0 1 H Note
0 1 1 0 0 I 8
1 1 0 1 0 J BELL
1 1 1 1 0 K (
0 1 0 0 1 L )
0 0 1 1 1 M .
0 0 1 1 0 N ,
0 0 0 1 1 O 9
0 1 1 0 1 P 0
1 1 1 0 1 Q 1
0 1 0 1 0 R 4
1 0 1 0 0 S '
0 0 0 0 1 T 5
1 1 1 0 0 U 7
0 1 1 1 1 V =
1 1 0 0 1 W 2
1 0 1 1 1 X /
1 0 1 0 1 Y 6
1 0 0 0 1 Z +
0 0 0 1 0 Carriage return
0 1 0 0 0 Line feed
1 1 1 1 1 Lettershift
1 1 0 1 1 Figureshift
0 0 1 0 0 Space
0 0 0 0 0 Not used
Note: On NATO keyboards, ITA no. 2 character #05 is
used as part of the end of message validation function,
if required.
Table 2.4.2-1
B̲a̲u̲d̲o̲t̲/̲A̲S̲C̲I̲I̲ ̲c̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲t̲a̲b̲l̲e̲
2.5 L̲T̲U̲X̲-̲S̲ ̲T̲O̲ ̲T̲R̲C̲/̲P̲O̲I̲N̲T̲-̲T̲O̲-̲P̲O̲I̲N̲T̲
This interfacetype requires the following V24 circuits
(ref. fig. 2.5-1):
102 : Signal ground
103 : Transmitted data (TXD)
104 : Received data (RXD)
107 : Data Set Ready (DSR)
108.2: Data Terminal Ready (DTR)
N̲o̲t̲e̲:̲ ̲A̲l̲l̲ ̲s̲i̲g̲n̲a̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲s̲ ̲a̲r̲e̲ ̲d̲e̲s̲c̲r̲i̲b̲e̲d̲ ̲a̲s̲ ̲s̲e̲e̲n̲ ̲f̲r̲o̲m̲
t̲h̲e̲ ̲L̲T̲U̲X̲-̲S̲ ̲u̲n̲l̲e̲s̲s̲ ̲o̲t̲h̲e̲r̲w̲i̲s̲e̲ ̲i̲n̲d̲i̲c̲a̲t̲e̲d̲.̲
The LTUX-S turns …08…ON…08… D̲T̲R̲ whenever it is ready to operate.
As long as D̲S̲R̲ (activated by the TRC or POINT-TO-POINT)
is …08…OFF…08… no data must be transmitted on T̲X̲D̲.
D̲S̲R̲ going …08…OFF…08… is caused by:
1) Link error
2) TRC/POINT-TO-POINT power off
These conditions shall be interpreted as errors (1
and 2 can…08…t be separated directly) and reported accordingly.
Fig. 2.5-1
L̲T̲U̲X̲-̲S̲/̲T̲R̲C̲-̲P̲O̲I̲N̲T̲-̲T̲O̲-̲P̲O̲I̲N̲T̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
2.6 L̲T̲U̲X̲-̲S̲ ̲T̲O̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲A̲L̲ ̲M̲U̲X̲.̲ ̲1̲
In this configuration the Statistical Multiplexer and
the LTUX-S are placed together within the CAMPS enclosure,
or within a stand alone rack enclosure.
This interfacetype requires the following V24 circuits
(ref. fig. 2.6-1):
102 : Signal ground
103 : Transmitted data (TXD)
104 : Received data (RXD)
105 : Request To Send (RTS)
106 : Clear To Send (CTS)
107 : Data Set Ready (DSR)
108.2: Data Terminal Ready (DTR)
N̲o̲t̲e̲:̲ ̲A̲l̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲c̲i̲r̲c̲u̲i̲t̲s̲ ̲a̲r̲e̲ ̲d̲e̲s̲c̲r̲i̲b̲e̲d̲ ̲a̲s̲ ̲s̲e̲e̲n̲
̲f̲r̲o̲m̲ t̲h̲e̲ ̲L̲T̲U̲X̲-̲S̲ ̲u̲n̲l̲e̲s̲s̲ ̲o̲t̲h̲e̲r̲w̲i̲s̲e̲ ̲i̲n̲d̲i̲c̲a̲t̲e̲d̲.̲
The LTUX-S turns …08…ON…08… D̲T̲R̲ and R̲T̲S̲ whenever it is ready
to operate.
As long as D̲S̲R̲ (activated by the Statistical Mux./remote
terminal) is …08…OFF…08… no data must be transmitted on T̲X̲D̲.
When the LTUX-S has data to be transmitted on T̲X̲D̲ it
shall for each character to be transmitted verify that
both D̲S̲R̲ and C̲T̲S̲ is …08…ON…08…. This indicates that:
1: the link to the remote terminal is ready to
operate (C̲T̲S̲),
2: bufferspace is available in the main site Statistical
Mux. (less than 80% of the allocated bufferspace
is occupied (C̲T̲S̲)) and
3: the remote terminal is ready to operate (D̲S̲R̲)
If either 1 or 2 fails during transmission this is
indicated by C̲T̲S̲ going …08…OFF…08…. Detecting this the LTUX-S
must stop transmitting data, and either wait for C̲T̲S̲
to go …08…ON…08… again, or report a link error. Separation
between the normal flowcontrol (2) and the link error
indication (1) can be solved via a software timer in
most of the cases.
D̲S̲R̲ going …08…OFF…08… is caused by:
4) Statistical Mux. (main site) power off
5) Flowcontrol activated by the remote terminal
6) Remote terminal power off
As seen from this D̲S̲R̲ going …08…OFF…08… provides no exact errorinformation.
A software timer would in most of the cases separate
condition 5 from 4 and 6 which are error conditions
to be reported.
Error conditions 4 and 6 are separated as follows:
Cond. 4 Cond. 6
D̲S̲R̲ …08…OFF…08… …08…OFF…08…
C̲T̲S̲ …08…OFF…08… …08…ON…08…
Fig. 2.6-1
L̲T̲U̲X̲-̲S̲/̲S̲T̲A̲T̲.̲ ̲M̲U̲X̲.̲ ̲1̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
2.7 L̲T̲U̲X̲-̲S̲ ̲T̲O̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲A̲L̲ ̲M̲U̲X̲.̲ ̲2̲
In this configuration the Statistical Multiplexer is
placed within a stand alone rack enclosure, while the
LTUX-S is placed within the CAMPS rack enclosure.
This interfacetype requires the following V24 circuits
(ref. fig. 2.7-1):
102 : Signal ground
103 : Transmitted data (TXD)
104 : Received data (RXD)
105 : Request To Send (RTS)
106 : Clear To Send (CTS)
107 : Data Set Ready (DSR)
108.2: Data Terminal Ready (DTR)
N̲o̲t̲e̲:̲ ̲A̲l̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲c̲i̲r̲c̲u̲i̲t̲s̲ ̲a̲r̲e̲ ̲d̲e̲s̲c̲r̲i̲b̲e̲d̲ ̲a̲s̲ ̲s̲e̲e̲n̲
̲f̲r̲o̲m̲ t̲h̲e̲ ̲L̲T̲U̲X̲-̲S̲ ̲u̲n̲l̲e̲s̲s̲ ̲o̲t̲h̲e̲r̲w̲i̲s̲e̲ ̲i̲n̲d̲i̲c̲a̲t̲e̲d̲.̲
The LTUX-S turns …08…ON…08… D̲T̲R̲ and R̲T̲S̲ whenever it is ready
to operate.
As long as D̲S̲R̲ (activated by the Statistical Mux./remote
terminal) is …08…OFF…08… no data must be transmitted on T̲X̲D̲.
When the LTUX-S has data to be transmitted on T̲X̲D̲ it
shall for each character to be transmitted verify that
both D̲S̲R̲ and C̲T̲S̲ is …08…ON…08…. This indicates that:
1: the link to the remote terminal is ready to
operate (C̲T̲S̲),
2: bufferspace is available in the main site Statistical
Mux. (less than 80% of the allocated bufferspace
is occupied (C̲T̲S̲)) and
3: the remote terminal is ready to operate (D̲S̲R̲)
If either 1 or 2 fails during transmission this is
indicated by C̲T̲S̲ going …08…OFF…08…. Detecting this the LTUX-S
must stop transmitting data, and either wait for C̲T̲S̲
to go …08…ON…08… again or report a link error. Separation between
the normal flowcontrol (2) and the link error indication
(1) can be solved via a software timer in most of the
cases.
D̲S̲R̲ going …08…OFF…08… is caused by:
4) Statistical Mux. (main site) power off
5) Flowcontrol activated by the remote terminal
6) Remote terminal power off
7) Link error between LTUX-S and main site Statistical
Mux.
As seen from this D̲S̲R̲ going …08…OFF…08… provides no exact errorinformation.
A software timer could in most of the cases separate
condition 5 from 4, 6 and 7 which are error conditions
to be reported.
Error conditions 4/7 and 6 are separated as follows:
Cond. 4/7 Cond. 6
D̲S̲R̲ …08…OFF…08… …08…OFF…08…
C̲T̲S̲ …08…OFF…08… …08…ON…08…
Conditions 4 and 7 can…08…t be separated directly.
Fig. 2.7-1
L̲T̲U̲X̲-̲S̲/̲S̲T̲A̲T̲.̲ ̲M̲U̲X̲.̲ ̲2̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
3̲ ̲R̲E̲M̲O̲T̲E̲ ̲S̲I̲T̲E̲ ̲C̲O̲N̲N̲E̲C̲T̲I̲O̲N̲S̲
To complete the picture of terminals connected to CAMPS
via LTUX-S channels, the three following figures (fig.
3-1 , 3-2 and 3-3) show how a remote site Stat. Mux.
is hooked up against a VDU/MSP (opto-fig. 3-1 and electric-fig.
3-3) and against an OCR (fig 3-2, reconfiguration option
2).
V24 signal transfer between the Main site Statistical
Mux. and the Remote site Statistical Mux. for one of
the 8 Mux. channels is shown in fig. 3-4. It should
be noted that the Stat. Mux. (Main and Remote) V24
circuit l06 (C̲T̲S̲) is generated based upon both the
…08…other end…08… input X (as shown in fig. 3-4) and the internal
buffer overflow control for the actual channel (the
two signals are AND-ed).
Fig. 3-1
R̲E̲M̲O̲T̲E̲ ̲S̲I̲T̲E̲ ̲S̲T̲A̲T̲.̲ ̲M̲U̲X̲.̲/̲V̲D̲U̲-̲M̲S̲P̲ ̲C̲O̲N̲N̲E̲C̲T̲I̲O̲N̲S̲
Fig. 3-2
R̲E̲M̲O̲T̲E̲ ̲S̲I̲T̲E̲ ̲S̲T̲A̲T̲.̲ ̲M̲U̲X̲.̲/̲O̲C̲R̲ ̲C̲O̲N̲N̲E̲C̲T̲I̲O̲N̲S̲
Fig. 3-3
R̲E̲M̲O̲T̲E̲ ̲S̲I̲T̲E̲ ̲S̲T̲A̲T̲.̲ ̲M̲U̲X̲.̲/̲V̲D̲U̲-̲M̲S̲P̲ ̲(̲E̲L̲E̲C̲T̲R̲I̲C̲)̲ ̲C̲O̲N̲N̲E̲C̲T̲I̲O̲N̲S̲
Fig. 3-4
M̲A̲I̲N̲ ̲S̲I̲T̲E̲ ̲S̲T̲A̲T̲.̲ ̲M̲U̲X̲.̲/̲R̲E̲M̲O̲T̲E̲ ̲S̲I̲T̲E̲ ̲S̲T̲A̲T̲.̲ ̲M̲U̲X̲.̲ ̲C̲O̲N̲N̲E̲C̲T̲I̲O̲N̲S̲.̲
