> 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/integrations/third-party-readers/idemia-morpho/configure/idemia-readers-morpho-wiegand-wiring-videos.md).

# Wire IDEMIA readers over Wiegand

Connect IDEMIA (Morpho) readers to Gallagher controllers using Wiegand and suitable power.

Wiring Sigma readers is relatively straightforward.

### Wiring (Wiegand)

* **Power 12V** (both + and 0V). Both positive and 0 volts must be connected.
* **Data:** D0, D1, and Wiegand ground to the Controller. These carry the data the Controller uses to identify the fingerprint. Also wire **Out 1 and Out 2** so the controller sends Access Granted and Denied to the reader.

{% hint style="warning" %}
**Do NOT power the Sigma reader from the Controller or URI/Door Module.** They are not rated for the draw. Ground (0V) to the Controller or URI **is** required.
{% endhint %}

![IDEMIA reader Wiegand pinout to Gallagher hardware: reader terminal numbers mapped to the 6000 8R/4R Plug-in Module, the 3000, and the GBus URI (V out, D0/D1, Out 1/Out 2, ground), with a Wiegand-variant table](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0b365a77b9147063f0eb84c6d7c6565827ab5e67%2FSECHUB-int-idemia-01-wiring-diagram.png?alt=media)

### Wiring videos

Engineering-produced wiring videos are available on YouTube. The Gallagher Engineering team produced these four videos for Sigma readers, and they are publicly accessible:

* [C6000 + 8R/4R Module (C300100)](https://www.youtube.com/watch?v=IV3ZbpMK3ic): IDEMIA (Morpho) Wiring, Controller 6000 with 8R or 4R Module.
* [FT GBUS URI (C200660)](https://www.youtube.com/watch?v=xvu3zPStMz4): IDEMIA (Morpho) Wiring, FT GBUS Universal Reader Interface.
* [GBUS URM Wiegand (C200665)](https://www.youtube.com/watch?v=UDy4Z0pbz1c): IDEMIA (Morpho) Wiring, GBUS Universal Read Module, Wiegand Variant.
* [HBUS 4-In 2-Out Wiegand (C300665)](https://www.youtube.com/watch?v=x-k0zxFERdY): IDEMIA (Morpho) Wiring, HBUS 4 in 2 Out Door Module, Wiegand Variant.

Older Sigma hardware can need a related wiring fix when a reader is failing to come back online after updating its mode or database: two isolating diodes on D0 and D1. See [IDEMIA reader does not come online after an update](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/troubleshoot/idemia-readers-morpho-reader-failing-to-come-back-online-after-updating.md).


---

# 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/integrations/third-party-readers/idemia-morpho/configure/idemia-readers-morpho-wiegand-wiring-videos.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.