> 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-compatibility.md).

# Space Compatibility

The Salto Space Lock Interface has been tested using:

* Command Centre (Windows Server 2019 64-bit using Microsoft Internet Explorer 11 and Microsoft Silverlight) with Microsoft SQL Server 2019, and
* Salto ProAccess SPACE 6.10.4.3 (on Windows Server 2019 64-bit) with Microsoft SQL Server 2019.

The Salto Space Lock Interface has been tested using the following card technologies:

* Salto encoded Guest cards: MIFARE Ultralight® C and MIFARE Classic® cards.
* Gallagher encoded Staff cards: MIFARE Classic®, MIFARE Plus® Security Level 3 (SL3), and MIFARE® DESFire® EV1 to EV3 cards. MIFARE Plus® X and S card types are supported.

The Salto Space Lock Interface has been tested using the following Salto hardware:

* Salto Wireless Gateway 2, part number GATEWAYW2C with mini node
* Salto Node, part number RFNODE
* Salto Expansion Relay Board, part number EB5008
* Salto Control Unit CU42E0
* Salto Control Unit CU4200
* Salto Relay Board CU4EB8
* Salto UBOX4000
* Salto Wired Reader WRDB0E0
* Salto Wired Reader with keypad WRDB0E0K
* Salto XS4 BLE Escutcheon AB650 (offline)
* Salto AElement RF2 Wireless Reader with Privacy
* Salto XS4 BLE RF2 Wireless Escutcheon with Privacy
* Salto Escutcheon E9450U00IM38-03
* Salto XS4 Locker Lock (offline)
* Salto E450 RF3 Escutcheon
* Salto ESDs ESD92UC (offline) and ESD92UIC (online)
* Salto Control Unit (CU5000) - firmware version 01.52, 2.21 and 5.03
* Salto Portable Programming Device PPD firmware version 02.18
* Salto RF3 Gateway, part number GATEWAYW3CAU with RF3 mini node
* Salto AElement Fusion
* Salto Neo Cylinder (RF3 BLE)
* Salto RF3 Repeater, part number REPEATER03AU

### Considerations

* Salto ProAccess SPACE 6.10.4.3 supports Salto RF2 and RF3 modes only. Salto RF mode 1 devices are not supported and will need to be replaced.
* Command Centre polls the Salto application every 10 seconds, this means a delay of up to 20 seconds may occur (allowing for network latency) before an event generated at a Salto online wireless reader is displayed in Command Centre.
* If a Salto device is disconnected from the network, the device and the wireless doors connected will go offline. No offline event is reported in the Salto audit trail, hence the corresponding Command Centre Salto doors continue to display as online. In this scenario, the events are stored on the Salto lock. The Salto events will be transferred to the Salto server when wireless connectivity is restored.


---

# 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-compatibility.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.
