Technical project

Embedded vehicle-test system

An onboard system guides the test driver through a mission and displays GNSS, CAN and results on a dedicated interface.

CONTEXT

Context and objective

During a test, the driver must follow a defined sequence, keep speed and distance within tolerance and read only the essential signals without distraction.

SYSTEM

Architecture

A configuration file describes the mission read by the onboard application. GPS and CAN channels feed test state, instructions, timer, progress chart and deceleration results directly on the device.

2.1

Devices and sensors

Rugged embedded display
GNSS receiver
CAN interface
Local storage for configurations and results

2.2

Connectivity and protocols

GNSS
CAN and configured signals
Local mission file
VBO logs and exportable results

2.3

Dashboards and operations

Contextual driver instructions
Real-time speed and tolerance
Timer, run and distance
Deceleration results and numerical screens

2.4

HDA contribution

Test-mission analysis
Interface design
Embedded application development
Field testing and documentation

Engineer configuring an embedded display connected to GNSS and CAN in a test vehicle — Embedded-display integration with GNSS and CAN signals.

Engineering workstation analysing the mission, CAN signals and vehicle-test results — Mission, tolerance and test-result analysis.

EVIDENCE

Outcomes and evidence

Device screens, configurations, logs and application files are available. The images document the interface; no approval outcome or vehicle-specific test result is published.

TRUST

Role of Trusted Data

Traceability across configuration, run and result files helps reconstruct a test. It does not replace procedure, instrument calibration or accountability in the testing process.