|
|
Post by sorbert on Apr 27, 2024 1:03:46 GMT
I just picked up my 24 gli and every app that does not say not supported fails when trying to activate. I was wondering is there anything I need to unlock so they can be written and activate? I got it working on my a 23 s5 and a 20 q5 so it does work. Read on the gli reddit people with the 40th anniversary can enable what I got and they are considered 24 year cars
|
|
|
|
Post by luisvillagreen on May 1, 2024 0:33:18 GMT
Make sure your hood is open and the ignition is ON. Idk what else could be wrong.
|
|
|
|
Post by damian0239 on May 1, 2024 18:51:18 GMT
Hello, the same thing happened to me with 3 jetta mk7.5, in an automatic application way as in manual, activate the modifications
|
|
|
|
Post by dv52 (Australia) on May 6, 2024 23:23:32 GMT
hmm........ I'm guessing - but the common element of the MY24 cars in this thread is that they likely ALL have the new 2nd version SFD protection that VAG uses on the very latest models.
To understand SFD (version 1) -read THIS. The reply below (in blue) is from OBD11 admin to a message from whataboutthis regarding SFD version 2: No news, Personally not expecting any fix soon as VW Have to provide the interface and then OBD11 have to build solution. But hopefully its an easy fix. and just to confirm support gave the following response Hello,
Thank you for reaching out to OBDeleven team.
Our technical experts are continuously exploring possible solutions and collaborating with VAG to overcome this new challenge. While we are unable to provide an exact timeline for when this protection can be disabled, we will keep you informed and write a post on our social platforms as soon as we have made progress in finding a solution.
Please be assured that your satisfaction is of utmost importance to us, and we are committed to resolving this matter to your complete satisfaction.
We genuinely value your loyalty as our customer and appreciate your support as we work through this unforeseen challenge together.
And this: Please be aware I am seeing more and more people having issues coding Audi Cars with a build date after Sept 23 From what I can gather this is the latest revision of the SFD Protection and means that only Authorised users (eg garages etc) can code these cars and Currently OBD11 is not in that camp. Update from OBD11 On Facebook VAG PR codes NI8 and NI9 on late 2023 and 2024 Audi’s won’t support coding.
OBD11 Reply
Juozapas M. PreikšaTop contributor
Justin Mix we are talking directly with VAG on the SFD2 integration and necessary changes to our software.
Will roll out app updated apps as soon as possible.
Thanks for sharing.
On a personal note I would not expect this to happen quickly,
Firstly VAG Tech have shown previously on SFD and on there cars that they are not the quickest kids on the block
Secondly OBD11 Have lost a few people recently and past experience does not lead me to expect a super quick turn around.
Latest update from support
We don't have an estimated time because we don't have any information from the VW side. Once it's clarified we'll share it on our social platforms. Thank you for understanding.
and when asked if they were going to update the website to warn people that currently they cant code the Audi 2024 Models
We're still trying to locate the issue regarding apps on vehicles manufactured in 2024; If the issue will be bigger than expected, we'll update the information on the website. Thank you for understanding.
Don
|
|
|
|
Post by whataboutthis on May 8, 2024 7:23:37 GMT
Just to add the latest results from OBD11 Support on SFD2
Hello,
Thank you for contacting the OBDeleven team.
We would like to inform you that the new Volkswagen Group (VAG) models from 2024 have been equipped with updated security features, as outlined in the UNECE R155 and R156 regulations.
These measures have been put in place to protect the car's software, particularly during over-the-air (OTA) updates. This added layer of protection, also known as "SFD2," ensures that the car's control units are safeguarded from unauthorized access.
Please note that under these new security measures, OBDeleven is only able to fully communicate with the car's main diagnostic component - the gateway control unit. As a result, we are unable to perform full scans or interact with other control units as we do with other car models.
However, we want to assure you that our development team is currently working on upgrading OBDeleven to be fully compatible with these new security features. We are in close consultation with VAG to ensure that our software meets all necessary requirements.
Our goal is to have OBDeleven fully functional with the 2024 models as soon as possible, so you can continue to diagnose and customize your car as you always have.
If you have any other questions please let me know.
|
|
|
|
Post by whataboutthis on May 9, 2024 17:13:47 GMT
SFD2 (UNECE)
SFD2 (UNECE) is the next level of SFD to meet the regulations of UNECE R155 & R156.
This variant begins with some vehicles from model year and will also affect new models from model year 2024.
If you would like to read the detailed information about UNECE R155 & R156, you can do so on the UN website. We have linked the pages here
UN Regulation No. 155 - Cyber security
UN Regulation No. 156 - Software update
Vehicle list SFD2 (as of February 22, 2024)
The following vehicles are currently known to be protected by SFD2:
VW Touareg (CR) facelift from model year 2024
VW Passat B9 (CJ) from model year
VW Tiguan (CT) from model year 2024
VW ID.7 (ED) from model year 2024
Audi Q8 e-tron (GE) from model year 2024
Audi A6 Avant (F2) from model year 2024
Audi e-tron GT (FW) from 2024
Identifying features of SFD2
Auto scan
There are 2 characteristics that indicate SFD or SFD2. In general, you can see in the autoscan in the VCID line whether a vehicle is protected by SFD. However, this can stand for either SFD or SFD2.
The ROD line indicates whether the vehicle is already using SFD2. If UNECE appears in the ROD file, then the control unit is already protected with SFD2.
Here using the example of a VW ID7:
Address 19: Diagnostic interface (J533) Label file: 1EE-937-012.clb
Part number SW: 1EE 937 012 B HW: 1EE 937 012
Component: ICAS1 Host-SG 021 0196
Serial number: SMERBG121023006 Data status number: V03935419WW 0001
GVL: 2D08080006C8D0FC8062904248180040C000400001060000040200000000DE57
ASAM data set: EV_GatewICAS1MEBUNECE 001001
ROD: EV_GatewICAS1MEBUNECE_VWE3.rod
VCID: 3337D2F77BB7EFF2E20-8066 SFD
PR Codes (equipment list)
The SFD expansion level can be seen in the equipment list. The following PR codes are currently used for this:
UN-ECE compound control
PR code meaning SFD stage autoscan
NI0 without UNECE CS&SU SFD
NI1 With UNECE CS&SU SFD2 not possible without SFD!
NI7 With UNECE CS (R155) and without SU (R156) SFD2
NI8 without UNECE CS (R155) and SU (R156) with SFD2-SG SFD2 autoscan possible
NI9 With UNECE CS&SU for countries without UNECE requirements SFD2 not possible without SFD!
Component protection
dv52 (Australia) Would I be correct in assuming the ROD file equates to ODX Name in OBD11 |
|
|
|
Post by dv52 (Australia) on May 10, 2024 2:43:18 GMT
whataboutthis : Very interesting information in the cartechnology site - once again, many thanks for your continued efforts in keeping us abreast of these new developments! Of course, the problem with our ability to identify SFD2 modules is that for reasons known ONLY to the deities on the OBD11 mother-ship - OBD11 does NOT disclose the ROD information.
Certainly there is NO ROD info on SCAN reports (which is where it should be and where it is on other diagnostic devices) and I'm fairly certain that Info option on the module screen doesn't disclose the ROD file data. Delighted to be told otherwise!!
Don
|
|
|
|
Post by whataboutthis on May 10, 2024 21:31:36 GMT
I spoke with support and they did not know what a .ROD file was. They did say that they use the ODX file to do what they do with the details.
As I dont have access to a tool that shows the rod file details if you could take a car you have a rod file on VCDS and check the ODX detail on OBD11 to see if they are the same as the format looks similar.
|
|
|
|
Post by dv52 (Australia) on May 10, 2024 23:43:28 GMT
whataboutthis : OK, I'm surprised at support's admission regarding ROD files. Clearly the deities on the OBD11 mother-ship do stuff an entirely different way - ain't nothing wrong with that! Anyhow, apropos of your question - this is how VCDS reports an Air-Con module on an Audi A3, 8V in my MQB platform database:
Adress 08: Auto HVAC (E87) Labels:| 8V0-820-043.clb
Part No SW: 8V0 820 043 Q HW: 8V0 820 043 Q
Component: AC Automat H03 0130
Revision: 20002000 Serial number: 00000001446081
Coding: 03100004110000001000000000001400
Shop #: WSC 06314 790 00021
ASAM Dataset: EV_AirCondiFrontVaAU37X 008022
ROD: EV_AirCondiFrontVaAU37X.rod
VCID: 40CC8568DBC26B4464-8014
And this is a picture of the OBD11 Info screen for the same module:
So yes, ROD = ODX name in OBD11 speak.
The fact that the VCDS file uses a .rod extension and the same ODX name suggests that the original data from VAG is altered in some way (probably to better integrate the original module information into other parts of the VCDS software- maybe?)
Given that the ODX name now appears to hold important information to OBD11 users like SFD2, is there any hope that maybe the ODX name can be included in OBD11 scan reports? Or do the deities on the mother-ship believe that when OBD11 users create SCAN reports, they need to separately access the Info screen for each individual module in the car to understand if SFD2 protection protocols are used? Or is my suggestion simply "too difficult"/"too unimportant", or just a temporary issue until a working SFD2 solution is implemented?
If my very last reason above and since it's likely that there will be a SFD3, SFD4........ version in subsequent years - maybe the SCAN should simply identify which version SFD is included on the car (by individual module because not ALL modules have SFD) -instead of the full ODX name?
Thanks for solving the ROD mystery - keep up the good work (please)
Don
|
|
|
|
Post by whataboutthis on May 11, 2024 22:21:11 GMT
i will speak to support on Monday to ask if they know that the ODX File can be used to identify SFD2 because if they did you would have thought they would have shared that information to help the user community (well maybe not)
With regards the changing of the Scan report i agree with your comments BUT currently my view is the dev team are working on BMW/TOYOTA and whatever comes next with only minor cheap tricks (like supporting BMW Bikes and the VIN Report) they don't seem to be fixing any of the bugs that have been out there for many years now.
Nor are there any indications they are going to fix the IOS Missing Features on VAG.
So wont hold my breath but I will raise the request
Update
Well it appears you can no longer raise a request for the VAG App on the Forum, only for one click apps. Bit of a bummer
Update 2
Renatas from OBDeleven
Tue, 14 May, 10:33 (1 day ago)
to me
Hello,
Thank you for contacting the OBDeleven team and for your feedback!
I'm letting you know that I passed your message to the responsible team which handles such requests.
Hopefully, the changes will be implemented in the future accordingly.
Have a good day!🙌
Renatas
OBDeleven
|
|
|
|
Post by phantommk75 on Sept 3, 2024 22:59:39 GMT
Okay, are we there any other alternative apps to OBD11 that would be able to access the one click apps for my MY 24 GLI that these clowns can’t?
|
|
|
|
Post by phantommk75 on Sept 3, 2024 23:01:10 GMT
I just picked up my 24 gli and every app that does not say not supported fails when trying to activate. I was wondering is there anything I need to unlock so they can be written and activate? I got it working on my a 23 s5 and a 20 q5 so it does work. Read on the gli reddit people with the 40th anniversary can enable what I got and they are considered 24 year cars None of mine work for other & im on a 24 40AE 6MT… |
|
