MOTODEMY™ SDV Platform | Enterprise Automotive Development Suite

Engine RPM

0rpm

Speed

0km/h

Coolant

20°C

Fuel

75%

Battery

12.6V

HV SOC

78%

🎛️ Instrument Cluster

RPM

Engine

KM/H

Speed

°C

Coolant

Fuel

Load

HV SOC

🎮 Vehicle Controls

Throttle0%

Brake0%

Warning Indicators

🔧

🛢️

🌡️

🔋

⛽

🛑

ABS

🎈

🚗

👁️

Exterior Lights & Controls

📊 Vehicle Data

Oil Temp

20°C

Oil Pressure

0 kPa

MAF

0 g/s

MAP

101 kPa

Odometer

12500 km

Runtime

00:00

Wheel FL

0 km/h

Wheel FR

0 km/h

🔌 Network Status

🖥️GW0x700

—

⚙️ECM0x7E0

—

🔄TCM0x7E1

—

🛡️ABS0x7B0

—

🎈SRS0x7B1

—

👁️ADAS0x7D0

🚗 Powertrain

Engine Speed

0 rpm

Vehicle Speed

0 km/h

Throttle Pos

Engine Load

Coolant Temp

20°C

Oil Temp

20°C

Fuel Level

75%

Gear

⚡ Electrical System

Battery Voltage

12.6V

Alternator

Current Draw

Battery SOC

100%

HV Battery

400V

HV SOC

78%

HV Temp

28°C

Charging

Idle

🏎️ Chassis & Dynamics

Steering Angle

0°

Yaw Rate

0 °/s

Lat Accel

0 g

Long Accel

0 g

TPMS FL

2.4 bar

TPMS FR

2.4 bar

TPMS RL

2.4 bar

TPMS RR

2.4 bar

💨 Emissions

MAF

0 g/s

MAP

101 kPa

O2 Sensor 1

0.45V

O2 Sensor 2

0.45V

Catalyst Temp

200°C

DPF Load

15%

NOx Sensor

0 ppm

Intake Temp

25°C

🔌 CAN Bus Monitor

ISO 11898

📋 CAN Frame Structure

Field	Bits	Description
SOF	1	Start of Frame
Identifier	11/29	Message ID (Std/Ext)
RTR	1	Remote Transmission Request
IDE	1	Identifier Extension
DLC	4	Data Length Code
Data	0-64	Payload (8 bytes CAN, 64 CAN-FD)
CRC	15	Cyclic Redundancy Check
ACK	2	Acknowledgement Slot
EOF	7	End of Frame

🔧 UDS DiagnosticsISO 14229-1

Default (0x01) 🔒 Locked ECM @ 0x7E0 P2: 50ms

📋 ISO 14229 Services & NRCs

Supported SIDs

SID	Service	Session	Security

NRC Reference (0x7F Response) - ISO 14229-1:2020

NRC	Category	Name	Description

📝 XCP ProtocolASAM MCD-1

Disconnected

💾 Memory Viewer

Connection

Active

Routing

Active

Messages TX

Messages RX

Latency

2.4ms

Errors

🌐 DoIP GatewayISO 13400-2Online

Logical Address

0x0001

Tester Address

0x0E80

Protocol

DoIP 2.0

Transport

TCP:13400 / UDP:13400

Vehicle Identification

VIN

WBA3A5G59DNP26082

EID

00:11:22:33:44:55

GID

AA:BB:CC:DD:EE:FF

Further Action

0x00 (None)

Gateway Actions

Send Diagnostic Message

📋 DoIP Message Log

📊 DoIP Entities

Entity	Logical Addr	Type	Status
Gateway	0x0001	DoIP Node	Online
ECM	0x0010	ECU	Online
TCM	0x0020	ECU	Online
BCM	0x0030	ECU	Online
ADAS	0x0040	ECU	Online

📋 DoIP Payload Types

Type	Name	Direction
0x0001	Vehicle ID Request	→ TX
0x0004	Vehicle Announcement	← RX
0x0005	Routing Activation Req	→ TX
0x0006	Routing Activation Resp	← RX
0x0007	Alive Check Request	↔
0x0008	Alive Check Response	↔
0x4001	Entity Status Request	→ TX
0x4002	Entity Status Response	← RX
0x8001	Diagnostic Message	→ TX
0x8002	Diagnostic Positive Ack	← RX
0x8003	Diagnostic Negative Ack	← RX

Services Offered

Subscriptions

Events/sec

245

Method Calls

1.2K

SD Messages

Errors

📡 Service DiscoverySOME/IP-SD

Service	ID	Instance	Status
VehicleMotion	0x1000	0x01	Offered
Powertrain	0x1001	0x01	Offered
ADAS	0x2000	0x01	Offered
RadarService	0x2001	0x01	Offered
CameraService	0x2002	0x01	Offered
BodyControl	0x3000	0x01	Offered
Infotainment	0x4000	0x01	Offered
Diagnostics	0x5000	0x01	Offered

📥 Event Subscriptions

Service	Event Group	Events	Status	Action
VehicleMotion	0x01	0	Active

Active subscriptions receive events in real-time based on vehicle simulation

🔧 Method Calls (RPC)

Available Methods

Service	Method	ID	Type
VehicleMotion	getSpeed	0x0001	REQUEST
VehicleMotion	getAcceleration	0x0002	REQUEST
Radar	getTargets	0x0001	REQUEST
Radar	getRange	0x0002	REQUEST
BodyControl	setLight	0x0010	REQUEST
BodyControl	setWindow	0x0011	REQUEST

