SigNET LS Voice Alarm Routing Matrix MPC Installation and Configuration Guide. Desk version. Wall version

Transcription

1 SigNET LS Voice Alarm Routing Matrix MPC Installation and Configuration Guide Desk version Wall version 2008, SigNET (AC) Ltd. Page 1 of 30 DCM ADS Rev 0.doc

2 Contents 1 IMPORTANT Overview Block Diagram Connection and installation Preparing to configure the MPC console Menu Structure Initial Set Up Advanced Configuration Options Night Service Mode Lamp Test Creating and Fitting Custom Labels Specifications IMPORTANT THIS SECTION MUST BE READ PRIOR TO THE INSTALLATION / MAINTENANCE OF THIS PRODUCT This equipment must only be installed and maintained by a suitably skilled and technically competent person. No responsibility can be accepted by the manufacturer or distributors of this product for any misinterpretation of an instruction or guidance note or for the compliance of the system as a whole. Voice alarm system design is beyond the scope of this document. An understanding of system components and their use is assumed. Errors and omissions excepted. The manufacturer s policy is one of continuous improvement and we reserve the right to alter product specifications at our discretion and without prior notice. 2 Overview This document is intended to guide design engineers and maintenance engineers through the main steps in setting up, using and maintaining any of the MPC series of paging consoles on a SigNET LS Voice Alarm Routing Matrix System. The MPC16, MPC32, MPC48 and MPC64 are desk mounted paging consoles and the MPC16W and MPC32W are wall-mount versions. The MPC16 has 16 programmable buttons and indicators; the MPC32 has 32 programmable buttons and indicators and so on. The MPC16W and 32W have close-talking fist microphones and are designed for use in noisy environments such as building lobbies, whereas the MPC16, 32, 48 and 64 have a noise-cancelling gooseneck microphone and are for use in quiet locations (-40 dba ambient) such as fire control rooms. Both comply fully with the requirements of BS5839 part 8 and BS EN and can be used as emergency microphones, paging microphones or both (the priority of the microphone can change with the user, such as the fire officer). If required, the configuration can be set so that routine users do not see fault status information, but it is visible to other users such as the Supervisor and Fire Officer. Each MPC is connected to the serial port on an SS2N (see the SigNET LS manual Document number DCR ) and to one of the audio inputs. Apart from the case design and number of programmable buttons, all the units are functionally identical and provide the following functions: 1. High quality gooseneck cardioid condenser microphone (close-talking dynamic fist mic in the case of the MPC16W and MPC32W). Page 2 of 30

3 2. Selection of loudspeaker zones or groups of zones for paging. 3. Selection of loudspeaker zones or groups of zones for routing music or other audio inputs. 4. Selection of pre-recorded messages and playing them in pre-set groups of zones. 5. Indication of status of loudspeaker zones. 6. LCD display showing system status and faults (if selected). 7. Support for up to eight users who may have access to different facilities via different PINs. These are: Engineer, Fire Officer, Supervisor, Unregulated and four definable users. 8. Option to enter the Fire Officer user mode by operating a manual call point or similar monitored switch. 9. Ability to control up to 128 zones with all facilities, 240 zones with restricted facilities see section 6, note 4 on page Block Diagram Monitor MPC Block Diagram Phantom Detect VCA EQ Audio out Rectifier 100 Hz User Controls 10kHz Fail Fault OK 2 x 40 character LCD µc RS422 RS422 Programmable buttons Shift register Shift register Tri-colour LEDs Chime PTT All Call + 24 V 0 V Page 3 of 30

4 4 Connection and installation SigNET LS MPC Range Installation and Configuration Guide 4.1 Interconnection block diagram All consoles communicate with an SS2N through a four-pair Cat 5 cable or two four-core fire-rated cables. 2 x 4-core 1.5mm 2 fire rated cables Max 500 m MPC RS 232- RS 422 converter SS2N SS2N OR (not life-safety) 1 x Cat5 UTP Max 50 m* SS2N SS2N network For life safety applications, cabling should consist of four two-core fire-rated cables, at least 1.0 mm 2 up to 500 metres. Do not use a single multi-core as this will result in audible interference and the consoles will not work properly. *For non-life safety applications, cabling should consist of Cat five UTP up to 50 metres. However, if the cable is longer than 50 metres, voltage drop will be significant and a local 24 VDC power supply is necessary (see connection details on page 6 and 7). Cat 5 FTP (Shielded) may not work over the same distances due to its much greater capacitance. The MPC console s data port is RS422 but the SS2N s data port is RS232, which has a short reliable range and so must be converted to RS422 using the RS422CONV as described in Doc No. DCP JH 30/7/99 rev Installing an MPC wall-mounted console Open the case, locate the fixing screws on the main PCB and the microphone chamber and unscrew both. The main PCB and microphone chamber can then be unhooked from the fixing pillars. Unscrew the lid hinge retaining screws and remove the lid, main PCB and microphone chamber. Remove two knockouts in the top of the lid nearest to the eight connection terminals. Fit suitable cable glands and fit the back-box to the wall at about 1.6 metres from the final floor level, using appropriate fixings. Terminate the cables as shown below and then reassemble the case. Page 4 of 30

