> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-ferrite-choke.md). # Ferrite Choke Identify the ferrite choke requirements for Controller 7000 installation and operation. With the initial release of the 7000 controller range, a **ferrite choke** was supplied with each controller. *** ## Purpose The ferrite choke is installed on the network cable to the controller, **as close as possible to the network port on the C7000**. It is required to allow the 7000 controller range to meet **EN 50130-4 compliance** (electromagnetic compatibility for alarm systems). *** ## Future removal The ferrite choke requirement will be removed in future hardware revisions of the controller when Gallagher re-submits for EMC testing. *** ## When the ferrite choke can be omitted The ferrite choke can be omitted if: * The site does not require network devices to be compliant with EN 50130-4, **and** * The controllers are not installed in a noisy EMF (electromagnetic field) environment. > **Installer note:** If EN 50130-4 compliance is required at the site, the ferrite choke must be installed as supplied. If the site has no such requirement and is in a low-EMF environment, the ferrite choke is optional. *** 🔗 **Related** * [Controller 7000](broken://pages/873trKCrdhjXzfqYdsdU). Variants, specifications, and accessories. * [Bringing Online and Networking](/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/configure/controller-7000-bringing-online-and-ne.md). Installing and connecting the controller. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-7000-and-7000-sdc/reference/controller-7000-ferrite-choke.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.