📋 SOME/IP Message Log

📊 Real-Time Event Data● LIVE

Speed

0km/h

RPM

Lat Accel

0.0g

Lon Accel

0.0g

Yaw Rate

0.0°/s

Radar Targets

HPC Load

24%

Active Apps

Containers

Signal Rate

2.4K/s

Memory

4.2GB

GPU Util

38%

🏗️ SDV ArchitectureSoftware-Defined Vehicle● LIVE

Vehicle Applications Layer ● 8 Running

ADAS Perception ADAS Planning Infotainment Diagnostics Connectivity OTA Agent ML Inference V2X Stack

Vehicle Services Layer ● Active

Vehicle Abstraction Data Broker Security Service Diagnostics Service Update Service Telemetry Service

Middleware Layer 0 msg/s

SOME/IP DDS MQTT gRPC Signal Router Zenoh

Vehicle Computer (HPC) ● Online

Hypervisor VECTRIX-OS Container Runtime GPU Compute NPU Accelerator

🗺️ Zone Controllers

🚗 Front Left

HeadlightTurnDoorWindowMirror

🚗 Front Right

HeadlightTurnDoorWindowMirror

🖥️ Front Central

HVACInfotainmentCluster

🚗 Rear Left

TaillightDoorWindow

🚗 Rear Right

TaillightDoorWindow

🖥️ Rear Central

HVAC RearDisplayBrake Light

📊 Real-Time Data Flow

Signal	Source	Value	Rate
Vehicle.Speed	VehicleMotion	0 km/h	100 Hz
Vehicle.RPM	Powertrain	0	100 Hz
Vehicle.Acceleration.Lat	IMU	0.0 g	200 Hz
Vehicle.Acceleration.Lon	IMU	0.0 g	200 Hz
Vehicle.YawRate	IMU	0.0 °/s	200 Hz
ADAS.Radar.Targets	RadarService	0	20 Hz
ADAS.Camera.Objects	CameraService	0	30 Hz
Battery.SOC	BMS	78%	1 Hz

💾 ECU Flash Programming

Ready--:--

0 / 2,097,152 bytes0%

Flash Operations

📋 Flash Sectors

Sector	Start	Size	Writable
BOOT	0x00000000	64 KB	No
CAL	0x00010000	128 KB	Yes
APP1	0x00030000	512 KB	Yes
APP2	0x000B0000	512 KB	Yes
DATA	0x00130000	64 KB	Yes

📡 FOTA - Firmware Over-The-Air

Current Version v4.2.1

Latest Available v4.3.0

Last Check Just now

Connection Connected

Available Packages

📋 Update Log

--:--:--FOTA system initialized

⚠️ Active DTCs & FIM0

🔴

Red Stop

🟠

Amber Warn

🟡

Protect

🔧

MIL

DTC	Severity	Status	Description	FIM Action
No active DTCs

📋 DTC Database (J1939 Severity)

Code	Severity	Description	FIM Action

🎚️ Calibration Parameters - ECM 0x7E0

Parameter	Address	Value	Unit	Range	Live

📊 Live Measurements - ECM

Signal	Address	Type	Value	Unit

📦 AUTOSAR Layered Software ArchitectureClassic Platform R21-11

Application Layer (SWC)

EngineControl_SWCTransmissionCtrl_SWCBrakeControl_SWCDiagServices_SWCDoorSensor_SWCLightActuator_SWC

Runtime Environment (RTE) - Virtual Function Bus Implementation

Sender/ReceiverClient/ServerMode SwitchTriggerRte_ReadRte_WriteRte_CallRte_IRead

Service Layer

COMDCMDEMFiMNvMOSEcuMBswMComMWdgMStbMDet

ECU Abstraction Layer

IoHwAbCanIfLinIfFrIfEthIfCanSMLinSMFrSMEthSMCanTpLinTp

MCAL (Microcontroller Abstraction Layer)

CanSpiAdcPwmPortDioGptFlsEepWdgMcuIcu

Complex Device Drivers (CDD)

InjectionCtrlBatteryMgmtCustomHW

🏢 AUTOSAR Partnership

Core Partners (9)BMW, Bosch, Continental, Daimler, Ford, GM, PSA, Toyota, VW

Premium Members65+

Development Partners80+

Associate Partners168+

🎯 AUTOSAR Objectives

🔄Reusability of functions across vehicles and OEMs

📐Standardization of interfaces and exchange formats

🧩Hardware abstraction from software

⚙️Configuration over implementation

✅Improved software quality via standardized BSW

🧩 Software Component Types

Type	Description	ECU Bound
Application SWC	Implements algorithms, portable	No
Sensor/Actuator SWC	I/O data preparation	Yes
Composition	Logical grouping of SWCs	No
Service SWC	BSW service access	No
ECU Abstraction SWC	ECU-specific abstraction	Yes
Complex Driver SWC	Direct HW access	Yes

🔌 Port Types & Interfaces

Port	Direction	Communication
P-Port (Provide)	Outgoing	Send data / Offer service
R-Port (Require)	Incoming	Receive data / Use service
PR-Port	Both	Bidirectional (AR4.x)

S/R Interface: Data elements, 1:n or n:1, async
C/S Interface: Operations, n:1, sync/async

