Skip to content

Fiat eDoblo: add passive lock status#1438

Open
strangesource wants to merge 1 commit into
openvehicles:masterfrom
strangesource:ftdo-passive-lock-state
Open

Fiat eDoblo: add passive lock status#1438
strangesource wants to merge 1 commit into
openvehicles:masterfrom
strangesource:ftdo-passive-lock-state

Conversation

@strangesource

@strangesource strangesource commented Jun 22, 2026

Copy link
Copy Markdown

Problem

The Fiat e-Doblo / Stellantis EMP2 module did not map the validated passive lock-state frame to the standard OVMS lock metric.

Validated passive signal:

  • CAN ID 0x612
  • Byte 1 bit 0x02 means unlocked
  • OVMS mapping: v.e.locked = !(d[1] & 0x02)

Validated payloads:

  • locked: 612 00 20 01 00 07 fe 00 10
  • unlocked: 612 00 22 01 00 07 fe 00 10

Root cause / code path

OvmsVehicleFiatEDoblo::IncomingFrameCan1() is the passive CAN decode path for the FTDO BSI CAN bus. It already decodes related body/status frames such as 0x412 door state, but had no case for the validated 0x612 lock-state frame.

Fix

Add a case 0x612 passive decode in vehicle_fiatedoblo.cpp and set:

StandardMetrics.ms_v_env_locked->SetValue((d[1] & 0x02) == 0);

Also update the FTDO user docs and changelog to mention passive lock status.

Validation performed

Runtime validation on an OVMS module configured as FTDO on Citroen e Berlingo

Notes:

  • Unlocking mechanically with the key while the car remains asleep did not emit 0x612; the metric remains the last observed passive CAN state until the BSI wakes and sends the frame.

@strangesource strangesource marked this pull request as ready for review June 22, 2026 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant