> 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/set-up-a-salto-reader-as-a-third-party-reader-using-wiegand-connection.md).

# Set up a SALTO reader as a Third-party reader using Wiegand connection

### Introduction

Cards encoded in Command Centre that include a Salto Object, will either be encoded as 26 bit, 64 bit or 128 bit.

**Notes:**

* You cannot use 26 bit, 64 bit and 128 bit Wiegand format on the same Salto Space Server. If you upgrade to Salto Native mode from an original 26 bit Wiegand format card type configuration, you will need to configure 26 bit Wiegand in Salto Space.
* You cannot return to 26 bit or 64 bit once at 128 bit.
* A card needs to be encoded before the Salto status in Command Centre will show as 128 or 64 bit.
* If you want to use mobile credentials with a Salto third party reader, 128 bit is required.

### Procedure

This procedure describes how to configure Salto Space Wiegand code so you can use a wired Salto reader as a third-party reader in Command Centre using Wiegand connection in Native Mode. 128 bit is recommended.

This procedure is split into four parts, as follows:

[1. Salto Space Procedure](#id-1.-salto-space-procedure)

[2. Salto Reader Configuration](#id-2.-salto-reader-configuration)

[3. Wiring SALTO reader as Wiegand connection third-party reader](#id-3.-wiring-salto-reader-as-wiegand-connection-third-party-reader)

[4. Third-party reader configuration in Command Centre](#id-4.-third-party-reader-configuration-in-command-centre)

#### 1. Salto Space Procedure

1. Log into Salto Space, select **System** > **General options** > **Users**.

   The Users tab displays.
2. Tick the **Wiegand code** checkbox, then select the **Profile code** radio button.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-15a8ac151f11a4b32405360a66ed5fe46a0e3cda%2Fsaltospace_users_wiegand1.png?alt=media)
3. Click the **CONFIGURE** button.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fa88b04ed6704475a79b437ed7110f9039bbc2f5%2Fsaltospace_users_wiegand2.png?alt=media)

   The Wiegand format configuration dialog box displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e2944a98d94d52ba444b1e2d43107b843164341f%2Fcuadap_1.png?alt=media)
4. Click the **ADD CODE** button. The Wiegand code definition dialog box displays.

   This allows you to specify the different parts that form the Wiegand code and define their characteristics.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-781d8e74325a0575b72201c5ace5286f55bd62af%2Fsaltospace_wiegandcodedefinitiondialog_128bita.png?alt=media)
5. Once you have configured A code for 128 Bit click **OK**, then click the **ADD CODE** button again and add another code for B code.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cfb96aaea2324996bfc320fbfbc6b90955d34098%2Fsaltospace_wiegandcodedefinitiondialog_128bitb.png?alt=media)
6. Click the **OK** button.

   The Wiegand code definition dialog box closes.
7. Add AB in th **Interface format** field.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cf067a7f465c06ad31bfd03ab092ccebf34870d3%2Fsaltospace_wiegand_128bit.png?alt=media)
8. Add 64 A’s followed by 64 B’s in the **Bit composition** field.

   AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB

   **Note:** We currently support Wiegand code for 26 bits (Legacy only), 64 bits and 128 bits. Refer to [Reason for using 128 bit Wiegand format](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) for details of the limitations there are with using 26 bit format.
9. Define the parts of the Wiegand code appropriate for the format you are using:

<details>

<summary>26 bit format (Legacy mode only)</summary>

The default **Code** option is "A", but you can change this if required.

Any letter can be entered except "P" as this is used to identify the parity of the codes at the beginning and end of the Wiegand code

|                       | Code A                                      | Code B                                    |
| --------------------- | ------------------------------------------- | ----------------------------------------- |
| **Description:**      | Facility code. Any description can be used. | Card number. Any description can be used. |
| **Bit order:**        | MSB                                         | MSB                                       |
| **Number of Digits:** | 2                                           | 4                                         |
| **Digit format:**     | Hexadecimal                                 | Hexadecimal                               |

