Difference between revisions of "PrisCom station - Configuration"

Revision as of 15:30, 8 January 2013

This article is a stub. You can help AlphaWiki by expanding it.

PrisCom Stations
1007061000 station
1007063000 station

This article describes how to configure the Prison Stations model 1007061000 and 1007063000.

Software requirements

AMC software v.9.09 or later
AlphaPro 9.21 or later

"Scream alarm from idle" is available from station software 01.02.

Decide the configuration starting point

When configuring a system with the 1007061000/1007063000 stations there are two options:

Start with a new AlphaPro database and fill in the parameters from scratch (Basic features)
Use a preprogrammed database from Zenitel (Advanced features)

"Basic features" are:

Call Button
Program Step button (without displaying selected channel)

"Advanced features" means support for:

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

When using the advanced features of the station, it is highly recommended to use the 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.

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 (E.g. C:\Program files\AlphaPro\Database).

Start AlphaPro and select the PrisCom database. Verify that the PrisCom database is visible.

Guard station configuration

Include Guard Station in UDP 1

Include Guard Station in a "Guard group", here group 10

In Users & Stations -> UDP, include the station in UDP 1
In Groups -> Local Groups, select a free group (e.g. group 10) and include the guard station in this “Guard group”. This is required even with a single guard station.

Prison station configuration

Prison station: Enable UDP 2, and enter the "Guard group" (here: 10) to receive the Call Request

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. When the call button is presses on the prison station, a call request is sent to all stations in this group.

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 redirect the DAK keys to point to physical station 500 and 501
Physical station 500 and 501 have preconfigured DAK keys according to the PrisCom Station features.

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. The Prison Stations are the only station 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. Most of the numbers are Event Triggers, starting from 9550 and upwards. Actions for these custom event triggers are defined in the event handler, using the event “15 Event Trigger Feature”.

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.

The format is as follows:

$DSPL <station> <length>

Station: The prison station
Length: The length of the data string.
Data: Display data command and parameters. For the Prison Station programming, sequential hex values are used to make the string.

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 preparation mode" on/off. When ON, all panel buttons trigger DAK 4.
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 23	Configure Scream alarm 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.

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

Note that the parameters are followed by two single apostrophes ('). Closing single quotation marks (‘…’) are not valid. A text editor like Word (and others) tends to convert apostrophes to single quotation marks, which will not work.

Volume Override

When using the PrisCom database and a conversation is established, the volume set by the user is overridden, and a preset volume is used. The preset volume is defined by the display data command 0x68. By default set to maximum ($DSPL L%1.dir U2 6806'').

The volume override ON is set by the display data command 0x23 when the conversation starts ($DSPL L%1.dir U1 23''), and the volume override OFF is set by the command 0x24 when the conversation ends ($DSPL L%1.dir U1 24'' ).

If the preset override volume is too loud, the following event can be modified:

Owner:    Event:                   Change to:
UDP 2     13-Faulty station line   OFF

In the "Action field" find the line:

$DSPL L%1.dir U2 6806'', and change 06 to a value 00-05. The value 00-06 sets what volume level to use when volume override is activated.

If volume override is not wanted at all, one can delete the line $DSPL L%1.dir U1 23'' from the "Conversation Incoming ON" event.

Changing the privacy setting

By default the Prison Stations are set in privacy mode. This means that a guard can’t call directly into the cell, but the prisoner has to accept the call by pressing the call button.

To change the station to operate in Open mode, the following event must be modified:

Owner:    Event:                   Change to:
UDP 2     13-Faulty station line   OFF

In the "Action field" find the line:

$SNV Q55 W5 W8 W%1.phy W17 (Prison stations in Private mode)

Change into:

$SNV Q39 W5 W8 W%1.phy W17 (Prison stations not in Private mode)

Changing Guard Presence timeout-alarm

When a guard marks his presence in a cell by turning the keyswitch to position 2, an alarm timeout is activated (no timeout for keyswitch position 1). The value of this timeout can be adjusted in the event handler.

The following event must be modified:

Owner:    Event:                   Change to:  Related to:    
UDP 2     15-Event trigger         ON          9554

Modify this action command:

$ST L%1.dir W2400 L9554

The value “W2400” is in 100ms resolution, which gives a 240 seconds (4 minutes) timeout. Change to desired value. Value is in decimal format.

Pulse relay instead of static relay for Relay Control output

By default the Relay Control output (connector P1/5 and P1/6) is configured as a static relay changing on/off each time the “light” button on the prison station is pressed. This can be changed to a pulse relay operation if such a relay is used.

The following event must be modified:

Owner:    Event:                   Change to:      
UDP 2     13-Faulty station line   OFF

Modify this action command:

$DSPL L%1.dir U3 6100 '' (Static relay)

into:

$DSPL L%1.dir U3 610A '' (Pulserelay, 10*10ms pulsetime)

The parameter "0A" to the display data command 0x61 in the string above defines the pulsetime in 10ms resolution. Value is in hex format.

Scream Alarm

The display data command 0x64 is used to set the level and duration necessary to trigger the scream alarm.

0x64 <volume level> <min-time> <max-time> <pause> [mode]

Default command is 64 A0 08 00 23, the values are in hexadecimal.

Volume level is the 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)
Pause is minimum time for re-enabling alarm is default 23 (= 3500ms)
Mode is an optional parameter, available from station software 01.02. 00=Scream alarm only in "alarm preparation mode". 01=Scream alarm from idle.

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

