10.56.5. EB5/NAL signaling 
EB5/NAL signaling is designed for the digital interface between OpenScape
4000 and the two-motion selector system EB5/34 from Deutsche Reichsbahn
(DR).
Loadware variant 5
The loadware with EB5/NAL signaling for the DIUC boards must be configured
on the OpenScape 4000 system hard disk as follows:
-
:PDS:APSP/LTG/LG57/PZFDCAS5 (for DIUC Q2185)
- You can configure the DIUC boards with loadware variant 5 as follows:
DIUC64:
ADD-BCSU:TYPE=DIU,LTG=gg,LTU=uu,SLOT=bbb, PARTNO="Q2185-X",LWVAR=5;
- The loadware variant can be subsequently assigned as follows:
DIUC64 (Q2185):
CHA-ZAND:TYPE=LOADWARE,LWTYPE=DCAS,LWVAR=5; (for DIUC Q2185)
IMPORTANT:
To load the LWVAR, the board with the AMO BSSU must be switched off and on again.
Device EB5NAL
For incoming traffic, the OpenScape 4000 needs to distinguish between
external transit traffic and tie trunk traffic so that a flashing signal
is only sent in the case of incoming external traffic. In the case of
OpenScape 4000 incoming seizure, EB5 signal generation offers no criteria
for distinguishing between the various types of traffic. Therefore, the
traffic must be channeled according to its origin into 2 separate trunk
groups in the EB5 and must also be implemented in this form in the OpenScape
4000. Both trunks can be on the same DIUC. The following example shows
the configuration of EB5/NAL trunk circuits with busy override and flashing.
- You can configure the class of trunk for EB5/NAL trunk circuits as follows:
ADD-COT:COTNO=x,PAR=ANS&USD&OVR&FLAC;
- You can configure the line parameter class for EB5/NAL trunk circuits as follows:
ADD-COP:COPNO=x,PAR=SDL&BR64&NO1A&IDP3&MSG& RLSA&LSUP;
- You can configure the EB5/NAL trunk group for tie trunk traffic (for example
30 circuits) as follows:
ADD-BUEND:TGRP=x,NAME="EB5-CO",NO=30;
- You can configure 30 trunk circuits with EB5/NAL signaling as follows:
ADD-TACSU:NO=30,PEN=gg-uu-bbb-1,COTNO=x,COPNO=x, TGRP=x,DEVTYPE=AS,DEV=EB5NAL;
The following example shows the configuration of EB5/NAL tie trunk circuits with busy override and suffix-dialing (the difference between trunk traffic and tie trunk traffic is determined via the trunk parameter "TIE"). - You can configure the class of trunk for EB5/NAL tie trunk circuits as
follows:
ADD-COT:COTNO=x,PAR=ANS&USD&OVR;
- You can configure the line parameter class for EB5/NAL tie trunk circuits as follows:
ADD-COP:COPNO=x,PAR=SDL&BR64&NO1A&IDP3&MSG& RLSA&LSUP&TIE;
- You can configure the EB5/NAL trunk group for tie trunk traffic (for example
30 circuits) as follows:
ADD-BUEND:TGRP=x,NAME="EB5--TIE",NO=30;
- You can configure 30 tie trunk circuits with EB5/NAL signaling as follows:
ADD-TACSU:NO=30,PEN=gg-uu-bbb-33,COTNO=x,COPNO=x, TGRP=x,DEVTYPE=AS,DEV=EB5NAL;
PTIME init block for device EB5NAL
The initialization data for the device EB5NAL are saved on the hard
disk in init block 41 (see AMO PTIME). The data are loaded automatically
by the AMO TACSU. To change a fixed default value (for example two-way,
incoming), the following steps must be taken:
- Load init timer block 41 from the hard disk into the DB (into TBLK 12,
for example) with:
COPY-PTIME:INIBLOCK=41,TBLK=12;
- You can change the value for the parameter P3 as follows:
CHA-PTIME:TYPE=REST,TBLK=12,BTYPE=PARA,P3=2;
- You can assign the new timer block 12 to all circuits of the trunk group with:
CHA-TACSU:PEN=gg-uu-bbb-ss,DEVTYPE=AS,DEV=EB5NAL, CIRCIDX=12;
IMPORTANT:
To load the new parameters, all relevant circuits with AMO DSSU must be switched off and on again. You can also selectively assign the changed timer block when configuring the circuits.