5 MPC-W Wall-Mounted Console Connections LOG-IN TERMINALS A B G H C F D E Fixing screw 4.3 Emergency log-in switch Remove the 6k8 resistor from the Log in terminals. Connect a fire alarm manual call point across the terminals and fit the 6k8 resistor across the switch. Connect a 470Ω resistor so that operating the switch connects it across the line. When the switch is operated, the console will log in to Fire Officer Mode. 4.4 Adjusting mic level, bass, treble and LCD controls Collector + - Emitter 6k8 Backlight Opto Buzzer Log in LCD Contrast A B G H C F D E Mic Darker Opto is used as a local fault output if required Reset Switch Bass Gain 24V 0V A+ A- T+ T- R+ R- PTT Sw Increase Treble Page 5 of 30

6 4.5 Installing a desk-mounted MPC Cat 5 cables are installed as structured cabling in many buildings and so are a convenient method of connecting MPC paging consoles to an SS2N system. However, there are some issues 1 Cat 5 cable is not suitable if the console is used for emergency control as it does not comply with the requirements of BS for standard or enhanced fire-resistant cable. 2 The resistance of Cat 5 cable combined with the current consumption of MPC paging consoles, particularly when all LEDs are lit, means that if the cable is longer than 50 metres, a local 24 VDC auxiliary power supply must be provided. The maximum distance for reliable data transmission is 500 metres using unscreened UTP cable. 3 It is often not possible to be certain how long any particular Cat 5 structured cable run will be when designing a system so it is good practice to always allow for a local power supply. 4 Of necessity, the connections to the MPC consoles do not comply with the normal standards for Cat 5 equipment and so it is essential that the MPC is not plugged into, for instance, a telephone socket, and that third party equipment is not plugged into a Cat 5 socket connected to an SS2N system. 4.6 Installing a MPC desk mounted console with Cat 5 cable The MPC console is intended for desk mounting and for the flexible Cat 5 cable to be plugged into a MPC Console RJ45 Wall Plate with CatCON connector 8 way 5 amp terminal block White/Orange Orange White/Green Blue White/Blue Green White/Brown Brown A B C D E F G H CatCON wall plate which is connected to the SS2N as shown below. The CatCON should be fitted to one half of a twin single-gang back-box and a blank plate should be fitted over the unused half. The fire rated cables should be glanded to the back box and the individual cores connected to the terminals as shown above. IMPORTANT It is essential that the flexible Cat 5 cable is protected from inadvertent damage and from being pulled out of the CatCON wall plate. Ideally, the CatCON should be installed in the desk where the MPC console is to be used Connecting a local power supply If the Paging console is more than 50 metres from the rack, voltage drop will make cause problems, especially if the system is running from batteries so local 24 V 500 ma power supply can be fitted to extend the cable range to 500 metres. As Cat 5 cable is not suitable for emergency use, the power supply does not need to have standby batteries or to comply with EN Page 6 of 30

7 MPC Console Wall Plate IMPORTANT (CatCon) Connections When using a 24 VDC power supply The 0V line (B) MUST be connected to the 0 V from the RS422CONV The 24 line (A) must NOT be connected to the 24 V line from the RS422CONV White/Orange Orange White/Green Blue White Blue Green White/Brown Brown Optional 24 VDC 500 ma PSU A B C D E F G H Connecting with Fire resistant cables MPC desk-mounted consoles are normally connected using the supplied flexible Cat 5 cable (see 4.6) However, if required, they may also be connected using fire-rated cables. When MPC consoles are connected via fire resistant cables such as MICC, FireTuf, FP200 Gold etc., it is necessary to avoid interference between audio and data so two four-core cables are required, with the following pairs grouped, cable 1 carries the green and blue Cat 5 pairs (A, B, D & E) and cable 2 carries the orange and brown Cat 5 pairs (C, F, G & H). Note that fire-rated cables must be connected to the case using special glands and must only be terminated by a competent person. Failure to separate the audio and data will cause data errors and digital noise in the audio. Maximum cable distance on fire resistant cable (1.00 mm2 or greater) and on FTP Cat 5 cable (with auxiliary power supply) is 500 metres Opening the desk console Separate the base from the lid by undoing the visible screws on the front of the base, at the sides and on the rear of the console. If extensions are fitted, there is no need to remove the screws connecting them to the main part of the console. The lid can be removed completely if required by disconnecting the four connectors shown opposite and the two-pin header to the LCD backlight. Care must be taken on re-assembly to reconnect in the correct sequence Removing the Cat 5 Cable and fitting the cable glands Slacken the gland nut and remove any internal cable ties from the Cat-5 cable. Using a terminal screwdriver, release the cable from the connector and remove the cable. Remove the fitted gland, which has a small diameter suitable for Cat 5 cable, and fit two glands suitable for the fire-rated cable Fitting the cable Remove about 200 mm of the outer sheath of each cable and remove the shielding and drain wire (if fitted) back to the sheath as if they are connected at the console end an earth loop will result. They MUST be connected to ground at the equipment cabinet. Remove 5 mm of insulation from each core then bend the core and fit it to the cables where the Cat 5 cable was connected, as shown below. Page 7 of 30