⚡ RTE Events & Runnables

Timing Events

TimingEvent BackgroundEvent

Data Events

DataReceivedEvent DataReceiveErrorEvent DataSendCompletedEvent

Operation Events

OperationInvokedEvent AsyncServerCallReturnsEvent

Mode Events

ModeSwitchEvent ModeSwitchAckEvent

Trigger Events

ExternalTriggerOccurredEvent InternalTriggerOccurredEvent

Init Event

InitEvent

// RTE API Examples
Rte_Read_<port>_<data>() - Direct read
Rte_Write_<port>_<data>() - Direct write
Rte_IRead_<runnable>_<port>_<data>() - Implicit read (buffered)
Rte_IWrite_<runnable>_<port>_<data>() - Implicit write (buffered)
Rte_Call_<port>_<operation>() - Client/Server call
Rte_Enter_<name>() / Rte_Exit_<name>() - Exclusive Area

🔧 Service Layer Modules

Module	Full Name	Function
OS	Operating System	Task scheduling, events, alarms
EcuM	ECU State Manager	Startup/shutdown coordination
BswM	BSW Mode Manager	Rule-based BSW control
ComM	Communication Manager	Bus state coordination
NvM	NVRAM Manager	Non-volatile data management
WdgM	Watchdog Manager	Alive supervision
DCM	Diagnostic Comm Manager	UDS protocol handling
DEM	Diagnostic Event Manager	DTC storage & management
FiM	Function Inhibition Manager	Function permission control
Det	Development Error Tracer	Debug error handling
Dlt	Diagnostic Log & Trace	Logging and tracing
StbM	Synchronized Time-Base Manager	Time synchronization

⚙️ MCAL Drivers

Module	Full Name	Function
Mcu	MCU Driver	Clock, power, reset control
Port	Port Driver	Pin configuration
Dio	Digital I/O Driver	Digital read/write
Adc	ADC Driver	Analog to digital conversion
Pwm	PWM Driver	Pulse width modulation
Icu	ICU Driver	Input capture unit
Gpt	GPT Driver	General purpose timer
Spi	SPI Driver	SPI communication
Can	CAN Driver	CAN controller access
Lin	LIN Driver	LIN controller access
Fr	FlexRay Driver	FlexRay controller access
Eth	Ethernet Driver	Ethernet controller access
Fls	Flash Driver	Internal flash access
Eep	EEPROM Driver	Internal EEPROM access
Wdg	Watchdog Driver	Hardware watchdog control

🔄 Mode Management Flow

EcuM
ECU States

→

BswM
Mode Rules

→

ComM
Comm States

→

CanSM/LinSM
Bus States

→

NmIf/CanNm
Network Mgmt

🚀 AUTOSAR Adaptive PlatformAP R22-11

Application Layer (Adaptive Applications)

ADAS_AppV2X_AppOTA_ManagerDiagnostics_AppTelemetry_AppML_Inference

ARA (AUTOSAR Runtime for Adaptive) - ara::*

ara::comara::diagara::perara::logara::execara::cryptoara::iamara::tsyncara::phmara::ucm

Middleware Services

SOME/IPDDSREST APIService DiscoverySerializationTime Sync (gPTP)

Operating System

POSIX PSE51Linux (PREEMPT_RT)QNXContainersHypervisor

📡 ara::com - Communication Management

Pattern	Description	Binding
Events	1:N publish/subscribe notifications	SOME/IP-SD
Methods	Request/Response (sync/async)	SOME/IP-RPC
Fields	Get/Set with notification	SOME/IP
Triggers	Fire-and-forget notifications	SOME/IP

// ara::com Service Proxy Example
auto proxy = radar::RadarServiceProxy::FindService();
proxy->GetTargets().then([](auto targets) {
  // Process radar targets
});

🔧 SOME/IP Services

Service	ID	Instance	Status
RadarService	0x1001	0x01	Offered
CameraService	0x1002	0x01	Offered
FusionService	0x1003	0x01	Offered
DiagService	0x2001	0x01	Offered
UpdateService	0x3001	0x01	Pending

⚡ ara::exec

ADAS_AppRunning

V2X_AppRunning

OTA_ManagerRunning

DiagnosticsRunning

ML_InferenceStopped

State: MachineFG_Running
Function Group: MachineFG

🔐 ara::crypto

Provider

HSM

Keys

Sessions

Status

📦 ara::ucm

Packages

Updates

Rollback

Ready

Status

Idle

📡 Communication Stack

COM Signal interface, PDU assembly, Signal gateway

IPDU Mux Multiplexed PDUs, Container PDUs (CAN-FD/ETH)

PDU Router PDU routing between modules, Gateway functionality

TP Layer CanTp | LinTp | FrTp | DoIP - Segmented transmission

Interface CanIf | LinIf | FrIf | EthIf - HW independent abstraction

Driver Can | Lin | Fr | Eth - Direct HW access

Transceiver CanTrcv | LinTrcv | FrTrcv | EthTrcv

📤 TX Flow (Sending)

1SWC writes signal via Rte_Write

2COM packs signal into PDU buffer

3PDU Router routes to correct bus

4Interface queues PDU

5Driver transmits frame

📥 RX Flow (Receiving)

1Driver receives frame (ISR/polling)

2Interface calls RxIndication

3PDU Router distributes PDU

4COM unpacks signals to buffer

5RTE notifies SWC / SWC reads

