Page 1 AES 7705ii MultiNet Receiver System User Manual AES Corporation 285 Newbury Street Peabody, MA 01960-1315 USA Tel (978) 535-7310 • Fax (978) 535-7313 www.aes-corp.com Copyright © 2018 AES Corp. All Rights Reserved 40-7705ii-UM Rev. 1 June 11, 2018...
Page 2 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.
Page 3: Table Of Contents
AES 7705ii MultiNet Receiver Table of Contents Product Description: ....................6 About AES IntelliNet: ................... 6 MultiNet Receiver: ....................6 7170 IP-Link Transceivers: ................... 7 Document Conventions: ..................7 Safety Considerations: ....................9 Technical Specifications: ....................9 Front Panel – Software Version: ................. 10 Rear Panel: ......................
Page 4 Admin GUI for Configuration and Administration:..........31 Server Configuration ................... 33 Define Business Units: (you must have at least one) .......... 34 Add a Business Unit – Alarm Automation Settings..........37 Business Unit Overview ..................42 Modify a Business Unit ..................43 Subscriber Database Setup ..................
Page 5 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..................
Page 6: Product Description
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...
Page 7: 7170 Ip-Link Transceivers
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 RS-232 serial COM port, send it out a printer port or perform whatever function the application is designed.
Page 8 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 purposes of redundancy. Page 8 40-7705ii-UM Rev.
Page 9: Safety Considerations
2.0 Safety Considerations: All equipment must be installed in accordance with National Electric Code, applicable UL Standards and local building codes. No user serviceable parts. Do not open enclosure. Unplug power before installing or removing unit. 3.0 Technical Specifications: The 7705ii is in a standard 2U 19” rack enclosure configuration. Operating voltage: 120 VAC, 60 Hz.
Page 10: Front Panel - Software Version
Front Panel – Software Version: The front panel has the user display and controls. Figure 3-1 shows a view of the front panel. Figure 3-1 3.1.1 LCD Display and Software Version: The LCD is a 4-line display with 20 characters per line. It shows messages for the 7705ii. Use this in conjunction with the Alert panel to interpret and acknowledge messages.
Page 11: Rear Panel
 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.
Page 12 Power Section Modem Single Board Computer Connection Section Figure 3-4 3.2.1 Power Section: Contains the power input connector and power supply On/Off switch as described below: Also contains the Power Supply fan.  Power input connector: Plug the female end of the supplied AC power cord into this connector and the male end of the power cord into a 120 VAC, 60 Hz receptacle supervised by a UL Listed UPS or a UL 1481 power supply.
Page 13 3.2.3 Single Board Computer Connector Section: Contains connectors for computer peripherals.  Serial Port 1 / (COM 1): [/dev/ttyS1] Used to connect to alarm monitoring system for signals communicated via RS-232. Appendix E for a list of Alarm messages generated. ...
Page 14: 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. Once properly configured and connected to a LAN, a network workstation is used to access and configure the receiver remotely.
Page 15: Software Installation
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.  7705ii must be installed in a UL Listed metal rack-mounting cabinet that complies with UL-60950 standard for IT equipment.
Page 16 Figure 4-1 Single MultiNet Receiver Connections to a 7170 for Initial Setup Page 16 40-7705ii-UM Rev. 1 June 11, 2018...
Page 17 Figure 4-2 Dual MultiNet Receiver Connections to Remote 7170 IP-Links thru Local Network Page 17 40-7705ii-UM Rev. 1 June 11, 2018...
Page 18 Figure 4-3 Dual MultiNet Receiver Connections to Remote 7170 IP-Links thru Internet Page 18 40-7705ii-UM Rev. 1 June 11, 2018...
Page 19: System Startup And Access
System Startup and Access: AES ships the 7705ii MultiNet Receiver with the Linux operating system and IP-Link 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.
Page 20: Power Down - Information
Power Down - Information: The power to the 7705ii should not just be removed without going through the proper shut down procedure. DO NOT REMOVE POWER OR TURN OFF POWER of the 7705ii 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.
Page 21: Linux Command Line
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 7705ii using VNC Viewer or your workstation program as instructed by the person or persons responsible for your configuration.
Page 22: The Gui Desktop And The Aes Menu
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”.
Page 23: Start The Terminal Program
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.
Page 24: Setting Time
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 = minutes .ss = seconds MM = month DD = day CCYY = 4 digit year...
Page 25: Review Your Tcp/Ip Configuration
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...
Page 26: Suggested Tcp/Ip Settings For Second Multinet Receiver
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.
Page 27 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 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”...
Page 28 In the xterm terminal window, enter the following command to initiate the script to modify the configuration of Ethernet port 1 (eth0). ./editnetworketh0<Enter> 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.
Page 29: Testing Tcp/Ip Configuration
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.
Page 30: User Logout From Directly Attached Keyboard & Monitor
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.
Page 31: Admin Gui For Configuration And Administration
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.
Page 32 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.
Page 33: Server Configuration
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"...
Page 34: Define Business Units: (You Must Have At Least One)
 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.