8 IMPORTANT SigNET LS MPC Range Installation and Configuration Guide The cores connected to the left hand four terminals must run in one cable and the cores connected to the right-hand four terminals must run in the other four core cable. If they are mixed digital noise will be heard on the audio. Taking the left-hand terminal shown as 1, connect to four pairs of cores as follows: Terminal from L to R in picture SigNET Standard Reference Description CAT 5 plug numbers and colours 1 A +24 VDC nominal 1 White/orange 2 B 0V 2 Orange/white 3 G Audio + 3 White/green 4 H Audio - 6 Green/white 5 D RS422 Transmit + 4 Blue/white 6 E RS422 Transmit - 5 White/blue 7 F RS422 Receive - 7 Brown/white 8 C RS422 Receive + 8 White/brown Cores connected to terminals 1 to 4 should be in one four-core cable and cores connected to terminals 5 to 8 should be in the other. If four two-core cables are used instead, then the cores should be kept in pairs as follows to avoid reliability problems: 1 & 2, 3 &4, 5 & 6, 7& Reassembling the case Reconnect the ribbon cables from the lid of the console to the base as shown in the following table and pictures: From lid To base Ways Description LCD Backlight Backlight connector 2 LCD Backlight LCD LCD connector 14 LCD Switch Board In connector SW16 connector 10 Connects to keyboards UP/Down/Tick/Cross PCB UDTX connector 14 Connects to menu navigation and fault indication board (by LCD) From PTT PCB PTT connector 10 Connects to PTT board Fit the lid to the base, ensuring that no wires are trapped and reinsert and tighten all the screws. Page 8 of 30

9 5 Preparing to configure the MPC console 5.1 Connection and Set-up All units communicate with the SigNET LS system via RS422 lines. However, SS2Ns use RS232 protocol and so a SigNET RS232/422 protocol converter is required at the SS2N end. For life safety applications cabling should consist of four two-core or four two-core fire-rated cables. Standard or enhanced grade cables to BS 7629 will both work equally well up to 500 metres. Do not use a multi-core as this will result in interference between control data and audio and the unit will not work properly. For non-life safety applications, cabling should consist of Cat five UTP (Unshielded twisted pair) up to 50 metres. For longer distances, a local 24 VDC 500 ma power supply is required. Note: Cat 5 STP (Shielded) may work but at shorter range due to increased capacitance. 5.2 Planning Keys All keys in the main part of the unit (between the LCD and the PTT switch) are configurable and thought should be given to the best use of each key. It is normal to use the first block of 8 configurable keys to address individual zones (an operation that can be done automatically see on p16). Another block of keys may be reserved for multi-zone groups. A final block of keys may be reserved for special functions such as sending test messages or controlling background music Users and PIN numbers The MPC series supports up to eight PIN numbers, four of which are special and four generalpurpose: 1. Unregulated no PIN number. Unregulated functions are available to anyone who has access to the console. 2. Fire Officer s PIN default The fire officer can log in by using this PIN, which can be changed if required. He can also access the controller by operating a special monitored switch (usually a break-glass manual call point), if fitted. Note if no break glass or manual call point is fitted a 6k8 resistor must be fitted internally to avoid fault reports. 3. Supervisor default This number usually allows access to more functions than a general user. For instance, the supervisor may be able to see fault information and adjust volume levels for paging and music. 4. Engineer default This PIN controls the entire configuration, and has access to all menu options. 5. User Default PINs These PINs are for general-purpose users. They are intended to give specific operators access to certain facilities whilst preventing access to other facilities. For instance, they give access to volume controls, but not to change the pre-announcement chime. Each may have different paging priorities, access to keys, numbers of chimes, and so on. If the unit is in a secure area, such as the fire control room, these user PINs are unlikely to be needed. Page 9 of 30

10 However, if the console is in an unrestricted area, these PINs allow different facilities to be accessed by logging in User Definition and Access Levels All users (including the unregulated user) may have a number of modifiable capabilities (access levels) and parameters specified as described below: 1. Name. A description of the user that is shown when the user is logging in and under some circumstances when the user is not logged in. The default names are as shown in above. 2. PIN. This is the 4-digit access code a user needs to log in. Note that although this can be specified for all users (including unregulated) that it is not used for the unregulated user. The Fire Officer can also be logged in automatically with an optional monitored break-glass switch. 3. Paging Priority. The priority with which a paging announcement is executed. Typically this will be 5 for the fire officer and 20 or lower for the others. The default values are 30 for unregulated, 5 for Fire Officer, 20 for supervisor and engineer, and 25 for other users. Any value between 1 and 250 is valid and exact values depend on the system configuration. 4. Time Out Period. The time (in seconds) of inactivity that can occur before the user is automatically logged out. Although this can be specified for the unregulated user, it is not used. By default, the Fire Officer and unregulated users are never logged out (time = 0). For all others, the default is 60 seconds. Note, if the Fire Officer is logged in using the break-glass switch, he is not logged out until the break glass switch is re-set. 5. Chime Option. The number of chimes that are issued when the user pages. The default is three chimes for the unregulated user. All other users, except the Fire Officer, default to be the same as the unregulated user (so if the unregulated user is changed to two chimes, all other users will follow suit unless specifically set to a different value). The Fire Officer defaults to no chimes. 6. View Faults. Determines whether this user can see a list of current faults. 7. Mute Buzzer. Determines whether this user can silence the fault buzzer. 8. Can see fault LEDs. Determines whether this user can see the fault LEDs (Panel Fault, Network Fault and General Fault). 9. Can see node fault LEDs. Determines whether this user can see individual node faults. If he can, when in view faults mode, areas in fault show steady yellow if in fault or flashing yellow/green if selected. Faults are not visible in other modes such as BGM (background music) or sending messages. 10. Can see Fault count. Determines whether this user can see how many faults are currently on the system. 11. Can view Fault Log. Determines whether this user is able to view the fault log. This is a timed log of when the last 99 faults occurred, and whether they have been accepted or not. When all faults have been accepted, the buzzer will stop. 12. Can accept faults. Determines whether this user can accept faults while viewing the fault log. 13. Can see Console status. Determines whether this user can see the console status, which tells you what the local faults are (if any). 14. Can See Paging Volume. Determines whether this user can see the current volume level used for paging (excluding emergency volume level, which is not available through the console). 15. Can Change Paging Volume. Determines whether this user can change the non-emergency paging volume levels. 16. Can See BGM volume. Determines whether this user can view background music volume levels. 17. Can Change BGM volumes. Determines whether this user can change background music volume levels. 18. Can Change volumes by node. For experienced users who know the internal site configuration, enabling this option allow individual stations to be adjusted, not just the groups associated with the group keys. 19. Can Select Chimes. Allows this user to turn chimes on and off using the chime key. Page 10 of 30

