Technical data
The unit, in numbers.
Everything an integrator needs before deciding whether Ulark5 fits the cabinet and the cabling already on site.
The unit
What connects where.
Equipment on one side, cabinet on the other. Every figure below is a published specification.
- Serial & fieldbus
- RS232 · RS485 · CAN · LON
- Connection ports
- 16, modules connectable
- Relay outputs
- 8 NO / 8 NC
- Network & host
- Ethernet · USB
- Mobile
- GSM 3G
- Power
- 12–30 V, 2 A
Ulark5
Specifications.
An industrial unit rather than a PC in a cabinet: relay outputs, a wide DC input and six wired interface types, so it can be wired into a line as it stands.
- Power
- 12–30 V, 2 A
- Relays
- 8 NO / 8 NC
- Interfaces
- RS232, RS485, Ethernet, CAN, USB, LON
- Connection ports
- 16, with hardware modules connectable
- Mobile
- GSM 3G module
- Wi-Fi
- Optional adapter, via Ethernet or USB
- Firmware
- Ulark5
- Operating system
- Linux
Interfaces
How it reaches the equipment.
Deliberately conventional. Longevity on an inspection line comes from interfaces that will still be supported in ten years.
Wired
How benches and analysers are reached
- RS232
- RS485
- CAN
- LON
- Ethernet
- USB
Wireless
Where cabling to the position is impractical
- Bluetooth
- Wi-Fi
- GSM 3G
Control & electrical
Device-level actuation and power envelope
- 8 NO / 8 NC relays
- 16 connection ports
- 12–30 V, 2 A
- Expansion modules
Vehicle
Read from the vehicle itself
- OBD
- OBFCM
Architecture
Where the unit sits.
The same chain as every installation: instruments, unit, applications, archive, register.
Optional
Expansion server.
Not required to run a line. It widens the archive beyond what the unit holds, which is what a station wants once several years of inspections have accumulated.
- Processor
- Intel Core i3 or higher
- Memory
- 4 GB RAM
- Archive storage
- 2 TB HDD
- Operational storage
- 256 GB SSD
Where it runs
Four places, one system.
The parts sit where the work happens rather than where the software would prefer.
On the line
The Ulark5 unit sits with the equipment and drives it directly over the wired interfaces.
At the station
DVS.WEB runs on the station server; an optional expansion server widens the archive beyond what the unit holds.
In hand
DVS.MOBILE runs on the handheld the inspector carries, paired to the benches over Bluetooth.
Without a connection
None of it depends on reaching the internet. Register submission resumes when the link returns.
Integrations
What it talks to beyond the line.
An inspection is not finished until it is filed with the register that requires it.
State register
Submission and lookupCompleted inspection results are submitted to the state vehicle inspection register, and vehicle data is retrieved from it at registration. Each country runs its own register, so the connection — including the payment handling a station needs at the counter — is configured per installation.
Google Workspace
Documents and schedulingThe system links to Drive for storing data, Docs for generating reports, Sites for publishing information and Calendar for scheduling.
Station systems
Onward transferProcessed information is archived and handed on to whatever the company already runs for accounting and resource planning.
Need the detail behind a number?
Integration questions go straight to the engineers who wrote the drivers.