Overview
The UXP Bridge is a middleware application that runs as a local Windows service. It connects attached peripheral devices – such as card printers, label printers and ID document readers – to higher-level systems and makes their functions available through a network-capable interface.
Through this interface, other systems on the local network – for example an IP terminal – can submit jobs to the Bridge. This allows a print job to be triggered or an ID document to be read from a central application, without the calling system needing direct access to the hardware.
In addition, the UXP Bridge provides connectors to external third-party systems in order to exchange data and events with control room and access control systems.
System requirements
Operating system
The UXP Bridge requires one of the following operating systems:
- Windows 10 (64-bit), current patch level
- Windows 11 (64-bit), current patch level
Minimum hardware requirements
The host computer should meet at least the following specification. For continuous operation with several attached devices, the recommended values are advised.
| Component | Minimum | Recommended |
|---|---|---|
| Processor (CPU) | Dual-core, 2.0 GHz | Quad-core, 2.5 GHz or higher |
| Memory (RAM) | 4 GB | 8 GB |
| Hard disk | 20 GB free, SSD | 50 GB free, SSD |
| Network | 1 × Ethernet 100 Mbit/s | 1 × Ethernet 1 Gbit/s |
| USB ports | depending on number of devices | USB 2.0 / 3.0, sufficient ports or active hub |
User account
A local administrator account on the host computer is required for installation and operation. This account is used to register the Windows service, install device drivers and apply the necessary network and firewall settings.
Connecting the peripheral devices
The peripheral devices are connected locally to the host computer via USB. The corresponding device drivers must be installed and the devices correctly recognised by the operating system before the UXP Bridge addresses them.
Supported hardware
The following hardware is currently supported:
| Device type | Model | Connection |
|---|---|---|
| Card printer | Zebra ZC300 | USB |
| Card printer | Zebra ZC350 | USB |
| Label printer | CUSTOM KPM180H | USB |
| Label printer | Brother QL-820NWB | USB |
| ID document reader | DESKO Penta Scanner | USB |
| ID document reader | REGULA 7028 | USB |
| LED controller | SEDUBASE LED Controller | USB |
Connectors to external systems
The UXP Bridge exchanges data and events with external third-party systems via connectors. The following connectors are currently available:
| Target system | Category |
|---|---|
| GESAB Datawall | Control room system |
| KENTIX One | Monitoring / building security |
| Modivision Face Control | Facial recognition / access control |
Operation as a Windows service
The UXP Bridge is started as a Windows service and therefore runs in the background – independently of a logged-in user session. The service starts automatically with the system and provides the interface once the computer has booted.
The rights of the local administrator account (see User account) are required to install, register and start the service.
Network configuration
Static IP address
The host computer requires a static IP address or a static IP reservation in DHCP. This is the only way to ensure that the Bridge is permanently reachable at the same address and that the calling systems (e.g. IP terminals) can be configured correctly.
Ports
The following ports must be reachable on the local network and must not be blocked by firewall rules:
| Port | Usage |
|---|---|
| 5000 | Communication on the local network (e.g. HTTP operation) |
| 5001 | Communication on the local network (e.g. HTTPS operation) |
Example use case
Via the released ports, an IP terminal can, for example, submit a print job to an attached printer or trigger the reading of an ID document. The terminal sends its request to the static IP address of the host computer and the corresponding port; the UXP Bridge processes the request and controls the respective device.
Operating mode HTTP / HTTPS
The UXP Bridge can be operated either via HTTP or HTTPS.
HTTP
In HTTP operation, communication is unencrypted. This mode is suitable for secured, isolated network segments.
HTTPS
In HTTPS operation, communication is encrypted. A total of three files are used for this, which are managed and provided by the UXP Admin. The decisive factor is where each file may be stored:
| File | Description | Storage location |
|---|---|---|
| Root certificate (Root CA) | Global UXP Admin root certificate for trust establishment | On all accessing devices (tablet, PCs with access to the UXP server admin UI) |
| Periphery Certificate (CRT) | Server certificate for the encrypted connection | Exclusively on the UXP server |
| Periphery Key (KEY) | Associated private key | Exclusively on the UXP server |
Distribution and protection of the files
Root certificate (Root CA): The root certificate is global for the UXP Admin and must be installed on all devices that access the UXP server – i.e. on the tablet as well as on all other PCs that, for example, use the UXP server admin UI. Only once the root certificate is installed is the connection established by the UXP server classified as trustworthy.
Commissioning checklist
- Windows 10 or 11 (64-bit) installed and at current patch level
- Minimum hardware requirements met
- Local administrator account available
- Peripheral devices connected via USB, drivers installed and recognised
- Static IP address or IP reservation set up
- Ports 5000 and 5001 released on the local network
- Operating mode (HTTP or HTTPS) defined
- For HTTPS: root certificate (Root CA) installed on all accessing devices (tablet, client PCs)
- For HTTPS: Periphery Certificate (CRT) and Periphery Key (KEY) stored exclusively on the UXP server (do not leave the server)
- UXP Bridge registered and started as a Windows service