11 20. Can Reset Console. Allows this user to reboot the console. 21. Can Reset Rings. Only for expert users. Allows this user to reset the SS2N ring network. 22. Show Busy States. Shows this user whether an area is busy before a page is sent. 23. Show FEWG states. Enabling this option allows this user to see where Fire Evacuation Warning Generator messages are playing. Evacuation messages flash red and Alert messages flash yellow. 24. Echo Group Contacts. This is an advanced option and should only be used by SigNET personnel or under their direct instruction. Note. Many of these options result in additional menu items being placed in the menu structure Site-specific details The following site-specific information should be determined before attempting to set up the unit. 1. Site Name, maximum 31 characters. By default this is SigNET (AC) Ltd. 2. Console Insert Node and Serial port node. Tells the network which node the microphone is connected to and the node number for the serial input. Usually, the two numbers are the same, or if the insert node is even, the serial input node will usually be one less. 3. If pre-recorded messages (DVA(s)) are to be triggered from the unit, tells the network their audio insert node number(s). 4. If background music (BGM) is to be used, tells the network the audio insert node number(s) for the music sources. 5. Determine whether night-service mode (where non-emergency volume levels are adjusted, usually downwards, at night) is to be used, and if so, the activation and de-activation times. 6. If night-service mode is used, it is normally controlled by a built-in timer. However, if required, a key maybe programmed to control the facility instead. 7. Any user restrictions required, such as access by specific users to specific keys and menu options. Page 11 of 30

12 6 Menu Structure SigNET LS MPC Range Installation and Configuration Guide The menu structure may be different for each user. Entries in the tree below are marked as follows: 1 Optional depending on user configuration 2 Only for the Engineer 3 Only for the Engineer and the Supervisor 4 Not available on systems with more than 128 nodes Each indent indicates a new level of menu (if the tick key is pressed on the preceding option). Options at the same level of indent are accessed by using the up and down arrow keys. Logged Out Screen Mute Buzzer 1 View Panel Status 1 View Current Faults 1 View Fault Log 1 Log In Mute Buzzer 1 View Console Status 1 View Current Faults 1 View Fault Log 1 Configure Key 2 Set Key Access 2 Set Key Function 2 [not used] 2 Zone Select 2 DVA 2 4 Contact ID Zone List 2 4 Zone Select (not in All Call) 2 DVA Type 2 4 (alert, evac, other) DVA Priority 2 4 DVA Insert Node 2 4 BGM 4 BGM Source Node 2 4 Remote Contact 2 Contact ID 2 Remote Contact Pair 2 Contact ID 2 Green Contact Key 2 Contact ID 2 Yellow Contact Key 2 Contact ID 2 Red Contact Key 2 Contact ID 2 Volume Control 2 (Users may access entry through a key, if defined.) Night Volume Override 2 Silence Buzzer 2 Show Faults (momentary) 2 Show Faults (Toggle) 2 Reset DVA message usage 2 4 Edit User Details 3 Select User 3 Name 3 Paging Priority 3 Chimes 3 Log Out Period 3 PIN Number 3 Options 3 View Current Faults 3 Page 12 of 30

13 Mute Buzzer 3 See Fault LEDs 3 Node Fault LEDs 3 View Fault Count 3 View Fault Log 3 Accept Faults 3 View Panel Status 3 View Paging Volume 3 Change Paging Volume 3 View BGM Volume 3 Change BGM Volume 3 Change Volumes By Node 3 Override Chimes 3 Reset Panel 3 Reset SS2N System 3 View Busy Status 3 View Alert/Evac Status 3 Echo Group Selects 3 Edit Volumes 3 Edit Node Volumes 3 Load Current volumes as Day Settings 3 Load Current Volumes as Night Setting 3 Edit Nodes 2 Learn Nodes on system 2 Manually edit nodes on system 2 Edit Faults 3 Edit Fault Text 3 Fault Tone 3 Continuous Siren 3 Pulsed Siren 3 Continuous Hi-Lo 3 Pulsed Lo-Hi-Lo 3 Mute 3 Blank fault texts 2 (resets fault texts to default values) Set Clock 3 Site Details 3 Site Name 3 MPP Insert Node 3 Night Service Mode 3 4 On/Off 3 4 Night Time Attenuation 3 (Only used if no Night Time volumes loaded) Keep Selects 3 (See for explanation) Evacuate Priority 2 Alert Priority 2 Systems functions Reset Panel Rest Network Test Mode 2 About 1 Product Name Internal Name Version Copyright Notice Site ID (read from SS2N) Station Code Version (read from SS2N) Page 13 of 30