Page 35 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. Business Units can also be used to separate elements of your operation;...
Page 36  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”...
Page 37: Add A Business Unit - Alarm Automation Settings
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.
Page 38 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.
Page 39  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”...
Page 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.
Page 41 Figure 6-7 Add a Business Unit - continued A partial view of the final screen indicating a successful add, is shown below. Figure 6-8 Add a Business Unit – completed Page 41 40-7705ii-UM Rev. 1 June 11, 2018...
Page 42: Business Unit Overview
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.
Page 43: Modify A Business Unit
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...
Page 44: Subscriber Database Setup
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”.
Page 45  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.
Page 46  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”...
Page 47: Alarm Data
Alarm Data There are several modifiable parameters that control data sent to the alarm monitoring system by ipctrl. 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 button on that screen.
Page 48: Close Your Browser When Finished With Admin Gui
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.
Page 49: Workstation Access And Login
7.0 Workstation Access and Login: Once properly configured, the 7705ii 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.
Page 50: Installing Vnc Viewer
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.
Page 51: Using Vnc Viewer
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.
Page 52: After Login
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: The GUI Desktop and the AES Menu:...
Page 53: Multinet Receiver Programs And Utilities
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.
Page 54: Multinet Utility Programs And Scripts
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...
Page 55 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.
Page 56: Special Purpose Circuits
Special Purpose Circuits: Listed below are some of the special purpose circuits to monitor for specific 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.
Page 57: Aes Menu In The Gui Desktop
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.
Page 58: Managing Users
9.0 Managing Users: Generally, users are created and managed within the MultiNet system through the creation of the Business Unit. See Define Business Units section. 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.
Page 59: Changing A User's Password
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.
Page 60: Change Admin Gui Access - Username And Password
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.
Page 61: Test New User Login
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 Section 9.2 Retrieving user Display Number Password:.
Page 62: Admin Gui Database Functions
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.
Page 63: Routing Table Screen
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.
Page 64: Ip-Link Status Screen
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.
Page 65: Close Your Browser When Finished With Admin Gui
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.
Page 66: Iplinkctrl (Ipctrl) Network Management Software
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”...
Page 67: Ipctrl Function Groups
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 <Alt>...
Page 68: Using The Pick List Pop Up To Select A Subscriber Id
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 <Enter>...
Page 69: The Message Function Group
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.
Page 70 Explanation of the Message Group Functions: Function Explanation • Sends text messages to a remote subscriber SEND TEXT MESSAGE • Press <ALT>+<A> unit. To receive the data, the remote unit must or <ALT>+<M>, then <S> have a 7041 Hand Held Programmer attached or •...
Page 71: Control Function Group
• Queries a remote unit for its model number (GET) SUBSCRIBER MODEL & REV (e.g. 7750F, 7450, 7050E, etc.) and its firmware • Press <ALT>+<M>, then <8> revision number. This information is stored in or Press <ALT>+<E> the database. • Select Target Unit •...
Page 72 Explanation of the Control Group Functions: Function Explanation • Re-enables transmitting on a remote subscriber unit that TURN ON TX • Press <ALT> + <C> has been turned off (see Turn Off TX, next). • Press <1> • Select Target Unit •...
Page 73 • Enables / Disables the subscriber units ability to be a SUBSCRIBER REPEATER FUNCTION repeater. • Press <ALT> + <C> • Works with Version 2 or higher subscriber units. • Press <5> • Select Target Unit CAUTION: Disabling the repeater capability may cause •...
Page 74: Programming Function Group
11.7 Programming Function Group: Figure 11-12 Program Pull Down Menu To access the Programming function menu group, hold down the <Alt> key and Press . The pop-up illustrated above will appear. Use the arrow keys to highlight a function and press the <Enter> to select it. Proceed by selecting your target unit, choosing a route of communication and then editing the presented form.
Page 75 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”...
Page 76 • 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.
Page 77 Function Explanation RADIO PACKET LIFE • Press <ALT> + See below for details on data entry for this function: • Press <R> • Select Target Unit • Select Route • Edit form as necessary Radio Packet Life – Data Entry Screen: Figure 11-14 Radio Packet Life Version 2.1 subscribers include the “Time-To-Live”...
Page 78 • 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.
Page 79 Function Explanation CONTROL RELAY OUTPUT • Press <ALT> + See below for details on data entry for this function: • Press <C> • Select Target Unit • Select Route • Edit form as necessary Control Relay Output – Data Entry Screen: This feature controls optional relay outputs (part number 7065) for model 7050 Subscribers units.
Page 80 Function Explanation ZONE CONFIGURATION • Press <ALT> + See below for details on data entry for this function: • Press <Z> • Select Target Unit • Select Route • Edit form as necessary This function configures alarm zone inputs for a premise unit. It is important to know which type of unit is being programmed.
Page 81 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.
Page 82 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...
Page 83 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.
Page 84 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.
Page 85 Function Explanation AUTOMATIC TEST SUPERVISION See below for details on data entry for this function: • Press <ALT> + • Press <A> • Select Target Unit • Edit form as necessary Automatic Test Time Supervision – Data Entry Screen: This feature enables the IPCtrl software to monitor automatic test timer check-ins.
Page 86: Data Radio Function Group
11.8 Data Radio Function Group: Figure 11-24 To access the DataRadio function group, hold down the <Alt> key and press <D>. 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 &...
Page 87 Function Explanation PRINT ALL DATABASE ID’s This function sends a listing of all ID’s that are in the • Press <ALT> + Database to the printer port. • Press • Click function • View available data This function displays a list of Units that are “routed VIEW PATHS/THRU •...
Page 88 Function Explanation EDIT RADIO FORWARD Forwarding is a function that causes the IPCtrl software to TABLE transmit a data packet to a remote Subscriber upon the • Press <ALT> + reception of a specific event by the same or another •...
Page 89  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. The following options are available: In some cases the only information forwarded is a message indicating that a packet of the selected type was sent and not the data itself, STAT →...
Page 90: System Function Group
11.9 System Function Group Figure 11-28 The Systems Function group menu is accessed by holding <Alt> and pressing <Y>. This group contains functions related to the operation on the software. Explanation of the System Group Functions: Function Explanation • Quickly cancels an unacknowledged packet sent to a sub- Abort Outbound Packet scriber unit by the receiver.
Page 91: Interpreting Screen Messages
11.10 Interpreting Screen Messages SAMPLE Check-In Message: The following information can be extracted from the sample message above: The message was received on September 15 at 12:57:01 The sequential packet number assigned to this packet is 6B The message originated at subscriber unit #9876, and its destination is Unit #0000 (the head end) Subscriber #1234 –...
Page 92: Operation
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.
Page 93: Warranty And Service Procedure
Repack equipment in original or equivalent packaging. Inside the box, please include a contact name, telephone number, address and a brief description of the reason for return. Ship items freight-prepaid to: Repair Services, RMA#__________ AES Corporation, 285 Newbury Street Peabody, MA 01960 USA (Contact AES for Return Material Authorization number.)
Page 94: Appendices
APPENDICES 40-7705ii-UM Page 94 Rev 1 June 11, 2018...
Page 95: Appendix A Common Linux Commands
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}<Enter> cd: change directory clear: clear the screen. cp: copy files grep: find lines matching a certain pattern.
Page 96: Appendix B Server-Generated Lcd Display Messages
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 7705ii. 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.
Page 97 #.## (C)2005-06 AES Server Fault Messages: The server will detect certain LN1 7070 18 E140 fault conditions in the system and light Status LEDs to GRP00 ZONE 0008 indicate the failure. The server will light these LEDs for faults whether alarm automation is on or off line. 07/07/06 12:19 When automation is on line and there is a fault, the Example of an Alarm...
Page 98: Appendix C Software Installation Instructions
Hard Disk Drive becomes unavailable. The CPU and Alert LED will be on and the Alert Sounder will be 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.
Page 99: Appendix D Sharing The Serial Port With Additional Business Units
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.
Page 100 9. Confirm the existence of the needed files with the ls command: ls<Enter> 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”.
Page 101: Appendix E Alarm Output Codes Produced By The Multinet Receiver
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.
Page 102 Event Code Usage for Ademco 685 Output Emulation Event  Code Universal Description AES specific Usage  Fire Subscriber Zone designated for Fire  Burglary Subscriber Zone designated for Burglary Subscriber’s Zone Input Off-Normal  Alarm  Expansion module tamper 7170 IP-Link Transceiver Enclosure Tamper (Zone/contact = 906) ...
Page 103 Example Message Strings Description of Event Produced by an AES Subscribers R1 ACCT 18 E602 00 C000 Automatic Supervisory Check-In. Zone/contact ID = 000 R1 ACCT 18 E140 00 C0nn Alarm Signal or input went active. Zone/contact ID = Zone Number R1 ACCT 18 P140 00 C0nn Prior Alarm.
Page 104 Example Message Strings Description of Event Produced by a MultiNet Receiver or IP-Link Transceiver R1 IPL# 18 E145 00 C906 7170, IP-Link Transceiver Enclosure Tamper ID = 906 R1 IPL# 18 R145 00 C906 7170, IP-Link Transceiver Enclosure Tamper Restore ID = 906 R1 REC# 18 E300 00 C902 LCD offline.
Page 105 Fault and Status Codes (Zone information): AES Subscribers and MultiNet Receiver (not all are used by each device): 800 = No Faults, Unit OK or Restoral of all Prior Faults. 801 = Low Battery - Voltage less than 11.0V 802 = RAM Data error or RAM corrupted - Zone activation will not be reported (Sub.
Page 106 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.
Page 107 Event plus Zone, Status and Fault Codes, Produced for Events Created by Subscribers: 10R1 ACCT A 000 A 000 Automatic Supervisory Check-In A NNN Alarm Signal Zone NNN ‫٭‬ 10R1 ACCT A nnn SA NNN Prior Alarm zone NNN ‫ ٭‬Input still active. Reported during Status Request or Check-In 10R1 ACCTSA nnn R NNN...
Page 108 Event plus Status and Fault codes, AES MultiNet Receiver: Diagnostic Fault - “RAM Data error or RAM corrupted” 10R1 IPL# Y 802 Y 802 Diagnostic Fault - “U11 RAM Chip missing or Internal Battery Bad” 10R1 IPL# Y 803 Y 803 Diagnostic Fault - “Reserved”...
Page 109 Line Card SIC used in Optex Morse Genesys 824 Alpha Signal format: 1RRLssssssACCTEEsNNNs<0x14> Line card 2 and SIC Not Supported by MultiNet system Line Card # 3 Contact ID received from IntelliTap. Events are translated. Signal format: 1RRLssssssACCTEEsNNNs<0x14> See “Line card #1”, “Signal format” in “Radionics 6500 compatible output” for Key to codes used in signal format for Line Card #3 above.
Page 110 Event Codes with numbers R4XX will be reported as: C NNN where NNN is the Point ID or Contact ID number All other Contact ID Event Codes will be reported as: Y XXX where XXX is a copy of the event code. OR SY XXX when PXXX is the event and where XXX is the Point ID or Contact ID number Note: AES recommends not using Radionics 6500 emulation, when using IntelliTap to report Contact ID.
Page 111: Appendix F Printer Messages Produced By The Multinet Receiver
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.

AES Corporation IntelliNet 7705ii User Manual

1 Product Description

2 Safety Considerations

3 Technical Specifications

4 Installation and Setup

5 System Startup and Access

6 Admin GUI for Configuration and Administration

7 Workstation Access and Login

8 Multinet Receiver Programs and Utilities

9 Managing Users

10 Admin GUI Database Functions

11 Iplinkctrl (Ipctrl) Network Management Software

12 Operation

13 Warranty and Service Procedure

Appendices

Appendix A Common Linux Commands

Appendix B Server-Generated LCD Display Messages

Appendix C Software Installation Instructions

Appendix D Sharing the Serial Port with Additional Business Units

Appendix E Alarm Output Codes Produced by the Multinet Receiver

Appendix F Printer Messages Produced by the Multinet Receiver

Quick Links

Need help?

Questions and answers

Related Manuals for AES Corporation IntelliNet 7705ii

Summary of Contents for AES Corporation IntelliNet 7705ii

Table of Contents