AES 7705i MultiNet Receiver System User Manual AES Corporation 285 Newbury Street. Peabody, Massachusetts 01960-1315 USA Tel (978) 535-7310.
NOTICE TO USERS, INSTALLERS, AUTHORITIES HAVING JURISDICTION, AND OTHER INVOLVED PARTIES This product incorporates field-programmable software. In order for the product to comply with the requirements in the Standard for Control Units and Accessories for Fire Alarm Systems, UL 864, certain programming features or options must be limited to specific values or not used at all as indicated below.
AES 7705i MultiNet Receiver Table of Contents 1.0 Product Description:............................................................................................... 6 1.1 About AES IntelliNet: ........................................................................................... 6 1.2 MultiNet Receiver: ................................................................................................ 6 1.3 7170 IP-Link Transceivers: ................................................................
6.0 Admin GUI for Configuration and Administration:......................................... 31 6.1 Server Configuration ........................................................................................... 33 6.2 Define Business Units: (you must have at least one) .......................................... 34 6.3 Add a Business Unit – Alarm Automation Settings. ........................................... 37 6.4 Business Unit Overview ..........................................................
11.2 Common data entry/selection menus and pop-ups:............................................. 67 11.3 Using the pick list pop up to Select a Subscriber ID ........................................... 68 11.4 Selecting a Route for Communication with a Subscriber Unit ........................... 68 11.5 The Message Function Group: ............................................................................ 69 11.6 Control Function Group........................................................................
1.0 Product Description: This document discusses the installation, configuration and use of the various programs and hardware in the AES MultiNet Receiver uses. This Receiver is the heart of the AES MultiNet system. All properly configured 7170 IP-Link Transceivers (see section 1.4) will send their received AES●IntelliNet packets to this Receiver via TCP/IP over a LAN, WAN, the Internet or if necessary and equipped, via Modem (as backup), for distribution to the appropriate application or external system.
Other programs in the MultiNet receiver evaluate and distribute the data to an appropriate application on this machine or another located on the LAN, WAN or Internet. These other applications may re-distribute the data, store it in a database for later retrieval, send it out a local RS232 serial COM port, send it out a printer port or perform whatever function the application is designed.
Typical MultiNet System It is highly recommended and required for UL systems that a redundant MultiNet Receiver be operational at the head end and that any location of 7170 IP-Link Transceivers have at least two for the purpose of redundancy.
2.0 Safety Considerations: All equipment must be installed in accordance with National Electric Code, applicable UL Standards and local building codes. Unplug power before opening enclosures to avoid electrical shock. 3.0 Technical Specifications: The 7705i is in a standard 2U 19” rack enclosure configuration. Operating voltage: 120 VAC, 60 Hz. +/- 10% Operating current: 0.
3.1 Front Panel: The front panel has the user display and controls. Figure 3-1 shows a view of the front panel. Alert Sounder DATE: TO: FROM: RE: Tactile Response Sounder LCD Display Power Button Status Panel Alert Panel Figure 3-1 3.1.1 LCD Display: The LCD is a 4-line display with 20 characters per line. It shows messages for the 7705i. Use this in conjunction with the Alert panel to interpret and acknowledge messages.
• Automation: Red Led - Indicates that the Alarm Automation process is unable to get Acknowledgements from a designated alarm monitoring system. • RF Interference: Red Led - Indicates that an RF interference condition exists and that signals may be hindered. RF interference is a condition where the Carrier Detect (CD) in the transceiver is active for more than 20 seconds. This LED will turn off if CD turns off for 100 milliseconds.
3.2 Rear Panel: The rear panel contains the connectors used to attach external connections, peripherals such as the monitor, keyboard, mouse and power. The main power switch is also located on the rear panel. The rear panel is divided into at four sections as outlined below. Figure 3-4 shows a view of the rear panel. Power Section Modem Single Board Computer Connection Section Printer Port Figure 3-4 3.2.
3.2.3 Single Board Computer Connector Section: Contains connectors for computer peripherals. • Serial Port 1 / (COM 1) Upper: [/dev/ttyS1] Typically used to connect to alarm monitoring system for signals communicated via RS-232. See Appendix E for a list of Alarm messages generated. • Serial Port 2 /(COM 2) Lower: Unavailable. Not Used. • Monitor, CRT (J8): Plug the video monitor into this Jack.
4.0 Installation and Setup : A separate “Initial Installation and Setup Guide” is provided to guide you through the initial installation and setup. A standalone Receiver requires a monitor, keyboard and mouse for user interface. See Figure 4-1. The standalone configuration is not recommended by AES Corporation for anything other than initial setup and preliminary testing of the system.
Notes: • • • • • • • Power Line, router/ switch, and telephone connections shall not leave the room where the AES equipment is installed. This must be accomplished by co-locating outlets and interfacing equipment in the room where AES equipment resides. 7705i must be installed in a UL Listed metal rack-mounting cabinet that complies with UL864. The cabinet must be provided with integral outlets and the ability to connect AC input via conduit.
Figure 4-1 Single MultiNet Receiver Connections to a 7170 for Initial Setup Local 16.5 Volt AC Transformer Default IP Address = 192.168.0.11 Intended for initial Setup and testing ONLY This configuration is used for initial setup only! Monitor, Keyboard and Mouse not to be left connected during normal operation.
Figure 4-2 Dual MultiNet Receiver Connections to Local 7170 IP Links thru a LAN AES Part Number 52-0054 EMR Corp Model 65610 Local 16.5 Volt AC Transformer Default IP Address = 192.168.0.11 UL 497B Surge Protector 2nd Local 7170 as shown above. UL 497B Surge Protector Suggested Address = 192.168.0.22 Optional Internet connection 2nd 7705i Receiver as shown below. For redundancy.
Figure 4-3 Dual MultiNet Receiver Connections to Remote 7170 IP-Links thru Internet Remote nd 2 Remote 7170 Default IP Address 192.168.0.11 Consult with IT Dept. 16.5 Volt AC Transformer Refer to equipment separation note in IP-Link Manual 40-7170 Acquire IP Addresses from IT Dept. UL 497B Surge Protector UL 497B Surge Protector Off Site Remote Location Customer Provided UL Ethernet Hub Internet Head End - Location of 7705i MultiNet Receivers Acquire IP Address from IT Dept.
5.0 System Startup and Access: AES ships the 7705i MultiNet Receiver with the Linux operating system and IPLink programs pre-installed and with basic configuration already complete to operate as shown in Figure 4-1. Each installation will have site-specific parameters that would typically be changed or entered during initial installation and setup. Refer to separate guide for assistance with initial setup.
5.3 Power Down - Information: The power to the 7705i should not just be removed without going through the proper shut down procedure. DO NOT REMOVE POWER OR TURN OFF POWER of the 7705i MultiNet Receiver WITHOUT USING THE PROPER SHUT DOWN PROCEDURE! This receiver is a Linux server and improper shut down could damage files and prevent operation. There are several ways to shut down a Linux server. Linux provides a command named “shutdown ” to perform this function.
Figure 5-1 Command Line Screen If your system’s configuration is a dual UL or a non-UL system that is configured for remote access only, then your installation most likely does not or will not have a directly attached keyboard, monitor or mouse. Connect to the 7705i using VNC Viewer or your workstation program as instructed by the person or persons responsible for your configuration. See “Workstation Access and Login:” 5.
5.7 The GUI Desktop and the AES Menu: Note: Access to this menu must be password protected for supervisors control only. The Linux GUI Desktop used in the AES MultiNet Receiver is the Motif Window Manager (MWM). It is configured as a blue screen with no icons. The normal mouse curser is a white trimmed black “X”. If you loose or unintentionally close the MWM, you can restart it by typing the following command at a command prompt: startx.
5.8 Start the Terminal Program: Some of the utilities needed to configure the MultiNet receiver are accessed from a command line. A terminal emulator program named xterm is an offered selection from the AES menu available by use of the right click on the desktop. The terminal program provides a command line, which can be used to run utilities mentioned above. Start the terminal emulator by selecting the “New Terminal” item in the AES Menu.
5.9 Setting Time: Time is very important and somewhat complex in a MultiNet System. Use the Linux date command to set the time as shown in one of the following examples: Where hh = hour MM = month mm = minutes DD = day .ss = seconds CCYY = 4 digit year date MMDDhhmm.ss date MMDDhhmmCCYY.ss date 10031055.00 Sets the time to Oct 3, 10:55:00 AM using current year For additional information on the date command, use: man date Press Q to exit man program. 5.
5.12 Review your TCP/IP Configuration: The TCP/IP parameters of all TCP/IP devices must be properly configured in order for the MultiNet Receiver to communicate with any local or remote IP-Link Transceiver(s), and any other TCP/IP devices it needs to communicate with. As stated before, if you are connected as shown in Figure 4-1 using the 7170 that was shipped with your receiver, then no configuration is needed for the pair to be operational.
5.14 Suggested TCP/IP Settings for Second MultiNet Receiver The table below shows some suggested settings for the TCP/IP devices in the second MultiNet Receiver / 7170 IP-Link Transceiver pair of a dual system. These suggestions should be appropriate for a network that is only made up of devices from a MultiNet System. If you are connecting to an existing network you must get these values from the administrator of that network.
In a Linux environment there are usually several ways to accomplish the editing of parameters and similar tasks. Following are instructions for using programs or scripts provided by AES for the purpose of setting up the TCP/IP parameters of each port. A script provided by AES for configuring these parameters is initiated by entering either the command “./editnetworketh0” or “./editnetworketh1” from a command line prompt. You will be instructed when to enter the above command, for now, read on.
In the xterm terminal window, enter the following command to initiate the script to modify the configuration of Ethernet port 1 (eth0). ./editnetworketh0 Don’t forget to first type the dot and forward slash “./”. The following window for the KWrite text editor with the configuration file for Port 1 should appear. Use caution as incorrect settings could disable the system, especially if it were already configured.
5.17 Testing TCP/IP Configuration: Before you can test the TCP/IP configuration you need to make the connection of the Ethernet Port(s) to the target network. Once TCP/IP setup is complete and the Ethernet cables are connected to an operational network, perform the following test to determine if your MultiNet Receiver is working properly in the network. To test your settings, ping another computer or device that is on your network.
5.18 User Logout from directly attached keyboard & monitor: You should log out the user that is logged in (usually root), when local access using the directly attached keyboard, monitor and mouse, to your system is no longer need. Depending on where you are and what you are doing the procedure will vary. Several options are outlined below. Option 1: Logout (preferred method) With this option you will log out and go back to the aes login screen. 1.
6.0 Admin GUI for Configuration and Administration: The Admin GUI is a set of files located in a directory linked to “Admin” under the Apache “htdocs” directory. To access this Admin GUI you need to connect using a Web Browser from a network workstation. The Apache Web Server running on the MultiNet receiver protects this connection with 128 Bit SSL Encryption. Some possible URL’s used to access the GUI are: http://192.168.0.101/Admin/home.
Once you get to the Admin GUI Homepage, there is a brief overview of the functions available through the GUI. There are links in the left hand column of this page and every page that can be used to select actions. Below is a sample screen from the Admin GUI. The following sections describe the functions of the Administration program.
6.1 Server Configuration Among the first parameters that must be configured are on the Server Configuration page. AES ships the receivers pre-configured as indicated throughout this manual. To review or edit the parameters, access the Admin GUI Server Configuration screen as indicated above and click on "Server Configuration" on the left hand side of the screen.
6.2 • Verbose: Controls the amount of information written to limited size log files. A pull down menu allows you to set this parameter to Off, On or Full. In most cases, the Off setting should be used, so that only critical messages are written to the log files. If more information about system operation is required, the On setting can be used. The Full setting should only be used at the direction of AES support personnel. This is an “Event” log.
Some systems will only have one type of application data and one access point, and thus will need to create only one Business Unit. If you have multiple types of data and need multiple remote access locations, define a Business Unit for each data type and or remote user. For example, if you have subscriber units that send GPS data, and subscriber units that send alarm data, you would need to define two Business Units.
• Alarm Automation System: If you have an Alarm Automation or monitoring system, check the “Alarm Automation System” checkbox. You will be presented with a data entry screen to enter its parameters. See following pages for screen examples and data fields. NOTE!: If a Business Unit will utilize a serial port that has already been configured and assigned to another Business Unit, DO NOT SELECT THE “Alarm Automation System” CHECK BOX.
6.3 Add a Business Unit – Alarm Automation Settings. Figure 6-5 Automation Settings o Alarm Automation System Settings: If the Check-In, Alarm, Status, Trouble and Restore messages produced by a subscriber unit will be monitored by an alarm automation system or monitoring software, you need to configure these parameters. Failure to do so may prevent vital messages like AC failure, Low battery and other faults from being reported. You must check the “Alarm Automation System?” checkbox.
WARNING! AVOID ERROR MESSAGES Be sure there is a functioning Alarm Automation system properly attached and in service on the configured port and or IP address, ready to receive signals immediately after the parameters are saved. Messages may be generated and any enabled heartbeat needs to get its proper responses.
Heartbeat: Enter the number of seconds between heartbeat signals on the IP port from Alarm Automation. The heartbeat is an upper case “S” when in Ademco 685 emulation. You should add a period of time as a window that the signal may be sent. Example: If your Alarm Automation sends an “S” every 20 seconds, you may want to set this parameter to 40.
Some Alarm automation systems may not be configured to properly report these types of messages. You may have some other reason not to send these to automation but, be aware, these are important messages as they indicate zones that are possibly stuck, improperly configured, improperly wired or in an alarm condition and may not be able to report a new event. Options are: Individual Subscriber Unit settings control delivery… , which is configured for each Subscriber in its configuration settings.
Figure 6-7 Add a Business Unit - continued A partial view of the final screen indicating a successful add, is shown below.
6.4 Business Unit Overview Once you have created at least one Business Unit you can select Overview to view its information. Below is a sample partial screen that shows several Business Units. You can select an underlined link, to view details. Figure 6-9 Business Unit Overview Below is a sample compressed screen that shows the details for the underlined link MySecurityOne.
6.5 Modify a Business Unit Select in Business Unit Details screen to make any changes. The following combined screens image may appear different depending on the type of Business Unit. Leave these fields blank if this BU will be linked to another that is already configured to use the Serial Port to alarm automation. Selecting a different receiver number for each BU will produce a unique alarm message for each. This affects the receiver number in the string of characters sent to alarm automation.
6.6 Subscriber Database Setup Each subscriber unit needs to be configured and assigned to a Business Unit, Subscriber configuration allows you enter the IDs of your units individually, or as a range of IDs within the same Business Unit. Add subscribers by clicking the link on the left hand menu, “Add” under “Subscribers”. Figure 6-12 Add Subscriber You will first be prompted to select the Business Unit to assign the added Subscriber. • 40-7705I-UM Business Unit: Select from the pull down list.
• After selecting the Business unit, click on The following fields will be presented. Figure 6-13 Add Subscriber to Business Unit Screen • Subscriber ID: The Add page first asks if you want to configure a single subscriber or a range of subscribers. Configuring a range of subscribers can be convenient if you have a series of subscriber units, consecutively numbered, for the same Business Unit.
• Enter optional address information in fields Line 1, Line 2, City, State, Zip and Country if desired. Once fields are edited select “Add Subscriber” button, the next screen will display the data you entered for verification. If displayed data is correct, click the “Insert Subscriber” button to add the subscriber to the database. If it is incorrect, use the “Back” button of your browser to return to the Add Subscriber page to make corrections.
6.7 Alarm Data There are several modifiable parameters that control data sent to the alarm monitoring system by ipctrl. See Appendix E for a listing of generated messages. You can also modify alarm data at a later time by viewing detailed data for the subscriber then clicking the screen.
When you have modified the fields click to accept any changes. The Add Alarm Data screen will ask you to verify the alarm data before it is added to the database. Figure 6-17 Add Alarm Data – Insert Alarm Data When you add a range of subscribers, you can configure identical alarm parameters for all subscribers in the range. If any subscribers need certain parameters to be different, you can then use the Modify Alarm page to change the parameters for individual subscribers. Figure 6-18 Alarm Data Added 6.
7.0 Workstation Access and Login: Once properly configured, the 7705i can be accessed by using programs running on a workstation. There are as usual multiple configurations and programs that will accomplish this task. As you have already experienced, password protected Web access to the Admin GUI is available as described in Section 6.0. Access using VNC Viewer should have been configured and be running.
7.2 Installing VNC Viewer: ● From a Windows workstation PC, start a Web browser and enter the URL of the Admin GUI on a MultiNet Receiver as described in Section 6.0. From the main or home page of the Admin GUI there is a link on the bottom of those available on the left side of the screen that can be used to download a copy of the VNC Viewer program.
7.3 Using VNC Viewer: From a Windows workstation PC, start the VNC Viewer by using the shortcut created in the previous section. The following screen should appear. Figure 7-1 VNC Connection Details Window Type into the “VNC server:” box, the IP address and Display number separated by a colon, of the MultiNet Receiver’s VNC Server Display you are attempting to access. The Display number is the unique number created for the user.
7.4 After login: • You should be presented with the Linux MWM GUI Desktop. You will now be able to start the authorized programs and perform functions you need to operate, configure and maintain the system. An example of the desktop screen as seen using remote access follows: Figure 7-3 Remotely accessed GUI Desktop Instructions for using the GUI Desktop can be found in: Section 5.
8.0 MultiNet Receiver Programs and Utilities: There are a number of programs, scripts and special purpose circuits that are installed in an AES MultiNet Receiver. Some are programs that are installed by AES to make your Linux Server a MultiNet Receiver. Others are utilities used to configure and maintain it. There are also a number of others that are part of the operating system installation. Also included are special purpose circuits for monitoring the proper operation of the programs and hardware.
8.2 MultiNet Utility Programs and Scripts: Listed below are some of the more commonly used programs, utilities and script files provided by AES or your Linux installation to manage, configure and maintain your MultiNet Receiver 1- Admin GUI 4- cleanLCD 2- aesctrl 5- editnetworketh0 3- chpass 6- editnetworketh1 1- Admin GUI: (Graphical User Interface) The Admin GUI is essentially a collection of Web pages that an administrator can use to manage a MultiNet System.
3- chpass is script is used to change the password of a user created by the new Business Unit function in the Admin GUI Web pages. You will be asked for the username and new password. Passwords must be exactly 8 characters made up of case sensitive letters and numbers. New passwords will take affect after executing this command because the VNC Server session for the user that the password is changing will be shutdown and restarted within this script. 4- cleanLCD Clears alarm messages on the LCD display.
8.3 Special Purpose Circuits: Listed below are some of the notable special purpose circuits whose purpose is to monitor certain faults or the proper operation of the MultiNet Receiver. 1- Watchdog Timer / Hung process detection 2- Power Supply Overheating Detection 1- Watchdog Timer / Hung process detection: Many of the critical programs in the MultiNet Server suite are providing a pulse to a Watchdog circuit on the LCD Board.
8.4 AES Menu in the GUI Desktop: There are no desktop shortcuts on the MultiNet Receiver’s GUI Desktop. Use the AES Menu to access some of functions that are available. Other functions are available from the command line prompt. This menu is only available for root user access. See Section 5.7 1- New Terminal – Shortcut to start the xterm terminal emulator used to get a command line prompt.
9.0 Managing Users: Generally, users are created and managed within the MultiNet system through the creation of the Business Unit. See section 6.2. Within a server environment a user would be given specific access rights to areas on a server where they could do things such as view, create, delete, modify and other actions to files while limiting access to areas where they do not need to be. This protects the system and other users.
9.3 Changing a user’s Password: AES has provided a script for use in changing the password of a user that already exists. Only the root user can change passwords using this script. Warning! This script should also successfully change the password for user root, but be very careful as the VNC Server for the user is stopped and restarted during this process effectively disconnecting you if the password being changed is for the root user and you are connected via VNC Viewer.
9.4 Change Admin GUI Access - Username and Password: The username and password used to gain access to the Admin GUI is factory set as username = Admin; Password = peabody. It is highly recommended that this password be changed. Not changing it means that anyone who knows or discovers the server could use the Admin GUI Web pages to modify and possibly disable your system. The factory default passwords are published. Follow these steps to change the username and password for Admin GUI access.
9.6 Test new user login: New user access should be tested after creating a Business Unit or changing a password. Read or confirm the new password and Display number from the file user_info as described above in Section 9.2. Log in using the new login information to verify the proper creation/modification of the user. ● If you are working from a remote workstation, you can test as outlined below: o Determine the display number and password by looking in the user_info file.
10.0 Admin GUI Database Functions: Once your AES MultiNet system is up and running, and has received signals from Subscribers, you can use the Admin GUI access to monitor Subscriber activity history. Admin GUI is usually accessed from your remote PC. 10.1 Subscriber Overview Following is a portion of the screen that is displayed when you select Subscriber / Overview. To review details about a specific unit select a Business Unit from the pull down and then click .
10.2 Routing Table Screen: Once you have configured your Business Unit(s) and added Subscribers you can go to the ipctrl program discussed later in this manual, to view live traffic and manage your network. Data will be stored in the various databases as traffic comes in. You can then return to the Admin GUI and review that data using the following screens. You can view Routing information by selecting a link located in the Business Units area of the Admin GUI.
10.3 IP-Link Status Screen: You can also view the status of IP-Link transceivers as shown in this partial screen view accessed from SysOp / IPLinks: Figure 10-6 IP-link Transceiver Status Screen 10.4 Get Signal History: Alarm data that is stored can also be viewed. The following screen, accessed by selecting SysOp / Alarms, lets you select the specifics about the alarm data you wish to view.
Shown in the following Figure is an example of a Signal History Screen for a Subscriber with an ID of 1010: Figure 10-8 An example Alarm Data (Signal History) Screen 10.5 Close Your Browser When Finished With Admin GUI: To help secure your MultiNet receivers configuration and help to limit unauthorized modifications to your system, you should close your browser when it is no longer needed. For the same reasons, do not leave untended, a workstation that has the Admin GUI Web pages open.
11.0 IPLinkCtrl (ipctrl) Network Management Software: Once your AES MultiNet system is up and running, you can use the IPCtrl program to monitor and manage your network. IPCtrl is usually accessed from the workststion PC that is connected using VNC Viewer. If the program IPCtrl is not running it can be started using the “aesctrl startall” item in the AES Menu, accessed by a right click on the Desktop or by entering the startALL command. IPCtrl is the IP-Link and Radio Management program.
11.1 IPCtrl Function Groups: There are five function groups including “ Message”, “Control”, “Program”, “DataRadio” and “System” They are accessed from the menu bar in the upper part of the screen. Each of the menu bar function groups has an underlined letter. Menu function groups can be selected by holding down the key pressing the function group’s underlined letter on your keyboard please see example on next page: or by clicking on the Menu Item with the mouse cursor. 11.
11.3 Using the pick list pop up to Select a Subscriber ID When a function is chosen from a function group, a “pick list pop-up” appears. You can type in the ID number of the Subscriber unit you wish to contact. Or use the arrow key to highlight the appropriate ID number and then press to select it. Figure 11-3 Pick list pop-up 11.
To manually enter a route to the subscriber unit, select the Manual Path Entry and fill out the manual routing screen as instructed below. Where the first to go thru is the ID of the IP-Link. Figure 11-5 Manual Routing Table Once you have entered your communications route, click OK to send the message to your subscriber unit using the route entered. 11.
Explanation of the Message Group Functions: Function SEND TEXT MESSAGE • Press + or +, then • Select Target Unit • Select Route • Type text message • Press + to send REQUEST STATUS • Press + or +, then <2> • Select Target Unit • Press for route GET SUBSCRIBER ROUTE TABLE • Press + or +, then <4> • Select Target Unit • Select Route GET ALL SUBSCRIBER DATA • Press +, then <5> or Press + • Select Target Unit • Select Route
(GET) SUBSCRIBER MODEL & REV • Press +, then <8> or Press + • Select Target Unit • Select Route (GET) SUBSCRIBER MODE DATA • Press +, then <9> or Press + • Select Target Unit • Select Route (GET) SUBSCRIBER PACKET LIFE SETTINGS • Press +, then or Press + • Select Target Unit • Select Route • Queries a remote unit for its model number (e.g. 7750F, 7450, 7050E, etc.) and its firmware revision number. This information is stored in the database.
Explanation of the Control Group Functions: Function TURN ON TX • Press + • Press <1> • Select Target Unit • Select Route TURN OFF TX • Press + • Press <2> • Select Target Unit • Select Route Explanation • Re-enables transmitting on a remote subscriber unit that has been turned off (see Turn Off TX, next). • Disables a remote subscriber unit should the need arise, such as when an alarm system fails and causes the transmitter to activate repeatedly.
SUBSCRIBER REPEATER FUNCTION • Press + • Press <5> • Select Target Unit • Select Route • Enter D to Disable, E to Enable Repeating • Enables / Disables the subscriber units ability to be a repeater. • Works with Version 2 or higher subscriber units. CAUTION: Disabling the repeater capability may cause problems with the network. Disable repeating for testing purposes only, or for mobile units, which are never to be used as repeaters.
11.7 Programming Function Group: Figure 11-12 Program Pull Down Menu To access the Programming function menu group, hold down the key and Press . The pop-up illustrated above will appear. Use the arrow keys to highlight a function and press the to select it. Proceed by selecting your target unit, choosing a route of communication and then editing the presented form.
will be retrieved from there. If no database entry exists, the factory defaults will be used. To be sure that the pre-filled values represent the current settings in the Subscriber, it is recommended that you retrieve the current parameters from the Subscriber before you edit and send new values. See “Get All Subscriber Data” under the Message Function Group earlier in section 11. • Enter Address: Freeform field to put location reference information.
• Contact Debounce Time (Loop Response) 7050 & 7750/UL only: Programs a debounce delay for the zone inputs of 7050 and 7750/UL subscriber units to prevent input switches or relays from causing nuisance alarms and repeated reports of the same alarm. The default setting is 0.12 seconds. If you choose to change this setting, simply enter the new value and press to move to the next field.
Function Explanation RADIO PACKET LIFE • Press + • Press • Select Target Unit • Select Route • Edit form as necessary See below for details on data entry for this function: Radio Packet Life – Data Entry Screen: Figure 11-14 Radio Packet Life Version 2.1 subscribers include the “Time-To-Live” (TTL) function. Like the Internet, AES•IntelliNet uses a packet-based technology. The Timeto-Live concept in the Internet is based on the fact that all data has a useful life.
• The timeout function works when a packet is stored for forwarding in any subscriber with TTL capability, which will decrement the TTL time for the packet it is storing. When TTL time has expired, the packet is aborted. This function does not work with non-TTL (pre-Version 2.1) subscribers. The TTL feature works best when the majority of subscribers, or the subscribers that are most heavily used, have the feature in the firmware. Call your AES representative for upgrade information.
Function Explanation CONTROL RELAY OUTPUT • Press + • Press • Select Target Unit • Select Route • Edit form as necessary See below for details on data entry for this function: Control Relay Output – Data Entry Screen: This feature controls optional relay outputs (part number 7065) for model 7050 Subscribers units. Using this remote control capability, an operator may open gates, activate cameras or control any devices at a remote location.
Function Explanation ZONE CONFIGURATION • Press + • Press • Select Target Unit • Select Route • Edit form as necessary See below for details on data entry for this function: This function configures alarm zone inputs for a premise unit. It is important to know which type of unit is being programmed. There are separate sub-menus to handle the different subscriber units. The submenu that will be presented upon selection of a subscriber ID is based on the database entries.
previous programming or retrieval. Next you are asked if any zones are to be programmed to respond similar to an "Inverted Fire circuit" or bugler loop. With this option you can select to reverse the logic for the fire input (refer to subscriber manual). This produces an alarm on an open and trouble on a short. If stored in the database, the current programming is displayed. IMPORTANT NOTES: • The zone programming options are limited.
Zone Configuration window for the 7050 DLR/7750 UL Bank 1 - 8 This option row not shown or available if Bank 1 is selected Select Bank Here Use arrows to scroll then click bank number to select. Figure 11-18 The zone configuration control block offers seven options for the programming of each alarm zone: Normally Open Normally Open with Restoral Normally closed Normally Closed with Restoral Bypassed Supervised (Not available on Bank 0, Zone 1-8) Supervised with Restoral.
Zone Configuration window for the 7050E, 7750/F8 and 7788 Figure 11-20 In this Subscriber type, the user has the ability to select an optional Contact ID Event Code to be sent to the Alarm Monitoring System for each of the 8 zones. The former standard produced only an E140, which is typically listed as a General Alarm. Select normal to have an E140 sent to alarm monitoring.
Zone programming window for the 7750-F4x4 and 7744 Refer to the appropriate Subscriber Manual for details on zone writing and programming. This screen below appears if the unit zone information is in the database. Figure 11-22 The Zone configuration pop-up window offers the following options for the programming of each alarm zone.
Function AUTOMATIC TEST SUPERVISION • Press + • Press • Select Target Unit • Edit form as necessary Explanation See below for details on data entry for this function: Automatic Test Time Supervision – Data Entry Screen: This feature enables the IPCtrl software to monitor automatic test timer check-ins. When enabled, it alerts an operator if a subscriber unit fails to report in within the programmed interval, plus 10% + 2 minutes as programmed in the subscriber’s timing Parameters function.
11.8 Data Radio Function Group: Figure 11-24 To access the DataRadio function group, hold down the key and press . The Pop-up screen illustrated at above will appear. Select a function. Proceed by selecting your target unit. Explanation of the DataRadio Group Functions: Function Explanation VIEW ROUTING & STATUS RECORDS This function views on the screen the Routing & Status Records of the selected ID.
Function PRINT ALL DATABASE ID’s • Press + • Press
• Click function • View available data VIEW PATHS/THRU • Press + • Press • Select Target Unit • View available data Explanation This function sends a listing of all ID’s that are in the Database to the printer port. This function displays a list of Units that are “routed through” the selected unit. This is important for demonstrating that a unit has multiple paths available.
Function EDIT RADIO FORWARD TABLE • Press + • Press Select / Enter Origin Unit ID • Edit form as necessary Explanation Forwarding is a function that causes the IPCtrl software to transmit a data packet to a remote Subscriber upon the reception of a specific event by the same or another Subscriber. See below for details on data entry for this function: Edit Radio Forward Table: Figure 11-27 The Forwarding table above is used to configure the event and subscriber to forward the data to.
• • • Select ALARM and/or ZREST plus desired Zones if Forwarding Alarm data is the objective. Select as desired any other type of data or feature that you want forwarded.
11.9 System Function Group Figure 11-28 The Systems Function group menu is accessed by holding and pressing . This group contains functions related to the operation on the software. Explanation of the System Group Functions: Function Explanation Abort Outbound Packet • Quickly cancels an unacknowledged packet sent to a subscriber unit by the receiver. This includes "Get" query functions.
11.
12.0 Operation This section describes two of the modes of operation your MultiNet Receiver may be in and how to operate it. 12.1 Manual Operation The MultiNet receiver defaults to Manual Operation when Alarm Automation is not in use Manual operation of the MultiNet receiver is a mode where alarm and other messages are not being sent to an Alarm Monitoring System. This would occur when the Alarm Monitoring System was offline, down or disconnected.
13.0 Warranty and Service Procedure: AES CORPORATION LIMITED PRODUCT WARRANTY AND TECHNOLOGY LICENSE LIMITED PRODUCT WARRANTY: AES Corporation (“AES”) warrants to the original purchaser that each AES Subscriber Product will be free from defects in material and workmanship for three (3) years from date of purchase and all other products purchased from AES including central station receivers and accessories will be warranted for one (1) year from the date of purchase.
APPENDICES 40-7705I-UM Page 94 Rev 4 March 16, 2007
Appendix A Common Linux Commands Below are some of the more common commands you will be using on the Linux operating system: cat: concatenate files and print on standard output. Ex: cat {filename} cd: change directory clear: clear the screen. cp: copy files grep: find lines matching a certain pattern. Ex: grep {string} {filename} ifconfig: displays current TCP/IP settings. less: filter for viewing files and directories.
Appendix B Server-generated LCD Display Messages. Top line description: The LCD is a 4-line display with 20 characters per line. It shows messages for the 7705i. Use this in conjunction with the Alert panel to interpret and acknowledge messages. There is also a tactile response sounder to provide audible confirmation of successful button activation. In most modes of operation, the top line will be constant and usually displays the LCD firmware version number and AES copyright. #.
#.## (C)2005-06 AES Server Fault Messages: The server will detect certain fault conditions in the system and light Status LEDs to indicate the failure. The server will light these LEDs for faults whether alarm automation is on or off line. When automation is on line and there is a fault, the server will write explanatory messages to the LCD display with additional information regarding the fault.
Hard Disk Drive Failure / Watchdog Timer / Hung process detection: The following is displayed if the COMM FAILED Hard Disk Drive becomes unavailable. The CPU and Alert LED will be on and the Alert Sounder will be VERSION #.## activated. This is an indication that a Hung Process has occurred which will occur for a number of failures including a Hard Disk Failure. Corrective action must be taken before the MultiNet Receiver can be put back into service.
Appendix D Sharing the Serial Port with additional Business Units An additional Business Unit that creates Alarm data to be sent to Automation using an already configured and assigned Serial Port must be linked to the Business Unit originally setup to use that specific serial port. When creating an additional Business Unit, do not select the Alarm Automation System checkbox in the create Business Unit screen.
9. Confirm the existence of the needed files with the ls command: ls There should be a file for each Business Unit. Each file begins with “ipctrl.” immediately followed by the case sensitive name of the Business Unit and ending with “.cfg”. 10. Next, using the cat command, view the contents of the each file and confirm that all files related to an existing Business unit have the same line as instructed to add in step 6 above. 11.
Appendix E Alarm Output Codes Produced by the MultiNet receiver Alarm Output Overview: For many events that occur in the MultiNet system, alarm messages are created and communicated to an automation system. Communicators (Subscribers) in the MultiNet system and the MultiNet Receiver itself generate these events. This appendix is a list and description of those messages. The MultiNet Receiver supports two different alarm output formats.
Event Code Usage for Ademco 685 Output Emulation Event Code 110 130 140 145 200 300 300 301 302 305 307 309 336 350 351 353 354 Universal Description / AES specific Usage Fire / Subscriber Zone designated for Fire Burglary / Subscriber Zone designated for Burglary Alarm / Subscriber’s Zone Input Off-Normal Expansion module tamper / 7170 IP-Link Transceiver Enclosure Tamper (Zone/contact = 906) Fire Supervisory / Subscriber Zone designated for Fire Supervisory System Trouble / Subscriber Zone designated for
ACCT ACCT ACCT ACCT ACCT ACCT 18 18 18 18 18 18 R140 E305 E305 E307 R307 P307 00 00 00 00 00 00 C0nn C901 C902 C8nn C800 C8nn ACCT ACCT ACCT ACCT ACCT 18 18 18 18 18 R354 R354 E356 E370 P370 00 00 00 00 00 C906 C915 C903 C0nn C0nn 40-7705I-UM Page 103 Rev 4 March 16, 2007 ACCT = Subscriber ID Description of Event Produced by an AES Subscribers Automatic Supervisory Check-In. Zone/contact ID = 000 Alarm Signal or input went active. Zone/contact ID = Zone Number Prior Alarm. Input still active.
C906 C906 C902 C903 C912 C911 C80n C907 C910 C910 C904 C906 C906 C905 C906 C907 C907 C908 C906 40-7705I-UM Page 104 Rev 4 March 16, 2007 ACCT = Subscriber ID Description of Event Produced by a MultiNet Receiver or IP-Link Transceiver 7170, IP-Link Transceiver Enclosure Tamper ID = 906 7170, IP-Link Transceiver Enclosure Tamper Restore ID = 906 LCD offline. Zone/contact ID = 902 Loss of LED. Zone/contact ID = 903 AC Failure at IP-Link. Zone/contact ID = 912 Battery Trouble at IP-Link.
Contact ID received through IntelliTap. RLsACCTs18sEEEEsGGsNNNNs 4+2 received through IntelliTap. RLsACCTsCC CC = two digit zone code. 40-7705I-UM Page 105 Rev 4 March 16, 2007 This Information is passed through. Receiver number is set as programmed in the MultiNet setup. Line card is set to 4. Input Signals: In Ademco mode the receiver will respond to 3 inputs or signals from the monitoring system.
Radionics 6500 compatible output format: This mode will provide the output of 3 line cards; line card 1 is for AES subscriber and receiver signals, line card 3 is for Contact ID signals from IntelliTap, and line card 4 is for 4+2 signals from IntelliTap. Contact ID signals are translated into an AES’ Radionics message as outlined under line card # 3 and 4 elsewhere in this appendix.
40-7705I-UM Page 107 Rev 4 March 16, 2007 Automatic Supervisory Check-In Alarm Signal Zone NNN ٭ Prior Alarm zone NNN ٭Input still active. Reported during Status Request or Check-In Alarm or Zone trouble Restoral or input to normal - Zone NNN ٭ Diagnostic Fault - “No Faults, Unit OK or Restoral of all Prior Faults” see Diagnostic Faults below Y 801 Diagnostic Fault - “Low Battery” - Voltage less than 11.
Page 108 Rev 4 March 16, 2007 Diagnostic Fault - “RAM Data error or RAM corrupted” Diagnostic Fault - “U11 RAM Chip missing or Internal Battery Bad” Diagnostic Fault - “Reserved” Diagnostic Fault - “U9 Modem Chip Failed or missing” Diagnostic Fault - “Timing Error between CPU and Modem” Diagnostic Fault - “U11 Ram Chip Read/Write test Failure” Diagnostic Fault - “Modem Loop back Failed” “Low Battery” “Low Battery Restore” “Unknown message revision, invalid report.
Contact ID received from IntelliTap. Events are translated. 1RRLssssssACCTEEsNNNs<0x14> 40-7705I-UM Page 109 Rev 4 March 16, 2007 Event Codes with numbers E1XX and E2XX will be reported as: see exception ♣ A NNN where NNN is the Point ID or Contact ID number ♣ Event Codes with numbers E12X will be reported as: D ( D followed by 4 spaces.
4+2 received from IntelliTap. Events are translated. 1RRLssssssACCTsAssCC<0x14> A = Character A for alarm event. CC = two digit zone code. See “Line card #1”, “Signal format” in “Mode 1 – Radionics 6500 compatible output” for explanation of other signal format codes. 40-7705I-UM Page 110 X.XX this reports the version number of the firmware 301ssAESs7000sVX.
Appendix F Printer Messages Produced by the MultiNet receiver For many events that occur in the MultiNet system, messages are created and printed on the attached printer. These events are be created by the communicators (Subscribers) in the MultiNet system, IP-Link Transceivers and by the MultiNet Receiver itself. There are also a number of reports that can be printed. Following is a list and description of some of those messages.