14 7 Initial Set Up Make sure all relevant information is to hand (see 5.2 Planning, page 9). For information on using MPC paging consoles with a SigNET LS system, see the SigNET LS manual, document number DCR Connection SS2N Connect the unit to the SS2N system, and make sure that the SS2N rings are intact. (See the SigNET LS manual, DocNo.DCR ) Fireman s automatic Log In device If fitted this is usually a manual call point (break-glass). It has a monitored input with 470Ω representing switch closed (log-in) and 6k8Ω representing switch open. If it is not fitted, a 6k8Ω resistor must be fitted internally across the Molex header marked Login. 7.2 SS2N configuration In order that the paging console will be monitored correctly the SS2N system must be configured appropriately. (See the SigNET LS manual, DocNo.DCR ) Monitoring The Serial Port Insert node should be configured with a tick in the monitor controller box. (See the SigNET LS manual,docno.dcr ) Phantom In order that the audio from the console to the SS2N system is correctly monitored the audio insert node must have phantom switched on. (See the SigNET LS manual,docno.dcr ). 7.3 Understanding how to use the paging console The paging console fascia has three areas; 1. The top of the console has the LCD display, fault and OK LEDs, and the up, down, tick and cross keys. 2. The middle section holds the configurable keys. The most common use for these keys is zone selection, but other possibilities are available as described above. 3. The bottom section holds the All Call, push-to- talk (PTT), and Chime keys Status LEDs There are two fault and one power LEDs. The Fault LEDs only operate if the user is set to see them. By default all users can see them; however, if the console is to be used as a non-primary console (i.e. fault logging is provided elsewhere) this may be disabled, particularly if the microphone is being used as a general paging microphone, rather than a life-safety one. Fail LED. This LED is on only if the unit has an internal failure. An internal failure will not necessarily stop a unit from operating, but should be attended to as soon as possible. Page 14 of 30

15 Internal failures are not directly entered into the log, but they are reported to the SS2N system, which in turn puts an entry into the log. Fault LED. This signifies a fault on the SS2N system, such as fault on a loudspeaker circuit, etc. Power LED. As long as the console is powered up, this is always on Menu System (LCD, up, down, tick and cross keys) The LCD, up down, tick and cross keys are used to navigate the menu system. The up, down, tick and cross keys may be used in one of four ways, depending on context. Menu Navigation Up = previous menu option at this level Down = next Menu option at this level Tick = select this menu option Cross = Go back to higher menu level. Number Entry Up = Increase number (up to maximum value) Down = Decrease number (down to minimum value) Tick = accept this number Cross = Abort (Revert to original value of the number.) This does not exit from numeric entry. Use Tick to exit. Text Entry Up = Next letter (A B, B C, etc). Down = Previous Letter (B A, C B, etc) Tick = accept letter and move to next. Cross = Exit. List Up = Previous Entry in List Down = Next Entry in List Tick = Toggle value (present/not) Cross = Exit. 7.4 Basic Configuration of the Console There are a number of aids to help set up the system correctly. Although the console can be set up with an incomplete or faulty SS2N system, it is much simpler if the main system is set up properly and all faults are cleared (see above). While building work continues a fault-free system cannot be guaranteed. In order to make set-up easier, the default configuration allows the open user more access than would normally be the case, Powering up There is no on/off switch on the console. It is powered automatically from the rack, and must be permanently live to allow proper fault monitoring. To power up simply plug the CAT-5 lead into the correctly wired wall socket see 4.6 on page 6). The fault buzzer will probably start to operate almost immediately. The unregulated user can, by default, silence the buzzer as follows: You should see the following (if the unit has a default configuration on power up) xx Faults on System for options XX:XX:XX XX/XX/XX Page 15 of 30

16 or possibly SigNET (AC) Ltd for options XX:XX:XX XX/XX/XX With the date and time to the right. If you see the entry screen xx Faults on System to log in XX:XX:XX XX/XX/XX Then the unregulated user does not have any options available, and you will need to log in as the engineer to silence the buzzer. Assuming that the buzzer is active, press the key. The following menu should appear: > Mute Buzzer View Panel Status Press the key again to mute the buzzer. Note that intermittent faults (such as marginal faults on amplifiers) will cause the buzzer to re-trigger Logging on as Engineer Only the Engineer may configure the console. The first stage therefore is to log on as the Engineer. If no user is logged in, then the second line of the LCD will either display [ for options] or [ to log in] If it is the first, then press to show the options. Use the key to select the option [ to log in] and press the key to start the log in process. From the list of users, select Engineer, or press the Zone 2 key. Press the key. Enter the PIN number, or press the zone keys corresponding to the Engineer PIN. By default this is 4444, but it should be changed after configuration to prevent unauthorised tampering. (Staff on most sites will either know or get to know this PIN number and this will allow them to alter settings without your knowledge!). Keep a record of this number and do not lose it as there is no backdoor PIN and without it the unit will have to be returned to the manufacturer for resetting Nodes on the system These can be defined in one of two ways, automatically or manually. The easiest method is automatically. This can only be done on a console connected to a fully configured SigNET LS system. The console does this by attempting to select each node in turn. If the process succeeds the node is assumed to be present. If not, it is assumed to be not present. To enter this mode, once you have logged in as the Engineer, select the option [Nodes on System] and then the sub-option [Learn Nodes On System]. If all goes well, this will quickly learn the nodes on the system, and then start to go very slowly as it looks for nodes that are not present up to the maximum value of 128. At this press the key to abort the process. This action will cause two things to happen; Firstly a list of available nodes will be stored on the console (for retrieving audio output node volume levels, for example), to allow correct key configuration, and secondly for each node found (up to 16), the corresponding zone key will be configured to select that node. This is enough to check that the console is working. To manually configure nodes present (or modify the existing list), log in as Engineer and select the option [Nodes on System] and then the sub-option [Mark Nodes On System]. Page 16 of 30

