Bharath2050
Novice Member
- Joined
- Jan 16, 2026
- Messages
- 1
- Reaction score
- 0
- Points
- 1
- Location (town/city + country)
- Bengaluru, India
- Driving
- ZS EV
Hi everyone,
I’m from India and working with a 2022 MG ZS EV facelift (LFP 50.3 kWh, Exclusive/Essence equivalent). I’m trying to understand the true hardware differences between:
India 2022 ZS EV (non-ADAS officially)
India 2024 ZS EV Pro (ADAS)
UK / AU / EU ZS EV (MG Pilot + V2L variants)
From ECU scans I can see:
• Front radar ECU present (ACC firmware branch)
• Forward Collision / FVCM module present
• Rear Cross Traffic radar ECU present
• Bosch ESP and EPS with longitudinal control capability
• Gateway and VCU showing driver-assist capability flags
• Some ECUs reporting V2L / Energy Export state machines
However, all functions are VIN-locked / feature-disabled and UI does not expose them.
My questions :
On global ZS EV / MG4 platforms, are ADAS and V2L blocked only by:
VIN feature entitlement / backend provisioning
Homologation profile
Calibration & safety certificate
rather than by different physical ECUs?
Has anyone confirmed whether India-spec 2022 cars physically lack:
ADAS fusion controller
Bidirectional OBC for V2L
Or whether the hardware is identical but region-coded?
For those with SIPS / VDI / VNCI access:
Does “feature not provisioned” mean cryptographic VIN lock, or simple configuration dataset difference?
Is calibration possible but actuation inhibited by safety domain?
Has anyone compared part numbers and safety partitions between:
ZS EV Pro (ADAS active)
ZS EV non-Pro (features hidden)
and found them identical at hardware level?
I am not trying to bypass safety or homologation.
I’m trying to understand the architectural difference between sensing-present vs function-certified vehicles on the SAIC E3 platform.
Any insight from MG4 / ZS EV / SAIC engineers or advanced diagnostic users would be highly appreciated.
Thanks in advance.
I’m from India and working with a 2022 MG ZS EV facelift (LFP 50.3 kWh, Exclusive/Essence equivalent). I’m trying to understand the true hardware differences between:
India 2022 ZS EV (non-ADAS officially)
India 2024 ZS EV Pro (ADAS)
UK / AU / EU ZS EV (MG Pilot + V2L variants)
From ECU scans I can see:
• Front radar ECU present (ACC firmware branch)
• Forward Collision / FVCM module present
• Rear Cross Traffic radar ECU present
• Bosch ESP and EPS with longitudinal control capability
• Gateway and VCU showing driver-assist capability flags
• Some ECUs reporting V2L / Energy Export state machines
However, all functions are VIN-locked / feature-disabled and UI does not expose them.
My questions :
On global ZS EV / MG4 platforms, are ADAS and V2L blocked only by:
VIN feature entitlement / backend provisioning
Homologation profile
Calibration & safety certificate
rather than by different physical ECUs?
Has anyone confirmed whether India-spec 2022 cars physically lack:
ADAS fusion controller
Bidirectional OBC for V2L
Or whether the hardware is identical but region-coded?
For those with SIPS / VDI / VNCI access:
Does “feature not provisioned” mean cryptographic VIN lock, or simple configuration dataset difference?
Is calibration possible but actuation inhibited by safety domain?
Has anyone compared part numbers and safety partitions between:
ZS EV Pro (ADAS active)
ZS EV non-Pro (features hidden)
and found them identical at hardware level?
I am not trying to bypass safety or homologation.
I’m trying to understand the architectural difference between sensing-present vs function-certified vehicles on the SAIC E3 platform.
Any insight from MG4 / ZS EV / SAIC engineers or advanced diagnostic users would be highly appreciated.
Thanks in advance.