</details>

<details>

<summary>64 bit format</summary>

* **Code:** A

  The default option is "A", but you can change this if required.

  Any letter can be entered except "P" as this is used to identify the parity of the codes at the beginning and end of the Wiegand code.
* **Description:** 64Bit

  Any description can be used.
* **Bit order:** MSB
* **Number of Digits:** 16
* **Digit format:** Hexadecimal

</details>

<details>

<summary>128 bit format</summary>

The default **Code** option is "A", but you can change this if required.

Any letter can be entered except "P" as this is used to identify the parity of the codes at the beginning and end of the Wiegand code

|                       | Code A                                | Code B                                |
| --------------------- | ------------------------------------- | ------------------------------------- |
| **Description:**      | 128 Bit. Any description can be used. | 128 Bit. Any description can be used. |
| **Bit order:**        | MSB                                   | MSB                                   |
| **Number of Digits:** | 16                                    | 16                                    |
| **Digit format:**     | Hexadecimal                           | Hexadecimal                           |

</details>

10. Click the **OK** button to return to the Wiegand format configuration dialog box.
11. Define the format of the Wiegand code appropriate for the format you are using:

<details>

<summary>128 bit format</summary>

* **Interface format:** AB
* **Bit composition:** <64 A's><64 B's>

  AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB

</details>

<details>

<summary>64 bit format</summary>

* **Interface format:** A
* **Bit composition:** <64 A's>

  AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

</details>

<details>

<summary>26 bit format (Legacy mode only)</summary>

* **Interface format:** AB
* **Bit composition:** \<P> <8 A’s> <16 B’s> \<P>

  < PAAAAAAAABBBBBBBBBBBBBBBBP >
* **Parity rule 1:** \<E> <12 X’s> <13 -‘s>

  < EXXXXXXXXXXXX------------- >
* **Parity rule 2:** <13 -‘s> <12 X’s> \<O>

  < -------------XXXXXXXXXXXXO >

</details>

12. Click the **OK** button to complete the custom Wiegand format.

    **Note:** Copy from notepad ++ to help count the letters for Bit composition.

#### 2. Salto Reader Configuration

1. From SALTO Space, select **System** > **SALTO Network** and expand **CU4xxx Controller** or **UBOX4000 Controller**.

   Click on **CU4xxx Auxiliary** or **UBOX4000 Auxiliary**.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c12bde070b4baced689c7dd38ef380c94430f26c%2Fsaltonetwork_controller.png?alt=media)
2. From the INPUTS panel, double-click on **IN3**, **IN4**, or **IN5**, **IN6** from the list.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fe8d4268dab09165eec93917c557c27530fdef89%2Fsaltonetwork_inputs.png?alt=media)

   The Edit input page displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-422228395ec9f6df35d0a9fafc7fbca2f455e80d%2Fsaltonetwork_editinput.png?alt=media)
3. Select the following options from the drop-down lists:
   * **Type:** CUADAP
   * **Interface and data type:** 24, WIEGAND - WIEGAND CODE - Software defined
   * **Reader number:** Reader #1

     Reader number can be different as required.
4. Click the **OK** button to apply.

#### 3. Wiring SALTO reader as Wiegand connection third-party reader

<table><thead><tr><th valign="top">From the UBOX4000/CU4xxx Controller:</th><th valign="top">From the Wiegand HBUS Module:</th><th valign="top">From an 8R Module connected to the Gallagher Controller:</th></tr></thead><tbody><tr><td valign="top">IN5+</td><td valign="top">DATA0</td><td valign="top">R1 In</td></tr><tr><td valign="top">IN6+</td><td valign="top">DATA1</td><td valign="top">R2 In</td></tr><tr><td valign="top">IN6-</td><td valign="top">GND</td><td valign="top">GND</td></tr><tr><td valign="top"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-422885fc59c32f0c35e999333b8d2f7f7c8b721e%2Fsalto_wiringfromcu4xxxcontroller.png?alt=media" alt=""></td><td valign="top"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e0150cbc859417e106cd8e97bfadf793660d369d%2Fsalto_wiringfromhbusuri.png?alt=media" alt=""></td><td valign="top"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f9e2a648da00a62314f08b4c2df09958053bd3e1%2Fsalto_wiringfromcccontroller.png?alt=media" alt=""></td></tr></tbody></table>

