ad1oe<OEDAS-PROD-2.

20-SP3>#spsy|/home/spsy> cd /home/s/src/param/ui_supply/config/
/home/s/src/param/ui_supply/config
ad1oe<OEDAS-PROD-2.20-SP3>#spsy|config> ls
L2 cnsd ethernetmodem.prop gsm.properties
lssd_config serialmodem.prop stmv vald
L2_nco consolemodem.properties fotm hopf medi
sms uipcoi vaop
acop dsBase_config fotm_text lampcheck* notesd
smsgw ulsd_config
agcsd_config dsBase_gdw/ gong lidi
oplsd_config* spmsd_config vadi
ad1oe<OEDAS-PROD-2.20-SP3>#spsy|config> vi gong
ad1oe<OEDAS-PROD-2.20-SP3>#spsy|config> cat gong

/* SPECTRUM: CONF
* Copyright (C) Siemens AG 1992-2016 All Rights Reserved.Confidential
* GONG configuration
*
* $NewRev$
* 220111 Muhsin KCETAS Gong Settings for MeCl15 and MeCl21
* 171226 Hakan KCETAS Gong Settings for MeCl13 and MeCl14
* 171128 Hakan KCETAS Gong Settings has reconfigured only for MeCl1 and MeCl2
* 161007 Mayh sp7-scada_v02.10_fu_ems00078190_gong_timer_vie
* 150717 Mayh sp7-scada_v01.30_df_ems00063916_gong_sp4_features_vie
* 140127 Mayh bf-ui_4_gongExtensions_47
* - MessageForAllGongs added
* - CentralGongMessage added
* 140115 Mayh bf-ui_GongMessageForAllGongs_47
* MessageForAllGongs added
* 130712 Mayh bf-ui_44901_gong_AutoEnableByTimer_47:
* config parameters added
* 100416 Mayh: ad-gong_AutoEnableByTimer_46: add gong messages
* 100324 Mayh: ad-gong_AutoEnableByTimer_46: redesign 'AutoEnable'
* gong status message (enabled/disabled)
* 100217 spc: SchG: APG_Upgrade: reset 'disable gong' keys by timer
* 131128 Mayh sp7-scada_v01.10_df_ems00046687_gong_odv_vie
* 121010 Mayh bf-ui_42008_gong_config_47: config comments added
* 120112 Mayh: bof-scada_v01.00_fu_ems562_cuman_vie
* cGong_App,cGong_Dis extende (cMaxMeCl 31)
* 080602 Mayh: feat-SpecUI_CR09_xt_gong: XT gong processing
* 071003 Mayh: bf-ui_38885_gongHeavyLoad_corr01_45:
* cHeavyLoadLimit removed
* 070912 Mayh: bf-ui_38885_gongHeavyLoad_45: heavy load processing
* cHeavyLoadLimit, cHeavyLoadCycle defined
* 070712 oppe : spr-38548 : non periodic gongs have to be lower prior
* 070329 oppe : spr-38070 : Disabled gong status signalized incorrectly
* 070306 kien - bf-globdev_spr37989_remo_mip_45 :
* remove obsolete program mip
* set parameter external_gong to false to prevent
* sbtransmit of program gong to program mip
* $NewRevEnd$
*
*/

/*
 Gong output selection ds ul
===================== -

General: The gong parameters are independent gong selections, which

------- can be combined. It is possible to use:
- central gong
- decentral gong
- external gong
in parallel.
*/

/* Central gong -> output via common loudspeaker on RT server */

central_gong false

/*
* Decentral gong configuration
*
* XT_DefaultGroup: Default XT Group, all not assigned XTs will
* set to XT_DefaultGroup number.
*
* XT_GroupDef1-20: First Parameter = XTGroup (1-cMaxXTGroup)
* + list of XT numbers (XIDs) which will be
* assigned to group
*
* decentral_gong: For each XT group the gong processing will
* enabled (=true) or disabled (=false)
* This parameter reflect to all assigned XIDs,
* this means XIDs where no gong processing should
* be done (e.g. admistrator XTs, ..) should be
* assigned to a disabled XT-Group.
*
* each_XT: The gong output will be done on each XT (=true)
* of group or only on the first XT (=false),
* fist XT = lowest XT number.
*
* NOTE: each_XT == true:
* The gong processing will be done individually
* for each assigned XID. All activities (enable
* /disable/stop) will impact on each XT
* according permissions (TeAr/MeCl).
*
* each_XT == false: The gong processing will be
* done for the group. The gong output will be
* done on the first XT (=lowest XID number) which
* represents the highest gong of all assigned
* XTs. User actions (enable/disable/stop) will
* will impact on all XTs the group.
*/

XT_DefaultGroup 1

/* XTGrp --------- XTs ---------- */

