| Component | Detail |
|---|---|
| Library | vsomeip 3.x (Bosch open-source SOME/IP stack) |
| Build | cmake; requires boost::asio |
| Config | vsomeip JSON config files per application |
| Goal | Provider exposes SpeedService; Consumer subscribes and receives events; verify with Wireshark |
Lab Scope: vsomeip Service Implementation
Exercise 1: vsomeip Service Provider
C++speed_provider.cpp
// vsomeip provider: SpeedService — fires SpeedEvent every 100ms
#include
#include
#include
#include
const vsomeip::service_t SPEED_SVC = 0x1234;
const vsomeip::instance_t SPEED_INST = 0x0001;
const vsomeip::event_t SPEED_EVT = 0x8001;
const vsomeip::eventgroup_t SPEED_EG = 0x0001;
int main() {
auto app = vsomeip::runtime::get()->create_application("SpeedProvider");
app->init();
// Offer service + event
app->offer_service(SPEED_SVC, SPEED_INST);
app->offer_event(SPEED_SVC, SPEED_INST, SPEED_EVT,
{SPEED_EG}, vsomeip::event_type_e::ET_FIELD);
// Publish thread: send speed event every 100 ms
std::thread publisher([&app]() {
float speed_kmh = 0.0f;
while (true) {
std::this_thread::sleep_for(std::chrono::milliseconds(100));
speed_kmh += 0.5f;
if (speed_kmh > 200.0f) speed_kmh = 0.0f;
// Serialise float to big-endian 4 bytes
std::shared_ptr payload =
vsomeip::runtime::get()->create_payload();
std::vector data(4);
uint32_t bits;
std::memcpy(&bits, &speed_kmh, 4);
data[0] = (bits >> 24) & 0xFF;
data[1] = (bits >> 16) & 0xFF;
data[2] = (bits >> 8) & 0xFF;
data[3] = bits & 0xFF;
payload->set_data(data);
app->notify(SPEED_SVC, SPEED_INST, SPEED_EVT, payload);
}
});
app->start(); // blocks until stop() called
publisher.join();
return 0;
} Exercise 2: vsomeip Service Consumer
C++speed_consumer.cpp
#include
#include
#include
const vsomeip::service_t SPEED_SVC = 0x1234;
const vsomeip::instance_t SPEED_INST = 0x0001;
const vsomeip::event_t SPEED_EVT = 0x8001;
const vsomeip::eventgroup_t SPEED_EG = 0x0001;
int main() {
auto app = vsomeip::runtime::get()->create_application("SpeedConsumer");
app->init();
// Register availability handler: called when service appears/disappears
app->register_availability_handler(SPEED_SVC, SPEED_INST,
[&app](vsomeip::service_t svc, vsomeip::instance_t inst, bool available) {
if (available) {
printf("SpeedService available — subscribing
");
app->request_event(svc, inst, SPEED_EVT, {SPEED_EG});
app->subscribe(svc, inst, SPEED_EG);
}
});
// Register message handler: called for each SOME/IP Notification
app->register_message_handler(SPEED_SVC, SPEED_INST, SPEED_EVT,
[](const std::shared_ptr &msg) {
auto payload = msg->get_payload();
if (payload->get_length() >= 4) {
const auto *d = payload->get_data();
uint32_t bits = ((uint32_t)d[0] << 24) | ((uint32_t)d[1] << 16)
| ((uint32_t)d[2] << 8) | (uint32_t)d[3];
float speed;
std::memcpy(&speed, &bits, 4);
printf("Speed: %.1f km/h
", speed);
}
});
app->request_service(SPEED_SVC, SPEED_INST);
app->start();
return 0;
} Summary
vsomeip is the open-source reference implementation of SOME/IP and is used in production by several OEMs and Tier-1s. The JSON configuration files specify the application's local address, service endpoints, and multicast groups — this maps directly to the AUTOSAR ARXML configuration used in production. The key integration test to run: capture the SD OfferService and SubscribeEventgroup exchange with Wireshark, verify the Notification events flow to the consumer, and confirm the event rate matches the specification (10 Hz for this exercise).
🔬 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.