May the force be with you! :)Quote:
Originally Posted by Michael_B
Printable View
May the force be with you! :)Quote:
Originally Posted by Michael_B
Re the SFD/SFD2 issue :
From one of the SeatCupra Net guys :
Good morning. The legal deadline for the EU was July 1, 2024 for UNECE and SFD2. However, the group has converted some models earlier. An authorized dealer can see this using the VIN, for example.
My car being manufactured on 17Feb24 and the VIN check done by this guy has indicated that mine is SFD (not SFD2 thankfully), so that's a win at least
Michael: The module identifier tells you whether the car has SFD2 protection and you should be able to access this information without unlocking the module!Quote:
Originally Posted by Michael_B
But first - SFD2 is the result of the 2 x UN documents below:
- UN Regulation No. 155 - Cyber security
- UN Regulation No. 156 - Software update
I'm not sure which diagnostic device(s) you will eventually choose - but no matter which, it will almost certainly work by reading the module identity and then selecting an ODX file which contains instructions about how to open and read the information in the module. If the identifier for the ODX file contains the term "UNECE" - then the protection protocol will be SFD2
Of course how the ODX file is disclosed will depend on the diagnostic device - but I provide the examples below for the way that VCDS & OBD11 identify the ODX file on the Gateway module for a VW ID7, which has SFD2:
- OBDeleven: ODX name = EV_GatewICAS1MEBUNECE_VWE3
- VCDS: ROD = EV_GatewICAS1MEBUNECE_VWE3.rod
So, look at the ODX file name on your chosen diagnostic device(s)
Don
Well, finally got the app that petemac110 suggested and it worked fine, but screens didn’t seem the same and couldn’t get much from the SFD screen. I could access the long coding screen, but too scared and too little knowledge to even know what I’m really looking at.
Found the EPB service, but for some reason didn’t work ???
Anyway, powered on and replaced the rear hubs and stuck it all back together but even after successfully clearing the codes, same issues came back. Tried a short drive and fully cycled steering but still the same outcome.
Have replaced anything that was damaged/suspected, but no change at all.
Beginning to thing that there is something else going on, and learning the hard way that what works for VW doesn’t always translate to Cupra.
Will post up some screen grabs later, but think the next step is a workshop or dealer that has more of an idea.
Haven’t heard back from Transporter or tigger73 (Adelaide based VCDS knowledge).
Anyone recommendations for workshops in Adelaide ?
Cheers
Michael
Any recommendations for a workshop to take the car to for diagnostic work in Adelaide ?
Thanks
Well dont know about down there but I played with our POLO and F'd a few bits up and it cost $500 to get it set back to factory. Had it done at a specialist place as VW virtually said " You stuff it you fix it , we dont want to know"Quote:
Originally Posted by Michael_B
Ah bugger, that's a shame.Quote:
Originally Posted by Michael_B
Yeah, I can imagine that happening too, but will find out.Quote:
Originally Posted by Hillbilly
All I did was change the brakes (rotors & calipers) and didn't do any coding, so maybe I won't get the same reception. I did contact two VW Performance workshops in Adelaide previously, and one said they don't do diagnostics atm, as too busy, and one never got back to me. Will try again.
@petemac110 : It is, but at the end of the day, it was pretty good and offered more than some others had, and saved me from buying the OBDeleven.
Just as an indicator I cant do anywhere near as much to my 21 Kamiq as I could to the 19 Tiguan with my Obdeleven since they changed the camera version and seem to have hobbled coding considerablyQuote:
Originally Posted by Michael_B