Actions

Difference between revisions of "PrisCom station - Configuration"

From Zenitel Wiki

(About Scream Alarm)
(Upload configuration to the AlphaCom)
Line 62: Line 62:
 
Note that every time a new Prison Station is added to the system, the above procedure should be used (SendAll, 2 x reset, GetAll).  
 
Note that every time a new Prison Station is added to the system, the above procedure should be used (SendAll, 2 x reset, GetAll).  
  
The dual reset procedure is only required after adding new PrisCom stations to the system. The first reset will trigger the "Faulty Line OFF" event. This event will automatically program the DAK keys and enable the "Two Tone DAK signalling", and it will send configuration data to the Prison Stations. The second reset is to make the changes take effect. The GetAll is required for AlphaPro to reflect the actual configuration in the exchange.
+
The dual reset procedure is only required after adding new PrisCom stations to the system. The first reset will trigger the "Faulty Line OFF" event. This event will automatically program the DAK keys and enable the "Two Tone DAK signalling", and it will send configuration data to the Prison Stations. The second reset is to make the changes take effect. At this stage the AlphaCom configuration is different from the AlphaPro. The GetAll is required for AlphaPro to reflect the actual configuration in the exchange.
  
 
== Description of the PrisCom database ==
 
== Description of the PrisCom database ==

Revision as of 10:35, 13 December 2012

100 7061 000 station
100 7063 000 station

This article describes how to configure the PrisCom stations 1007061000 and 1007063000.

Software requirements

  • AMC software v.9.09 or later
  • AlphaPro 9.21 or later


Decide the configuration starting point

The station properties are programmed from AlphaPro. One can either start with a new AlphaPro database, or one can use a preconfigured AlphaPro database, which includes all neccessary event handler programming for advanced features of the PrisCom stations.

Basic features: Start with a new AlphaPro database and fill in all parameters from scratch.

"Basic features" are:

  • Call Button
  • Program Step button (without displaying selected channel)


Advanced features: When using the advanced features of the station, it is highly recommended to use a preconfigured AlphaPro database as a starting point. The advanced features is depending on Event Handler programming, and a lot of work is saved by using an already preconfigured database.

"Advanced features" includes support for:

  • Light button
  • External key switch
  • Corridor lamp and/or group lamp
  • Display for selected program channel
  • Tamper alarm and Power failure
  • Scream alarm
  • AlphaVision

Basic feature programming

The 7061 and 7063 uses “Two tone DAK signaling", not regular DAK signaling 

  • In Users & Stations -> User Preferences set DAK signaling to "(3) Two tone signaling w/ack“
  • In Users & Stations -> DAK assign numbers to the panel buttons: 
    • DAK 2 = Call button, normally configured to "I 623 I xxx", where xxx is the number of the Guard Station
    • DAK 3 = Program Step button, normally configured to "I 790" (button not available on the 100 7061 000)

Advanced feature programming

Download the PrisCom database from the download site. Copy the PrisCom database to the AlphaPro Database folder. Start AlphaPro and select the PrisCom database.

Guard station configuration

  • In Users & Stations -> UDP, include the station in UDP 1
  • In Users & Stations -> Group, include the station in a “Guard group”. This is required even with a single guard station

Prison station configuration

  • In Users & Stations -> UDP, include the station in UDP 2
  • In Users & Stations -> UDP, enter the “Guard group” index number in the Used Defined Parameter field. This is the target for calls from this station.

Notes on DAK programming:

  • No DAK programming is required
  • The event handler programming in the PrisCom database will automatically set “Two tone DAK signaling”, and program the DAK’s to point to physical station 500 and 501
  • Physical station 500 and 501 are preconfigured with PrisCom Station DAK keys

Also note that only Prison Stations model 1007061000 or 1007063000 should be in UDP 2. If there are other types of prison stations in the system, they should not be in UDP 2.

Upload configuration to the AlphaCom

  • After the PrisCom stations are connected to the AlphaCom, upload the configuration to the AlphaCom by selecting “SendAll” from AlphaPro
  • When the upload is finished, reset the AlphaCom. When the exchange is up and running, reset once more
  • Now do a “GetAll” to update AlphaPro with the correct settings

