> 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-hardware/salto-ubox4000-and-cu42e0-controllers.md).

# Configure UBOX4000 and CU42E0 controllers

Configure UBOX4000 and CU42E0 controllers for Gallagher Wiegand reader connections.

These controllers connect a Salto wired reader to a Gallagher Wiegand input.

* **UBOX4000** works **only as an updater**. It pushes data to third parties (Gallagher) to open a door. It **cannot open physical doors** or run other SALTO door controllers, and requires **SALTO Space v6.5.2.1+**. Although labelled CU42E0, it **cannot** be used as one.
* **CU42E0** is the **master door controller** (2 onboard doors, plus an auxiliary CU42E0/CU4EB8 for lift, floor, and alarm). It can act as a UBOX, but is more expensive.

### Salto Space CUADAP configuration

Go to SALTO Network → the UBOX-4000 or CU42E0 node → the input (3/4/5/6) → Edit → Type **CUADAP**, option **24. WIEGAND – WIEGAND CODE – Software defined**, then choose the reader.

**Firmware minimums:** UBOX4000 Device 0163 v01.01+; CU42E0 Device 0119 v02.30+. Place the file in `C:\SALTO\ProAccess Space\firmwares`, then System → SALTO Network → Show Firmware → Update.

### Wire an HBUS Wiegand module

| UBOX4000/CU42E0 | HBUS Wiegand Module |
| --------------- | ------------------- |
| IN5 +           | DATA0               |
| IN6 +           | DATA1               |
| IN5 -           | GND                 |

{% hint style="warning" %}
A common ground (black wire) between the UBOX4000/CU42E0 and the Gallagher Wiegand module is required.
{% endhint %}

![UBOX4000/CU42E0 IN5/IN6 terminal wiring photo (with Ethernet)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-4746bbc7c3071f9a6d14f392115762ddbd449496%2FSECHUB-SALTO-04-ubox4000-in-terminals.png?alt=media)

### Mobile credential support (CC v9.40+)

128-bit Wiegand enables mobile credentials at wired SALTO readers via UBOX4000/CU42E0, in **SALTO Native mode only**.

{% hint style="warning" %}
Moving to 128-bit is not reversible to 64/26-bit. Command Centre alarms to configure Salto Space to 128-bit; existing cards still work at 64/26-bit; 128-bit also works with CUADAP CU9000 (cards only). Only recent Salto wired reader models support Mobile Connect as a third-party reader. Device 0125 readers need upgrading.
{% endhint %}


---

# 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-hardware/salto-ubox4000-and-cu42e0-controllers.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.
