Connecting SOME/IP with Middleware / 2026-09-03

[rolandreichweinbmw]

General

• Time 16:00 CEST

Participants

• @johannes-esr
• @kimwoelfel
• @ArnavChatterjee
• @AndreuMontiel
• @LarsVoelker
• @joaofaria
• @LuisCastela
• @filipe-cuim
• @jordioliva
• @paragkaranjekar
• @rolandreichweinbmw

Agenda

How to integrate Middleware with SOME/IP since the communication patterns are overlapping and Middleware could be ideal to distribute SOME/IP between cores ECU internally.

• @kimwoelfel: Experience from past projects: Via glue code connection between MW and SOME/IP
• Generating common code, for Middleware interfaces
• Currently not ready for Open Sourcing
• New format / configuration via SysDaC (FLYNC): Would be natural choice for configuration
• @LarsVoelker: Proposing to configure the whole setup in SysDaC/FLYNC
  • Proposal by Technica Engineering / KPIT
• @filipe-cuim : taking into account signal based communication, upcoming in Middleware
• Previous work: Intermediate model, also done in FLYNC

Plan:

• @kimwoelfel provides an example for glue code
• @ArnavChatterjee can provide a generator for glue code based on FLYNC
• @LarsVoelker: Application for ETS (Enhanced Testability Service) : Open Alliance TC8 specification - support for running the tests to individually implement
• @kimwoelfel can provide an example for provider and consumer, with small example to demo the main feature