Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

Skeleton Side: Offer Service & Send Events

C++skeleton_app.cpp
// Generated by arxml2cpp from ARXML ServiceInterface
#include "skeleton/temperature_service_skeleton.h"
#include <ara/exec/application_client.h>

void SkeletonMain() {
    ara::core::Initialize();

    TemperatureServiceSkeleton skel(
        ara::core::InstanceSpecifier{
            "SkeletonApp/TemperatureService/Instance0"});
    skel.OfferService();

    ara::exec::ApplicationClient appClient;
    appClient.ReportApplicationState(
        ara::exec::ApplicationState::kRunning);

    float temp = 20.0f;
    while (running) {
        skel.Temperature.Send(temp);  // send Event at 10 Hz
        temp += 0.1f;
        std::this_thread::sleep_for(std::chrono::milliseconds(100));
    }

    appClient.ReportApplicationState(
        ara::exec::ApplicationState::kTerminating);
    skel.StopOfferService();
    ara::core::Deinitialize();
}

💡 OfferService()

OfferService() registers the skeleton with ara::com CM and triggers a SOME/IP-SD Offer Service message. Subscribers will receive all future Send() calls. The skeleton destructor automatically calls StopOfferService() if not called explicitly.

Proxy Side: Find Service & Subscribe

C++proxy_app.cpp
#include "proxy/temperature_service_proxy.h"
#include <ara/exec/application_client.h>

void ProxyMain() {
    ara::core::Initialize();

    // Asynchronous service discovery — callback on offer/stop-offer
    TemperatureServiceProxy::StartFindService(
        [](ara::com::ServiceHandleContainer<TemperatureServiceProxy::HandleType> handles,
           ara::com::FindServiceHandle) {
            if (!handles.empty()) {
                auto proxy = std::make_unique<TemperatureServiceProxy>(handles[0]);
                proxy->Temperature.SetReceiveHandler([&proxy] {
                    proxy->Temperature.GetNewSamples(
                        [](auto sample) {
                            LogTemperature(*sample);
                        }, 10 /* maxSampleCount */);
                });
                proxy->Temperature.Subscribe(10); // cache up to 10 samples
            }
        },
        ara::core::InstanceSpecifier{
            "ProxyApp/TemperatureService/Instance0"});

    ara::exec::ApplicationClient appClient;
    appClient.ReportApplicationState(ara::exec::ApplicationState::kRunning);
    WaitForShutdown();
    ara::core::Deinitialize();
}

Manifest Wiring & Common Mismatches

Manifest FieldValueMust Match
serviceInterfaceRef/SkeletonApp/TemperatureServiceInterfaceARXML ServiceInterface shortName path
someIpServiceInstanceId.serviceId0x1234Same in both provider and consumer manifests
someIpServiceInstanceId.instanceId0x0001Consumer must request same or use 0xFFFF wildcard
networkEndpoint.port50001UDP port open on provider; not blocked by netfilter

🔍 Debug Tip

Capture SD traffic with sudo tcpdump -i eth0 udp port 30490 -w sd.pcap and open in Wireshark with the SOME/IP dissector. Verify the Offer Service message appears and the Subscribe Eventgroup Ack is returned. If the Ack is missing, check the instance ID mismatch or firewall rules.

Launch via Execution Manager

JSONapplication_manifest.json
{
  "shortName": "SkeletonApp",
  "executable": {
    "path": "bin/SkeletonApp",
    "startupConfig": {
      "schedulingPolicy": "OTHER",
      "startupTimeout": 5000,
      "shutdownTimeout": 2000
    }
  },
  "functionGroupStateMembership": [
    {"functionGroup": "MachineFG", "states": ["Driving"]}
  ]
}

💡 Observing State Transitions

On a Linux-based platform, filter the systemd journal: journalctl -f -t ExecutionManager. You will see entries like Process SkeletonApp transitioned to Running and Terminating as you change Function Group states.

Summary

A minimal Adaptive application requires: generated skeleton/proxy headers from arxml2cpp, correct InstanceSpecifier paths matching the Service Instance Manifest, ReportApplicationState calls to EM, and valid manifest files in the Software Package. All other complexity builds on this foundation.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousSOME/IP & Service-Oriented ArchitectureNext →Service Interface Definition (ARXML)