Difference between revisions of "User:Peter"

From Ross-Tech Wiki
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
= WARNING: RESTRICTED ACCESS =
  
 +
Your attempt to access this page is considered UNAUTHORIZED!
 +
'''ERROR 401: UNAUTHORIZED'''
  
−
==  Audi A5 (8T) Active/Dynamic Steering == 
+
Your IP address has been logged.
  
−
== Coding ==
 
  
−
'''Coding for this Control Module is normally done via Software Version Management (SVM). If the old Control Module is still accessible read/copy it's Coding to the new Module.
 
  
 +
------------------------------------------------------------
  
  
−
== Basic Setting ==
 
  
−
=== 1B-Active Steering ===
 
  
  
−
'''<u>Prerequisites:</u>'''<br>
 
−
* Battery Voltage = 12.0 - 14.0 V'''<br>
 
−
* No fault codes other than [[01087 | 01087 - Basic Setting Not Performed]]'''<br>
 
  
−
* Perform G85-Steering Angle Sensor Basic Settings found on this Ross-Tech wiki page: [[Audi A5 (8T) Steering Wheel Electronics#Basic Setting|Audi A4/A5 (8K/8T) Steering Angle Sensor (G85) Calibration]]
 
  
  
−
 
  
  
−
<span style="color:#000000; background:#FFFF00"> '''- Continue Only after successfully completing the G85 basic settings -''' </span>
 
  
−
*Leave the steering wheel in the straight ahead position during the next steps.
 
  
  
−
'''[Select]'''<br>
 
−
'''[1B-Active Steering]'''<br>
 
  
−
'''[Security Access - 16]'''<br>
 
−
Enter 61378, to enable the basic setting.'''<br>
 
−
'''[Do it!]'''<br>
 
  
 +
= Volkswagen SFD, SFD2 & Service Reminder Reset (SRI) with VCDS =
  
−
'''[Basic Settings - 04]'''<br>
+
== Overview ==
−
Group 101<br>
 
−
'''[Go!]'''<br>
 
−
'''[ON/OFF/Next]''' <br>
 
  
−
* The results should be stored after a key cycle and fault code(s) should clear.
+
Volkswagen Group introduced SFD ('''Schutz der Fahrzeugdiagnose''' – Protection of Vehicle Diagnostics) in 2020 to enhance cybersecurity and control access to vehicle software. In 2024, a second layer called '''SFD2''' was introduced, requiring cryptographic validation for critical changes.
  
 +
This page explains how VCDS interacts with SFD and SFD2 systems and provides step-by-step instructions for resetting the Service Reminder (SRI) on protected vehicles.
  
−
'''[Done, Go Back]''' <br>
+
== What is SFD and SFD2? ==
−
'''[Fault Codes - 02]'''<br>
 
−
Check and clear fault codes.<br>
 
−
'''[Close Controller, Go Back - 06]'''<br>
 
  
 +
'''SFD (v1)''' restricts coding, adaptations, and other “write” functions unless a one-time unlock token is used. VCDS supports this system using a manual token entry method.
  
 +
'''SFD2 (v2)''' is used in 2024+ vehicles and protects specific data changes using encrypted, per-operation validation. SFD2 requires Volkswagen’s online infrastructure and is currently unsupported by VCDS.
  
 +
SFD and SFD2 do '''not''' block:
 +
* Reading fault codes (DTCs)
 +
* Viewing live data (Measuring Blocks)
 +
* Performing an Auto-Scan
  
 +
== How VCDS Works with SFD ==
  
 +
VCDS supports SFD by:
 +
* Detecting SFD-protected modules
 +
* Displaying the module's challenge string
 +
* Allowing manual entry of the corresponding unlock token
  
 +
VCDS does not generate or request unlock tokens itself. Tokens must be obtained separately and are valid for:
 +
* One module only
 +
* One session (approximately 90 minutes)
  
 +
'''SFD2 is not supported by VCDS.'''
  
 +
== Manual Unlock Process in VCDS ==
  
−
======================================================================
+
# Open VCDS and connect to the module
 +
# Attempt a function (e.g., Adaptation or Security Access)
 +
# Copy the displayed challenge string
 +
# Submit the challenge to a trusted token provider
 +
# Paste the returned release token into VCDS
 +