17 This presents you with a node list, with current valid nodes ticked. See how to modify lists in the 7.3.2, page 15, Menu System Setting the Insert Node for the Microphone Make sure you are logged in as the Engineer and select the menu option [Edit Site Details], followed by the option [Edit Insert Node]. Use the up, down and tick keys to select the correct insert node for the console Setting the Time and Date Make sure you are logged in as the Engineer (see page 16) and select the menu option [Change Date/Time]. You should get a display similar to the following (the date and time may be different): Date: / 01 Time: 13 : 02 : 49 The and symbols bracket the field that is currently being changed. Use the up & down arrows to change the value and the tick key to move to the next field. When you have accepted the final field the date and time on the real time clock on board will be updated to the new value Changing Unregulated Paging Priority Normally a paging console will be used to page without the need to log in. Before testing the paging function, we need to verify that paging will be issued at the correct priority. Each user (including the Unregulated User) has a paging priority. By default the Unregulated User has a priority of 30. This value is suitable for most installations, but if it is necessary to change it, use the following procedure. 1. Log in as Engineer (see ). 2. Select the menu option [Edit User]. 3. Select the user [Unregulated]. (This name may have been changed!). 4. Select the menu option [Change Paging Priority]. 5. Change the value to the required new value Changing Chimes for unregulated user If you have just changed the paging priority, select the option [Set Paging Chime Values]. If not, then log in as Engineer, select the [Edit User] menu option, and select the unregulated user as in first. There are four options: No Chimes, 1 Chime, 2 Chimes or 3 Chimes. (Note: for users other than the unregulated user, there is an additional option to be the same as the unregulated user.) Once you have done this (unless you have selected no chimes) you will be allowed to say how long a chime operates for. This facility is provided to allow for custom chimes, but these are not currently supported. The default value is suitable for the standard chimes of an SS2N system Testing Paging Make sure that you are logged out. Select the area you wish to test by pressing the appropriate zone key(s). Press the PTT key. Instructions/comments appear on the LCD display, telling you if an area is busy or chimes are being broadcast. When you get the message [Speak now] you may speak clearly into the microphone, do not whisper or shout. Page 17 of 30

18 8 Advanced Configuration Options 8.1 Key Configuration DVA Keys DVA keys control pre-recorded Digital Voice Announcement messages. Method of use. These keys put the paging console into DVA mode for a particular message. In this mode, selection keys select the areas at message priority (not user priority) and pressing the PTT triggers the message. Exit from the DVA mode by pressing the DVA key again, or change to an alternative DVA mode by pressing another DVA key. Each key is tied to a single message. Whilst in DVA mode for that key, the key will illuminate steady when selected (not playing) and flash when playing. Setting up a DVA key. Before starting it is necessary to know the node number of the audio insert node for the message, the priority of the message and the type of message. The type of message affects the colour of the key LEDs. This can be a useful visual aid, but usually is not required in which case use message type other for all message types. To configure the key, log in as Engineer, and select the option [Edit Key]. All of the key LEDs will flash. Press the key that you wish to program as a DVA key. Select the menu option [View/Change Key Function]. Select the menu option [DVA Select] Select the key type. [Evacuate Message] will use red LEDs. The default message text is [Evacuate], the default priority is 10 and the default insert node is 1. [Alert Message] will use yellow LEDs. The default message text is [Alert], the default priority is 15 and the default insert node is 2. [Other Message] will use green LEDs. The default message text is [General], the default priority is 25 and the default insert node is 4. Edit the DVA text if required (next option shown), up to 31 characters. Modify the priority if required (shown after text edit). Modify the insert node as required (shown after the priority) Background Music Keys Method of Use. An insert node is associated with each background music key. Pressing the key the first time enters background music mode for this source. Pressing it a second time reverts to paging mode. Pressing the PTT key also leaves background music mode. In background music mode, all nodes currently playing music from the source associated with the key are shown green. New areas can be added or removed by pressing the appropriate zone key. Setting up a Background Music Key. Before starting it is necessary to know the node number of the audio insert node for the music source. To configure the key, log in as Engineer, and select the option [Edit Key]. All of the key LEDs will flash. Press the key that you wish to program as a Background Music key. Select the menu option [View/Change Key Function]. Select the menu option [BGM Group Select]. Modify the insert node if required (shown next). Page 18 of 30

