|
|
Post by stoperf on Aug 21, 2024 6:45:00 GMT
Hello!
Obdeleven says that module 51 is not protected by sfd. VCDS and Odis say different things. VCDS generates sfd token, and odis tries to log dss in to unlock sfd. Is there any way to fix this, or maybe someone can manually unlock it in vcds (I will ask for a token)?
Best regards
Krystian
|
|
|
|
Post by whataboutthis on Aug 21, 2024 12:19:52 GMT
How are you defining that the control unit is not SFD Protected please.
If you are using the SFD activated status in Live data are you saying that element is not there.
What happens if you try and make changes to the control unit do you get an error message.
With regards to the live data, my limited understanding is this is picked up from the ODX File (Which can be found under Info on the control unit), are there other ODX Files available if so try one of those and see if it changes the live data.
Otherwise its talking with Support directly and hopefully they can do something.
|
|
|
|
Post by stoperf on Aug 21, 2024 17:57:16 GMT
I am trying to make basic settings (permission to delete dtc) and remove crash from this module. obdeleven says that the module is not protected by sfd. vcds generates a request and odis tries to perform dss logging in order to remove sfd.
I've been trying to contact support since morning. but no results
|
|
|
|
Post by whataboutthis on Aug 21, 2024 21:15:09 GMT
With regards to support I understand as they seem to all have gone on holiday. Response is very slow.
I dont have your car in my garage but I do have an ID4 X with control unit 51 and according to the live data lookup (dont have access to the car any more) it is not protected by SFD
On this car there is only one Basic Setting and that is DTC memory entry deletion trigger (0302) which I guess is what you are after.
What happens if you run it, do you get an error or warning message.
Silly question but do you have Auto SFD Unlock enabled on your account/car and another you do have the bonnet open dont you (sorry just silly things that can get forgotten)
|
|
|
|
Post by stoperf on Aug 22, 2024 16:54:56 GMT
Today I tried on id3 too. It's the same situation, obdeleven writes that there is no sfd protection, but when I connect vcds it generates a sfd query, odis tries to log in dss. (try connecting vcds if you have it to your id3). I unlocked such a car (id3) after replacing the pyrofuse in the battery via odis online dss and did the sfd unlock before unlocking the deletion. Unfortunately, after changes in vag recently, popular rice geko services do not have dss in their offer.
|
|
|
|
Post by whataboutthis on Aug 22, 2024 21:46:09 GMT
OK But if you try and do anything do you get an error message from OBD11
|
|
|
|
Post by dv52 (Australia) on Aug 22, 2024 22:38:04 GMT
Hello! Obdeleven says that module 51 is not protected by sfd. VCDS and Odis say different things. VCDS generates sfd token, and odis tries to log dss in to unlock sfd. Is there any way to fix this, or maybe someone can manually unlock it in vcds (I will ask for a token)? Best regards Krystian Kyystian: huh......? How does VCDS generate a SFD token?
AFAIK, VCDS can NOT generate SFD tokens - the best that VCDS can do is use a SFD token that is generated by another method (i.e by OBD11, or via a GEKO account)!
Which version VCDS do you have that generates a SFD token?
Don
|
|
|
|
Post by stoperf on Aug 24, 2024 6:11:30 GMT
Hello! Obdeleven says that module 51 is not protected by sfd. VCDS and Odis say different things. VCDS generates sfd token, and odis tries to log dss in to unlock sfd. Is there any way to fix this, or maybe someone can manually unlock it in vcds (I will ask for a token)? Best regards Krystian Kyystian: huh......? How does VCDS generate a SFD token?
AFAIK, VCDS can NOT generate SFD tokens - the best that VCDS can do is use a SFD token that is generated by another method (i.e by OBD11, or via a GEKO account)!
Which version VCDS do you have that generates a SFD token?
Don
Did you read carefully? In VCDS in module 51 the SFD window appears. VCDS generates an SFD query. Like this video Odis tries to log geko DSS. The module is 100% protected by SFD, and OBDELEVEN has an error. I am closing the discussion, because it is not leading anywhere. Ticked accepted by support. |
|
|
|
Post by dv52 (Australia) on Aug 24, 2024 23:12:05 GMT
Notwithstanding your advice "I am closing the discussion", yes I did "read carefully". That's why I asked my question (because I did "read carefully")- but thank you for the suggestion! Your video shows the SFD token already entered into VCDS from another source - I suspect from a GEKO account. If the video in your last post had started at an early point in the diagnostic session - it would have shown the VCDS screen below: Notice the words "Release token (enter below)" in the section highlighted. So, VCDS is requesting that the user separately enter the SFD token. VCDS does NOT generate this token - it must be provided by a non-Ross-Tech application! This omission functionally separates VCDS from other diagnostic devices like OBD11 because unlike OBD11, Ross-Tech products do NOT provide an integrated solution for SFD (and VCDS hasn't done so for the past 5 years)
Hence my original question to your statement in your post "VCDS generates sfd token". This statement is factually NOT correct!
Also, I don't understand your words "Odis tries to log geko DSS". If you have access to a true GEKO account and a genuine ODIS diagnostic device - why use VCDS at all? Or asked another way - why would you expect a non-VAG diagnostic tool (like VCDS, or OBD11) to fix a problem that the official VAG tool can't solve?
Don |
|
