|
|
Post by flagstone on Jun 9, 2024 19:10:00 GMT
does the control unit you changed have SFD on it because according to OBD11 if it does then you cant code it was my understanding. Gotcha. I'm still learning all this, so I appreciate the info you're bringing to this thread. I didn't realize that the SFD2 lock was per module instead of per car. My experience was that on v0.82, I couldn't do anything with OBDeleven on my 2024 RS5. With v0.83 I got an SFD unlock message (see screenshots posted above, sadly in reverse order) I can get a report of any codes being thrown and even apply some apps. Sadly it seems the majority of apps pop up a message that says they're not supported as you open up the app. I guess this could be the per-module SFD lock you mention. |
|
|
|
Post by smokeythebear on Jun 10, 2024 1:27:19 GMT
I just tried today on my 2024 S5 Sportback. I’m new and don’t know all the the things. So take it easy on me, plz.
I was able to turn on Auto Parking Brake and Highway Lights. I was not able to turn on Key Fob Range Limitation, MMI Welcome Sound, or RS Taillights animation. I’m on iOS 1.9.36. And I set up whatever SFD it prompted me for with the Google Authenticator. All that seems to work fine, albeit I have no clue if I’m on SFD or SFD 2. Still, no dice of on the latter three I mentioned.
|
|
|
|
Post by dv52 (Australia) on Jun 10, 2024 2:03:12 GMT
whataboutthis : I sympathize with those that have SFD2 encrusted vehicles - it must be very frustrating to have purchased OBD11 and not have access to those modules in the car that are locked by the newest protocol However, another aspect of this matter is that notwithstanding the problems with SFD2, the deities on the OBD11 mother-ship appear to be light years ahead of their competitors! As an example and despite the CEO of Ross-Tech promising a fix for his diagnostic cables years ago, VCDS still doesn't have a integrated solution to version 1 of SFD!! And no, this doesn't reduce the imperative for a speedy SFD2 fix for OBD11 - but it DOES put the problem in perspective - IMO, of course! Don
|
|
|
|
Post by whataboutthis on Jun 10, 2024 7:00:15 GMT
Totally agree, but in fairness to VCDS they tried the US Contact first and wasted a lot of time, they also got a work around for PRO users by being able to enter the unlock code. I also think its going to be interesting to see how VCDS handles the unlock process as they are not an online tool but thats just my personal curiosity.
My complaint about OBD11 (in this instance) is lack of clear communication, I have suggested several times they create a thread for Application Issues (like when the SFD Interface went down or they have a server crash) that way everybody would know whats going on and what motors are impacted by the issue. But just as importantly they update it on a regular basis.
Once again its up to user community to share what snippets they learn and get from the support team when asking a direct question.
|
|
|
|
Post by dv52 (Australia) on Jun 10, 2024 22:56:55 GMT
Totally agree, but in fairness to VCDS they tried the US Contact first and wasted a lot of time, they also got a work around for PRO users by being able to enter the unlock code. I also think its going to be interesting to see how VCDS handles the unlock process as they are not an online tool but thats just my personal curiosity.
hmm....... you are being your normally kind self (alas, I hold Ross-Tech to a much higher standard)! I knew Uwe Ross for many years albeit ONLY as an ex forum colleague. He is a very intelligent man - but I have no doubt that the glacial pace of VCDS's progress towards an integrated SFD solution is due in no small part to Ross-Tech's historic relationship with the VAG group, which as I understand can best be described as adversarial!
I don't believe that Ross-Tech has a corporate board. Or if it does, I suspect that it will be Ross family members with Uwe as a strong Chairman - steering the mother-ship. So the CEO's role in the failed SFD roll-out cannot be denied - and ultimately neither can accountability!!
And I'm not sure that the "work around" is particularly useful for VCDS users. This solution ONLY works if users have a GEKO account - but this is entirely impracticable for users in the enthusiast market! Unbelievably, the suggested approach for non-professional users during my time as a VCDS forum member was that they purchase OBD11 to generate the token - then copy-and-paste the token-number to VCDS! Yes, this was a serious suggestion!!
My complaint about OBD11 (in this instance) is lack of clear communication, I have suggested several times they create a thread for Application Issues (like when the SFD Interface went down or they have a server crash) that way everybody would know whats going on and what motors are impacted by the issue. But just as importantly they update it on a regular basis.
Great idea!! |
|
|
|
Post by stoffle32 on Jul 1, 2024 10:07:23 GMT
Problem is VW Group themselves also dont have a solution for sfd2 yet either. They themselves at dealership level cannot unlock the cars.
Example we had a q5 2024 in for 360 camera retrofit. When we tried to unlock it with OBD eleven did not work got stuck in a loop, the car was then sent to the dealership to unlock and they could not unlock 5f. It unlocks but then when you try code asks you to unlock again. Which it seems is what obd eleven is also battling with.
|
|
|
|
Post by 81dollar on Jul 2, 2024 21:24:17 GMT
Does anyone know if module 46 can be unlocked? I had issues trying to write to the module but it seems the unlock / 2FA works...
|
|
|
|
Post by dv52 (Australia) on Jul 2, 2024 22:26:07 GMT
A bunch of us participated in a discussion (initiated by whataboutthis ) regarding how to detect if a module has SFD2 protection which you can read HERE
To summarize the outcome of this dialogue, use the following instructions to find-out if a module has SFD2 protection: - Ignition ON, Engine OFF (IOEF)
- Fire-up OBD11 software and connect to the dongle
- Navigate to the Control Units screen and select the module
- Select Info - it's the first option
- Read the entry ODX name
- If the term "UNECE" appears in the entry, the module has SFD2 protection - example below for Gateway module for a VW ID7 (from my link above):
- EV_GatewICAS1MEBUNECE_VWE3
Don |
|
|
|
Post by 81dollar on Jul 3, 2024 0:20:30 GMT
A bunch of us participated in a discussion (initiated by whataboutthis ) regarding how to detect if a module has SFD2 protection which you can read HERE
To summarize the outcome of this dialogue, use the following instructions to find-out if a module has SFD2 protection: - Ignition ON, Engine OFF (IOEF)
- Fire-up OBD11 software and connect to the dongle
- Navigate to the Control Units screen and select the module
- Select Info - it's the first option
- Read the entry ODX name
- If the term "UNECE" appears in the entry, the module has SFD2 protection - example below for Gateway module for a VW ID7 (from my link above):
- EV_GatewICAS1MEBUNECE_VWE3
Don Thanks, tried that but there’s no mention of UNECE in the OBX name of module 46. SFD Protection is apparently unlocked, but I can’t write anything to the module in long coding. Tried with hood open and closed. For my 2024 S5 Sportback, for Comfort System (46) the ODX name is EV_BCM2HellaAU736 but i'm still getting "Something went wrong. Try again" message when trying to save changes in long coding. |
|
|
|
Post by dv52 (Australia) on Jul 4, 2024 0:37:37 GMT
81dollar : OK - a 2024 S5 Sportback is built on a MLB/MLP-evo platform. I'm not 100% sure - but I can't find ANY modules on this car that has either SFD, or SFD2 protection - See VCDS scan below. I've used a VCDS scan because OBD11 scans do NOT show the ODX name- look at the ROD name in the scan below. If this model has either SFD, or SFD2 - I am very surprised that the 46 -Central Convenience module (J393) is NOT covered by this protection protocol Are you sure that these protocols apply to this model Audi? If these protocols do NOT apply to this car - maybe the problem of access to the module is that you need a security code (instead of unlocking SFD/SFD2)? I'm guessing! Don
2023 Audi S5 Sportback 3.0V6T CWGD
Sunday,07,January,2024,17:46:23:55713
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 11 x64
VCDS Version: 23.11.0.0 HEX-NET2 CB: 0.4643.5
Data version: 20231027 DS351.0
www.Ross-Tech.com
VIN: WAUB4CF5XPA032568 License Plate: LYKUNO3
Mileage: 12643km-7855mi Repair Order:
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Chassis Type: F5-AU49 (80C)
Scan: 01 02 03 08 09 13 15 16 17 19 1B 32 36 3C 42 44 46 52 5F 6C
6D 74 75 81 82 8B A5 A9 BB BC CA CF D6 D7 DE
VIN: WAUB4CF5XPA032568 Mileage: 12643km-7855miles
01-Engine -- Status: OK 0000
02-Auto Trans -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
13-Auto Dist. Reg -- Status: OK 0000
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: Malfunction 0010
1B-Active Steering -- Status: OK 0000
32-Differential Locks -- Status: OK 0000
36-Seat Mem. Drvr -- Status: OK 0000
3C-Lane Change -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
46-Central Conv. -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
5F-Information Electr. -- Status: OK 0000
6C-Back-up Cam. -- Status: OK 0000
6D-Trunk Elect. -- Status: OK 0000
74-Chassis Control -- Status: OK 0000
75-Telematics -- Status: OK 0000
81-Gear Shift -- Status: OK 0000
82-Head Up Display -- Status: OK 0000
8B-Adaptive Cruise 2 -- Status: OK 0000
A5-Frt Sens. Drv. Assist -- Status: OK 0000
A9-Struct. Borne Sound -- Status: OK 0000
BB-Door Rear Drv -- Status: OK 0000
BC-Door Rear Pass -- Status: OK 0000
CA-Sunroof -- Status: OK 0000
CF-Lane Chge Asst 2 -- Status: OK 0000
D6-Light Ctrl Left 2 -- Status: OK 0000
D7-Light Ctrl Right 2 -- Status: OK 0000
DE-Charger 1 for mobile dev -- Status: OK 0000
-------------------------------------------------------------------------------
Address 01: Engine (J623-CWGD) Labels: None
Part No SW: 8W0 907 559 AC HW: 06M 907 309 G
Component: V6 3.0l TFSI H11 0001
Revision: B8H11000 CVN: 99107398
Coding: 1A2A00322366010E34380000000000000000000000000000
Shop #: WSC 06324 790 00001
ASAM Dataset: EV_ECM30TFS0118W0907559AC 001001
ROD: EV_ECM30TFS011_AU49.rod
VCID: 865E7BA0D8DA372A95F-81D2
VINID: 9D1952113585A204400C21462072539B4F
No fault code found.
Readiness: 0000 0100
-------------------------------------------------------------------------------
Address 02: Auto Trans (J217) Labels:| 0BK-927-156.clb
Part No SW: 8W0 927 158 BC HW: 0D5 927 156 N
Component: 0D5 30TFSINAR H06 0003
Revision: --H06--- CVN: 80EA9269
Coding: 100000
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_TCMALX52011 002016
ROD: EV_TCMALX52011_AU49.rod
VCID: 845A61A8EEE6053A8BB-81D0
No fault code found.
-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104) Labels: 8W0-907-379-PRE-V1.clb
Part No SW: 8W0 907 379 BH HW: 8W0 907 379 BH
Component: ESP9 Premium H01 0930
Dataset Number: 8W2909504P 0001 CVN: CCE46E7E
Coding: 1CAA149A30A50A9811A34897428558A2E5359A38280C508812421A45A7AC59
Shop #: WSC 06324 790 00001
ASAM Dataset: EV_ESP9BOSCHCMP 002013
ROD: EV_ESP9BOSCHCMP_004_AU49.rod
VCID: 8C4A4988C6B64D7AC3B-81D8
No fault code found.
-------------------------------------------------------------------------------
Address 08: Auto HVAC (E87) Labels:* Redir Fail!
Part No SW: 8W0 820 043 BJ HW: 8W0 820 043 BJ
Component: Klima Zone 3 H60 0291
Dataset Number: 8W2909862B 0023
Coding: 1608050D5548010D10020100080000000000000000000000000000000000
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_AirCondiBHTCAU491 001029
ROD: EV_AirCondiBHTCAU491.rod
VCID: FCAA194896167DFAF3B-81A8
Fresh air blower control module (front):
Subsystem 1 - Part No SW: 4M1 820 021 C HW: 4M1 820 021 C
Component: J126 FLuftV H09 0004
Serial number: 00000000000008179976
Humidity sensor: exterior:
Subsystem 2 - Part No SW: 4H0 907 658 C HW: 4H0 907 658 C
Component: G935 MuFu H06 0012
Serial number: B595810500PAG0MUFU04
Rear air conditioning block 1:
Subsystem 3 - Part No SW: 8W0 919 158 A HW: 8W0 919 158 A
Component: E265 Kli Fond H40 0080
No fault code found.
-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519) Labels:* None
Part No SW: 8W1 907 063 CN HW: 8W1 907 063 N
Component: BCM1 MLBevo H11 0750
Dataset Number: 8W6909514A 0010
Coding: 07000360C0291CDD050D578918AD9CA9130B35040000009801050A0060001601084902BBA2B70A0000000000000000000000000000000000000000000000000000
Shop #: WSC 00046 000 00000
ASAM Dataset: EV_BCM1BOSCHAU651 019005
ROD: EV_BCM1BOSCHAU651_018_VW53.rod
VCID: 8A464F90CCC2534AF17-81DE
Wiper motor control module:
Subsystem 1 - Part No SW: 8W6 955 119 D HW: 8W6 955 119
Component: 494 LL 191122 038 0490
Serial number: 00000002211040301721
Coding: FFC7F7
Rain/Light Recognition Sensor:
Subsystem 2 - Part No SW: 81A 955 555 B HW: 81A 955 555
Component: G397_RLFSS H06 0004
Serial number: 44318937X81A955555B0
Coding: 02005D
Light switch:
Subsystem 3 - Part No SW: 4M0 941 531 AT HW: 4M0 941 531 AT
Component: E1 - LDS H07 0008
Serial number: 14 07 2022 03203901
Garage door opener control module:
Subsystem 4 - Part No SW: 4N0 907 410 C HW: 4M0 907 410 A
Component: USHL5 GX1 H12 0300
Serial number: 0000009600373Z00B102
Coding: 250000
Automatic dimming interior mirror:
Subsystem 5 - Part No SW: 8W0 857 511 H HW: 8W0 857 511 B
Component: Y7_Innenspieg H01 0002
Serial number: GX1CE104082224111235
Coding: 010000
Interior Light Module:
Subsystem 6 - Part No SW: 4K0 947 135 AH HW: 4K0 947 135 AH
Component: Dachmodul H42 0419
Serial number: A01073535
Coding: 0D0104
Valve block 1 in front seat driver side:
Subsystem 7 - Part No SW: 8W0 907 182 B HW: 8W0 907 182 B
Component: J873 MKS_FSv H03 0010
Serial number: 7009137235A224619993
Coding: BF0500
Valve block 1 in front seat passenger side:
Subsystem 8 - Part No SW: 8W0 907 182 B HW: 8W0 907 182 B
Component: J872 MKS_BFSv H03 0010
Serial number: 7009137235A224619901
Coding: B30500
No fault code found.
-------------------------------------------------------------------------------
Address 13: Auto Dist. Reg (J428) Labels:* None
Part No SW: 8W0 907 561 H HW: 8W0 907 561
Component: LRR4 H13 0452
Dataset Number: 8W2909863R 0002
Coding: B5779FF358FFEC06757B61A1
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_ACCBOSCHAU49X 003024
ROD: EV_ACCBOSCHAU49X_003_AU49.rod
VCID: C3D8A2B4AB68C202F21-8196
No fault code found.
-------------------------------------------------------------------------------
Address 15: Airbags (J234) Labels:| 8W0-959-655.clb
Part No SW: 8W0 959 655 N HW: 8W0 959 655 N
Component: Airbag10.44 H20 0109
Serial number: 0030D000XBCT Dataset Number: 8W2909602BE 0001
Coding: BFCCF0C000800000A0000033D24C00000000
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_AirbaAU10BPAAU736 006016
ROD: EV_AirbaAU10BPAAU736_006.rod
VCID: D4FA91E85E0655BA5BB-8180
Left seat belt tensioner:
Subsystem 1 - Part No SW: 4M0 980 945 B HW: 4M0 980 945 B
Component: BeltPretRevFL 306 2044
Serial number: 8W0857705M0347W01070
Coding: 882007
Right seat belt tensioner:
Subsystem 2 - Part No SW: 4M0 980 946 B HW: 4M0 980 946 B
Component: BeltPretRevFR 306 2044
Serial number: 8W0857706P0346W00186
Coding: 882007
Seat occupied recognition passenger side:
Subsystem 3 - Part No SW: 4M0 959 339 HW: 4M0 959 339
Component: BF-Gewichtss. H14 0022
Serial number: IBH0000D22000JDZBP0.
Crash sensor for side airbag: driver side:
Subsystem 4 - Part No SW: ----------- HW: 442 061 011 22
Component: SideSensor_Df 1E2 0887
Serial number: 3577Y00BD0BB6924739D
Coding: 2D2D2D
Front Passenger's Side Airbag Crash Sensor:
Subsystem 5 - Part No SW: ----------- HW: 442 061 511 22
Component: SideSensor_Pf 1E2 0887
Serial number: 3587Y00BB0B8A923827A
Coding: 2D2D2D
Rear Side Airbag Crash Sensor (on driver's side):
Subsystem 6 - Part No SW: ----------- HW: 442 0B2 411 22
Component: SideSensor_Dr 1C7 0148
Serial number: 3517700A90B083C43265
Coding: 2D2D2D
Passenger side rear thorax airbag crash sensor:
Subsystem 7 - Part No SW: ----------- HW: 442 0B2 411 22
Component: SideSensor_Pr 1C7 0148
Serial number: 3527700A70B083C0C135
Coding: 2D2D2D
Crash sensor for front airbag: driver side:
Subsystem 8 - Part No SW: ----------- HW: 442 0C0 811 22
Component: FrontSensor_D 1C5 014A
Serial number: 3557500B90A11515610W
Coding: 2D2D2D
Crash sensor for front airbag: front passenger side:
Subsystem 9 - Part No SW: ----------- HW: 442 0C0 811 22
Component: FrontSensor_P 1C5 014A
Serial number: 3567500B70A11514D02
Coding: 2D2D2D
No fault code found.
-------------------------------------------------------------------------------
Address 16: Steering wheel (J527) Labels: 4M0-907-129.clb
Part No SW: 4N0 907 129 MJ HW: 4N0 907 129 MJ
Component: Lenks.Modul H03 0009
ASAM Dataset: EV_SMLSKLOAU736 007012
ROD: EV_SMLSKLOAU736_007_AU49.rod
VCID: 855C7CACE5DC3C329C5-81D0
No fault code found.
-------------------------------------------------------------------------------
Address 17: Instruments (J285) Labels:* None-SRI2
Part No SW: 8W5 920 790 M HW: 8W5 920 790 L
Component: FBenRDW------ H12 0219
Dataset Number: 8W1909525H 0022
Coding: 8BCF36CB7EB8CF050290636018004B0008000800
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_DashBoardAU65X 002027
ROD: EV_DashBoardAU65X_002_AU49.rod
VCID: CCCA898886360D7A03B-8198
No fault code found.
-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533) Labels:* None
Part No SW: 80C 907 468 G HW: 80B 907 468 B
Component: Gateway H08 0623
Serial number: F0224417315771 Dataset Number: 8W0909515S 0043
Coding: 03030001000006405407000000590012FC980000920000000100008E04000000
Shop #: WSC 06335 790 00001
GVL: 01507C580800000040DCC8008002C800110C0000000000000000000000006500
ASAM Dataset: EV_Gatew31xAU65x 003281
ROD: EV_Gatew31xAU65x_AU49.rod
VCID: B43AF168FEC675BA7BB-81E0
Multifunction steering wheel control module:
Subsystem 1 - Part No SW: 83A 951 523 L HW: 83A 951 523 L
Component: J453 MFL H07 0004
Serial number: 20221123131309 30682
Battery Monitoring Control Module:
Subsystem 2 - Part No SW: 8S0 915 181 C HW: 8S0 915 181 C
Component: J367-BDMHella H11 9070
Serial number: 3961360906
Steering Wheel Touch Recognition Control Module:
Subsystem 3 - Part No SW: 4M8 419 508 B HW: 4M8 419 508 B
Component: J1158 KLR H14 0012
Serial number: 00000000000000075112
Coding: FFFFFF
1 Fault Found:
528146 - System Voltage
P0560 00 {00001001} - Malfunction
{BDM_Component_Error}
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Priority: 4
Fault Frequency: 1
Reset counter: 196
Mileage: 12643 km
Date: 2024.01.07
Time: 17:42:20
-------------------------------------------------------------------------------
Address 1B: Active Steering (J792) Labels: None
Part No SW: 8W0 907 144 J HW: 8W0 907 144 C
Component: SCU_MLBevo H03 0710
Serial number: 30303030303030 Dataset Number: 8W2909848L 0002
ASAM Dataset: EV_SCUZFLSAU49X 002019
ROD: EV_SCUZFLSAU49X_002.rod
VCID: C2D6A7B0B472CB0AF97-8196
No fault code found.
-------------------------------------------------------------------------------
Address 32: Differential Locks (J187) Labels: None
Part No SW: 8W0 907 163 A HW: 8W0 907 163
Component: QSP QCU Gen2 H08 0070
Revision: 5WK12701 Serial number: 605245518200407
Coding: 0001
Shop #: WSC 06324 790 00001
ASAM Dataset: EV_TVDCQSP22 001008
ROD: EV_TVDCQSP22_AU49.rod
VCID: BA26DF50DCA283CAA17-81EE
No fault code found.
-------------------------------------------------------------------------------
Address 36: Seat Mem. Drvr (J136) Labels:* None
Part No SW: 4M6 959 760 HW: 4M4 959 760
Component: MEM-FS 009 0064
Serial number: 00000484449901 Dataset Number: 8W2909856E 0021
Coding: 015C1A400000B4010003010101010000000000000000000000000000004000
Shop #: WSC 00046 000 00000
ASAM Dataset: EV_SCMDriveSideCONTIAU736 006013
ROD: EV_SCMDriveSideCONTIAU736_AU49.rod
VCID: FBA81A5493187AC2FA1-81AE
No fault code found.
-------------------------------------------------------------------------------
Address 3C: Lane Change (J769) Labels:* None
Part No SW: 4M0 907 566 G HW: 4M0 907 566
Component: MRR1Rear H24 0452
Revision: -------- Dataset Number: 8W0909535D 0003
Coding: 0EC002
Shop #: WSC 06324 790 00001
ASAM Dataset: EV_RearRadarS1BoschAU736 001022
ROD: EV_RearRadarS1BoschAU736.rod
VCID: B924C05CD9A488D2A8D-81EC
No fault code found.
-------------------------------------------------------------------------------
Address 42: Door Elect, Driver (J386) Labels:* None
Part No SW: 4M8 959 793 N HW: 4M8 959 793 N
Component: TSG FS 001 0390
Serial number: 0000484688153 Dataset Number: 8W2909872E 0034
Coding: 005DCB625200108000010432
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_DCU2DriveSideMAXHCONT 001005
ROD: EV_DCU2DriveSideMAXHCONT_VW41.rod
VCID: D1F498FC6114209270D-8184
No fault code found.
-------------------------------------------------------------------------------
Address 44: Steering Assist (J500) Labels:* None
Part No SW: 8W0 909 144 J HW: 8W0 909 144 B
Component: EPS_MLBEVO_ZF H08 0411
Dataset Number: 8W2909852R 0037
Coding: 85888380008080
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_EPSZFAU49X 003023
ROD: EV_EPSZFAU49X_003.rod
VCID: C4DAA1A8AE66C53ACBB-8190
No fault code found.
-------------------------------------------------------------------------------
Address 46: Central Conv. (J393) Labels:* None
Part No SW: 8W1 907 064 DC HW: 8W1 907 064 C
Component: BCM2 MLBevo 044 0604
Dataset Number: 8W2909501P 0019
Coding: 013463004FB100C0650BA0006C01080203000000810426502F0400000F04803F001E0681002F31
Shop #: WSC 00046 000 00000
ASAM Dataset: EV_BCM2HellaAU736 020017
ROD: EV_BCM2HellaAU736_020_AU49.rod
VCID: 815468BCF1F41012A0D-81D4
Anti-theft alarm system sensor:
Subsystem 1 - Part No SW: 5Q0 951 177 A HW: 5Q0 951 172 B
Component: Sensor, DWA 004 0403
Serial number: 000000000ZL2232904GT
Alarm horn:
Subsystem 2 - Part No SW: 5Q0 951 605 B HW: 5Q0 951 605 B
Component: Sirene, DWA 004 0007
Serial number: 00000000000002899731
left tail lamp 1:
Subsystem 3 - Part No SW: 8W6 945 423 A HW: 8W6 945 423 A
Component: SHL_li1 H03 0017
Serial number: 0000000000000L0T84RC
left tail lamp 2:
Subsystem 4 - Part No SW: 8W6 945 429 A HW: 8W6 945 429 A
Component: SHL_li2 H03 0017
Serial number: 0000000000000L0TADPE
Right rear tail lamp 1:
Subsystem 5 - Part No SW: 8W6 945 424 A HW: 8W6 945 424 A
Component: SHL_re1 H03 0017
Serial number: 0000000000000L0S3LTA
Right rear tail lamp 2:
Subsystem 6 - Part No SW: 8W6 945 430 A HW: 8W6 945 430 A
Component: SHL_re2 H03 0017
Serial number: 0000000000000L0STD0U
No fault code found.
-------------------------------------------------------------------------------
Address 52: Door Elect, Pass. (J387) Labels:* None
Part No SW: 4M8 959 792 N HW: 4M8 959 792 N
Component: TSG BFS 001 0390
Serial number: 0000484718333 Dataset Number: 8W2909873E 0033
Coding: 005DCB225E00108000010430
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_DCU2PasseSideMAXHCONT 001005
ROD: EV_DCU2PasseSideMAXHCONT_AU49.rod
VCID: D0F29DF86A1E299A7F3-8184
No fault code found.
-------------------------------------------------------------------------------
Address 5F: Information Electr. (J794) Labels:* None
Part No SW: 8W2 035 050 M HW: 8W2 035 050 A
Component: MU-TH-NS-US 044 3809
Serial number: GRO-63314.12.22 Dataset Number: 8W1909545Q 0052
Coding: 14930000804220000000000000000000000000000000000000
ASAM Dataset: EV_MUTI 001010
ROD: EV_MUTI_VW53.rod
VCID: BB28DA54D398BAC2BA1-81EE
Multimedia System 1:
Subsystem 1 - Part No SW: 8W2 919 620 A HW: 8W2 919 620 A
Component: DU Top AU49x H42 0080
Serial number: TPO00106112210110329
Data carrier:
Subsystem 2 - Part No: V03 959 820 KT
Component: MIB3_NA_ 0986
Compact disc data bank:
Subsystem 3 - Part No: V03 959 800 EG
Component: Gracenote2 3007
Volume Control 1:
Subsystem 4 - Part No SW: 8W1 919 616 D HW: 8W1 919 616 D
Component: LSR-B9PA H20 0103
Serial number: ALJAL219102200040264
Media socket:
Subsystem 5 - Part No: 8W0 035 708 A
011 0010
Digital Sound System Control Module 2:
Subsystem 6 - Part No SW: 8Y0 035 465 A HW: 8Y0 035 465 A
Component: B_A_3_P_0_AU H11 0100
Serial number: HHA-07319.11.2234860
No fault code found.
-------------------------------------------------------------------------------
Address 6C: Back-up Cam. (J928) Labels:* None
Part No SW: 8W0 907 428 C HW: 4M0 907 428
Component: Areaview 2 H18 0108
Serial number: C854611JJ034091 Dataset Number: 8W2909460L 0026
Coding: 02940302BE0FA10038004000
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_CamSysRVAV2CE2MLBPA 002001
ROD: EV_CamSysRVAV2CE2MLBPA_002.rod
VCID: C0D2ADB8BA7ED91AEF3-8194
No fault code found.
-------------------------------------------------------------------------------
Address 6D: Trunk Elect. (J605) Labels:| 5Q0-959-107.clb
Part No SW: 4KE 959 107 A HW: 4KE 959 107 A
Component: HDSG-Modul H05 0335
Revision: -------- Serial number: A2-C765-4921-3 Dataset Number: 8W2909541F 0013
Coding: 0630
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_DeckLidCONTIAU536 001002
ROD: EV_DeckLidCONTIAU536_AU37.rod
VCID: C4DAA1A8AE66C53ACBB-8190
No fault code found.
-------------------------------------------------------------------------------
Address 74: Chassis Control (J775) Labels:* None
Part No SW: 8W0 907 777 T HW: 8W0 907 777 C
Component: Fahrwerk-SG H38 1215
Serial number: 2611221522 Dataset Number: 8W2909576L 0001
Coding: 5460484958
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_ChassContrContiAU426 001003
ROD: EV_ChassContrContiAU426.rod
VCID: D8E265D842EE71DAB73-818C
No fault code found.
-------------------------------------------------------------------------------
Address 75: Telematics (J949) Labels:* None
Part No SW: 4KE 035 283 G HW: 4KE 035 283 B
Component: CB_H_NAR 042 0481
Serial number: A971L0N2591488 Dataset Number: 8W0909612J 0031
Coding: 01E0E0F8C04080F6F0
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_ConBoxHighAU49X 001004
ROD: EV_ConBoxHighAU49X_AU49.rod
VCID: C0D2ADB8BA7ED91AEF3-8194
No fault code found.
-------------------------------------------------------------------------------
Address 81: Gear Shift (J587) Labels: 4MX-713-041-81.clb
Part No SW: 8W1 713 041 P HW: 4M1 713 041 G
Component: GSM-LL H10 0077
Revision: 0L0D5012 Serial number: 22081983323828
ASAM Dataset: EV_GSMWaehlZFAU736 001017
ROD: EV_GSMWaehlZFAU736_AU49.rod
VCID: C0D2ADB8BA7ED91AEF3-8194
No fault code found.
-------------------------------------------------------------------------------
Address 82: Head Up Display (J898) Labels:| 4M0-919-617-V1.clb
Part No SW: 8W6 919 617 F HW: 8W6 919 617 F
Component: HeadUpDisplay H15 1952
Coding: 4F01E0
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_HudNSEIKAU736 001017
ROD: EV_HudNSEIKAU736_AU49.rod
VCID: CCCA898886360D7A03B-8198
No fault code found.
-------------------------------------------------------------------------------
Address 8B: Adaptive Cruise 2 (J850) Labels: None
Part No SW: 8W0 907 541 H HW: 8W0 907 541
Component: LRR4 H13 0452
Dataset Number: 8W2909885H 0003
ASAM Dataset: EV_ACC2BOSCHAU49X 003024
ROD: EV_ACC2BOSCHAU49X_003_AU49.rod
VCID: C1D4A8BCB174D012E0D-8194
No fault code found.
-------------------------------------------------------------------------------
Address A5: Frt Sens. Drv. Assist (R242) Labels:* Redir Fail!
Part No SW: 8W6 907 217 E HW: 8W6 907 217 D
Component: BVS H30 0070
Dataset Number: 8W2909466E 0037
Coding: 0404090300000204012023AECD0000FCB0F0C024E280
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_BVSMLBevKOSTAAU736 002028
ROD: EV_BVSMLBevKOSTAAU736_002_AU49.rod
VCID: C4DAA1A8AE66C53ACBB-8190
No fault code found.
-------------------------------------------------------------------------------
Address A9: Struct. Borne Sound (J869) Labels: 4H0-907-159.clb
Part No SW: 8W0 907 159 M HW: 4K0 907 159
Component: SAS-GEN 2.5 H08 0001
Serial number: 221026290534
ASAM Dataset: EV_SoundActuaGen2AU64X 003010
ROD: EV_SoundActuaGen2AU64X.rod
VCID: CBC88A9483380A420A1-819E
No fault code found.
-------------------------------------------------------------------------------
Address BB: Door Rear Drv (J388) Labels:* None
Part No SW: 4M8 959 795 N HW: 4M8 959 795 N
Component: TSG HFS 001 0390
Serial number: 0000484809832 Dataset Number: 8W2909897F 0034
Coding: 000DC9220000108040000020
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_DCU2RearDriveMAXHCONT 001005
ROD: EV_DCU2RearDriveMAXHCONT_VW37.rod
VCID: D3F892F45B085282421-8186
No fault code found.
-------------------------------------------------------------------------------
Address BC: Door Rear Pass (J389) Labels:* None
Part No SW: 4M8 959 795 N HW: 4M8 959 795 N
Component: TSG HBFS 001 0390
Serial number: 0000484796999 Dataset Number: 8W2909896F 0034
Coding: 000DC9220000108040000020
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_DCU2RearPasseMAXHCONT 001005
ROD: EV_DCU2RearPasseMAXHCONT_VW37.rod
VCID: D3F892F45B085282421-8186
No fault code found.
-------------------------------------------------------------------------------
Address CA: Sunroof (J245) Labels:| 4M0-907-594.clb
Part No SW: 4K0 907 594 AC HW: 4K0 907 594
Component: SAD_STG_1 006 0002
Dataset Number: 8W2909469F 0005
Coding: 268040049301
Shop #: WSC 06335 790 00001
ASAM Dataset: EV_SunRoofCONTIAU736 009011
ROD: EV_SunRoofCONTIAU736_009_VW37.rod
VCID: F5BC0C6CB53C2CB28C5-81A0
No fault code found.
-------------------------------------------------------------------------------
Address CF: Lane Chge Asst 2 (J770) Labels: None
Part No SW: 4M0 907 590 G HW: 4M0 907 590
Component: MRR1Rear H24 0452
Revision: --------
Coding: 0EC002
Shop #: WSC 00000 000 00000
ASAM Dataset: EV_RearRadarS2BoschAU736 001022
ROD: EV_RearRadarS2BoschAU736.rod
VCID: B63ECB60E8BA67AA45F-81E2
No fault code found.
-------------------------------------------------------------------------------
Address D6: Light Ctrl Left 2 (A31) Labels: 7PP-941-572.clb
Part No SW: 4K0 941 592 AD HW: 4K0 941 592 A
Component: LMS_MLBevo H11 0040
Dataset Number: 8W2909471D 0008
ASAM Dataset: EV_LMSLeftHELLAAU58X 001015
ROD: EV_LMSLeftHELLAAU58X_AU37.rod
VCID: F2B63770C4523B8AA97-81A6
No fault code found.
-------------------------------------------------------------------------------
Address D7: Light Ctrl Right 2 (A27) Labels: 7PP-941-572.clb
Part No SW: 4K0 941 592 AJ HW: 4K0 941 592 A
Component: LMS_MLBevo H20 0147
Dataset Number: 8W2909472D 0008
ASAM Dataset: EV_LMSRightHELLAAU58X 001015
ROD: EV_LMSRightHELLAAU58X_AU37.rod
VCID: F8A20558A22E51DA973-81AC
No fault code found.
-------------------------------------------------------------------------------
Address DE: Charger 1 for mobile dev (J1146) Labels:* 4N0-035-502.clb
Part No SW: 4K0 035 502 B HW: 4K0 035 502 B
Component: WLC Front H14 0061
Dataset Number: 4N0909485A 0007
Coding: 800000
Shop #: WSC 06324 790 00001
ASAM Dataset: EV_Charg1MobilDevicAU651 004001
ROD: EV_Charg1MobilDevicAU651_004_AU37.rod
VCID: A0120D385A3EF91A8F3-81F4
No fault code found.
End----(Elapsed Time: 02:47, VBatt start/end: 12.1V/12.1V. VIgn 12.0V)----- .
.
|
|
|
|
Post by whataboutthis on Jul 6, 2024 17:06:19 GMT
|
|
|
|
Post by 81dollar on Jul 6, 2024 19:52:14 GMT
81dollar : OK - a 2024 S5 Sportback is built on a MLB/MLP-evo platform. I'm not 100% sure - but I can't find ANY modules on this car that has either SFD, or SFD2 protection - See VCDS scan below. I've used a VCDS scan because OBD11 scans do NOT show the ODX name- look at the ROD name in the scan below. If this model has either SFD, or SFD2 - I am very surprised that the 46 -Central Convenience module (J393) is NOT covered by this protection protocol Are you sure that these protocols apply to this model Audi? If these protocols do NOT apply to this car - maybe the problem of access to the module is that you need a security code (instead of unlocking SFD/SFD2)? I'm guessing! Don
2023 Audi S5 Sportback 3.0V6T CWGD
Interesting. The automatic SFD unlock as described on this page has seemingly always worked for me, but I am unable to write anything to this module with engine on / off, hood open / closed, or any other combination. It might be the security code, I've tried searching online but the two I've found don't seem to work (41067 and 16017). I'll keep trying, thanks for the help. |
|
|
|
Post by dv52 (Australia) on Jul 6, 2024 22:06:45 GMT
whataboutthis: hmm......... yes, I did see this list when I fist replied - but there is a fundamental contradiction in the response from the deities on the OBD11 mother-ship provided to your question (about the "UNECE" label) and the evidence in my SCAN!
The two pieces of information simply can NOT be true - in logic! Someone it telling porkies! 
Don
|
|
|
|
Post by whataboutthis on Jul 7, 2024 11:43:24 GMT
dv52 (Australia) I agree there is something not right on what we understand so far.
So the first thing to confirm 81dollar is what car do you have and have you checked the live data to confirm you car has SFD Protection (check control unit 09 live data SFD Activated status.) then at least we will know if the car is protected or not.
Secondly you state you cant long code have you tried making changes to adaptatoins rather than long coding in this and other control units.
Thirdly from memory the work OBD11 have done so far is only to unlock the control units so that we can see them (at the start you could not) but further information said if the control unit is protected by SFD then you cant code but if its not protected then you can.
|
|
|
|
Post by leventcur on Jul 23, 2024 17:05:26 GMT
whataboutthis : I sympathize with those that have SFD2 encrusted vehicles - it must be very frustrating to have purchased OBD11 and not have access to those modules in the car that are locked by the newest protocol However, another aspect of this matter is that notwithstanding the problems with SFD2, the deities on the OBD11 mother-ship appear to be light years ahead of their competitors! As an example and despite the CEO of Ross-Tech promising a fix for his diagnostic cables years ago, VCDS still doesn't have a integrated solution to version 1 of SFD!! And no, this doesn't reduce the imperative for a speedy SFD2 fix for OBD11 - but it DOES put the problem in perspective - IMO, of course! Don It sucks… I bought this with the intentions of using it for one click apps only and their site is such a bait and switch unless you knew about SFD2, and I didn’t, till I came here. I feel dupped and taken advantage of seeing as how they still show that one click apps are compatible for my 2024 Audi SQ5. Please do those a favor and fix the webpage, cause it’s misleading, either get it going or I foresee tons of angry people. |
|
|
|
Post by whataboutthis on Jul 23, 2024 17:52:22 GMT
I am afraid they are rubbish at updating web sites and communicating state of play with bug fixes.
My personal view is support and obd11 staff dont spend much time reading this forum so use the help function to report issue.
If you have just purchased the dongle you could try asking for a refund as they have not provided the access the web site says it does.
|
|
|
|
Post by diabolik on Jul 29, 2024 10:47:04 GMT
hi, this is a latest email from the OBD team:
" 25 july 2024
Hello,
Thank you for reaching out to 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.
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.
Let me know if you have any other questions.
Erikas
OBDeleven"
|
|
|
|
Post by mroth824 on Aug 5, 2024 12:37:27 GMT
hi, this is a latest email from the OBD team: " 25 july 2024 Hello, Thank you for reaching out to 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. 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. Let me know if you have any other questions. Erikas OBDeleven" When I try to change anything in adaptions I get a failed message. Anyone else seeing that? Could it be related to the new security? I have a 24 Audi q3. |
|
agilis
New Member
Just learned about SFD & SFD2 :(
Posts: 8
|
Post by agilis on Aug 12, 2024 18:34:38 GMT
hmm....... you are being your normally kind self (alas, I hold Ross-Tech to a much higher standard)! I knew Uwe Ross for many years albeit ONLY as an ex forum colleague. He is a very intelligent man - but I have no doubt that the glacial pace of VCDS's progress towards an integrated SFD solution is due in no small part to Ross-Tech's historic relationship with the VAG group, which as I understand can best be described as adversarial! I don't believe that Ross-Tech has a corporate board. Or if it does, I suspect that it will be Ross family members with Uwe as a strong Chairman - steering the mother-ship. So the CEO's role in the failed SFD roll-out cannot be denied - and ultimately neither can accountability!! And I'm not sure that the "work around" is particularly useful for VCDS users. This solution ONLY works if users have a GEKO account - but this is entirely impracticable for users in the enthusiast market! Unbelievably, the suggested approach for non-professional users during my time as a VCDS forum member was that they purchase OBD11 to generate the token - then copy-and-paste the token-number to VCDS! Yes, this was a serious suggestion!!
Hello there, I am an Enthusiast Ross-Tech VCDS user. I recently traded-up from a Hex-CAN interface which I used on my 2015 Audi RS5 to a Hex-NET for my 2024 Audi RS5. I am one of many now learning about SFD, SFD2, and the complications that now exist that were not present in my 2015 RS5. And this was very eye-opening for me. And so I quickly learned that there is no date when the SFD unlocking would be available that could be promised by Uwe Ross First and foremost, I appreciate your candid response. I was thinking about buying an OBDEleven w/ Pro Subscription however I am reading that OBDEleven is not supported by 2024 Audi models. I also understand that OBDEleven's relationship with VAG Group is a lot stronger than its competitors, including Ross-Tech. All things to consider, what should an Enthusiast such as myself do? Do you think Ross-Tech and OBDEleven will be able to fully support 2024 Audi vehicles? Currently I would like to code 3 things: - Automatic Parking brake with ignition off
- Disable MMI lock-out when moving
- Disable seat belt chime
As of right now I do not believe those 3 things are possible EXCEPT disabling the Seat Belt Chime. So please, can you tell me if the money is worth it as an Enthusiast even when my vehicle is not supported and may never be fully supported? |
|
|
|
Post by dv52 (Australia) on Aug 12, 2024 23:23:44 GMT
agilis :Hi and welcome! Because we are discussing this matter on a OBB11 forum - there are commercial sensitivities that clearly need to be understood. In this respect, I appreciate the forum's leniency in allowing this discussion! And again in this respect - please understand that I have NO association with the parent company for OBD11 and my views as expressed in this thread are entirely and independently mine!
For what it's worth, I have written many posts on numerous forums expressing my views for those considering whether to purchase OBD11, or VCDS (or any other good diagnostic device). In the main, my consistent advice has been that both devices have their different advantages and their various bad points (this advice being IMO, of course). However, for those that have cars that were built in the 21st Century - the question of SFD in it's two current incarnations becomes (or rather, should become) a binding consideration in the decision of which path to take (again, IMO). It would appear in this instance that you have opted for VCDS as your diagnostic device of choice! I make absolutely NO judgement regarding your decision because I am totally ignorant of how you value stuff! Yes, when choosing between OBD11 and VCDS "value" is probably far more important than price, or technical performance! As those that are familiar with the practice of buying stuff will tell you, having made a choice to buy a Ross-Tech product - you have taken a position in the diagnostic device market and the money paid is now a "sunk-cost". In this sense, you now have a financial commitment to Ross-Tech and because your car was built in the 21st century, your use of VCDS is entirely predicated on Ross-Tech's progress with an integrated solution to SFD in general and SFD2 in particular. Alas as we are both aware - Ross-Tech's track-experience with SFD has not been good and more remarkably, Ross-Tech's complete absence of a public explanation to their users over the past 5 years has been deafening
Of course only the deities on the Ross-Tech mother-ship know the financial impact of their failure to provide a SFD solution. And no one outside Ross-Tech knows whether they are even progressing a SFD2 solution! However, we can all reasonably conclude that sales MUST have dropped over the past 5 x years because their devices are incompatible with cars built in the 21st century. Ross-Tech doesn't emphasize the limitations of their products in their advertising - so I suspect that they are relying on their reputation for new sales (perhaps this was your motivation to buy?). Nevertheless, with time and a greater understanding in the market of the incompatibility of VCDS, this will change.
In any event and after 5 years, I would expect the impact of this failure to be strongly felt by the shareholder(s) - which I suspect greatly increases the prospect of a SFD solution in the near future (defined any way you want). But, I'm speculating and I freely admit that I have absolutely no knowledge of what drives Ross-Tech's corporate strategies!!
Plus - the other matter that I've not mentioned above when considering diagnostic devices is "user expectation" - which I suspect is important in this instance. It's an obvious fact, but still worth stating that there is only ONE diagnostic device that will keep pace with the technical changes made by VAG to their latest release models - that device is the dealer tool ODIS. Every other third-party diagnostic device (regardless of whether it's Ross-Tech, or VOLTIS-IT) will be playing the catch-up game - which ALWAYS means a delay in new-car coverage!!
So, without any offense intended - since you have taken a position in the diagnostic device market and since your purchase is now a sunk-cost, I respectfully suggest that IMO your best way forward is to join the Ross-Tech forum and add your voice to the growing throng of VCDS users seeking an integrated SFD solution. Or, at the very least as a VCDS user, legitimately harass Ross-Tech and request more information about an expected delivery date (even Ross-Tech must accept that VCDS users are entitled to more information after a period of 5 years of unfulfilled promises)!
Don
PS: Of course you could "hedge-your-bet" and also buy OBD11, but I don't see how you are advantaged by this option until OBD11 has a stable and proven solution for your car. However, this option is economically inefficient given your VCDS purchase. I make absolutely no comment on which of the 2 x competing diagnostic devices is more likely to win the SF2 solution race - I suggest that your judgement based on the past performance of the 2 x competing companies is as good as anyone else!!
PPS: If you eventually do buy OBD11, there would appear to be no value in also owning VCDS (doesn't make sense for this late model car). In this scenario - maybe consider cutting-your-loss and sell VCDS on the 2nd-hand market. However, if you adopt this approach, perhaps also consider that the 2nd hand value of VCDS devices will likely drop as the failure of a SFD solution continues (so, sell quickly!)
|
|
agilis
New Member
Just learned about SFD & SFD2 :(
Posts: 8
|
Post by agilis on Aug 13, 2024 1:11:23 GMT
dv52 (Australia) Wow! That was an amazing response and that is exactly why I went to you for guidance/advice. Don, I must clarify that I chose Ross-Tech VCDS because I used VCDS in the past with a 2015 Audi RS5 using an older interface. When I saw that the older interface was not compatible with my 2024 Audi RS5, I did not hesitate to trade-up to the Ross-Tech HEX-NET. I will admit, foolishly I did not know about SFD, SFD2, OBDEleven, etc. Regrettably, I did not research this properly. In my defense, I feel like I should not have had to. Ross-Tech, during the order process, asked me specifically what vehicle the HEX-NET would be used with, and I stated "Audi RS5 2024" and no one from Ross-Tech cautioned me about my vehicle not being supported due to SFD/SFD2. That has upset and unfortunately, I think I know why  I have reached out to Ross-Tech for help regarding this matter. It makes no sense to own a Ross-Tech VCDS device if my vehicle is not supported. Don, thank you again for your candid response. I understand your opinion is your own. I am judging my decision based on what is advantageous for me. Currently, I am not married to either device while both devices and software that drives the hardware lack support for my vehicle, which may never be supported. -- Rick
|
|
|
|
Post by dv52 (Australia) on Aug 13, 2024 2:57:12 GMT
Ross-Te during the order process, asked me specifically what vehicle the HEX-NET would be used with, and I stated "Audi RS5 2024" and no one from Ross-Tech cautioned me about my vehicle not being supported due to SFD/SFD2. That has upset and unfortunately, I think I know why Rick: first thanks for the kind words!
Uwe Ross's handle on the VCDS forum is "Benevolent Dictator". During my many years as an active forum participant (I no longer am), I have experienced the impact of both descriptors:Uwe's generous largess for my meager contributions on the forum and the sting of Uwe's absolute power for the temerity of expressing a different view that American gun ownership contributes to the heinous slaughter of American school children (Uwe has an ultra right-wing position on 2nd amendment rights)
Nevertheless, I never doubted (and I still don't doubt) Ross-Tech's trading ethics as an honest business. I'm sure that Ross-Tech will make-good your purchase when you explain the illogical sale of a HEX-NET cable for a car that has SFD2 protection!
Don
|
|
agilis
New Member
Just learned about SFD & SFD2 :(
Posts: 8
|
Post by agilis on Aug 13, 2024 18:05:26 GMT
Nevertheless, I never doubted (and I still don't doubt) Ross-Tech's trading ethics as an honest business. I'm sure that Ross-Tech will make-good your purchase when you explain the illogical sale of a HEX-NET cable for a car that has SFD2 protection! You are very welcome Don!! Thank you once again for your response and insight. I have reached out to Ross-Tech and waiting for hear back. |
|
|
|
Post by fliegerstefan on Aug 18, 2024 11:06:54 GMT
I have a new Kodiaq 2. Since it also has SFD2 protection, I asked OBD-ELEVEN whether the system can handle SFD 2. This was explicitly confirmed to me in writing that SFD 2 activations are possible. I asked again, somewhat implausibly, about SFD 2. Again, I was confirmed: It works.
I then bought the system and set it up.
OBD ELEVEN cannot even find the vehicle and cannot read the VIN. After entering the VIN, the vehicle was recognized and the gateway was found, but the SFD protection could not be removed from the gateway either.
The system cannot therefore do what was promised just 2 days previously. In legal circles, it is called fraud if I sell a product that knowingly does not have the promised properties, and this is a criminal offense under the German Criminal Code.
OBD Eleven could certainly offer to take the parts back or I could admit it. However, this does not solve my problem that I want to remove the SFD protection on a control unit so that I can make changes.
Is there any information as to whether this will still be possible?
|
|
|
|
Post by whataboutthis on Aug 18, 2024 21:01:55 GMT
From what we get from support (who have already given you a wrong answer) they are still working on it..... In theory they have a good working relationship with VAG group so hopefully in the end they will fix it but currently my understanding is some control units will allow coding when SFD is unlocked but others are protected by the SFD2 and those you cant. OBD11 are the only people who can give you a definitive answer but personally I would return the product and get a refund and when they finally get is sorted purchase the item again because we have no idea how long.
UPDATE: I asked the bad AI tool for a status update (waiting till the morning for a real person to come back) and this was the answer
The current status of SFD2 is that it's partially functional but with limitations.
OBDeleven has made progress in addressing SFD-protected control units, allowing for full scans on all control units. However, manual coding may not work on control units with SFD protection, and some One-Click Apps might be affected.
OBDeleven does offer an "SFD Unlock" feature in their Ultimate VAG Plan, suggesting some level of SFD functionality. However, the company is still working on adding coding to SFD-protected control units and developing solutions for new 2024 VAG cars.
If you're experiencing issues, ensure you have the latest app version (iOS 1.9.36+ or Android 0.83.0+) and check your connection to the car.
Source
OBDeleven
|
|
|
|
Post by fliegerstefan on Aug 20, 2024 10:06:07 GMT
Of course I could use my right of return. But that doesn't solve my problem because I need a solution to unlock it.
The outrageous thing is that they claim that it works. Nothing works on vehicles with SFD 2 protection. I already have Android version 0.86.0 or 1.9.40 on the I-pad.
|
|
|
|
Post by whataboutthis on Aug 20, 2024 10:22:39 GMT
There are many people looking for a solution but I am afraid OBD11 Currently (in my view) have a partial offering where on some cars and some control units it works but from what i have read the main control units are still locked out.
Again in my personal view VAG Released this security upgrade because of the legislation to stop cars being controlled via over the air updates but have not so far managed to get it working for third party apps like OBD11 or caristaapp or VCDS.
Bottom line you will have to wait and i only suggested you return as you have paid for something that does not do what was advertised and based on previous experience they wont extend you license because of this.
|
|
agilis
New Member
Just learned about SFD & SFD2 :(
Posts: 8
|
Post by agilis on Aug 20, 2024 13:52:12 GMT
Again in my personal view VAG Released this security upgrade because of the legislation to stop cars being controlled via over the air updates but have not so far managed to get it working for third party apps like OBD11 or caristaappapp or VCDS. Hi there, can you please explain what you mean by "legislation to stop cars being controlled via over the air updates." I thought SFD and SFD2 was put in place to allow manufacturers to offer "enhancements" to vehicles via a subscription model. - Thanks! |
|
agilis
New Member
Just learned about SFD & SFD2 :(
Posts: 8
|
Post by agilis on Aug 20, 2024 13:59:44 GMT
fliegerstefan Unfortunately, nothing available right now will solve your problem. OBDEleven claims they can unlock SFD but it's only partially implemented, at best. Right now, it's only for certain modules, and some of the modules, even though they are unlocked, cannot be written to. I have a 2024 RS5 and there is no solution for my vehicle other than ODIS, and even that cannot unlock SFD2 protected modules. And the only reason I know this is because I have spoken to NPG Technology concerning this. Returning is the only option. Good luck!
|
|
|
|
Post by whataboutthis on Aug 20, 2024 21:39:01 GMT
Sure so SFD according to OBD11 Vehicle Diagnostic Protection (also known as SFD – Schutz Fahrzeug Diagnose) is an additional security layer that requires authorization between the vehicle and manufacturer. It's been introduced by Volkswagen AG to help protect vehicle owners from fraud by providing information on who and when has made modifications to their vehicles. SFD restricts functions like adaptations, coding, and parametrization So from my perspective VW now have a full record of who has been working on the car (from memory they don't record what was changed just that you requested a token to unlock the car). SFD2 as it is know is not related to SFD its just what the community calls it CHECK OUT support.obdeleven.com/en/articles/9187989-does-obdeleven-work-with-vag-vehicles-manufactured-from-2024. However the driving force according to obd11 is The United Nations Economic Commission for Europe Regulation No. 155 - Cyber security and cyber security management system and Regulation No. 156 - Software update and software update management system. With regards to the subscription model whilst all the major manufacturers are building in controls to limit what users can code around they have still left some features open as I am guessing if they stopped all coding then they would loose the revenue that OBD11 and others pay VAG to enable users to code there own cars. And yes there is a lot of RIGHT TO REPAIR going on around this sort of feature but again my personal view is they allow more than just repair features so there must be a money motivation. |
|
