| Component | Technology | Purpose |
|---|---|---|
| Vehicle service | Python + COVESA Kuksa.val SDK | Subscribe to speed signal, compute average |
| Container runtime | containerd + runc (OCI) | Isolate service from host OS |
| OTA deployment | Eclipse Leda (kanto-cm) | Deploy container via MQTT from cloud |
| Signal source | Eclipse Kuksa.val databroker | Provides VSS signals to container |
Lab: Container-Based Vehicle Application
Exercise 1: Vehicle Speed Service Container
# Vehicle speed averaging service
FROM python:3.11-slim
WORKDIR /app
# Install Kuksa.val Python SDK
RUN pip install kuksa-client==0.4.2
COPY speed_avg_service.py .
# Non-root user (security best practice for vehicle apps)
RUN useradd -r -s /bin/false vehicle_app
USER vehicle_app
CMD ["python", "speed_avg_service.py"]Exercise 2: Speed Averaging Service
#!/usr/bin/env python3
"""Vehicle speed averaging service using COVESA Kuksa.val."""
import asyncio
import statistics
from kuksa_client.grpc import VSSClient
KUKSA_ADDRESS = "127.0.0.1"
KUKSA_PORT = 55555
SPEED_VSS = "Vehicle.Speed" # COVESA VSS signal path
WINDOW_SIZE = 10 # 10-sample rolling average
async def main():
speed_history = []
async with VSSClient(KUKSA_ADDRESS, KUKSA_PORT) as client:
print(f"Connected to Kuksa.val at {KUKSA_ADDRESS}:{KUKSA_PORT}")
async for update in client.subscribe_current_values(
[SPEED_VSS]
):
speed_val = update[SPEED_VSS]
if speed_val is not None:
speed_kmh = speed_val.value
speed_history.append(speed_kmh)
# Rolling window average
if len(speed_history) > WINDOW_SIZE:
speed_history.pop(0)
avg_speed = statistics.mean(speed_history)
print(f"Speed: {speed_kmh:.1f} km/h "
f"Avg({WINDOW_SIZE}): {avg_speed:.1f} km/h")
# Publish averaged speed back to Kuksa
await client.set_current_values({
"Vehicle.OBD.Speed": speed_kmh # OBD mirror
})
if __name__ == "__main__":
asyncio.run(main())Summary
The container-based vehicle application lab demonstrates the Eclipse SDV open-source stack in practice. Kuksa.val provides a standardised vehicle signal broker implementing the COVESA VSS taxonomy -- any container subscribing to Vehicle.Speed gets the same signal regardless of whether the physical source is a CAN message from the wheel speed sensor, a SOME/IP service from the chassis ECU, or a simulated value during HIL testing. This abstraction is the practical realisation of the SDV portability promise: the speed averaging service runs unchanged on a development PC (with a Kuksa simulator), a HIL bench, and a real vehicle. Eclipse Leda provides the deployment infrastructure: the container image is published to a registry, and Leda pulls and starts it on the vehicle when instructed via MQTT from the cloud.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.