> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/access-control/installation/badge-reader-support.md).

# Badge Reader Support

Learn about the badge reader types supported by Verkada’s access control system

Verkada’s access control system supports the popular Wiegand protocol for badge readers which encompasses most of the Human Interface Device (HID) and similar readers deployed today. Verkada also supports Open Supervised Device Protocol (OSDP) through Verkada and third-party badge readers.

{% hint style="warning" %}
The AC41 does not support voltage above 7V on the D0/D1 ports.
{% endhint %}

## How it works

### Wiegand

Wiegand badge readers generally have 6 outputs:

* \+ (Positive)
* \- (Negative)
* D0
* D1
* RLED
* GLED

Each of these outputs has a corresponding input on each [AC41](https://docs.verkada.com/docs/door-controller-ac41-datasheet.pdf) door cartridge, as shown in the highlighted section of this door cartridge diagram. Each input has its label directly to the left.

### OSDP

OSDP badge readers have 4 outputs:

* \+ (Positive)
* \- (Negative)
* A
* B

Similar to Wiegand, each of these outputs has a corresponding input on each AC41 door cartridge, as shown in the highlighted section of this door cartridge diagram. Each input has its label to the left of the Wiegand labels.

Once [wired](/access-control/configuration/configure-a-door-in-command/wire-a-door-to-an-ac41-cassette.md), the badge reader is ready to go and you only need to activate the [door cassette](/access-control/configuration/configure-a-door-in-command.md) in Command to have it running alongside your other 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.verkada.com/access-control/installation/badge-reader-support.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.