+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: Secure coding in BMWs (unit list) (/showthread.php?tid=75725)
RE: Secure codings in SDP 4.40.12 - ferbmw - 24-03-2023
(11-03-2023, 14:08 PM)ferbmw Wrote:update: finally flashed to 23-3-537 with success. No secure coding requested. I did it with ista 4.39.20 and psdzdata 4.40.32. So I do not know why Esys was asking for secure back end connection as mentioned in my OP. ISTA did it with no warnings at all. DME was the ECU requesting secure back end connection but it was flashed and coded with no issues with ISTA. Vehicle is G20 pre LCI, S18A.(08-03-2023, 00:25 AM) ferbmw Wrote: I upload again the msg since I has attached a link and that is not permited, sorry for that.
Problem is I received a warning from Esys asking for Ethernet conection when I tried to flash my G20 . Warning was for DME BAC2. In the log attached it can be seen the system is asking for Secure Back End conection, if I am not wrong.
If it is so, I believe flashing at leats for DME will no longer be possible.
Update: after finding original i level, 21-11-566, tried to flash backwards with Esys to that level and again is asking for back end connection for DME. It seems DME has been securily encoded when flashed to current i level ( 22-11-561 ) to always ask for Back End connection from now on and there is no way to come back. ( I was trying to flash backwards to avoid the secure encoding )
I will try later with Ista to see how it responds to be flashed to newer i level but I pressume it will behave the same as with Esys, with newer or older versions of psdzdata.
Is there anyother way flashing backwards to by pass this secure encoding inside DME?
What I did is calculate TAL with Esys based on i shipment 21-11-560 and target i level 21-11-566; car is currently in 22-11-561. I wanted to flash backwards from 22-11-561 to 21-11-566.
Help is appreciated
RE: Secure codings in SDP 4.40.12 - smilo - 29-03-2023
Today, first time I experiment this in the new U06 Activ Tourer.
In fact, there is no CAFD in psdzdata for latest ecu ! I'm wrong ? so there is no possibility even to VO code the car with Esys. Only possible to modify the FA.
RE: Secure codings in SDP 4.40.12 - chang2 - 29-03-2023
(29-03-2023, 18:07 PM)smilo Wrote: Today, first time I experiment this in the new U06 Activ Tourer.
In fact, there is no CAFD in psdzdata for latest ecu ! I'm wrong ? so there is no possibility even to VO code the car with Esys. Only possible to modify the FA.
Did you read all the posts? everything has already been mentioned and explained.
RE: Secure codings in SDP 4.40.12 - masa52 - 29-03-2023
I have experienced the same where 3.40 wont program and 3.36 done without any problem
3.40 has few more options expoll or something like that which cant be unticked
RE: Secure codings in SDP 4.40.12 - smilo - 30-03-2023
(29-03-2023, 20:45 PM)masa52 Wrote: I have experienced the same where 3.40 wont program and 3.36 done without any problem
3.40 has few more options expoll or something like that which cant be unticked
I tried with different Esys versions and psdzdata levels, same issue: File for "cafd_XXXX" not found! [C012]
Surely because the car is too new U006-22-11-544
Only MGU and RAM can be read and coded
RE: Secure codings in SDP 4.40.12 - jaramillo - 30-03-2023
(30-03-2023, 00:15 AM)smilo Wrote:(29-03-2023, 20:45 PM)masa52 Wrote: I have experienced the same where 3.40 wont program and 3.36 done without any problem
3.40 has few more options expoll or something like that which cant be unticked
I tried with different Esys versions and psdzdata levels, same issue: File for "cafd_XXXX" not found! [C012]
Surely because the car is too new U006-22-11-544
Only MGU and RAM can be read and coded
Thats is not related...
Coding 2.0 already implemented. I recommed to read all thread.. you need online ISTA to VO code... until now forget about fdl coding
RE: Secure codings in SDP 4.40.12 - Mwahab - 30-03-2023
Even if you have online ISTA, you still can't vo code if there is a difference in hwel, not installed ecu, any god damn error ista doesn't like it, you can't touch the car until u fix it.
I hope there is someone can modify native ista or ista AOS tal caclulation, i tried to understand where and how does it calculate the test plan, but couldn't find any.
RE: Secure codings in SDP 4.40.12 - smilo - 30-03-2023
Someone tried to flash controllers with Esys in case of Coding 2.0 ?
For MGU ID8, I can code the HU, but I have IP Error when I try to flash the unit.
RE: Secure codings in SDP 4.40.12 - donke - 04-04-2023
(30-03-2023, 00:15 AM)smilo Wrote:(29-03-2023, 20:45 PM)masa52 Wrote: I have experienced the same where 3.40 wont program and 3.36 done without any problem
3.40 has few more options expoll or something like that which cant be unticked
I tried with different Esys versions and psdzdata levels, same issue: File for "cafd_XXXX" not found! [C012]
Surely because the car is too new U006-22-11-544
Only MGU and RAM can be read and coded
I have here a X1 U011 -> Here also the FZD is readable and codable, besides of them I only can read MGU and RAM. Every other ECU has no cafds available in the psdzdata ...
RE: Secure codings in SDP 4.40.12 - smilo - 04-04-2023
(04-04-2023, 13:05 PM)donke Wrote:(30-03-2023, 00:15 AM)smilo Wrote:(29-03-2023, 20:45 PM)masa52 Wrote: I have experienced the same where 3.40 wont program and 3.36 done without any problem
3.40 has few more options expoll or something like that which cant be unticked
I tried with different Esys versions and psdzdata levels, same issue: File for "cafd_XXXX" not found! [C012]
Surely because the car is too new U006-22-11-544
Only MGU and RAM can be read and coded
I have here a X1 U011 -> Here also the FZD is readable and codable, besides of them I only can read MGU and RAM. Every other ECU has no cafds available in the psdzdata ...
That is correct. cafd are generated in real time by the backend.
It truly seems like the end of an era…