> 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/configuration-client/integrated-systems/nedap-readers/nedap-upass-readers.md).

# Nedap uPASS Readers

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Connecting the reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/nedap-readers/nedap-upass-readers.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating a new third party reader](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/nedap-readers/nedap-upass-readers.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating a new Card Type](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/nedap-readers/nedap-upass-readers.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating a new Universal Card Format](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/nedap-readers/nedap-upass-readers.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Assigning the new items to the Controller](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/nedap-readers/nedap-upass-readers.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating cards for cardholders and/or vehicles](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/nedap-readers/nedap-upass-readers.md)

#### Connecting the reader

A Nedap Reader is connected to a Gallagher Controller as a Wiegand Reader. For Wiegand Reader connection details, refer to the Gallagher Controller installation note.

**Note:** Instructions for connecting uPASS Go and uPASS Target readers to an HBUS 4 In 2 Out Door Module - Wiegand are as follows:

<table><thead><tr><th width="167">For a uPASS...</th><th width="245">Connector 2 Wiegand...</th><th>to the HBUS 4 In 2 Out Door Module - Wiegand...</th></tr></thead><tbody><tr><td>Go reader</td><td>OUT2</td><td>R1/R2 DATA 0</td></tr><tr><td></td><td>OUT3</td><td>R1/R2 DATA 1</td></tr><tr><td></td><td>GND</td><td>GND</td></tr><tr><td>Target reader</td><td>Pin 2 Data 0</td><td>R1/R2 DATA 0</td></tr><tr><td></td><td>Pin 4 Data 1</td><td>R1/R2 DATA 1</td></tr><tr><td></td><td>GND</td><td>GND</td></tr></tbody></table>

#### Creating a new third party reader

Create a new third party reader for each Nedap Reader.

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens.
2. **Right click** and select **New\...Third Party Reader**.

   By default the **General** tab displays.
3. Enter a Name and Description, and select the division for this third party reader.
4. Configure the remaining tabs as required, and click the **OK** button.

#### Creating a new Card Type

1. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** List Window opens.
2. **Right click** and select **New\...Card Type**.

   By default the **General** tab displays.
3. Enter a Name and Description, and select the division for this Card Type.
4. Configure the remaining tabs as required, and click the **OK** button.

#### Creating a new Universal Card Format

Create a new Universal Card Format for each tag format you will be using.

1. Click **Configure** from the menu bar, then **Universal Card Format**.

   The **Universal Card Format** List Window opens.
2. **Right click** and select **New\...Universal Card Format**.
3. Enter a Name and Description, and select the division for this Universal Card Format.
4. Click the **Format** tab.
5. Select the **Wiegand** radio button.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-87af19eb94e3ad69606ecc908741f423ecc1d9d0%2Fucfformat.png?alt=media)
6. Change the following fields to the figures indicated, for the type of reader you are using:

   <table><thead><tr><th width="186">Field</th><th width="237">uPASS Reader and 6 bit tags</th><th>uPASS Reader and 38 bit tags</th></tr></thead><tbody><tr><td><strong>Number of Bits:</strong></td><td>26</td><td>38</td></tr><tr><td><strong>Bits in Facility Code:</strong></td><td>8</td><td>12</td></tr><tr><td><strong>First Bit of Facility Code:</strong></td><td>2</td><td>2</td></tr><tr><td><strong>Bits in Card Number:</strong></td><td>16</td><td>24</td></tr><tr><td><strong>First Bit of Card Number:</strong></td><td>10</td><td>14</td></tr><tr><td><strong>Facility Code:</strong></td><td>A00010</td><td>A00010</td></tr></tbody></table>
7. Click the **OK** button.

#### Assigning the new items to the Controller

1. From the **Hardware** List Window, open the property pages for the Controller that the third party reader will be assigned to.
2. Click the **Readers** tab.
3. Assign the third party reader to the appropriate slot, depending on how you wired it to the Controller, or HBUS Wiegand Reader port.
4. Click **OK**.
5. Click the **Card Formats** tab.
6. On the **Universal Card Format** List Window, highlight the new Universal Card Format (created in the previous procedure), and drag and drop it into the **Card Formats** tab of the Controller.

   **Note:** If using a uPASS Reader and both 26 and 38 bit tags, drag and drop both Universal Card Formats (previously created) into the **Card Formats** tab of the Controller.
7. Click the **OK** button.

#### Creating cards for cardholders and/or vehicles

Create cards for each of the cardholders and/or vehicles as required.

See [Adding a Card to a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-card-to-a-cardholder.md) for the complete procedure.

**Note:** When using uPASS Readers, ensure that the Card Type selected uses the Facility Code A00010 as entered into the new Universal Card Format you created earlier.


---

# 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/configuration-client/integrated-systems/nedap-readers/nedap-upass-readers.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.
