> 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/salto-lock-interface/command-centre-site-configuration/encoding-cards/reason-for-using-128-bit-wiegand-format.md).

# Reason for using 128 bit Wiegand format

The Salto Integration supports encoding a card’s number in 26 bit Wiegand format on one of the Salto sectors of the card. However, there are limitations with the 26 bit format, namely:

* The range of Card Numbers that can be supported is 1 to 65,000.
* The Issue Level is ignored so changing the Issue Level on a card assignment has no impact on the cardholder's ability to gain access through Salto doors using third party readers.
* Only the first two characters (first byte) of the Card's Facility Code will be encoded on the Wiegand portion of the card which means that where there are two cards with the same Card Number, different Facility Codes but the first two characters of those Facility Codes are the same, Command Centre will be unable to distinguish between them.

Command Centre v9.40 introduces support for 128 bit Wiegand data format, enabling mobile credentials to work seamlessly with wired SALTO readers and Gallagher controllers via the UBOX 4000 hardware. Command Centre now supports access and event tracking for mobile devices alongside traditional cards at SALTO wired readers setup as Gallagher Third party Wiegand readers. Note this functionality is only available in SALTO Native mode.

### Configuring Salto wired readers to display green/red LED based on access decision

Where a Salto reader is used but the access decision is being made by Command Centre, the latter should control whether the LED on the Salto reader goes green to indicate access is granted or red when access is denied. To achieve that the system must be configured in the following way:

**To pulse the green LED on the Salto Control Unit when access is granted:**

1. Create an Output to be activated when the door is unlocked.
2. Create a Logic Block with the following:
   * A Rule which triggers when the Unlock Output on the door is ON.
   * Timing so that the ‘Logic Block is pulsed when the rules are met’. The Pulse on time should be configured so that it is long enough for the cardholder to see that access has been granted.
   * Create a reflected Output and assign it to the reflected output page of the logic block and connect it to the door input on the Salto Control Unit. This Output will be activated when the logic block turns ON.
3. Navigate to UBOX 4000 / CU42E0 controller Auxiliary, click on the input you choose to have the Green signal display.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ee5ad1ccbf675373f69487bb132c08f00b9a526c%2Fsaltonetwork_editinput_greensignal.png?alt=media)
4. Wire up the output controlling the Green signal to the input selected on the Salto controller.

   **Note:** A Logic Block is required because the time an Output will be pulsed by some door mechanisms supported, (e.g. boom gates), will be insufficient for this purpose.

**To pulse the red LED on the Salto Control Unit when access is denied:**

1. Create an Action Plan and assign it to the Access denied Event Group of the door.
2. Create an Output to be triggered when the Action Plan is activated. Assign the Output in all Action Plan tabs, (i.e. Armed, Disarmed, User1 and User2), and connect this Output to the Exit Input of the Salto Control Unit.
3. On the **Advanced** tad of the Output, configure the number of seconds the Output is to be pulsed. When the Output is turned ON the Red LED on the Salto Control Unit will display for a number of seconds configured for the Output to pulse.
4. Navigate to UBOX 4000 / CU42E0 Auxiliary and click on the input you choose to have the Red signal display.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4284ef3040e68ca5230801f61aa439941567fa37%2Fsaltonetwork_editinput_redsignal.png?alt=media)
5. Wire up the output controlling the Red signal to the input selected on the Salto controller.


---

# 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/salto-lock-interface/command-centre-site-configuration/encoding-cards/reason-for-using-128-bit-wiegand-format.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.