🔧 DCM - Diagnostic Communication Manager

Implements ISO 14229 (UDS) protocol handling

SID	Service
0x10	DiagnosticSessionControl
0x11	ECUReset
0x14	ClearDiagnosticInformation
0x19	ReadDTCInformation
0x22	ReadDataByIdentifier
0x27	SecurityAccess
0x2E	WriteDataByIdentifier
0x31	RoutineControl
0x34-37	Upload/Download
0x3E	TesterPresent
0x85	ControlDTCSetting

⚠️ DEM - Diagnostic Event Manager

DTC storage, aging, and event management

📋Event status management

💾DTC storage in NvM

📸Freeze frame capture

📊Extended data records

⏱️Aging and healing

🔗FiM integration

API: Dem_SetEventStatus(EventId, Status)
Status: PASSED | FAILED | PREPASSED | PREFAILED

🚫 FiM - Function Inhibition Manager

DEM Events

P0300, P0217, C0035...

→

FiM Inhibit Conditions

Event combinations & masks

→

Function IDs (FID)

ACC, LKA, AEB, ESC...

→

Permission State

TRUE (allowed) / FALSE (inhibited)

API: FiM_GetFunctionPermission(FID, &Permission) | Permission: TRUE = Function allowed, FALSE = Function inhibited

💾 Memory Stack Architecture

NvM (NVRAM Manager) Block management, read/write jobs, CRC, redundancy

MemIf (Memory Interface) Abstract interface to memory drivers

Fee Flash EEPROM Emulation

Ea EEPROM Abstraction

Fls (Flash Driver) Internal flash access

Eep (EEPROM Driver) Internal/External EEPROM

📦 NvM Block Types

Type	Description
NATIVE	Standard block, no redundancy
REDUNDANT	Dual storage for safety
DATASET	Multiple datasets per block

Features: CRC protection, Write verification, Default values, Immediate writes

🔄 NvM API

// Async operations
NvM_ReadBlock(BlockId, DstPtr)
NvM_WriteBlock(BlockId, SrcPtr)
NvM_RestoreBlockDefaults(BlockId, DstPtr)
NvM_EraseBlock(BlockId)
NvM_InvalidateBlock(BlockId)
// Status check
NvM_GetErrorStatus(BlockId, &Status)
// Immediate (sync)
NvM_SetRamBlockStatus(BlockId, Changed)

👁️ Sensor Fusion ViewSensors OK

● Vehicle ● Pedestrian ● Obstacle

🎮 ADAS Controls

🚗 ACC - Adaptive Cruise Control

🛣️ LKA - Lane Keep Assist

🛑 AEB - Auto Emergency Brake

🔲 BSM - Blind Spot Monitor

📊 ADAS Status

ACC Status

Standby

LKA Status

Off

AEB Status

Armed

BSM Status

Active

Objects Detected

Lead Vehicle

-- m

TTC

-- s

FCW

Clear

📋 ADAS Events

--:--:--ADAS system initialized

HSM Status

Active

Secure Boot

Verified

SecOC

Enabled

Threat Level

Low

Active Keys

Cert Expiry

364d

🛡️ Security ArchitectureISO 21434

Application Security

App AuthenticationSecure APIsInput ValidationCode Signing

Communication Security

SecOCTLS 1.3MACsecIPsecDTLS

Network Security

FirewallIDSIPSVLAN SegmentationDeep Packet Inspection

Platform Security

HSMSecure BootTPM 2.0TEEMemory Protection

📋 Security Events

12:45:23INFOSecOC MAC verified on CAN0 (0x123)

12:44:18INFOTester authenticated via PKI certificate

12:43:05INFOHSM AES-256 key derivation complete

12:42:00OKSecure boot chain verified (3 stages)

12:41:55INFOIDS rule update applied (v2.4.1)

🔐 Hardware Security ModuleSHE+ / EVITA Full

HSM Type

EVITA Full

Vendor

Infineon SLS32

Firmware

v3.2.1

Status

Operational

Key Slots

24 / 32

Temperature

42°C

Tamper Status

Clear

RNG Status

Active

Supported Algorithms

AES-128/256 AES-CMAC AES-GCM SHA-256/384/512 HMAC-SHA256 RSA-2048/4096 ECDSA P-256/P-384 ECDH Ed25519 PBKDF2

⚡ HSM Operations

Operation	Count	Avg Time	Status
AES Encrypt	12,847	0.8ms	OK
AES Decrypt	11,923	0.9ms	OK
MAC Generate	45,291	0.3ms	OK
MAC Verify	44,872	0.4ms	OK
ECDSA Sign	892	12ms	OK
ECDSA Verify	1,204	15ms	OK
Key Derive	156	5ms	OK
RNG Generate	8,423	0.1ms	OK

Quick Actions

🔒 Secure Onboard Communication (SecOC)AUTOSAR 4.4

Protected PDUs

MACs Verified

45.2K

MAC Failures

Freshness Counter

0x8A3F

📡 Protected PDU Groups

PDU ID	Name	Algorithm	Key	MAC Len	Status
0x100	Brake_Cmd	CMAC	KEY_01	64-bit	OK
0x110	Steering_Cmd	CMAC	KEY_01	64-bit	OK
0x120	Throttle_Cmd	CMAC	KEY_02	64-bit	OK
0x200	ADAS_Control	CMAC	KEY_03	128-bit	OK
0x210	ACC_Target	CMAC	KEY_03	64-bit	OK
0x300	Diag_Request	CMAC	KEY_DIAG	64-bit	OK
0x400	FOTA_Data	GMAC	KEY_OTA	128-bit	OK

