> 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/product-advisories/historical-notices/f-series-fence-controllers-advisory-up.md). # F Series Fence Controllers product advisory update — June 2023 Review the 2023 firmware fix for the F Series optical tamper issue. **16 June 2023.** This is an update to the [March 2023 advisory](/knowledge-hub/products/product-advisories/historical-notices/f-series-fence-controllers-product-adv.md). The **firmware update has been completed and rolled into Command Centre**. It adapts the behavioural relationship between the higher-brightness communications LED and the optical tamper. It is included in the following controller firmware versions and the full release of Command Centre CCFT8.90: * vCR8.50.230406a * vCR8.60.230406a * vCR8.70.230406a * vCR8.80.230406a Sites experiencing the optical tamper issue should update the device (controller) firmware. Sites on earlier Command Centre versions experiencing the issue should upgrade to a later version of Command Centre. ## Affected part numbers Same as the March 2023 advisory: * G21920 / G21921 / G21922 (F31 / CAN / APAVE) * G21930 / G21931 / G21932 (F41 / CAN / APAVE) * G21940 / G21941 / G21942 (F32 / CAN / APAVE) * G21950 / G21951 / G21952 (F42 / CAN / APAVE) *** 🔗 **Related** * [F Series Fence Controllers Product Advisory - March 2023](/knowledge-hub/products/product-advisories/historical-notices/f-series-fence-controllers-product-adv.md). The original advisory and the interim workarounds. * [Product Advisories](/knowledge-hub/products/product-advisories.md). The full register of obsolescence, security, and deprecation notices. --- # 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/product-advisories/historical-notices/f-series-fence-controllers-advisory-up.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.