19 8.1.3 Volume Control Key SigNET LS MPC Range Installation and Configuration Guide Method of use. Pressing this key causes the unit to enter volume update mode, which is a menubased mode. Pressing again causes the mode to be exited. Precisely how this behaves will depend on the authority of the user. Volumes may be modified either on a node-by-node basis, or in groups. Normal operation is by groups, so by default only the Engineer has the ability to change volumes on a node-by-node basis. If a user is given the facility to modify nodes individually, he will be given a menu option that allows him to either select the node, or select by group (by pressing the select keys). He will then, depending on selection, go to the volume control screen for nodes, or for groups. If a user does not have that authority, he will only be able to select on a group basis, and will go straight to the volume control screen for groups. Volume Control Screen for Nodes. The user will be able see either the current paging volume level for the selected node, or the current background music (BGM) volume level, or both, depending on authority. The use of this screen to control volumes is identical to the Volume Control Screen for Groups, and both are described under Changing Volumes below. Volume Control Screen for Groups. Visually this is the same as the Volume Control Screen for nodes, but zones affected are selected by pressing the appropriate Group Selection keys and/or the ALL CALL key. The volume shown is that of the first node in the group, and if any volume changes are issued, all selected zones will be changed to the new value. Changing Volumes. Regardless of authority to view volumes, a user must also have authority to change volumes before any volumes can be changed. By default, all users can both view and change both paging and BGM volumes. The screen will look something like the one below: Paging Volume: BGM Volume: 0.0 db -1.5 db Press the to toggle between paging volume and BGM volume (if allowed) and use the up and down keys to vary the volume. Setting up a Volume Control Key. To configure the key, log in as Engineer, and select the option [Edit Key]. All of the key LEDs will flash. Press the key that you wish to program as a Background Music key. Select the menu option [View/Change Key Function]. Select the menu option [Control Volumes] Night Volumes Key Method of use. This key overrides night service mode (also see section 9, page 25 on how to set up night service mode). Night service mode changes the volumes on the site so that, for example, nonemergency paging is quieter at night. The LED on the key is illuminated if night service mode is active, and off if not (regardless of whether the mode was entered automatically or by pressing the key). To override the current setting, turn the key on or off. The key operates even if the automatic mode is off, so a purely manual night service system can be implemented if required. Setting up a Night Volumes Key. To configure the key, log in as Engineer, and select the option [Edit Key]. All of the key LEDs will flash. Press the key you wish to program as a Background Music key. Select the menu option [View/Change Key Function]. Select the menu option [Toggle Day/Night Volumes]. Page 19 of 30

20 8.1.5 Silence Alarm Key SigNET LS MPC Range Installation and Configuration Guide This key allows the fault buzzer to be silenced without the user needing to select a menu option. The key will flash when the buzzer is active. To configure the key, log in as Engineer, and select the option [Edit Key]. All of the key LEDs will flash. Press the key that you wish to program as a Silence Alarm key. Select the menu option [View/Change Key Function]. Select the menu option [Silence Alarm] No Operation Sometimes a key s programming is no longer required. It may, for example, have been temporarily configured for test purposes. To remove a key s functionality, log in as Engineer, and select the option [Edit Key]. All of the key LEDs will flash. Press the key that you wish to remove the functionality from. Select the menu option [View/Change Key Function]. Select the menu option [Not Used] Group Keys These are used to select a group (of one or more) nodes for other operations such as paging, sending messages, and so on. To configure the key, log in as Engineer, and select the option [Edit Key]. All of the key LEDs will flash. Press the key that you wish to program as a Group key. Select the menu option [View/Change Key Function]. Select the menu option [Group Select] or [Group Select (not in All Call)]. The difference between these options is that nodes defined in [Group Select (not in All Call)] are not automatically added to the all call key (unless they are also used on another key of type [Group Select]). The next option allows [Contact ID]. This is for advanced use, and should be left at zero unless instructed to the contrary by a SigNET employee. Finally you will see a list of nodes, with those currently in the group displayed with a beside them. The tick key toggles whether the currently selected node is in the group or not. When the group list is correct, press the key to exit the process Other Key Options There are a number of other key options (Remote Contact, Remote Contact Pair, Red Contact Key, Yellow Contact Key and Green Contact Key). All of these are for advanced use with WCTLs (SigNET s proprietary scenario controller) and should only be used under direction of SigNET staff. 8.2 User Configuration The console is designed so that different users can have different levels of access and different priorities, etc. There are 4 general purpose users, 3 specialised users and the Unregulated User, which controls how the console operates when no one in particular is logged in. In practice, very few use this facility, and almost exclusively the Unregulated User uses the unit. Page 20 of 30

21 8.2.1 Selecting a User to Change To change a user s options, log on as Engineer or as Supervisor, then select the menu option [Edit User], and choose the user whose properties you wish to change. Each specific option is detailed below Changing a User s Name Log in as Engineer or Supervisor and select the user to edit as described in Then select the option [Change User Name]. The current name will be displayed, which you may edit using the text entry mode described in Changing a User s Paging Priority Log in as Engineer or Supervisor and select the user to edit as described in Then select the option [Change Paging Priority]. The current paging priority will be displayed, which can be changed by using the up and down arrows. Confirm the new value with the tick key. A user s paging priority affects the level at which a user s paging is issued. It does not affect the priority at which messages are sent Changing a User s Chime Count A user s chime count specifies the number of chimes that are heard before a user starts to page. On most systems, all users have the same chime count, and by default the system is set up this way. However, you could set it up so that, e.g., normal users have two chimes, but the fire officer has three. By default all users use the Unregulated User s value, so changing this value changes all users simultaneously. To change a user s chime count, log in as Engineer or Supervisor and select the user to edit as described in Then select the option [Set Paging Chime Values]. Select a new value from the options presented which are: 1. Default (see unregulated user) (Not shown for the unregulated user) 2. No Chimes 3. Single Chime 4. Double Chime 5. Triple Chime Once selected (except for Default & No Chimes) you are asked how long a delay to use for the chimes to play. You should not need to change this value. The value determines how long a delay is imposed before the user is told he can speak when paging User Log out period If a user is logged in and the unit is left inactive for a considerable period of time (by default, 60 seconds), the unit will automatically logged out. Some long running functions (for example learning nodes on the system) do not time out, but most do. One exception is the fire officer. If he is logged in by break glass operation, he will not be logged out until the break glass is restored. By default, if he is logged in by PIN number he will never be logged out either, because a Fire Officer s function may involve long periods of activity while the situation is being assessed or developing. To change a user s log out period, log in as Engineer or Supervisor and select the user to edit as described in Then select the option [Change Logout Period]. The current value will be shown. Use the up and down arrow keys to change the value, and tick to accept. Page 21 of 30