⏱️ Freshness Management

Freshness Type

Trip Counter + Msg Counter

Trip Counter

0x0042

Sync Status

Synced

Sync Master

GW_ECU

SecOC Configuration

AuthDataFreshnessLen: 24 bits
AuthDataFreshnessStartPos: 0
AuthInfoTxLength: 64 bits
SecOCFreshnessValueTxBitLength: 8
SecOCAuthenticationBuildAttempts: 3
SecOCAuthenticationVerifyAttempts: 3

🔑 Key Management SystemAUTOSAR Key Manager

Key ID	Name	Type	Algorithm	Size	Usage	Expires	Status
0x01	MASTER_KEY	Symmetric	AES	256-bit	Key Derivation	Never	Active
0x02	SECOC_KEY_01	Symmetric	AES-CMAC	128-bit	SecOC MAC	2026-01-01	Active
0x03	SECOC_KEY_02	Symmetric	AES-CMAC	128-bit	SecOC MAC	2026-01-01	Active
0x04	DIAG_AUTH_KEY	Symmetric	AES	128-bit	UDS Security	2025-12-31	Active
0x05	FOTA_SIGN_KEY	Asymmetric	ECDSA P-256	256-bit	OTA Signing	2027-06-30	Active
0x06	TLS_SERVER_KEY	Asymmetric	ECDSA P-384	384-bit	TLS Server	2026-03-15	Active
0x07	V2X_SIGN_KEY	Asymmetric	ECDSA P-256	256-bit	V2X Signing	2025-09-01	Expiring
0x08	DEBUG_KEY	Symmetric	AES	128-bit	Debug Access	N/A	Disabled

📜 Certificate Store

Subject	Issuer	Type	Expires	Status
ECU_ID_CERT	OEM Root CA	X.509	2027-01-01	Valid
TLS_SERVER	OEM Sub CA	X.509	2026-03-15	Valid
CODE_SIGN	OEM Code CA	X.509	2027-06-30	Valid
V2X_PSEUDONYM	SCMS CA	IEEE 1609.2	2025-09-01	Expiring

🔄 Key Operations

IDS Status

Monitoring

Rules Active

247

Alerts (24h)

Blocked

Packets Analyzed

1.2M

ML Model

v2.1

🚨 Intrusion Detection Rules

Rule ID	Category	Description	Severity	Action
CAN-001	Anomaly	Unexpected CAN ID on bus	High	Alert + Log
CAN-002	DoS	CAN bus flood detection	Critical	Block + Alert
CAN-003	Injection	Diagnostic ID spoofing	Critical	Block + Alert
ETH-001	Scan	Port scan detection	Medium	Alert
ETH-002	DoS	SYN flood detection	High	Block + Alert
ETH-003	MITM	ARP spoofing detection	Critical	Block + Alert
UDS-001	Auth	Brute force security access	High	Lockout
UDS-002	Anomaly	Unusual service sequence	Medium	Alert

📊 Threat Intelligence

Last Update

2h ago

Threat Feed

Connected

IOCs Loaded

1,247

ML Inference

Active

Recent Alerts

11:23:45WARNETH-001: Port scan from 192.168.1.50

09:15:22WARNUDS-002: Unusual ReadDID sequence

YesterdayINFORule update: 5 new signatures added

🎯 Penetration Testing SuiteTest Mode Only

CAN Bus Tests

UDS Security Tests

Network Tests

📋 Test Results

Test	Result	Vulns	Time
CAN Fuzzing	Pass	0	12.4s
UDS Brute Force	Pass	0	45.2s
Port Scan	Info	2 open	8.1s

📊 Security Assessment Summary

Tests Passed

Warnings

Vulnerabilities

Coverage

94%

Last Full Scan

2d ago

Compliance

ISO 21434

Communication

8ISO 15118

Charging Safety

6ISO/IEC

Connectors

3IEC 62196

Charging Modes

4IEC 61851

Security

3ISO

1️⃣ 🔌 Core EV Charging Communication (MOST IMPORTANT) Vehicle ↔ Charger

ISO 15118 is the core communication protocol between electric vehicles and charging stations. It enables Plug & Charge, smart charging, and V2G functionality.

ISO 15118-1

General information & use cases

ISO 15118-2

Network & application protocol (Plug & Charge, V2G)

ISO 15118-3

Physical layer (Power Line Communication – PLC)

ISO 15118-4

Conformance testing

ISO 15118-5

Physical layer for wireless power transfer

ISO 15118-8

Wireless communication (future scope)

ISO 15118-20 ⭐

Next-gen EV charging: Bidirectional (V2G/V2H/V2L), AC+DC unified, Mandatory for 2026+ platforms

✅ Used by:

CCS Chargers Plug & Charge Smart Charging OTA Billing PKI Certificates Bharat EV (India)

2️⃣ ⚡ Charging System & SafetyCritical

Defines electrical safety, isolation, and protection requirements.

ISO 17409

Safety requirements for conductive charging

ISO 6469-1

Functional safety of EVs

ISO 6469-2

Vehicle operational safety

ISO 6469-3

Electrical shock protection

ISO 18246

Measurement of charging power (accuracy)

3️⃣ 🔌 Connector & InterfaceIEC (Hardware)