Note that every time a new Prison Station is added to the system, the above procedure should be used (SendAll, 2 x reset, GetAll).

The dual reset procedure is only required after adding new PrisCom stations to the system. The first reset will trigger the "Faulty Line OFF" event. This event will automatically program the DAK keys and enable the "Two Tone DAK signalling", and it will send configuration data to the Prison Stations. The second reset is to make the changes take effect. At this stage the AlphaCom configuration is different from the AlphaPro. The GetAll is required for AlphaPro to reflect the actual configuration in the exchange.

Description of the PrisCom database

The Prison Stations 7061 and 7063 are mainly operating by sending a "Two tone" DAK digits to the exchange for input events, and receiving display data messages in response. These Prison Stations are the only stations types which are using the "double-tone" DAK signalling. The event handler programming in the PrisCom database will automatically set the Prison stations to use “Two tone DAK signaling”.

Display messages are used to e.g. turn lamps on, set alarm preparation mode during guard presence, or control other features. These messages are mostly defined as commands in the AlphaCom event handler. To change functionality one will have to change these commands or add/remove/change events.

DAK Keys on physical numbers 500 and 501

The Priscom stations have common DAK key programming. The DAK configuration is programmed on physical number 500 and 501, and the event handler programming in the PrisCom database will upon reset cause the AlphaCom to automatically program the DAK’s of the Prison Stations to point to these physical numbers 500 and 501. The DAK table of the physical numbers 500 and 501 are preconfigured according to the table below.

DAK keys 1-10 is from physical number 500, and DAK key 11-20 is from physical number 501.

PrisCom station connectors
DAK key DAK string Description
1 E 9558 Panelkey 1: Light button
2 M I 9550 Panelkey 2: Call Request / "Answer" on incoming calls
3 I 790 Panelkey 3: Program button
4 E 9551 Panelkeys in alarm mode: Alarm call
5 E 9552 Tamper switch
6 E 9553 IN KEY1 (Guard Keyswitch 1)
7 E 9554 IN KEY2 (Guard Keyswitch 2)
8 E 9555 Guard Keyswitch Reset
9 E 9556 Power fail
10 E 9557 Power OK
11 IN1 ON (Input 1): (Set as default alarm input during guard presence by display command 0x63. See below)
12 M I 9550 IN1 OFF (Input 1): External Call Request / "Answer" on incoming calls
13 IN2 ON (Input 2)
14 IN2 OFF (Input 2)
15 IN3 ON (Input 3)
16 IN3 OFF (Input 3)
17 IN4 ON (Input 4)
18 IN4 OFF (Input 4)
19 E 9561 Scream detector
20

IND Commands used by Prison Stations

The outputs on the Prison Stations are controlled by IND commands executed in the event handler. There are eight outputs:

IND output Description Comment
1 L1 - Output 1 Red lamp (Call)
2 L2 - Output 2 Green lamp (Present)
3 L3 - Output 3 Blue lamp (Tamper alarm)
4 L4 - Output 4 Group lamp
5 L5 - Output 5 Spare
6 L6 - Output 6 Spare
7 Relay Cell light
8 Call LED, External LED Also controlled by microphone active (polarity reveral of C/D-wire during conversation)

Syntax:

  • IND <station phys.no> <output> <1> <Indtype> [state]

Example:

  • IND %1.phy 1 1 3 ON: Turn the red lamp ON, flashing



Display data commands

Some properties of the Prison Station are configured in the station it self. The configuration data is sent to the Prison Station as display data, using the Event Handler and the $DSPL command.

