Exploring the architecture and software openness of Turkish EV platforms – need your thoughts

10 Eyl 20:37

The Turkish EV platforms tend to go for a “modular‑in‑the‑back” layout rather than the skateboard chassis you see on most European models. The powertrain is often bolted onto a separate sub‑frame, which makes it easier to adapt a conventional ICE‑derived suspension and to fit larger battery packs in the trunk area. In practice this means the motor‑inverter unit is less tightly integrated with the chassis electronics, so manufacturers have to juggle extra wiring and CAN‑gateway mapping that you don’t usually see on a VW ID. or a Tesla. That extra complexity can bite you when you try to squeeze the same torque curves into a lighter, locally‑built drivetrain – you’ll notice a bit more heat buildup in the inverter housing under aggressive rally‑style driving. On the software side, most Turkish OEMs are still using a semi‑closed telematics stack. The OTA update mechanism is there, but it’s usually locked behind a proprietary gateway that only the OEM’s own server can access. A few startups have managed to get a read‑only API for vehicle diagnostics, but pushing third‑party apps or custom charge‑profile tweaks still requires a dealer‑signed firmware key. The big challenge for BMS adaptation is the hot‑summer, cold‑winter swing: the cooling loops are often sized for milder Mediterranean temps, so you’ll see higher cell temperature variance in August, and the thermal management software can struggle to keep the pack in the optimal 20‑30 °C window during rapid charging. In my own rally prep, we had to add an auxiliary coolant pump and a simple “climate‑aware” charge limit script to avoid premature degradation – not a perfect solution, but it shows how the openness (or lack thereof) forces you to hack around the OEM’s constraints.