#### 4. Third-party reader configuration in Command Centre

1. Create a card type containing a SALTO object, as follows:

   **Note:** For Native mode from v9.40 or later, 64 bit and 128 bit Wiegand card formats are set in SALTO Space only, not through the card type in Command Centre.

   1. In Command Centre Configuration Client, add a Salto MIFARE object to the card layout.

      Refer to [Adding Salto MIFARE objects to a card layout](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/encoding-cards/adding-salto-mifare-objects-to-a-card-layout.md) for the procedure.
   2. If you are using 26 bit format, when configuring the Card Type the following ranges are supported:

      * Facility Code = 1 - 255
      * Card Number = 1 - 65535

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-07c20c42c5e35b4cc08a2e770a96c93266a92dc7%2Fsaltospace_wiegand_26bit_cardtype.png?alt=media)
2. Create a Third-party reader and assign it to a Controller, as follows:
   1. In Command Centre Configuration Client, click **Configure** from the menu bar, then **Hardware**.

      The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
   2. **Right click** and select **New\...Third Party Reader**.

      See [Creating Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-readers.md) for the full procedure.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dc0fce5ffe9418641d81aeae7231dfcc1e9e3670%2Fsalto_thirdpartyreader_hwwindow.png?alt=media)
   3. Click the **Type** tab.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-93eb624918abbb2ac9878778c04e340dfd4e00ff%2Fthirdpartyreader_typetab.png?alt=media)
   4. Select the appropriate Format from the drop-down list.
   5. Did you select 'Salto' as the Format?

      If **yes**, no **Key Map** is necessary. Go to the next tab.

      If **no**, go to Step f.

      **Note:** The current Wiegand Format supported will display on the **Status and Overrides** tab of the Salto Server properties.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6adabaa30cfd9939e94d07b645f52f52922d98dd%2Fsaltostatus%26overridestab_wiegandformat.png?alt=media)

      **Notes:**

      * It is not possible to change back to a smaller Wiegand format once 128 bit is configured.
      * New Salto sites are by default given a 128 bit Wiegand format.
      * Legacy mode does not support 128 bit, nor does it support mobile connect at a Salto Third Party reader outputting Wiegand data.
      * When upgrading from legacy mode, as long as the legacy mode was configured with 26 bits, then it can be supported in native mode. 26 bit format is also required to be configured in Salto Space.
   6. Assign the third-party reader to a Controller by:

      * opening the property pages for the Controller that the third-party reader is to be assigned to,
      * clicking the **Readers** tab, and assigning the third-party reader to the appropriate slot.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-63a90e444cbff73dea39b0e198b56d59744eff42%2Fsalto_thirdpartyreader_controllerproperties.png?alt=media)
   7. Click the **OK** button to exit the Controller properties and save your changes.
3. Add the SALTO Third-party reader to a Door, as follows:
   1. From the **Hardware** List Window, select the Door that you want to add the SALTO third-party reader to.
   2. Click the **Entry Zone** tab.
   3. Select the third-party reader from the relevant **Reader(s)** drop-down list.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4679b9e99ca5c12f45088474a0737224d46bb063%2Fsalto_thirdpartyreader_doorproperties.png?alt=media)
   4. Click the **OK** button to exit the Door properties and save your changes.
4. Encode a card for a cardholder with SALTO card type assigned.

   Refer to [Printing and/or Encoding a card from a cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/printing-encoding-cards/printing-and-or-encoding-a-card-from-a-cardholder.md) for the procedure.


---

# 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/set-up-a-salto-reader-as-a-third-party-reader-using-wiegand-connection.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.
