Diagnostics - Weekly

[FScholPer]

2026-07-20

Participants

@zinklaj
@stmuench
@FScholPer

Agenda

• PR Gateway cda int inc_diagnostics#6

Minutes

• Change from inc_diagnostics to diagnostics with alias
• build: add bazel configs for QNX 8 inc_diagnostics#10 (Toolchain should be updated to newer version)
• We should clarify which rust toolchain should be used in both projects.
• UDS API should be there because of legacy support.
• Which requirements should be asilb and where to locate them or how to break them down.
• Check Requirements against whats scope of S-CORE and whats scope of OpenSOVD.

[FScholPer]

2026-08-03

Participants

@zinklaj
@stmuench
@FScholPer
Rama

Agenda

• score/mw/diag: Add C++ API for DID & RoutineControl inc_diagnostics#4 -> should be reviewed and merged as soon we have a good state
• Bazel Integration into OpenSOVD build(bazel): add bazel build for opensovd-core eclipse-opensovd/opensovd-core#146 -> @FScholPer stops working on it

Meeting Minutes

[FScholPer]

2026-09-07

Participants

@stmuench
@FScholPer

Agenda

• PR score/mw/diag: Add DTC C++ API for diag_lib inc_diagnostics#26

Meeting Minutes

• PR score/mw/diag: Add DTC C++ API for diag_lib inc_diagnostics#26 should be reviewed.
• Define how to proceed (@FScholPer proposal issue )
• Decide if we should reuse the existing faultlib of https://github.com/eclipse-opensovd/fault-lib/tree/main/src
• Feature Requirements should be linked to opensovd component requirements. (currently docs-as-code is not used in opensovd)
• Clearify with Opensovd-core if they can provide component requirements

[FScholPer]

2026-10-05

Participants

@stmuench
@FScholPer

Agenda

• PR score/mw/diag: Add DTC C++ API for diag_lib inc_diagnostics#26

Meeting Minutes

• First integration into S-CORE should be done with existing components
• @FScholPer to check how new apps can be registered in core
• @FScholPer draft first integration with example app

[FScholPer]

2026-10-26

Participants

@stmuench
@FScholPer
@RaviprasadBS

Agenda & Meeting Minutes

• PR Gateway cda int inc_diagnostics#6 -> @RaviprasadBS ferrocene toolchain pr
• Waiting on bazel build system in opensovd/core & cda
• Next year try to get aligned docs-as-code artifacts
• Please check also first demo application and adapter layer: V1.0 scope inc_diagnostics#42
• @FScholPer check if we can switch Gateway cda int inc_diagnostics#6 back to hermetic cpp toolchain. Update Readme and pr comment.