Cmd Parameters Default Description
0x23 None Volume override ON.
0x24 None Volume override OFF.
0x45 None Disable call LED. ("Silent monitoring" mode).
0x46 None Enable call LED. (End "Silent monitoring" mode).
0x47 None Set flag for preventing call-request button from generating a callrequest in station's offline mode
0x48 None Clear flag for preventing call-request button from generating a callrequest in station's offline mode
0x60 ; 00 = off, 01 = on 60 00 Set alarm prepare mode on/off.
0x61 ; 00 = static relay, >00 = pulse length 61 00 Select light relay type: Static or pulserelay.
0x62 ; 00 = none, 01 = type1 62 01 Select offline mode operation type. Required for offline mode operation.
0x63 63 02 00 00 00 Configure general inputs. One byte for each input. Select inverted input (bit0) and alarm-trigger input (bit1)
0x64 64 A0 08 00 14 Configure VOX detector. Volume level (00=set default), min scream-time (00=set default), max scream-time, min pause before re-enabling alarm. Times in 100ms resolution. (Note: Parameters are not saved to EEPROM, and lost when the station is moved).
0x65 65 0960 Set guard alarm timeout. Value is 16-bit, 100ms resolution. Max value = 0x199A (11 minutes).
0x66 66 00 Select front-panel key types: Capacitive sensor-key (0) or switch input (1). Each bit represents one key (bit0 = light-button, bit1 = callrequest, bit2 = program, bit3 = vol up, bit4 = vol dn).
0x67 67 00 0A Configure keyswitch inputs: Static switches (00) or toggle-switches (01). Delay after activation in 100ms resolution.
0x68 68 06 Set default volume override level (selected by messages 0x23/0x24). Min=00 Max=06.
0x70 None 70 Restore EEPROM defaults.
0x71 TBD (Software download control-command - not yet used)
0x72 TBD (Software download data-command - not yet used)


Examples:
$DSPL L%1.dir U2 6100 '' : Set light relay to static mode
$DSPL L%1.dir U1 23 '' : Volume override ON

About Scream Alarm

The display data command 64 controls the level and duration necessary to trigger the scream alarm. Details:

0x64 <volume level> <min-time> <max-time> <pause>			

Default is 64A0080023, the values are in hexadecimal.

  • Volume (trigger) level = 00-FF, A0 is default. See table below.
  • Minimum scream time = 08 Default (800ms). Noise must be present this time to trigger an alarm
  • Maximum time = 00 default (optional). Noise longer than this do not trigger an alarm (Background noise)
  • Minimum pause for re-enabling alarm is default 23 (= 3500ms)

The scream alarm is triggering DAK 19, and for testing the DAK key can be programmed to “I 101” or similar.

When using the PrisCom database, the scream alarm is active only when the station is in "alarm preparation mode", i.e. when the guard is present by turning the key switch in position 1 or 2 (display data command 0x60). To enable scream alarm from idle and to adjust the scream alarm parameter do the following:

Put all scream alarm stations in the same UDP Add an event with this UDP as owner Event type 13 “Faulty station” When change to OFF This event will trigger when the exchange is reset and if station is reconnected Action is: $DSPL L%1.dir U6 64A008001401 $DSPL L%1.dir U5 64A0080014


Relation between sound pressure and the programmed scream alarm volume:

Volume
(00-FF)
Sound Pressure
(dBA, +/-3dB)
40 74
50 77
60 80
78 83
90 86
A8 89
C0 92
D0 95
E0 98
F0 101

Event Handler programming

The use of UDD variables

User Defined Data (UDD) are variables which can be used to store status information. In the PrisCom database the physical number of the station is used as index for the UDD. A bitmask is used - one word per station:


Bit (value) Description
11 (2048) (Not used)
10 (1024) Call request mode / tamper call
9 (512) Guard present
8 (256) Light status on
7-0 (Not used)

Examples of using UDD's:

  • Read: %udd(%1.phy) will return the content of the UDD
  • Write: WUDD %1.phy 3 will write the value 3 in the UDD


Events

Owner Event Sub-type Chg to Rel to Description Action Comment
UDP 1 25 Event Trigger w/ User Parameter 0 ON All Ext Light control IND %2.phy 7 1 1 ON Feature no 095/0, dirno 9559. Guard dials "9559 103 C" to turn cell-light on.
           