Defines how the plug physically mates with the vehicle.

IEC 62196-1

General requirements for plugs & sockets

IEC 62196-2

AC charging connectors (Type 2 – Europe/India)

IEC 62196-3

DC charging connectors (CCS2)

⚠️ IEC standards are mandatory companions to ISO 15118 (ISO = communication, IEC = hardware)

4️⃣ ⚡ Charging Modes & Power LevelsIEC 61851

Defined jointly with IEC standards for AC/DC charging.

IEC 61851-1

General charging system requirements

IEC 61851-23

DC fast charging stations

IEC 61851-24

Digital communication for DC charging

Mode 2/3 – AC Slow Mode 4 – DC Fast

5️⃣ 🛡️ Cybersecurity for EV ChargingMandatory

Mandatory for connected charging & Plug & Charge.

ISO 21434

Automotive cybersecurity engineering

ISO 24089

Secure software update (OTA)

ISO/IEC 27001

PKI & certificate management (backend)

Certificate Auth Secure Billing Charger-Cloud Comm

6️⃣ 🔋 Grid Interaction & Energy MgmtV2G/V2H/V2L

For smart charging & bidirectional power flow.

ISO 15118-20

V2G / V2H / V2L bidirectional charging

ISO 50001

Energy management systems

ISO/TR 14187

Power quality reference

7️⃣ 🌡️ Environmental & Electrical Robustness

ISO 16750

Electrical & environmental conditions

ISO 7637

Electrical disturbances & transients

ISO 20653

IP protection (water & dust)

ISO 9227

Corrosion (salt spray testing)

🔁 EV Charging Stack (Mental Model)

👤 User / Grid

Billing / Authentication

ISO 15118 (Plug & Charge)

🚗↔🔌 Vehicle ↔ Charger

Communication: ISO 15118-2/20

Safety: ISO 17409 / 6469

Power: IEC 61851 / 62196

🛡️ Security Layer

ISO 21434

ISO 24089

⚡ Power Hardware

Connectors: IEC 62196

Modes: IEC 61851

⚖️ AC vs DC Charging – ISO Relevance

Area	AC Charging	DC Fast Charging
Communication	ISO 15118 (optional)	ISO 15118 (mandatory)
Connector	IEC 62196-2 (Type 2)	IEC 62196-3 (CCS2)
Safety	ISO 6469	ISO 17409 + 6469
Smart Charging	Limited	Full (V2G, Plug & Charge)

🎯 What Engineers Actually ImplementReality Check

If you work on EV BSW / diagnostics / charging, you mainly touch:

ISO 15118-2 ISO 15118-20 ISO 17409 ISO 6469-3 ISO 21434 IEC 61851 IEC 62196

💡 CAN / Ethernet diagnostics (UDS) still exists alongside charging protocols

🇮🇳 India ContextBharat EV

CCS2 + ISO 15118

Bharat EV ecosystem standard

Plug & Charge

Adoption starting in India

ISO 15118-20

Will dominate 2026+ EV platforms

📚 Quick Reference Actions

⚡ EV Charging Simulation

Disconnected --

SELECT CONNECTOR TYPE

CHARGING MODE

Power Level 0 kW

0 kW 350 kW

Voltage

0 V

Current

0 A

Energy

0 kWh

BATTERY STATE OF CHARGE

20%

Range

80 km

Time to 80%

--:--

Capacity

75 kWh

Battery Temp

25°C

Charge Rate

0 C

COMMUNICATION PROTOCOL LOG

📋 Connector Standards Comparison

Connector	AC Standard	DC Standard	Max AC	Max DC	Communication	Region
CCS1	SAE J1772	IEC 62196-3	19.2 kW	350 kW	ISO 15118 (PLC)	🇺🇸 North America
CCS2	IEC 62196-2	IEC 62196-3	43 kW	350 kW	ISO 15118 (PLC)	🇪🇺 Europe / 🇮🇳 India
NACS	SAE J3400	SAE J3400	11.5 kW	1000 kW*	ISO 15118 / PLC	🇺🇸 N. America (New)
GB/T	GB/T 20234.2	GB/T 20234.3	27.7 kW	250 kW	GB/T 27930 (CAN)	🇨🇳 China
CHAdeMO	Type 1 (J1772)	CHAdeMO 2.0	19.2 kW	400 kW	CAN Bus	🇯🇵 Japan (Legacy)

* NACS V4 specification supports up to 1MW for commercial vehicles

〰️ AC Charging Modes (IEC 61851-1)

Mode 1

Direct socket connection (No PWM, No protection) - Not recommended

Mode 2

In-cable control box (ICCB) • PWM signaling • Up to 3.7 kW • Home charging

Mode 3 ⭐

Dedicated EVSE • PWM + Pilot signal • Up to 43 kW • Public/Home wallbox

CP Signal: Control Pilot • 1kHz PWM • Duty cycle = Max current

⚡ DC Charging Mode 4 (IEC 61851-23/24)

Mode 4

DC Fast Charging • Off-board charger • Direct DC to battery • 50-350+ kW

CCS/NACS

ISO 15118 (PLC)

CHAdeMO/GB/T

CAN Bus Protocol

Charging Curve: Constant Current → Constant Voltage → Taper

🚀 Build PipelineBuild #1247main

✓ Checkout

→

✓ Dependencies

→

✓ Static Analysis

→

✓ MISRA Check