The default behavior of the Prison Station is that the scream alarm is active only when the station is in "alarm preparation mode" (controlled by display data command 0x60), i.e. when the guard is present by turning the key switch in position 1 or 2.

For special applications it is possible to enable scream alarm also from idle:

$DSPL L%1.dir U6 64A008002301 '' : Enable scream alarm from idle
$DSPL L%1.dir U6 64A008002300 '' : Enable scream alarm only when in "alarm preparation mode" (Default)

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

Example: $DSPL L%1.dir U5 6478080023 '' will set the scream alarm level to 78 (83 dBA).

Event Handler programming

This paragraph describes the event handler programming used in the PrisCom database.

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. If there is a need to use additional UDD's in the database, avoid using index numbers in the same range as the physical numbers for the Prison Stations. In order to store several statuses in one 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

External light control ON

Guard dials "9559 + 103 + C" to turn the cell-light relay on. Dirno 9559 is feature no 95/0.

Event Owner: UDP 1 (Guards)
Event Type:  25 - Event Trigger w/Parameter
Sub Event:   0
When Change To: ON
Related To: All
Action: 
IND %2.phy 7 1 1 ON

External light control OFF

Guard dials "9560 + 103 + C" to turn the cell-light relay off. Dirno 9560 is feature no 95/1.

Event Owner: UDP 1 (Guards)
Event Type:  25 - Event Trigger w/Parameter
Sub Event:   1
When Change To: ON
Related To: All
Action: 
IND %2.phy 7 1 1 OFF

Conversation start

When conversation is established, "volume override" is activated and status lamps are switched off.

Event Owner: UDP 2 (Prison stations)
Event Type:  07 - Conversation incoming
When Change To: ON
Related To: All
Action: 
$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 Call Request 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

Conversation end

When the conversation is ended, "volume override" is turned off.

Event Owner: UDP 2 (Prison stations)
Event Type:  07 - Conversation incoming
When Change To: OFF
Related To: All
Action: 
$DSPL L%1.dir U1 24 ''                     Volume override OFF

Private Ringing start

When the Prison station starts to ring, and the station already has made a Call Request or the Guard is already present (Key Switch in pos.1 or 2), then autoanswer is triggered (simulating M-key press), and the converation is automatically established. If no autoanswer (still ringing), a flag is set to prevent the call button from triggering the call lamps when the button is pressed to answer the call.

Event Owner: UDP 2 (Prison stations)
Event Type:  09 - Private Ringing mode
When Change To: ON
Related To: All
Action: 
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 push 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

Private Ringing end

When the ringing stops, clear the flag that prevents the call button from triggering the call lamps when the button is pressed to answer the call.

Event Owner: UDP 2 (Prison stations)
Event Type:  09 - Private Ringing mode
When Change To: OFF
Related To: All
Action: 	
$DSPL L%1.dir U1 48 ''               Clear the flag that prevents the call button from generating a callrequest in station's offline mode

Initialization of stations. DAK redirection

When the prison station is reported up (e.g. after a system restart), this event will send configuration data to the station using the $DSPL command. The event will also, with an IF statement, check if the station is already configured as a Prison station in the AMC by checking the station flags2 bits for Two-tone signaling and audio program display. If not already configured with these settings, they will be applied, and the DAK key 1 will be programmed to ">501" and DAK 2 to ">502".

Event Owner: UDP 2 (Prison stations)
Event Type:  13 - Faulty Station line
When Change To: OFF
Related To: All
Action: 	
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	                                         Stop if the bit pattern already is 1X0111, as the station is already set as Prison Station.
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	                 Sets bit 4, 5, 6 and 14 in station_flags1.
$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"

LOG when a station is faulty

This event is triggered when a station is reported faulty, and an error message is sent to the System log.

Event Owner: UDP 2 (Prison stations)
Event Type:  13 - Faulty Station line
When Change To: ON
Related To: All
Action: 	
LOG "St %1.phy, %1.dir %1.nam: Line fault"           Send to System log that station is FAULTY

Call Request - Event Trigger 9550

This event is triggered when the call button is pressed. A Call Request is sent to the Guard station(s), and the call- and group lamps are turned ON.

Event Owner: UDP 2 (Prison stations)
Event Type:  15 - Event Trigger Feature
Sub Event:   0
When Change To: ON
Related To:  9550
Action: 	
$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

Alarm Call Request - Event Trigger 9551

This event is triggered when the status is "Guard Present" (i.e. the keyswitch is in position 1 or 2), and any button is pressed. An Alarm Call Request is sent to the Guard station(s), the lamps are turned ON, and a message is sent to AlphaVision.

Event Owner: UDP 2 (Prison stations)
Event Type:  15 - Event Trigger Feature
Sub Event:   0
When Change To: ON
Related To:  9551
Action: 	
$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

Alarm Call Request - Event Trigger 9552