> 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/nedap/nedap-upass-readers.md).

# Nedap - uPass Readers

UPass is a UHF reader for long-range windscreen-tag reading.

{% hint style="warning" %}
A **uPASS reader can only read uPASS tags.** It cannot read Gallagher cards (no booster changes this), and **uPASS tags must be purchased from Gallagher** (they need a specific format).
{% endhint %}

![Nedap uPASS windscreen tag](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e96f4bb99c026f328f5ae10d5a2269712a4294c8%2FSECHUB-NEDAP-05-upass-windscreen-tag.png?alt=media)

## Wiring

| uPASS Reader         | 6000/7000 Controller 4H/8H Module | Wiegand URI |
| -------------------- | --------------------------------- | ----------- |
| Wiegand OUT2 (Data0) | R1 IN                             | R1 Data0    |
| Wiegand OUT2 (Data1) | R2 IN                             | R2 Data1    |
| Wiegand GND          | GND                               | GND         |

![uPASS reader wiring diagram — K2 (DATA-0/DATA-1/GND, OUT1-3) and K1 (12V)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e28899df58ae1447a4c65effa351fd30feed9a1c%2FSECHUB-NEDAP-06-upass-wiring.png?alt=media)

* HBUS URI Data0/Data1 (IN) must be **> +2.5VDC** (else use pull-up/down resistors). Controller 6000/7000 Reader IN terminals are **+5VDC** (the 6000 auto-biases, so resistors are usually not needed).
* Create the uPASS as a **3rd Party Reader**. The door needs an **Alarm Zone**. Always connect Wiegand Ground plus D0/D1.

***

🔗 **Related**

* [Nedap - Hardware](/knowledge-hub/products/integrations/third-party-readers/nedap/nedap-hardware.md). UCF and hardware models.


---

# 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/nedap/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.