XT_GroupDef1 1 0 0 0 0 0 0 0 0 0 0
XT_GroupDef2 2 72 75 87 0 0 0 0 0 0 0
XT_GroupDef3 2 0 0 0 0 0 0 0 0 0 0
XT_GroupDef4 2 0 0 0 0 0 0 0 0 0 0
XT_GroupDef5 3 0 0 0 0 0 0 0 0 0 0
XT_GroupDef6 3 0 0 0 0 0 0 0 0 0 0
XT_GroupDef7 4 0 0 0 0 0 0 0 0 0 0
XT_GroupDef8 5 0 0 0 0 0 0 0 0 0 0
XT_GroupDef9 5 0 0 0 0 0 0 0 0 0 0
XT_GroupDef10 5 0 0 0 0 0 0 0 0 0 0
XT_GroupDef11 6 0 0 0 0 0 0 0 0 0 0
XT_GroupDef12 6 0 0 0 0 0 0 0 0 0 0
XT_GroupDef13 6 0 0 0 0 0 0 0 0 0 0
XT_GroupDef14 7 0 0 0 0 0 0 0 0 0 0
XT_GroupDef15 7 0 0 0 0 0 0 0 0 0 0
XT_GroupDef16 7 0 0 0 0 0 0 0 0 0 0
XT_GroupDef17 7 0 0 0 0 0 0 0 0 0 0
XT_GroupDef18 8 0 0 0 0 0 0 0 0 0 0
XT_GroupDef19 8 0 0 0 0 0 0 0 0 0 0
XT_GroupDef20 8 0 0 0 0 0 0 0 0 0 0

/* XT group 1 2 3 4 5 6 7 8 */
/* Parameters ------------------------------------------------ */
decentral_gong true true true true true true true true
each_XT true true false false false false false false

/* !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!*/
/* ATTENTION : program mip - output via horn on mimic board obsolete !*/
/* see Defect 37989 */
/* !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!*/
/* External gong? -> output via horn on mimic board */
/* SIMATIC number 1 2 3 4 5 6 */
external_gong false false false false false false
fleeter_timeout 3 /* mimic board fleeter timout [s] */

/* Configuration of gongs (sounds)

----------------------
Configure 'cMaxGong' gongs (standard system provides 4 gongs)

How to add new gongs:

- set cMaxGong
- store new audio files on $SPECPATH/tone/TONE
- edit: ./param/base/odb/fillrel/tone.j
- execute tone.j.
NOTE: tone.j conaines the LOFI option, in this case the
audio sequence will be loaded binary to relation TONE.
- assign new gongs in this configuration.
*/

/* Gong step adjustments */

Key1 9 /* selector 1 for relation 'Tone' */
Key2 1 /* selector 2 for relation 'Tone' */

/* Key3........selector 3 for relation 'Tone'; selects gong sample

Volume .....gong step volume [-1..100]
Period[s]...gong step period (intervall); pause between active
gong sample.
'0'...no cyclic gong; output just for one time
all non cyclic gongs must have lower priority
than all cyclic gongs
GongKeyNo key number which enable/disable gong
GongInfo info number for gong messages
Set: SendXTGongMessage true
GongInfo = 0, no gong message will be sent
GongInfo can also be combined, if all gongs
have the same info, the message will be set
 if one of the assigned gong is active
TA:/SystemB1/SystemB2_Terms/XID
/GongMessageElem/GongInfo

Example-1: info for each gong

GongInfo 86 87 88 90
Example-2: two gongs share one info
GongInfo 86 86 88 88
Example-3: one info for all gongs
GongInfo 86 86 86 86

GongStatusInfo info number for display of enabled/disabled gong

status. A disabled gong will be sent with status
- disabled gong -> status on
- enabled gong -> status off
Several gongs can be assigned to one message
or one info for each gong.
Set: SendXTGongMessage true
GongStatusInfo == 0, no gong status message
TA:/SystemB1/SystemB2_Terms/XID
/GongMessageElem/GongStatusInfo
NOTE: only used gong status messages (assigned in
cGong_App/cGong_Dis) will be sent.

Example-1: info for each gong

GongStatusInfo 91 92 93 94
Example-2: two gongs share one info
GongStatusInfo 91 91 93 93
Example-3: one info for all gongs
GongStatusInfo 91 91 91 91
NOTE: on standard system only info 91
is configured in NIM

/* Gong steps > 1 2 3 4 */

/* \/ Parameters --------------------*/
Key3 1 2 3 4
Volume 70 60 70 70
Period 0 20 15 15
GongKeyNo 2 2 2 2
GongInfo 0 0 0 0
GongStatusInfo 0 0 0 0

/* Message classes > */

/* 10 12 14 16 18 20 22 24 26 28 30 */
/* 1 2 3 4 5 6 7 8 9 11 13 15 17 19 21 23 25 27 29 31*/
/* \/ ---------------------------------------------------------------*/
/* Gong steps */
cGong_App 0 0 0 0 0 0 0 0 0 0 0 0 3 3 1 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0
cGong_Dis 0 0 0 0 0 0 0 0 0 0 0 0 3 3 1 0 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0