→

✓ Compile

→

✓ Unit Tests

→

⟳ Integration

→

HIL Tests

→

Security Scan

→

Deploy

Started: 14:32:15 Duration: 12m 34s Triggered by: commit a3f8c21 Author: [email protected]

Build Success Rate

94.2%

Test Coverage

87.5%

MISRA Compliance

98.1%

Avg Build Time

18min

Deployments (Week)

MTTR

2.4h

📋 Stage Details

Stage	Status	Duration	Agent
Checkout	✓	8s	linux-01
Dependencies	✓	45s	linux-01
Static Analysis	✓	2m 12s	linux-01
MISRA Check	✓	3m 45s	linux-02
Compile	✓	1m 23s	linux-02
Unit Tests	✓	4m 12s	linux-03
Integration	⟳	-	hil-bench-01

📜 Build Log

14:44:49INFO[Integration] Starting HIL test suite...

14:44:45PASS[Unit Tests] 1,247 tests passed (0 failed)

14:40:33INFO[Unit Tests] Running test suite...

14:39:10PASS[Compile] Build successful (0 warnings)

14:37:47PASS[MISRA] 98.1% compliance (12 deviations)

📦 Recent Builds

Build	Branch	Commit	Author	Status	Duration	Time
#1247	main	a3f8c21	dev@vectrix	Running	12m 34s	14:32
#1246	main	b7e2f19	alice@vectrix	Success	17m 22s	11:45
#1245	feature/adas	c4d9a33	bob@vectrix	Success	19m 08s	10:20
#1244	main	e1f5b82	dev@vectrix	Success	16m 55s	09:15
#1243	hotfix/can	f8a2c71	carol@vectrix	Failed	8m 12s	Yesterday
#1242	main	d3b7e65	alice@vectrix	Success	18m 33s	Yesterday
#1241	develop	a9c4f28	bob@vectrix	Success	20m 11s	Yesterday
#1240	main	b2e8d44	dev@vectrix	Success	17m 45s	2 days ago

📊 Build Trend (7 days)

⚙️ Build Configuration

Toolchain

GCC 12.2

Target

ARM Cortex-R5

Optimization

-O2

Standard

C11 / C++17

🖥️ Build Agents

linux-01Idle

linux-02Idle

linux-03Idle

hil-bench-01Busy

hil-bench-02Idle

Tests Passed

1,247

Tests Failed

Tests Skipped

Coverage

87.5%

MC/DC Coverage

82.3%

Execution Time

4m 12s

🧪 Test Suites

Suite	Tests	Passed	Coverage	Time
CAN Driver	187	187	92%	34s
UDS Stack	312	312	89%	52s
SecOC Module	145	145	95%	28s
NvM Manager	98	98	88%	18s
COM Stack	234	234	84%	41s
DCM Module	156	156	91%	29s
DEM Module	115	115	87%	21s

📊 Coverage Breakdown

Statement Coverage

89%

Branch Coverage

85%

MC/DC Coverage

82%

Function Coverage

94%

Test Types

Unit: 847 Integration: 312 System: 88

🔬 HIL Test ResultsIn Progress

Test Case	ECU	Status	Duration	Result
TC_CAN_001: Bus-off recovery	GW	Done	12s	Pass
TC_CAN_002: Message timing	GW	Done	8s	Pass
TC_UDS_001: Session transitions	ECM	Running	-	-
TC_UDS_002: Security access	ECM	Pending	-	-

MISRA Compliance

98.1%

Code Smells

Tech Debt

2.4d

Duplications

1.2%

Complexity (Avg)

4.2

Vulnerabilities

📏 MISRA C:2012 Violations

Rule	Category	Count	File	Status
Rule 10.4	Required	3	can_driver.c	Deviation
Rule 11.3	Required	2	mem_util.c	Deviation
Rule 14.3	Required	4	uds_handler.c	Deviation
Rule 17.7	Required	3	nvm_manager.c	Deviation

Total: 12 deviations with approved deviation records

🔍 Static Analysis

Polyspace

Pass

Coverity

Pass

PC-lint

Pass

CERT C

Pass

Findings by Severity

🔴 Critical0

🟠 High0

🟡 Medium8

🟢 Low16

📈 Quality GatePassed

Metric	Threshold	Actual	Status
Test Coverage	≥ 80%	87.5%	✓
MISRA Compliance	≥ 95%	98.1%	✓
Critical Vulnerabilities	= 0	0	✓
Code Duplication	≤ 3%	1.2%	✓
Cyclomatic Complexity	≤ 15	4.2 (avg)	✓

📦 Build ArtifactsBuild #1246

Artifact	Type	Size	Checksum (SHA256)
vectrix_ecu_v2.4.1.hex	Firmware	2.4 MB	a3f8c21b...
vectrix_ecu_v2.4.1.elf	Debug	8.7 MB	b7e2f198...
vectrix_ecu_v2.4.1.a2l	Calibration	1.2 MB	c4d9a334...
test_report.html	Report	456 KB	e1f5b821...
coverage_report.html	Report	1.8 MB	f8a2c712...
misra_report.pdf	Report	234 KB	d3b7e652...
sbom.json	SBOM	89 KB	a9c4f283...

🗃️ Artifact Repository

Repository

Artifactory

Storage Used

45.2 GB

Retention

90 days

Versions

247

Recent Versions

v2.4.1Today

v2.4.03 days ago

