Utility · Free download

V5 Device Bridge — plug your scales, printers and instruments into V5 Ultimate.

A tiny signed local agent that runs on the workstation next to your hardware. USB, serial, Bluetooth and Ethernet/IP devices become first-class citizens in the batch record — reads land against the current step, prints are audit-logged, and no browser plug-ins are needed.

Code-signed & notarized Localhost bind — no inbound ports Auto-update on Stable channel

What it does

The bridge between the browser kiosk and the metal on your floor.

Browsers can't talk directly to a Mettler XS204, a Zebra ZT411 or a Waters HPLC. Device Bridge does — as a service on the workstation — and streams every event into V5 Ultimate over a signed local channel.

Any transport

USB HID, serial (COM/tty), Bluetooth Classic/LE, Ethernet/IP, TCP sockets. One agent, every protocol.

Runs as a service

Windows Service / launchd daemon. Starts at boot, auto-reconnects, survives kiosk reloads and browser restarts.

Audit-logged

Every read, weight, print, calibration and reconnect is stamped with device serial, user and step context — Part 11 / Annex 11 evidence.

Supported devices

Ships with profiles for the hardware you already own.

New models are added as vendor firmware ships — not as custom code. If your device speaks a documented protocol, chances are we already have the profile.

Scales & balances

•Mettler Toledo (XS, XP, XPR, IND)
•Sartorius Cubis / Entris
•A&D FX/GX/GH
•Ohaus Adventurer / Explorer

USB HID · Serial · Ethernet/IP · BT

Label & ZPL printers

•Zebra ZT / ZD / ZQ series
•Honeywell PC/PM/PX
•SATO CL4NX / CL6NX
•TSC MH / MX

USB · Serial · Ethernet · Wi-Fi

Barcode & RFID

•Zebra DS/LI 2200/3600/8100
•Honeywell Xenon / Granit
•Datalogic PowerScan / Gryphon
•Impinj / Zebra RFID readers

USB HID · Bluetooth · Ethernet

Lab instruments

•Waters / Agilent HPLC & GC
•Shimadzu LC / UV / GC
•Metrohm Karl Fischer titrators
•Dissolution baths (Distek, Sotax)

Serial · Ethernet · File watch

Full compatibility matrix ships inside the installer. If a device isn't listed, the integrations team adds a profile — days, not months.

System requirements

Runs on any workstation you already put on the floor.

Requirement	Windows	macOS
OS	Windows 10 21H2+, Windows 11, Windows Server 2019+	macOS 12 Monterey or newer (Intel / Apple Silicon)
CPU / RAM	x64, 2 cores, 2 GB free RAM	Intel or Apple Silicon, 2 GB free RAM
Disk	150 MB install + rolling logs (~200 MB)	150 MB install + rolling logs (~200 MB)
Network	Outbound HTTPS 443 to tenant only	Outbound HTTPS 443 to tenant only
Local port	127.0.0.1:47317 (browser ↔ agent only)	127.0.0.1:47317 (browser ↔ agent only)
Runtime	Bundled — no .NET / JRE dependency	Bundled — no runtime dependency
Permissions	Local admin to install service; runs as LocalService after	Admin to install; runs under _v5bridge daemon user

Install & pairing

Four steps from download to first weight in the batch record.

01
Download
Get the signed installer for the workstation OS. IT can push the same package via Intune / Jamf / SCCM.
02
Install
Runs the installer once with admin. The service registers, opens the localhost port, and starts on boot.
03
Pair with your tenant
Sign in to V5 Ultimate in the kiosk browser, click 'Pair this workstation'. A short-lived pairing token binds the agent to your site.
04
Devices auto-discover
Plugged-in scales, scanners and printers show up in the kiosk device tray. Assign them to workstations or steps and start weighing.

Silent / mass deployment

Both installers accept an unattended flag plus a site-scoped pairing key so IT can pre-provision a whole plant without touching each workstation. Ask your CSM for the current MSI transform / .pkg payload template.

msiexec /i V5DeviceBridge.msi /qn PAIRING_KEY=<site-key>sudo installer -pkg V5DeviceBridge.pkg -target / && v5bridge pair --key <site-key>

Security posture

Signed, localhost-only, no inbound ports — passes IT review on the first pass.

Signed installers

Windows: Authenticode EV. macOS: Developer ID + notarization. SHA-256 checksums published per release.

Localhost bind

Agent listens on 127.0.0.1 only. Nothing on your LAN can reach it — only the browser on the same workstation.

Outbound TLS to tenant

TLS 1.3 to your V5 tenant, certificate pinned. Egress can be locked to your tenant domain in the firewall.

Update channels

Stable auto-updates; Validated pins to the version in your assessment pack; Beta for pre-release device profiles.

Rolling audit logs

Every pair, connect, read, print and update is logged locally and mirrored to your V5 audit trail.

Fail-safe

If the agent can't reach the tenant, devices go read-only and the kiosk shows an unambiguous banner — never silent data loss.

On-prem specification Validated release channel

Troubleshooting

The four checks that resolve 90% of device tickets.

Device doesn't appear in the kiosk tray

Confirm the agent is running (system tray icon on Windows, menu bar on macOS). Restart the V5 Device Bridge service. Unplug/replug USB devices to trigger re-enumeration.

Scale reads intermittent / wrong unit

Open the device profile in the tray → verify baud rate and unit (g / kg / lb). Mettler XS/XP need continuous mode enabled from the balance's menu.

Zebra printer prints blank labels

Check the ZPL profile matches the printer model (203 vs 300 dpi). Send a test label from the tray — if it prints, the template is the issue, not the bridge.

Agent can't reach tenant

Firewall must allow outbound HTTPS 443 to your tenant domain. Corporate proxies with TLS inspection need our root CA pinned exception — see the docs bundle in the installer.

Agent logs live at C:\ProgramData\V5\DeviceBridge\logs (Windows) or /Library/Logs/V5DeviceBridge/ (macOS). Attach the latest log when opening a support ticket.

Release channel

One agent, three channels — match your validation posture.

Stable

Recommended

Auto-updates as new device profiles ship. Best for most workstations.

Validated

Regulated / Private Cloud

Pinned to the exact version in your assessment pack. Manual promotion aligned with your V5 Ultimate release.

Beta

Opt-in

Pre-release device profiles and new transports. Use on a spare workstation, never on a production kiosk.

FAQ

The questions IT and QA always ask.

Do we need one Device Bridge per workstation?: Yes — one per workstation that has devices physically attached. It's a local agent, not a network server. A shared bench with 3 kiosks that share one PC still needs only one install.
Does it work over Citrix / RDS?: Yes, with USB redirection enabled at the session host, or by installing the bridge on the thin client and pairing it to the same tenant.
Can we install it ourselves?: Yes. The self-install path is documented on the on-prem specification page — most IT teams complete a whole plant in an afternoon.
What happens to devices when we update V5 Ultimate?: Nothing — the bridge and the tenant version-negotiate on connect. Old agents keep working with new tenants for at least one major version.
Is it part of the validated release?: Yes. Private Cloud / Validated customers pin a specific bridge build in the same assessment pack as V5 Ultimate itself.

Not sure if your hardware is supported?

Send us the make/model list — we'll confirm profiles and flag anything that needs a new driver before you buy.

Hardware concierge