> 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-transit-readers.md).

# Nedap - Transit Readers

Transit readers are a windscreen-booster system for reading Gallagher-encoded cards at range. Two generations exist: **Transit Ultimate** (current) and **Original Transit** (older).

> ⚠️ **Gallagher only supports Transit readers with S97 firmware.** The S97 firmware uses the **default DIP-switch settings (all ON)**.

![Nedap Transit Ultimate reader (current)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-51120fb0140b6199bb97b0e6f9128f355cf28523%2FSECHUB-NEDAP-09-transit-ultimate-photo.png?alt=media)

![Original Nedap Transit reader (older)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-76c669fb9c9bd9175cceb748dfcb6d28dbad5436%2FSECHUB-NEDAP-07-transit-original-photo.jpg?alt=media)

![Transit DIP-switch default setting — all switches ON, RS232 baud 9600, applicable to all tags](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-38814e46c690c90d41b70efc769338250b1985f9%2FSECHUB-NEDAP-10-transit-dip-default.png?alt=media)

![Transit reader PCB wiring — HF/GND/TAMPER/D0/D1 terminals and DIP switches (SW1)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e73d849f98329b5188c11b3da9996a432354ec40%2FSECHUB-NEDAP-11-transit-wiring-dip-board.png?alt=media)

## Boosters

Transit readers need a **Booster** to read Gallagher-encoded cards. Use **dual authority** through the door the Transit is connected to. See [Nedap - Boosters](/knowledge-hub/products/integrations/third-party-readers/nedap/nedap-boosters.md) for booster detail and DESFire support.

## If the reader was not supplied by Gallagher

A Transit reader not supplied by Gallagher will have the wrong firmware. See [Transit reader not supplied from Gallagher](/knowledge-hub/products/integrations/third-party-readers/nedap/nedap-transit-reader-not-supplied-from-gallagher.md).

***

🔗 **Related**

* [Nedap - Boosters](/knowledge-hub/products/integrations/third-party-readers/nedap/nedap-boosters.md). Reading Gallagher and DESFire cards through a Transit.
* [Nedap - Hardware](/knowledge-hub/products/integrations/third-party-readers/nedap/nedap-hardware.md). UCF and wiring values.


---

# 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-transit-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.