22 8.2.6 Change User PIN SigNET LS MPC Range Installation and Configuration Guide To change a user s log out period, log in as Engineer or Supervisor and select the user to edit as described in Then select the option [Change User PIN]. Enter the new value, either using the up, down and tick keys, or using the select keys (1-9 = 1-9, 10 = 0), just as if you were logging in Other User Options These entries control access to the paging console and are either on ( ) or off. The options are: 1. View Current Faults. Allows the user to see any currently active faults (but not the fault log or any fault LEDs). If this option is on, the user will be able to hear the alarm buzzer (unless the alarm option is set to mute). 2. Mute Buzzer. Allows the user to silence the fault buzzer. If this option is on, the user will be able to hear the alarm buzzer (unless the alarm option is set to mute). 3. See Fault LEDs. Allows the user to see the fault LEDs. If this option is on, the user will be able to hear the fault buzzer (unless the alarm option is set to mute) 4. Node Fault LEDs. This option determines whether any fault on any node in a group should be shown against the corresponding group as a yellow fault indication. 5. View Fault Count. This option determines whether the current fault count (if not zero) should be visible to the user. 6. View Fault log. Determines whether a user can view a history of the last 99 faults that have occurred on the system. Note that this is independent of the ability to view current faults. 7. Accept Faults. Determines whether a user can mark faults as accepted. When all faults have been accepted, the buzzer will mute (if it has not been muted by other means). This option is meaningless unless the View Fault Log option is also ticked. 8. View Console Status. Determines whether a user has access to the menu option that allows all self-monitored status values to be viewed. 9. View Paging Volume. Modifies the action of the Volume Control menu and Volume control Keys by hiding the Paging Volume line if the option is disabled. 10. Change Paging Volume. Modifies the action of the Volume Control menu and Volume control Keys by disabling the ability to change the Paging Volume if the option is disabled. 11. View BGM Volume. Modifies the action of the Volume Control menu and Volume control Keys by hiding the Background Music Volume line if the option is disabled. 12. Change BGM Volume. Modifies the action of the Volume Control menu and Volume control Keys by disabling the ability to change the Background Music Volume if the option is disabled. 13. Volumes by node. Modifies the action of the Volume Control menu and Volume control keys by disabling the ability to select individual nodes for volume control if the option is disabled. Only the ability to change group volumes is enabled. 14. Override Chime. Determines whether the user can turn chimes on and off with the Chime key. 15. Reset Console. Determines whether the user can reset the console. It is recommended that only the Engineer have access to this option. 16. Reset SS2N Ring. Determines whether the user can reset the SS2N network. It is recommended that only the engineer have access to this function. 17. View Busy Status. Determines whether the user can see if an area is busy before he attempts to page it. Most sites prefer to have this option set for all users. 18. View Alert/Evac Status. Determines whether the user can see if emergency messages are playing into areas. 19. Echo Group Selects. This is an advanced option that should only be set on if instructed by SigNET staff. Page 22 of 30

23 8.3 Fault Options Fault Descriptions. SigNET LS MPC Range Installation and Configuration Guide Each node on the system has one of four possible fault types associated with it; In order to help faultfinding, the texts associated with these faults can be edited. Note that local fault texts and network faults (ring break, etc.) cannot be edited. To change fault texts, log in as the Engineer or Supervisor and select the menu option [Edit Fault Options] followed by [Edit Fault Text]. Select the node to change from the following list. Then select the fault to edit and change it as described in above. The changes will be immediately reflected in the fault log and current faults screens Edit Fault Tone Many specifications say that the fault warning must be different from any other fault warning that may be heard so this function changes the tone heard when a new fault appears. To change the fault tone, log in as Supervisor or Engineer and select the menu option [Edit Fault Options] followed by [Edit Fault Tone]. Choose from the following options: 1. Continuous Siren 2. Pulsed Siren 3. Continuous Hi-Lo 4. Pulsed Lo-Hi-Lo 5. Off As each option is selected, the appropriate tone will be heard. Note that it is often useful to turn the fault tone off during commissioning, but it is essential that it is turned on again prior to handover. 8.4 Change Clock. To change the clock, log in as the Supervisor or Engineer; select the option [Change Date/Time]. The date and time will be shown. Use up, down and tick keys to edit each field in turn (the current field is shown by the and symbols). 8.5 Site Details Site Name This is the text displayed when no one is logged in and there are no faults on the system (or the unregulated user cannot see the fault count). By default this says [SigNET (AC) Ltd]. To change this, log in as the Supervisor or Engineer, select the option [Edit Site Details], followed by the option [Edit Site Name]. Change it as described in above Insert Node for Microphone Make sure you are logged in as the Engineer and select the menu option [Edit Site Details], followed by the option [Edit Insert Node]. Use the up, down and tick keys to select the correct insert node for the console Night Service Mode See section 9 page 25 for a detailed description on how to set up and use Night Service Mode. Page 23 of 30