# The module unlocks for ~90 minutes
  
 +
== Resetting the Service Reminder (SRI) ==
  
 +
=== Vehicles Without SFD (Pre-2020) ===
  
−
001 Upper Limit Exceeded<br>
+
Older vehicles do not require SFD unlocks. 
−
002 Lower Specified Value too Low<br>
+
→ [https://www.ross-tech.com/vcds/tour/sri-reset.php SRI Reset Tour Page]
−
003 Mechanical/Hydraulic Fault<br>
 
−
004 No signal/communication<br>
 
−
005 No or Incorrect Basic Settings/Adaptation<br>
 
−
006 Short Circuit to positive<br>
 
−
007 Short to Ground<br>
 
−
008 Implausible Signal/Ranger or Performance<br>
 
−
009 Open Circuit/short to ground<br>
 
−
010 Open Circuit/short to positive<br>
 
−
011 Open Circuit<br>
 
−
012 Electrical fault in Circuit<br>
 
−
013 Check/Read DTC memory<br>
 
−
014 Defective<br>
 
−
015<br>
 
−
016 Signal outside of Tolerance<br>
 
  
−
<br>
+
=== Vehicles With SFD ===
  
−
027 Implausible Signal<br>
+
Some newer vehicles (e.g., Golf 8, ID.4) have SFD in:
−
028 Short Circuit to positive<br>
+
* '''17-Instruments'''
−
029 Short to Ground<br>
+
* '''5F-Infotainment'''
−
030 Open Circuit<br>
 
−
031 Open Circuit/short to ground<br>
 
−
035 No Indication in Display<br>
 
−
036 Open Circuit<br>
 
−
037 Faulty<br>
 
−
045 Connector<br>
 
−
049 No Communications<br>
 
−
079 Checking DTC Memory<br>
 
−
194 Comparison not Carried Out<br>
 
  
 +
Steps:
 +
# Retrieve the challenge string in VCDS
 +
# Obtain and enter the unlock token
 +
# Perform the SRI reset within the 90-minute window
  
 +
=== Vehicles With SFD2 / Gateway Filtering ===
  
 +
Newer platforms may also use a diagnostic filter in '''19-Gateway'''.
  
 +
Steps:
 +
# Retrieve and unlock 19 using a token
 +
# In 19, go to Adaptation and set: 
 +
  <code>DE16611 – Diagnosis filter: temporary deactivation → not active</code>
 +
# This disables the diagnostic filter for ~20 km
 +
# Unlock 5F (or other protected modules) using tokens
 +
# Perform the SRI reset
  
 +
<span style="color:orange;"><b>Tip:</b> While in R-Mode, you can collect challenge strings for both 19 and 5F and request both tokens at once.</span>
  
 +
== SFD Requirement Matrix for SRI Reset ==
  
 +
{| role="presentation" class="wikitable" style="background:lightgray; text-align:center; width:99%;" border="0"
 +
|-
 +
! Service function !! Vehicles Without SFD !! SFD in 17-Instruments !! SFD in 5F-Infotainment !! SFD2 Gateway Filter
 +
|-
 +
! SRI (Service Reminder) Reset
 +
| style="background:limegreen" | Just perform SRI reset || style="background:orange" | Unlock 17 first || style="background:orange" | Unlock 5F first || style="background:red" | Unlock 19, then unlock 5F
 +
|-
 +
! Is SFD Unlock Required?
 +
| style="background:limegreen" | No || style="background:orange" | Yes || style="background:orange" | Yes || style="background:red" | Yes in 19 and 5F
 +
|-
 +
! Can You Save Adaptation Values?
 +
| style="background:limegreen" | Yes || style="background:orange" | Yes, after unlocking 17 || style="background:orange" | Yes, after unlocking 5F || style="background:red" | Unlock 19 to disable filter, then unlock other modules
 +
|}
  
 +
<sup>1</sup> 17 – Instrument Cluster 
 +
<sup>2</sup> 5F – Infotainment / MMI 
 +
<sup>3</sup> 19 – CAN Gateway with SFD2 diagnostic filtering
  
 +
== NIx Coding Index Table ==
  
 +
Some vehicles contain a PR code indicating cybersecurity level:
  
 +
{| class="wikitable"
 +
|-
 +
! NIx Index !! Cybersecurity Protection !! Software Update Protection !! SFD2 Gateway Present?
 +
|-
 +
| NI0 || No || No || No
 +
|-
 +
| NI1 || Yes || Yes || No
 +
|-
 +
| NI7 || Yes || No || No
 +
|-
 +
| NI8 || No || No || Yes
 +
|-
 +
| NI9 || Yes (non-UNECE markets) || Yes (non-UNECE markets) || No
 +
|}
  
 +
== Factory Tool vs VCDS Comparison ==
  
−
__FORCETOC__
+
{| class="wikitable"
−
== 18613/P2181/008577 - Performance Malfunction in Cooling System ==
+
! Feature !! ODIS (Factory Tool) !! VCDS
 +
|-
 +
| Token Handling || Online and automatic || (still in development)
 +
|-
 +
| Backend Access || Yes || (still in development)
 +
|-
 +
| Lockout Behavior || Immediate logout or session close || Timeout (~90 minutes)
 +
|-
 +
| Token Source || VW Dealer Portal || (still in development)
 +
|}
  
−
==== Possible Causes ====
+
== Related Control Module Addresses ==
  
−
* Faulty Coolant Sensor
+
* '''17 – Instruments''': Cluster, odometer, service interval
−
* Faulty Coolant Thermostat
+
* '''5F – Infotainment''': MMI, media interface
−
* Faulty Wiring, Connections
+
* '''19 – Gateway''': Network access, diagnostic filter
  
−
''Note'': This fault code sets when engine coolant temperature mapping is lower and out of expected range based on operating conditions of the engine.
+
== Resources ==
−
* For example: Engine warms up, thermostat opens and stays open, coolant temperature drops below normal operating range. The ECM knows the coolant temperature should stay within 80.0...110.0 °C typically after warm up. Thus a drop in coolant temperature below normal operating temperature is not possible without a malfunction in cooling system.
 
  
−
==== Possible Solutions ====
+
* [https://www.ross-tech.com/vcds/tour/sri-reset.php SRI Reset Tour]
 +
* [https://www.ross-tech.com/vcds/tour/adaptations.php Adaptations Function Tour]
 +
* [https://forums.ross-tech.com/ Ross-Tech Forums]
  
−
* Check G62 - Engine Coolant Temperature Sender <br>
+
<span style="color:#d93025;"><b>Note:</b> If readiness or service reset functions fail, ensure the engine control unit software is up to date and that a full OBD drive cycle has been completed.</span>
−
** Inspect wiring for G62 (Coolant Migration, damage, corrosion, etc)
 
−
 
 
−
* Check (if applicable) G83 - Radiator Outlet, Coolant Temperature Sender <br>
 
−
** Inspect wiring for G83 (Coolant Migration, damage, corrosion, etc)
 
−
 
 
−
* Check Coolant Thermostat
 
−
**  Use Graph function in VCDS, Measuring Value Blocks - MVB
 
−
** Start Engine cold, graph Coolant Temperature Sender (G62) Typically MVB Group-001
 
−
** Hold RPM around 1,500rpm and watch coolant temp increase in Graph until thermostat opens, indicated by a slight drop in coolant temp
 
−
** If coolant temp drops below minimum operating temperature (80°C) or never reaches operating temperature, (verified by external thermometer) suspect failed thermostat
 
−
 
 
−
* Vehicles with both G62-Engine Outlet, Coolant Temperature Sensor and G83-Radiator Outlet, Coolant Temperature Sensor
 
−
** Use Measuring Value Block group MVB-130 instead on MVB-001
 
−
** G62 should increase in Temperature before G83 increase when engine coolant is cold
 
−
** G83 will increase when the thermostat opens and after G62 reaches operating temperature (80°C)
 
−
** If G62 and G83 both increase while engine warms up, suspect failed thermostat
 
−
 
 
−
 
 
−
==== Special Notes ====
 
−
 
 
−
* Check the stored Freeze Frame data with this fault code.  Freeze Frame information will be found in the fault code description (if the module supports it) or in Generic OBD-II if the vehicle complies with those regulations.
 
−
** Freeze Frame data stored at -40*C is generally an indication of a faulty ECT or wiring.
 
−
** Freeze Frame data stored at +140*C is generally an indication of a faulty ECT or wiring.
 
−
** Freeze Frame data stored with in the 68*C ~ 80*C range is an indication that the vehicle was close to, but not within, the cooling systems normal operation range. The Thermostat itself or Cooling system components may be at fault.
 
−
 
 
−
 
 
−
-----------------------------------------------------------------------------------------------------------------------------
 
−
 
 
−
 
 
−
 
 
−
==Clean Diesel Readiness Status (non UDS Controllers)  ==
 
−
 
 
−
====This information can be found in the [01-Engine] Measuring Value Blocks in the form of binary data.====
 
−
====Below is a guide so it is possible to read and understand the binary data in the fields.====
 
−
 
 
−
* Measuring Value Block Group [089]
 
−
** Field 1 - 0000 0000  -  Fault codes stored and Check Engine Light Status
 
−
** x??? ???? - Fault code count in binary
 
−
** ?xxx xxxx - Check Engine Light On = [1], Off = [0]
 
−
 
 
−
Field 2 = 0000 0000
 
−
?xxx xxxx - N/A
 
−
x?xx xxxx - Comprehensive component monitor readiness status, Incomplete =  [1], Complete = [0]
 
−
xx?x xxxx - Fuel system monitor readiness status, Incomplete =  [1], Complete = [0]
 
−
xxx? xxxx - Misfire monitor readiness status, Incomplete =  [1], Complete = [0]
 
−
xxxx ?xxx - Ignition monitors - Spark or Compression , Supported Function = [1]
 
−
xxxx x?xx - Comprehensive component monitors, Supported Function = [1]
 
−
xxxx xx?x - Fuel system monitor, continuous, Supported Function = [1], Not Supported = [0]
 
−
xxxx xxx? - Misfire monitor, continuous, Supported Function = [1], Not Supported = [0]
 
−
 
 
−
Field 3 = 0000 0000  - Monitors that are supported
 
−
?xxx xxxx - EGR/VVT System Monitor, Supported Function = [1], Not Supported = [0]
 
−
x?xx xxxx - DPF (Diesel Particle Filter) Monitor, Supported Function = [1], Not Supported = [0]
 
−
xx?x xxxx -  Exhaust Gas Sensor Monitor, Supported Function = [1], Not Supported = [0]
 
−
xxx? xxxx -  Not used on diesel vehicles at this time
 
−
xxxx ?xxx -  Indicates Boost Pressure System Monitor, Supported Function = [1], Not Supported = [0]
 
−
xxxx x?xx -  Not used on diesel vehicles at this time
 
−
xxxx xx?x -  NOx/SCR After-treatment Monitor, Supported Function = [1], Not Supported = [0]
 
−
xxxx xxx? -  NMHC Catalyst Monitor, Supported Function = [1], Not Supported = [0]
 
−
 
 
−
 
 
−
Field 4 = 0000 0000    - Readiness status of the supported systems
 
−
?xxx xxxx - EGR/VVT System monitor readiness status, Incomplete =  [1], Complete = [0]
 
−
x?xx xxxx -  DPF readiness status, Incomplete =  [1], Complete = [0]
 
−
xx?x xxxx -  Exhaust Gas Sensor monitor readiness status, Incomplete =  [1], Complete = [0]
 
−
xxx? xxxx -  Not used on diesel vehicles at this time
 
−
xxxx ?xxx -  Boost pressure system monitor readiness Status, Incomplete =  [1], Complete = [0]
 
−
xxxx x?xx -  Not used on diesel vehicles at this time
 
−
xxxx xx?x -  Readiness status of NOx/SCR After-treatment Monitor, Incomplete =  [1], Complete = [0]
 
−
xxxx xxx? -  Readiness status of NMHC Catalyst Monitor, Incomplete =  [1], Complete = [0]
 
−
 
 
−
 
 
−
- Abbreviations -
 
−
DPF = Diesel Particle Filter
 
−
NOx = Oxides of nitrogen
 
−
SCR = Selective catalytic reduction systems
 
−
NMHC = Non-methane hydrocarbons
 
−
EGR = Exhaust Gas Recirculation
 
−
VVT = Variable valve timing
 
−
 
 
−
 
 
−
- Ignition Type -
 
−
Spark = Gasoline
 
−
Compression = Diesel
 

Revision as of 14:37, 30 July 2025

WARNING: RESTRICTED ACCESS

Your attempt to access this page is considered UNAUTHORIZED! ERROR 401: UNAUTHORIZED

Your IP address has been logged.









Volkswagen SFD, SFD2 & Service Reminder Reset (SRI) with VCDS

Overview

Volkswagen Group introduced SFD (Schutz der Fahrzeugdiagnose – Protection of Vehicle Diagnostics) in 2020 to enhance cybersecurity and control access to vehicle software. In 2024, a second layer called SFD2 was introduced, requiring cryptographic validation for critical changes.

This page explains how VCDS interacts with SFD and SFD2 systems and provides step-by-step instructions for resetting the Service Reminder (SRI) on protected vehicles.

What is SFD and SFD2?

SFD (v1) restricts coding, adaptations, and other “write” functions unless a one-time unlock token is used. VCDS supports this system using a manual token entry method.

SFD2 (v2) is used in 2024+ vehicles and protects specific data changes using encrypted, per-operation validation. SFD2 requires Volkswagen’s online infrastructure and is currently unsupported by VCDS.

SFD and SFD2 do not block:

  • Reading fault codes (DTCs)
  • Viewing live data (Measuring Blocks)
  • Performing an Auto-Scan

How VCDS Works with SFD

VCDS supports SFD by:

  • Detecting SFD-protected modules
  • Displaying the module's challenge string
  • Allowing manual entry of the corresponding unlock token

VCDS does not generate or request unlock tokens itself. Tokens must be obtained separately and are valid for:

  • One module only
  • One session (approximately 90 minutes)

SFD2 is not supported by VCDS.

Manual Unlock Process in VCDS

  1. Open VCDS and connect to the module
  2. Attempt a function (e.g., Adaptation or Security Access)
  3. Copy the displayed challenge string
  4. Submit the challenge to a trusted token provider
  5. Paste the returned release token into VCDS
  6. The module unlocks for ~90 minutes

Resetting the Service Reminder (SRI)

Vehicles Without SFD (Pre-2020)

Older vehicles do not require SFD unlocks. → SRI Reset Tour Page

Vehicles With SFD

Some newer vehicles (e.g., Golf 8, ID.4) have SFD in:

  • 17-Instruments
  • 5F-Infotainment

Steps:

  1. Retrieve the challenge string in VCDS
  2. Obtain and enter the unlock token
  3. Perform the SRI reset within the 90-minute window

Vehicles With SFD2 / Gateway Filtering

Newer platforms may also use a diagnostic filter in 19-Gateway.

Steps:

  1. Retrieve and unlock 19 using a token
  2. In 19, go to Adaptation and set:
 DE16611 – Diagnosis filter: temporary deactivation → not active
  1. This disables the diagnostic filter for ~20 km
  2. Unlock 5F (or other protected modules) using tokens
  3. Perform the SRI reset

Tip: While in R-Mode, you can collect challenge strings for both 19 and 5F and request both tokens at once.

SFD Requirement Matrix for SRI Reset

1 17 – Instrument Cluster 2 5F – Infotainment / MMI 3 19 – CAN Gateway with SFD2 diagnostic filtering

NIx Coding Index Table

Some vehicles contain a PR code indicating cybersecurity level:

NIx Index Cybersecurity Protection Software Update Protection SFD2 Gateway Present?
NI0 No No No
NI1 Yes Yes No
NI7 Yes No No
NI8 No No Yes
NI9 Yes (non-UNECE markets) Yes (non-UNECE markets) No

Factory Tool vs VCDS Comparison

Feature ODIS (Factory Tool) VCDS
Token Handling Online and automatic (still in development)
Backend Access Yes (still in development)
Lockout Behavior Immediate logout or session close Timeout (~90 minutes)
Token Source VW Dealer Portal (still in development)

Related Control Module Addresses

  • 17 – Instruments: Cluster, odometer, service interval
  • 5F – Infotainment: MMI, media interface
  • 19 – Gateway: Network access, diagnostic filter

Resources

Note: If readiness or service reset functions fail, ensure the engine control unit software is up to date and that a full OBD drive cycle has been completed.

Retrieved from "https://wiki.ross-tech.com/wiki/index.php?title=User:Peter&oldid=9743"