FIBER SENSYS FD525 Application Note
  1. Manuals
  2. Brands
  3. FIBER SENSYS Manuals
  4. Measuring Instruments
  5. FD525
  6. Application note

FIBER SENSYS FD525 Application Note

Apu networking
Hide thumbs
Table of Contents

Advertisement

Quick Links

APU Networking
Application
Note
Confidential – Limited Distribution
AN-ESW-006 APU Networking Rev G

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FD525 and is the answer not in the manual?

Questions and answers

Related Manuals for FIBER SENSYS FD525

Summary of Contents for FIBER SENSYS FD525

  • Page 1 APU Networking Application Note Confidential – Limited Distribution AN-ESW-006 APU Networking Rev G...
  • Page 2 This manual is provided by Fiber SenSys, Inc. While reasonable efforts have been taken in the preparation of this material to ensure its accuracy, Fiber SenSys, Inc. makes no express or implied warranties of any kind with regard t o the documentation provided herein.

  • Page 3: Table Of Contents

    Contents Introduction ......................... 4 Physically connecting an APU to the network ..............5 Networking Enabled APUs Overview ..................5 Logging the Hardware (MAC) Address ................... 6 Configuring the network settings on the APU ..............6 ® Lantronix DeviceInstaller Overview ..................6 Locating an APU using DeviceInstaller ...................

  • Page 4: Introduction

    This feature allows many APUs connected into a local-area network (LAN) to integrate with an existing head end, or other annunciator/monitoring equipment. The physical network supported by Fiber SenSys APUs is 10/100 wired Ethernet and the networking protocol supported is TCP/IP.

  • Page 5: Physically Connecting An Apu To The Network

    Networking Enabled APUs Overview As of 2015, the entire 500 Series, FD322, and FD348R APUs have networking capability by default. The FD33X and FD34X series products are available with networking optionally and are identified by having “IP” in the model name. If you cannot locate the network port on your FD33X or FD34X series APU, it may be that your APU does not support networking.

  • Page 6: Logging The Hardware (Mac) Address

    DeviceInstaller Overview ® ® Fiber SenSys APUs use Lantronix XPort embedded Ethernet device servers for network communication. To configure the XPort device, you must use Lantronix’ DeviceInstaller software. Install and run the software on a PC connected to the same physical network as the APU.

  • Page 7: Locating An Apu Using Deviceinstaller

    NOTE: This will locate all XPort devices on your network, regardless of whether they are APUs or other non-Fiber SenSys devices. If the MAC address for an APU is not shown in DeviceInstaller, then the APU is not reachable on the physical network. This typically means that it is not physically connected to the network.

  • Page 8: If You Do Not Know The Ip Address That You Want To Assign Or You Prefer To Use A Dynamically Assigned Ip Address (Dhcp)

    Figure 4: Launching the assign IP wizard 3. Observe that the IP Assignment wizard window appears as shown below. The rest of this section will describe how to use the wizard to assign an address. Figure 5: IP Assignment Wizard If you do not know the IP address that you want to assign or you prefer to use a dynamically assigned IP address (DHCP): 4.

  • Page 9: Configuring The Network Settings

    Note: These values are specific to your network. If the default values of these fields are not sufficient consult your network administrator to determine the correct values. Figure 6: IP Settings screen 9. Click the Assign button to apply the entered setting to the APU. This may take some time to complete.
  • Page 10 2. In the address box of the browser, enter the IP address that was previously assigned to the APU: Figure 8: Entering the APUs IP address into the browser 3. Press the Enter key. A login screen will appear as shown on the following page. Figure 9: XPort device login screen 4.
  • Page 11 5. Determine whether the connection to the APU will be incoming or outgoing. a. Incoming connections are made by the monitoring equipment to the APU. This is used with for integration with the Fiber SenSys Integrator software for Lenel OnGuard or Milestone XProtect.
  • Page 12 10. Serial and network settings are complete. Close the browser window. The APU is now ready for network operation. If you have any problems or questions with the process of setting the APU up in your network, contact Fiber SenSys Customer Service.

  • Page 13: Appendix A Identifying The Network Port

    Appendix A Identifying the Network Port The following images should assist with the identification of the proper RJ-45 jack on APU models that also support accessory modules. Refer to your APU model’s manual to identify the exact location of the jack. CAUTION: For APU models that provide support for accessory modules, it is important to use the proper jack for the network port, because the APU may not operate correctly (even for other functions) if the improper jack is used.

  • Page 14: Appendix B Configuring Apus With Older Xports

    Appendix B Configuring APUs with older XPorts Fiber SenSys APUs manufactured during 2014 or earlier have an older version of the XPort firmware that requires additional effort to set up. The web page for such devices looks like this: Figure 15: XPort Device Server Configuration Manager home screen.

  • Page 15: Connection Settings

    APU will be incoming or outgoing, so please refer to the appropriate figure. a. Incoming connections are made from external equipment to the APU. This is used for integration with the Fiber SenSys Integrator software for Lenel OnGuard or Milestone XProtect. i. set the Accept Incoming menu to Yes ii.
  • Page 16 Outgoing connections are made from the APU to external monitoring equipment. This is used for integration with Fiber SenSys FiberCommander. i. set the Active Connect menu is set to Auto Start ii. In the Endpoint Configuration section of the Connection Settings...

  • Page 17: Apply The New Settings

    Configurable Pin Settings The final step is to set configurable pins. Select the Configurable Pins option from the main menu. The Configurable Pin Settings screen displays. Figure 19: The Configurable Pins Settings screen 2. Make sure all radio buttons for Direction and Active Level are set as shown above, to ensure proper communication with the APU.
  • Page 18 5. Configure the monitoring equipment/software using the instructions provided by the manufacturer. If you have any problems or questions with the process of setting the APU up in your network, contact Fiber SenSys Customer Service.

  • Page 19: Appendix C Software Integration Of Apus

    Software developers using the Device SDK do not need to understand the communications protocol used by the APU. Moreover, Fiber SenSys reserves the right to modify and adjust the protocol itself over time. However, the rest of this section provides information that can be useful in constructing software that attempts to communicate with APUs using the protocol.

  • Page 20: Apu Communication Behavior

    APU Communication Behavior Fiber SenSys APUs implement a specific behavorial state machine for communication. A flowchart roughly describing the state machine is displayed below. Later subsections will describe the communication states in more detail. Figure 21: APU network communication flowchart...

  • Page 21: Establishing Communication

    Establishing Communication As noted in the communication flowchart, the APU sends a platform status report (PSR) every 20 seconds and a ping response every 130 seconds in order for the system to identify the APU and to determine whether to communicate with it. When a ping request is received, the APU sends the handshake messages shown below.
  • Page 22 Figure 23: Ping request Figure 24: Ping Response The <DeviceName> field in the <DeviceIdentification> blocks is shown in the above illustrations as CUSTOMNAME. The actual value should correspond with the name of the APU with a maximum length of 15 characters. The maximum channel name length is also 15 characters, while the <RequestorIdentification>...

  • Page 23: Events

    Events There are three types of events recognized by the APU: • Intrusion or alarm • Fault (a bent or broken fiber or a hardware malfunction) • Tamper (indicating that the device enclosure has been opened) When any type of event occurs, an ID field index, <ID>SZ0001</ID>, is updated. This ID field acts as an event counter.
  • Page 24 Figure 26: Fault message...
  • Page 25 The <DetectionEvent> field displays the value Fault. A <Device Status Report> always follows this message indicating that since the fault has occurred an intrusion can no longer be detected device. <DeviceState> field indicates Fault, <CommunicationState> field shows the communication status as Fail. When the fault condition is repaired, the following message indicates that the internal fault condition has ended, and communication is restored.
  • Page 26 Figure 28: Tamper message If an APU is connected to a tamper switch (either directly or through a Fiber SenSys accessory device such as the OM525), a tamper alarm is signaled when the switch opens. This condition is indicated by <DeviceState> and <DetectionEvent> field values of Tamper.

  • Page 27: Platform Status Report

    Platform status report Events, alarms, and faults affect the status of the APU. Whenever the device state changes, a platform status report, or PSR, is immediately sent to notify the system and users. Figure 29: Platform status report...

  • Page 28: Apu Configuration Parameters

    Each status report includes the same basic information as shown in this sample: <DeviceName>CUSTOMNAME</DeviceName> - this tag indicates the name of the APU and must correspond with the actual device name. The notation HZONE-X and ZONE-X indicate the affected hyperzone and zone. <DeviceState>Secure</DeviceState>...
  • Page 29 Figure 30: Device configuration document This document includes, as a minimum, the following tags: <DeviceIdentification> - this parameter must be the actual name of the unit being addressed, or the unit will not respond. The notation HZONE-X indicates the affected hyperzone. <ConfigurationSettingName>...

  • Page 30: Moving Zones (Specific To 500 Series Apus)

    Moving zones (specific to 500 Series APUs) When you move a zone from one hyperzone to another, using the 500 Series Suite software, an XML report is sent to notify the remote system of the change. For example, suppose a system has one hyperzone, HZONE-1, which contains two zones, ZONE-1 and ZONE-2, and ZONE-1 is moved to a newly created hyperzone, HZONE-2.
  • Page 31 Figure 32: PSR indicating a zone move, part 2 Figure 33: PSR indicating a zone move, part 3...

Table of Contents