SendXTGongMessage false /* send XTerm gong messages */

SendXTGongStatusMsg false /* send XTerm status messages */

/*
* Element number for all kind of gong messages
* - XT specific: gong message, gong status message
* - Central gong message
* - GongMessageElem == 0 -> means no messages at all
*/
GongMessageElem 10 /* LogOnEl element (0 no messages) */

/*
* Send a GongMessage for for active or all gongs
* false: GongMessage only for active gong will be send
* true : GongMessage for all currently available gongs will be sent
* e.g. currently messages for Gong 1,2,3 are unacknowleged
* - Sound for Gong 3 is triggered
* - GongMessages for 1,2,3 will be sent to mepr
* NOTE: it's implemented only for decentral gong
* NOTE: if there is no GongInfo configured or if either Element or
* infos are not availalbe in NIM, this parameter is irrelevant
*/
MessageForAllGongs false

/*
* Central gong message config parameter
* All currently active central (system) gongs may be sent by a gong
* message.
* TA is specified by:
* - CentralGongMsgB1/B2/B3/GongMessageElem/GongInfo
* GongInfo may be combined (e.g. 1+2->Info 86, 3->Info 87)
*
* Properties:
* - TA need to be valid for messages
* (e.g. CentralGongMsgB1 == 0 or GongMessageElem == 0) no message
* - SendCentralGongMsg need to be 'true'
* - technological permission (TeAr/MeCl) is NOT considered
* even if there is no XT logged in, central messages are triggerd
* - 'Disable' or 'Stop Gong' is NOT considerd
*
*/
CentralGongMsgB1 0 /* SYSTEM 1 */
CentralGongMsgB2 0 /* X-Terms 14 */
CentralGongMsgB3 0 /* X001 1 */

SendCentralGongMsg false /* send central gong messages */

/*
* Non Periodic gongs - general rules / remarks
*
* - all non periodic gongs NEED to be lowest priority, this means
* all non periodic gong numbers need to be lower than the first
* periodic gong (checked at runup with error message).
*
* - non periodic gongs will be sent only once (exactly when it
* happens). Afterwards the event counter will deleted in internal
* administration. This means, if an XT will be connected a non
* periodic gong will not be triggerd again even if the event is still
* not acknowledged (Alternative: periodic gong with greater period).
*
* - NonPeriodicRepeat > 0 [sec]:
* I may happen, that non periodic gongs will be triggered several
* times if many events (leading to a non periodic gong) will be
* received (e.g. GI). For this case it is possible to set a
* NonPeriodicRepeat > 0. This means: The same non periodic gong
* will not be triggerd if it has been triggered within the previous
* (NonPeriodicRepeat) seconds.
*
 * Recommendation
* --------------
* Try to avoid non-periodic gongs. For lower priority alarms it is
* a better way to configure a periodic gong with greater period.
* Due to the gong repeat of peroidic gongs, it may not be faild to
* hear by dispatchers.
*/
NonPeriodicRepeat 2

/* All gongs disabled at runup - gong key status in BaSiDi */

KeysAllDisabled true

/* heavy load parameter

*
* cHeavyLoadCycle defines the cycle [sec] of gong processing / output
* if not all softbus requests can be processed
* softbus orders sagong > 0 - during heavy load)
*/
cHeavyLoadCycle 10

/* configuration for deactivation of gong steps - StopGong*/

/* see constants ./ui_supply/DEF/dicgong.h */
/* cStopExtGong 4, cStopCentGong 2, cStopDecGong 1 */
/* combinations possible */
cGong_Stop 7

/* reset 'disable gong' to enable gong after configurable */

/* time - either fixed in minutes or at time received by */
/* ODV */
/* Priority: */
/* 1.) ResetDisableKeyMin > 0: configured minutes will be */
/* used (highest prio), received ODV time will be */
/* ignored. */
/* 2.) ResetDisableKeyMin == 0, */
/* MinOdvDisableKeySec > 0, MaxOdvDisableKeySec > 0 */
/* received odv time (when key has to be enabled) is */
/* checked if it's within configured min/max range - */
/* gong keys will be enabled at this time. */
/* if received time is out of range the time will be */
/* set either to MinOdvDisableKeySec or to */
/* MaxOdvDisableKeySec. */
/* NOTE: hardcoded MinOdvDisableKeySec: 10 sec */
/* MaxOdvDisableKeySec: 21600 sec (6h)*/
/* */
/* NOTE if automatic reset is used allDisabled will by set*/
/* to false anyway - at runup all gongs are enabled */
ResetDisableKeyMin 0 /* default value [min] */
MinOdvDisableKeySec 0 /* minimum disable [sec] */
MaxOdvDisableKeySec 0 /* maximum disable [sec] */