UDP 1 25 Event Trigger w/ User Parameter 1 ON All Ext Light control IND %2.phy 7 1 1 OFF Feature no 095/1, dirno 9560. Guard dials "9560 103 C" to turn cell-light off.
UDP 2 07 Conversation - Incoming   OFF All Conv. End $DSPL L%1.dir U1 24 Volume override OFF
UDP 2 07 Conversation - Incoming   ON All Conv. Start $DSPL L%1.dir U1 23 Volume override ON
IF %op(%op(%udd(%1.phy),&,1024),==,1024) If the station is in call request mode or tamper call (bit 10)
WUDD %1.phy,%op(%udd(%1.phy),&,64511) Reset cal req mode / tamper call (bit 10)
IND %1.phy 3 1 1 OFF Turn tamper-lamp off when communication is established.
IND %1.phy 1 1 1 OFF Turn call-lamp off when communication is established.
IND %1.phy 4 1 1 OFF Turn group-lamp off when communication is established.
ENDIF
UDP 2 09 Private ringing mode OFF All Inc. call (priv) end $DSPL L%1.dir U1 48 Clear flag for preventing call-request button from generating a callrequest in station's offline mode
UDP 2 09 Private ringing mode ON All Inc. call (priv) IF %op(%op(%op(%udd(%1.phy),&,512),==,512),||,%op(%op(%udd(%1.phy),&,1024),==,1024)) If Guard Present (bit 9) or Call Req mode (bit 10)
$M L%1.dir simulate M-key to connect the call without ringing
$MREL L%1.dir
STOP
ENDIF
$DSPL L%1.dir U1 47 Set flag for preventing call-request button from generating a callrequest in station's offline mode
UDP 2 13 Faulty station line OFF Faulty line OFF LOG "St %1.phy, %1.dir %1.nam: Line fault reset" Send to System log that station is OK
$DSPL L%1.dir U2 6100 Set light relay type to static
$DSPL L%1.dir U2 6201 Offline mode: 01
$DSPL L%1.dir U5 6302000000 Set input 1 (external call button) to alarm trigger input when station is in alarm mode.
$DSPL L%1.dir U5 64A0080023 Configure scream alarm. Volume = A0, min. scream time = 08 (800ms), max. time = 00, pause = 23 (3500 ms)
$DSPL L%1.dir U3 650960 Guard timeout: 0x0960 = 2400 ms = 4 min.
$DSPL L%1.dir U2 6600 Key type: Capacitive sensor keys
$DSPL L%1.dir U3 67000A Keyswitch: Static
$DSPL L%1.dir U2 6806 Max. Volume override level = 06
IF %OP(%op(%GNV(5,8,%1.phy,17),&,65519),==,39) Is testing the bit pattern 1X0111 against st_profile[n].flags2 (but removes bit 5 first, counted from 1, this bit controls privacy.)
STOP
ENDIF
$SNV Q55 W5 W8 W%1.phy W17 Q55: Sets the bit pattern to 110111 (display, two-tone w/ack, privacy). Q39: Sets the bit pattern to 100111 (display, two-tone w/ack)
$SNV Q16496 W5 W8 W%1.phy W16
$SNV Q62 W5 W8 W%1.phy W0 W0 W0 Configure DAK 1 to ">500" and DAK 2 to ">501". Set first char in DAK 1 to ">"
$SNV Q53 W5 W8 W%1.phy W0 W0 W1 Set second char in DAK 1 to "5"
$SNV Q48 W5 W8 W%1.phy W0 W0 W2 Set third char in DAK 1 to "0"
$SNV Q48 W5 W8 W%1.phy W0 W0 W3 Set fourth char in DAK 1 to "0"
$SNV Q62 W5 W8 W%1.phy W0 W1 W0 Set first char in DAK 2 to ">"
$SNV Q53 W5 W8 W%1.phy W0 W1 W1 Set second char in DAK 2 to "5"
$SNV Q48 W5 W8 W%1.phy W0 W1 W2 Set third char in DAK 2 to "0"
$SNV Q49 W5 W8 W%1.phy W0 W1 W3 Set fourth char in DAK 2 to "1"
UDP 2 13 Faulty station line ON Faulty line ON LOG "St %1.phy, %1.dir %1.nam: Line fault" Send to System log that station is faulty
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9550 Call Request $SM L%1.dir NG%1.exp U103 NM18 GV U3 'Call' Send call request to the "Guard Group" (%1.exp) with priority 103
LOG "St %1.phy, %1.dir %1.nam: Cell callrequest" Send information to System log
WUDD %1.phy,%op(%udd(%1.phy),|,1024) Set Call Request mode / tamper call (bit 10)
IND %1.phy 1 1 1 ON Turn call-lamp on
IND %1.phy 4 1 1 ON Turn group-lamp on
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9551 Cell Alarm $STM L%1.dir NG%1.exp U143 '%1.dir Alarm!' U1 Send alarm request to the "Guard Group" (%1.exp) with priority 143
LOG "St %1.phy, %1.dir %1.nam: Alarm call!" Send information to System log
IND %1.phy 1 1 3 ON Turn call-lamp on, flashing
IND %1.phy 4 1 3 ON Turn group-lamp on, flashing
IND %1.phy 2 1 1 ON Turn guard present-lamp on
@01FF M7C01 U01 W%1.phy U%3.CHG(3,0) Send message to AlphaVision
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9552 Tamper Alarm $SM L%1.dir NG%1.exp U36 NM18 GV U2 'Tamper alarm!' Send tamper alarm request to the "Guard Group" (%1.exp) with priority 36
LOG "St %1.phy, %1.dir %1.nam: Tamper Alarm!" Send information to System log
WUDD %1.phy,%op(%udd(%1.phy),|,1024) Set Call Request mode / tamper call (bit 10)
IND %1.phy 3 1 1 ON Turn tamper-lamp on
@01FF M7C01 U01 W%1.phy U%3.CHG(2,0) Send message to AlphaVision
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9553 Guard present 1 $TPROG L%1.dir U0 Switch off audio prog temporarily
$CANM L%1.dir NG%1.exp Cancel all requests from this station
$STM L%1.dir NG%1.exp U33 '%1.dir Grd present' U0 Send "Guard present" message
LOG "St %1.phy, %1.dir %1.nam: Guard present" Send information to System log
$DSPL L%1.dir U2 6001 Cmd 60 01: Set Alarm preparation mode
WUDD %1.phy,%op(%udd(%1.phy),|,512) Set Guard present (bit 9)
IND %1.phy 1 1 1 OFF Turn call-lamp off
IND %1.phy 4 1 1 OFF Turn group-lamp off
IND %1.phy 2 1 1 ON Turn guard present-lamp on
IND %1.phy 7 1 1 ON Switch on the cell light
@01FF M7C01 U01 W%1.phy U%3.CHG(3,0) Send message to AlphaVision
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9554 Guard present 2 $TPROG L%1.dir U0 Switch off audio prog temporarily
$CANM L%1.dir NG%1.exp Cancel all requests from this station
$STM L%1.dir NG%1.exp U33 '%1.dir Grd present' U0 Send "Guard present" message
LOG "St %1.phy, %1.dir %1.nam: Guard present" Send information to System log
$DSPL L%1.dir U2 6001 Cmd 60 01: Set Alarm preparation mode
WUDD %1.phy,%op(%udd(%1.phy),|,512) Set Guard present (bit 9)
$ST L%1.dir W2400 L9554 Start a 240 second alarm-timer
IND %1.phy 1 1 1 OFF Turn call-lamp off
IND %1.phy 4 1 1 OFF Turn group-lamp off
IND %1.phy 2 1 1 ON Turn guard present-lamp on
IND %1.phy 7 1 1 ON Switch on the cell light
@01FF M7C01 U01 W%1.phy U%3.CHG(3,0) Send message to AlphaVision
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9555 Guard reset $TPROG L%1.dir U1 Restore audio program
$CANM L%1.dir NG%1.exp Cancel all requests from this station
LOG "St %1.phy, %1.dir %1.nam: Guard reset" Send information to System log
$DSPL L%1.dir U2 6000 Cmd 60 00: Clear Alarm preparation mode
WUDD %1.phy,%op(%udd(%1.phy),&,65023) Reset Guard Present (bit 9)
WUDD %1.phy,%op(%udd(%1.phy),&,64511) Reset Call Request mode / tamper call (bit 10)
$ST L%1.dir W0 L9554 Stop the alarm-timer
IF %op(%op(%udd(%1.phy),&,256),!=,256) If the cell light was off before "Guard Present"...
IND %1.phy 7 1 1 OFF ...turn light off
@01FF M7C01 U01 W%1.phy U0 Send message to AlphaVision
ENDIF
IND %1.phy 0 0 0 OFF Switch off all lamps
@01FF M7C01 U01 W%1.phy U0 Send message to AlphaVision
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9556 Power fail ON $STM L%1.dir NG%1.exp U30 '%1.dir Power failure!' U0 Send "Power failure" message to guard group, priority 30
LOG "St %1.phy, %1.dir %1.nam: Power failure" Send information to System log
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9557 Power fail OFF $CANM L%1.dir NG%1.exp NM255 U30 Remove "Power failure" message (i.e. all mails with priority 30)
LOG "St %1.phy, %1.dir %1.nam: Power failure reset" Send information to System log
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9558 Light switch IF %op(%op(%udd(%1.phy),&,256),==,256) If cell light is currently on...
WUDD %1.phy,%op(%udd(%1.phy),&,65279) reset the light status (bit 8)
IND %1.phy 7 1 1 OFF switch light off
STOP
ENDIF
WUDD %1.phy,%op(%udd(%1.phy),|,256) If cell light is currently off, set the light status (bit 8)...
IND %1.phy 7 1 1 ON ..and switch the light on. (If pulserelay, light will toggle on both ON and OFF message)
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9561 Sound detector IF %op(%op(%udd(%1.phy),&,512),==,512) If "Guard Present" status (bit 9)
$STM L%1.dir NG%1.exp U143 '%1.dir Scrm alarm!' U1 Send "Scream alarm" message
LOG "St %1.phy, %1.dir %1.nam: Scream alarm!" Send information to System log
IND %1.phy 1 1 3 ON Turn call-lamp on, flashing
IND %1.phy 4 1 3 ON Turn group-lamp on, flashing
IND %1.phy 2 1 1 ON Turn guard present-lamp on
@01FF M7C01 U01 W%1.phy U%3.CHG(4,0) Send message to AlphaVision
STOP
ENDIF
UDP 2 15 Event Trigger Feature 0 ON Dirno: 9562 GSM detector $SM L%1.dir NG%1.exp U103 NM18 GV U2 'GSM detector' Not implemented!
UDP 2 17 SxMember 0 ON/OFF All Silent call $DSPL L%1.dir U1 %chg(45,46) When in SX conference (monitoring mode), disable/enable call LED
UDP 2 21 Event Timeout 0 ON Dirno: 9554 Guard timeout - Alarm $STM L%1.dir NG%1.exp U143 '%1.dir Alarm!' U1 Send "Alarm" message to Guard Group
LOG "St %1.phy, %1.dir %1.nam: Alarm call! (timeout)" Send information to System log
IND %1.phy 1 1 3 ON Turn call-lamp on, flashing
IND %1.phy 4 1 3 ON Turn group-lamp on, flashing
IND %1.phy 2 1 1 ON Turn guard present-lamp on
UDP 8 07 Conversation - Incoming OFF All Conv. End LOG "Conversation reset : %2.dir -> %1.dir" Send information to System log
UDP 8 07 Conversation - Incoming ON All Conv. Start LOG "Conversation established: %2.dir -> %1.dir" Send information to System log
UDP 8 09 Private ringing mode ON All Inc. call (priv) LOG "Call in private : %2.dir -> %1.dir" Send information to System log
UDP 8 13 Faulty station line ON/OFF All Faulty line On/Off @01FF M7C06 %1.REF U%3.CHG(1,0) Send message to AlphaVision