> 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/space-site-configuration/salto-ethernet-encoders-dongles.md).

# Salto Ethernet Encoders/Dongles

### Introduction

Every site requires a Salto Ethernet encoder/dongle, regardless of whether they will be encoding. To encode cards with Salto data from Command Centre, you will need a Command Centre USB encoder and/or a printer, (e.g. Fargo HDP5000 Printer) connected to Command Centre. The Salto Ethernet encoder is used by the Salto system for card encryption, but is not used when encoding cards from Command Centre.

The Salto Ethernet encoder must be connected to the Salto server. The Command Centre USB encoder and/or printer must be connected to the Command Centre server or a Command Centre workstation.

**Note:** If cards are encoded off-site, then the off-site bureau connects to the Salto server on the site, which then connects to the Salto Ethernet encoder.

### Procedure

1. If your site is using an old encoder, select **System** > **General Options** > **Devices**.
2. Within the "LEGACY DEVICES' section, select the **Enable legacy devices** checkbox.

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

   **Note:** Sites using an old Encoder will not be able to encode cards with the **Disable legacy devices** checkbox ticked. The **Disable legacy devices** setting is on by default with new installations.
3. Select **System > SALTO Network**.

   The SALTO Network screen is displayed.
4. Click **Add**.

   The Add network device dialog box is displayed.
5. Select **Encoder** or **Ncoder** as applicable from the drop-down list, and click **OK**.

   The Encoder information screen is displayed.

   This screen will differ depending on the type of encoder you selected. The example below is the screen for the **Ncoder**, and includes some additional fields that don’t appear on the screen for the **Encoder**:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-97182177f815d251fee7d089d1d9c55af2a9c2cf%2Fnewencoder_ncoder.jpg?alt=media)
6. Type a name for the encoder in the **Name** field.
7. Type a description for the encoder in the **Description** field.
8. Select the appropriate **Partition** from the drop-down list.
9. Type the media access control (MAC) address in the **MAC address** field.

   **Note:** This field only appears for the Ncoder, (i.e. it does not appear for the Encoder).
10. Did you select **Encoder** or **Ncoder**?

    <table><thead><tr><th width="94">If...</th><th>then...</th></tr></thead><tbody><tr><td>Ncoder,</td><td><p>select either the <strong>Network name (DHCP)</strong> or <strong>IP address</strong> option.</p><p>If you select <strong>Network name (DHCP)</strong>, an IP address is automatically assigned to the RF gateway. A Dynamic Host Configuration Protocol (DHCP) server and a DNS are required for this option.</p><p>If you select <strong>IP address</strong>, you must type a static IP address in the field.</p></td></tr><tr><td>Encoder,</td><td><p>type the <strong>IP address</strong> you are going to assign to this Ethernet encoder in your local area network.</p><p><strong>Note:</strong> Consult your LAN Administrator if you are not sure which IP address should be given to this device. Ensure the IP address is a valid one that is not already in use by another device.</p></td></tr></tbody></table>
11. Select the **Run update reader** checkbox, if required.

    This option is used to configure an Ethernet encoder to update user keys automatically when users present their keys to it. If you select this option, the encoder runs continuously but it can only update keys. It cannot be used to encode keys with access data from the Salto software.
12. Select the **Enable beeper** checkbox, if required.

    If you select this option, the encoder emits beeps when in use.
13. Select the **Enable dongle mode** checkbox. The encoder will be used by the SALTO service to encrypt data using a third-party reader.
14. Click the **Save** button.
15. On the physical Ethernet encoder, use a pen or pencil to push the **Address** button (shown below) for three seconds until it starts flashing. Once flashing, click the **Address** button on the Encoder information screen (in the Salto application).

    <div><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9313c50728559c2163449e2102b4b5e39e37704d%2Fclrbutton_encoder.png?alt=media" alt="
    Encoder"> <img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c81d4f3b0481b824cf25f0a1f6abd0387aca2273%2Fclrbutton_ncoder.png?alt=media" alt="
    Ncoder" width="375"></div>

    The Address dialog disappears and the Encoder will be available.
16. Click the **Back to Salto Network** button.

    The Encoder information screen closes and you are returned to the SALTO Network screen, with the newly created Ethernet Encoder appearing in the list.
17. Select the **admin** tab.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ee0d8c387cb67de366e93e9a7b9ff1784cd9c6f3%2Fsalto_admintab.png?alt=media)
18. Change the ENCODER SETTINGS to "Online" and select the **Salto Ethernet network encoder** from the drop-down list.

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

### Sending MIFARE keys from Command Centre to Salto

By default, Salto Space has no MIFARE SAM keys set. The MIFARE keys need to be sent from the Command Centre to Salto.

An override exists on the Salto Server **Status and Overrides** property page to send the MIFARE keys that are used for Salto data on cards, from Command Centre to Salto, in order for the keys to be put onto Salto locks. This allows the locks to read cards that are encoded with Salto data.

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

This override option only appears on the Command Centre server machine while logged in with an operator that has "Manage Keys" privilege. If you log in on a workstation machine with the same operator, the override option will not appear.

Apply the override “Configure Encryption” the MIFARE SAM keys are sent from Command Centre to Salto. This should preferably be done before connecting the PPD to any of the Salto devices. If the PPD is plugged into the Salto devices before applying the MIFARE SAM keys, the devices will be set with has no MIFARE SAM keys and this will then have to be applied at a later stage.


---

# 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/space-site-configuration/salto-ethernet-encoders-dongles.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.