v2.3.51 week ago

v2.3.42 weeks ago

📋 Software Bill of Materials

Component	Version	License
AUTOSAR BSW	R21-11	Proprietary
FreeRTOS	10.5.1	MIT
mbedTLS	3.4.0	Apache 2.0
LwIP	2.1.3	BSD
tinycbor	0.6.0	MIT

Production ECUs

Test Benches

Deployments Today

Rollback Available

Yes

🎯 Deployment Targets

Target	Environment	Version	Status
HIL-Bench-01	Test	v2.4.1	Updating
HIL-Bench-02	Test	v2.4.0	Online
SIL-Server	Test	v2.4.1	Online
Proto-Vehicle-A	Staging	v2.3.5	Online
Proto-Vehicle-B	Staging	v2.3.5	Online
Fleet-Pilot	Production	v2.3.4	Online

📜 Deployment History

14:45:12INFO[HIL-Bench-01] Flashing v2.4.1 (45%)

14:44:30INFO[HIL-Bench-01] Starting deployment

11:23:45OK[SIL-Server] v2.4.1 deployed successfully

10:15:22OK[HIL-Bench-02] v2.4.0 deployed successfully

YesterdayOK[Proto-Vehicle-A] v2.3.5 deployed

🔄 Deployment Pipeline

✓ Build

→

✓ Unit Tests

→

✓ SIL Tests

→

⟳ HIL Tests

→

Staging

→

Approval

→

Production

✅ A-SPICE Compliance

SYS.1

SYS.2

SWE.1

SWE.2

SWE.4

SWE.6

🛡️ ISO 26262 ASIL Coverage

ASIL-D

ABS, SRS

ASIL-C

HVB

ASIL-B

ECM, TCM

BCM, IPC

Network Standards

7ISO/IEEE

Diagnostic Standards

12ISO

Safety & Security

5ISO

OBD/Emissions

8ISO

🔌 1. Vehicle Networks & Physical CommunicationCAN/LIN/FlexRay/Ethernet

Defines how ECUs talk electrically and at data-link level.

ISO 11898-1

CAN Data Link Layer

ISO 11898-2

High-Speed CAN (500 kbps / 1 Mbps)

ISO 11898-3

Low-Speed / Fault-Tolerant CAN

ISO 17987

LIN Protocol

ISO 17458

FlexRay Communication System

ISO 13400 (DoIP)

Diagnostics over Ethernet

IEEE 802.3

Automotive Ethernet PHY (with ISO 13400)

✅ Used in:

Powertrain ECUs BCM ABS EPS ADAS Controllers Infotainment

📡 2. Transport & Network LayerAbove CAN/Ethernet

Defines segmentation, flow control, addressing.

ISO 15765-1

Diagnostic communication over CAN (DoCAN)

ISO 15765-2

Transport protocol (segmentation & flow control)

ISO 15765-3

UDS on CAN mapping

ISO 15765-4

Emissions diagnostics on CAN

ISO 13400-2

DoIP transport & routing

🔧 3. Diagnostics - Unified Diagnostic Services (UDS)Core of Passenger Vehicles

ISO 14229-1

UDS services (ReadDataByID, RoutineControl, DTCs)

ISO 14229-2

Session layer

ISO 14229-3

UDS on CAN

ISO 14229-5

UDS on IP (DoIP)

ISO 14229-7

UDS on LIN

Used for:

Flashing (OTA & Service) Manufacturing Diagnostics Dealer Service Tools Warranty & Fault Analysis

🚨 4. OBD / EmissionsLegally Mandatory

Required for BS-VI / Euro-6 / EPA compliance.

ISO 15031-1

OBD general information

ISO 15031-2

Diagnostic Trouble Codes (emissions)

ISO 15031-3

Diagnostic services (OBD modes)

ISO 15031-4

External test equipment

ISO 15031-5

Emission-related data

ISO 15031-6

Communication (aligned with SAE J1979)

ISO 27145

WWH-OBD (newer global OBD standard)

⚡ 5. Electrical Power & Energy

ISO 16750

Environmental conditions (temp, vibration, voltage)

ISO 7637

Electrical disturbances & transients

ISO 6469

EV high-voltage safety (EV/Hybrid)

ISO 21498

Electrical load management

🛡️ 6. Functional SafetyMandatory

ISO 26262 (Part 1-12)

Functional Safety (ASIL A-D)

Applies to:

Brakes Steering Powertrain ADAS Battery Management

🔐 7. CybersecurityNow Mandatory

ISO 21434

Automotive cybersecurity engineering

ISO 24089

Secure software update (OTA)

Used with:

Secure Boot Secure Diagnostics Encrypted DoIP Flashing

📦 8. Software Architecture & LifecycleUsed by all OEMs

AUTOSAR Classic

Classic Platform

AUTOSAR Adaptive

Adaptive Platform

ISO 12207

Software lifecycle processes

ISO 15288

System lifecycle processes

ℹ️ AUTOSAR itself is not ISO, but designed to comply with ISO 26262 & ISO 21434

👤 9. Human-Vehicle & Legal Interfaces

ISO 7736

Dashboard symbols & warning icons

ISO 4040

Control indicators

ISO 2575

Road vehicle symbols

🔧

⛽

🌡️

🔋

⚠️

🚗 Vehicle Settings

📡 CAN Bus Settings

⚠️ FIM Settings (J1939)

🔧 Simulation Settings