What the Executone IDS Installation Manual Actually Covers
The Executone IDS Installation Manual is the primary reference document for deploying Executone's IP Device System. This isn't a single book, it's a collection of documents that change depending on which generation of IDS hardware you're working with. The system uses IP networking to connect notification appliances, control panels, and endpoint devices instead of traditional hardwired loops. If you've been around fire alarm work for a while, the basic concept is similar to addressable systems, but the networking layer adds a whole other set of problems that show up on the jobsite.Downloading the Executone Ids Installation Manual
The most recent versions live on the Honeywell/Interlogix support portal since Executone was acquired years ago. You'll need a registered account to access the current PDFs. The older documents, especially for IDS-1000 series and earlier, sometimes float around on contractor forums but those are unverified. Stick to the official source because page numbers matter when you're troubleshooting in the field. If you're working on a legacy system, you may find the manuals indexed by part number rather than by system model, which is annoying but manageable if you know your unit's label.The manual typically runs 80 to 150 pages depending on the revision. It covers power requirements, network topology, device addressing, zone programming, and firmware update procedures. Some editions include a quick-start section that's actually useful, but most of the dense information is in the later chapters.
What Happens When You Actually Install This Stuff
The first thing you need to understand is that IDS devices talk to each other over Ethernet using a proprietary protocol layered on top of standard TCP/IP. That means you can run them over regular Cat5e or Cat6, but you also need to think about VLANs, switch configuration, and PoE budgets in a way that traditional fire alarm installers aren't used to. I ran into this on a hospital retrofit where the IT department had the entire medical equipment network on a separate VLAN and the IDS devices couldn't reach the main control panel because of an unconfigured trunk port. We spent three hours talking to two network engineers before realizing the switch had port security enabled and was blocking the devices' MAC addresses. The workaround was to configure the switch ports with static MAC address bindings for each IDS device and disable the dynamic port security on those specific ports.Power and Network Basics
Most IDS endpoint devices draw power through the network cable using PoE. Your switch needs to support IEEE 802.3af or the newer 802.3at standard depending on the device model. The installation manual will have a power budget table that you actually need to reference before you buy switches. I've seen contractors order managed switches that looked fine on paper and then discover mid-install that the total PoE draw exceeded the switch's power capacity. The system would partially boot, devices would drop off the network randomly, and troubleshooting that looks nothing like a normal power issue because everything stays online intermittently.Network cabling should be rated for the environment. In a commercial building this usually means CMP or CMR rated cable depending on whether it's running in plenum spaces. The manual doesn't stress this enough because it's basic fire alarm knowledge, but it's where people slip up when they're new to IP-based systems.
Addressing and Configuration
Each IDS device gets a unique IP address, usually assigned through DHCP with reservations, though manual static addressing works too. The system uses a hierarchical addressing scheme where devices are organized by floor, zone, and position. The software you use for configuration is called IDS Configurator, and it scans the network to discover devices automatically. This is one area where the manual is fairly thorough.The counter-intuitive part is that device addressing on an IDS system isn't purely physical. You can move a notification appliance to a different switch port or even a different building segment and re-address it in software without rewiring anything. This is powerful but also means your documentation needs to stay current. I've worked on systems where someone moved a speaker along the corridor during maintenance and never updated the configurator file, which caused a mismatch between the printed address labels and what the panel actually thought was connected. When the inspection came up, the authority having jurisdiction flagged the discrepancy and the whole system failed the test.
Get the Full Details
Common Pitfalls That the Manual Doesn't Highlight
DHCP scope exhaustion is a real problem on larger installations. If your network doesn't have a dedicated DHCP scope or reserved address pool for the fire alarm system, the IDS devices can grab addresses from the wrong pool or lose them when the lease expires. This causes devices to disappear from the panel during normal operations, which triggers trouble conditions that look like hardware failures. Set up a static DHCP reservation list or configure the IDS controllers to use static IP addresses exclusively.Another issue that comes up repeatedly is switch redundancy. If your IDS system relies on a single switch for all communication and that switch fails, the entire system goes down. The manual mentions backbone redundancy but doesn't emphasize how critical it is for life safety systems. Use managed switches with redundant power supplies and consider running the system across at least two switches with proper spanning tree configuration. This adds cost but prevents a single point of failure that nobody would catch until it's too late.
Firmware Updates
The IDS controllers and endpoint devices receive firmware updates periodically. The installation manual includes a section on this but it's easy to rush through. Always back up the current configuration before updating firmware. I lost an entire building's IDS configuration once because the update process corrupted the controller's memory during a power fluctuation. The system came back online but all the zone assignments and device mappings were gone. There was no backup on file because the contractor who installed it didn't save one. That's a lesson I never forgot.Testing and Commissioning
The manual outlines a commissioning procedure that involves verifying every device on the network, checking audio output levels for speakers, and confirming that all notification appliance circuits respond correctly to each fire alarm sequence. This is where the networking aspect becomes visible because you need to verify not just that devices work, but that they respond within the required time frames. IP networks introduce latency that traditional hardwired systems don't have, and while that latency is usually minimal, it needs to be measured and documented.Use a network switch with port mirroring capability to capture traffic between the controllers and endpoint devices during testing. This gives you visibility into packet loss and retransmission events that could affect system reliability. The manual doesn't discuss this level of testing, but it's something I learned from doing enough of these installations to see where things break in practice.
