> 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/salto/salto-troubleshooting/salto-encoder-or-card-update-issue.md).

# Salto encoder or card update issue

Resolve Salto encoder contact errors and configure encoder settings for compatible Salto Space versions.

For the error **"The salto encoder could not be contacted"**:

1. **Check the encoder selection.** In Salto Space, confirm the correct encoder (dongle) is selected, especially on Space **v6.8.5.0 or earlier**.

![Salto Space General Options → Devices → Dongle Encoder dropdown](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-50a20a1a5b25c31478ff510395d0f77c2de0f691%2FSECHUB-SALTO-14-dongle-encoder-selection.png?alt=media)

2. **Confirm connectivity.** The encoder must be online at all times.
3. **Space 6.8.5.0+:** the encoder must be online and **Enable Dongle Mode** set (System → Salto Network).
4. **Space 6.10.x.x+ with an Encoder v1:** tick **Enable legacy devices** (System → General Options → Devices).

![Salto Space General Options → Devices: LEGACY DEVICES "Enable legacy devices" selected](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-fc91aecbb9d5ce4378fc510468e78951e478ebd4%2FSECHUB-SALTO-15-enable-legacy-devices.png?alt=media)

***

🔗 **Related**

* [Salto connection and sync issues](/knowledge-hub/products/integrations/third-party-readers/salto/salto-troubleshooting/salto-connection-and-sync-issues.md). Broader connection checks.


---

# 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/salto/salto-troubleshooting/salto-encoder-or-card-update-issue.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.