> 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/current-advisories/communication-protocols-and-idemia-dev.md).

# IDEMIA device communication protocols

Check IDEMIA protocol support and firmware requirements before upgrading Command Centre.

Since **January 2022, IDEMIA stopped supporting the Legacy (MA2G) communication protocol** for all their devices. Gallagher will no longer actively support MA2G. Users need to update firmware to **MA5G** as required.

> ⚠️ **Note:** Command Centre **v9.30 and above no longer supports the IDEMIA MA2G protocol**. Ensure all readers are using Native (MA5G) mode **prior to upgrading**.

* All devices shipped from IDEMIA since **October 2020** are preloaded with MA5G firmware.
* IDEMIA recommend keeping device firmware up to date. Regular improvements protect against potential cyberattacks.
* Device firmware can be downloaded from the [IDEMIA Biometric Devices Portal](https://biometricdevices.idemia.com/s/products).

Due to a new IDEMIA SDK, which does not support Legacy (MA2G) and is required for supporting the **VisionPass SP** in Command Centre v9.30, the removal of the MA2G protocol was **brought forward to Command Centre v9.30**, scheduled for release May 2025. This is a date change from the November 2024 Gallagher Security newsletter announcement.

## Supported IDEMIA devices and firmware versions

| IDEMIA device         | Communication protocol                   | Recommendation                                 | Most current firmware version available |
| --------------------- | ---------------------------------------- | ---------------------------------------------- | --------------------------------------- |
| MA Sigma Light Series | MA5G or MA2G (unsupported from CC v9.30) | Update firmware to Native (MA5G), as required  | Firmware 4.16.8                         |
| MA Sigma Wide         | MA5G or MA2G (unsupported from CC v9.30) | Update firmware to Native (MA5G), as required  | Firmware 4.16.8                         |
| MA Sigma Extreme      | MA5G or MA2G (unsupported from CC v9.30) | Update firmware to Native (MA5G), as required  | Firmware 4.16.8                         |
| MA Wave XP            | MA5G only                                | Update firmware to latest version, as required | Firmware 2.13.3                         |
| MA Wave SP            | MA5G only                                | Update firmware to latest version, as required | Firmware 2.2.1                          |
| MA VisionPass         | MA5G only                                | Update firmware to latest version, as required | Firmware 2.14.4                         |

## Unsupported end-of-life IDEMIA devices

These are not supported from Command Centre v9.30:

| IDEMIA device          | IDEMIA End of Life (EOL) date | Recommendation                     |
| ---------------------- | ----------------------------- | ---------------------------------- |
| MA100 Series           | January 2013                  | Replace with MA Sigma Light Series |
| MAJ Series             | February 2016                 | Replace with MA Sigma Light Series |
| MA500 Series           | July 2016                     | Replace with MA Sigma Wide         |
| Finger Vein Print - VP | June 2021                     | Replace with MA Wave               |

***

🔗 **Related**

* [Upgrade IDEMIA SIGMA fingerprint sensor firmware](/knowledge-hub/products/product-advisories/current-advisories/firmware-upgrade-idemia-sigma-wide-lit.md). Install the SIGMA range firmware fix.
* [Morpho MA VP Series planned phase-out — March 2019](/knowledge-hub/products/product-advisories/historical-notices/morpho-ma-vp-series-planned-phase-out.md). Review the end-of-life finger vein readers.


---

# 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/current-advisories/communication-protocols-and-idemia-dev.md?ask=<question>&goal=<user_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.