|
Post by audi4real on Oct 5, 2024 23:03:41 GMT
I’m getting the following Gateway faults after SFD unlocking:
- Release Active, Fault Code B184C00 - Function Limitation Due To Missing Message, Code U111100 - Blank Static Fault with no fault code
I’ve tried clearing them but they immediately come back. Any ideas or suggestions?
|
|
|
Post by dv52 (Australia) on Oct 6, 2024 0:20:12 GMT
audi4real : Hi. I'm not sure why the error happens - but according to one of our colleagues who was a beta tester, "this is all normal"!! Hi, just some information when doing the Sfd Unlocking. A fault "B184C00 - Activation active" will appear in the control unit you have unlocked and it will remain static until the control unit gets relocked. After that the error could disappear, if not just clear it. It might also appear in the data bus control unit 19. This is all normal
Again, I'm not sure, but as an uninformed suggestion if the error won't clear - maybe try unlocking SFD on the module again, then re-lock the module?
Don
|
|
|
Post by audi4real on Oct 6, 2024 18:47:12 GMT
audi4real : Hi. I'm not sure why the error happens - but according to one of our colleagues who was a beta tester, "this is all normal"!! Hi, just some information when doing the Sfd Unlocking. A fault "B184C00 - Activation active" will appear in the control unit you have unlocked and it will remain static until the control unit gets relocked. After that the error could disappear, if not just clear it. It might also appear in the data bus control unit 19. This is all normal
Again, I'm not sure, but as an uninformed suggestion if the error won't clear - maybe try unlocking SFD on the module again, then re-lock the module?
Don
How do I go about unlocking SFD and relocking it again?
|
|
|
Post by dv52 (Australia) on Oct 6, 2024 23:37:53 GMT
audi4real : OK, no offense intended - but that's a really basic question!!! Maybe I should commence my reply by explaining the SFD process - my apology in advance if you already know this stuff!.
After you register to make coding changes on a vehicle with SFD and you fire-up the OBD11 software - the first thing that happens is that a request is made to the VW mother-ship for a coding authority called a "Token". The Token is a one-time-only-use license and it also has a time-limit.
So the important features of each individual SFD Token are: - A Token is valid ONLY for a single diagnostic session, and
- The unique coding-license will automatically lapse after a set time-period
Once generated, the Token is then wielded via the OBD11 software to the vehicle and it is validated by the module. If correctly accepted, the module is unlocked and coding changes are allowed. Note: the user identity and details of the coding changes are made available to VW - if required!
When the diagnostic session ceases -by exiting the OBD11 software, the Token is disabled and it is no longer valid. More importantly, because the Token is no longer valid - the module re-locks and coding access ceases until the SFD process is repeated and a new Token is generated/accepted by the module!
So, the suggestion in my previous reply is ostensibly about re-starting a brand new diagnostic session - which basically means repeating the entire SFD unlock process once more. This entails generating a new Token, unlocking the module again- but NOT making any coding changes. Then simply close the diagnostic session by exiting the OBD11 software! Does the error disappear, or can you clear the fault after the repeated SFD diagnostic session?
Again, I'm guessing - hence, no guarantee of success (but it is an easy try - so worth a shot, IMO of course)!!
Don
|
|
|
Post by audi4real on Oct 7, 2024 16:04:46 GMT
audi4real : OK, no offense intended - but that's a really basic question!!! Maybe I should commence my reply by explaining the SFD process - my apology in advance if you already know this stuff!.
After you register to make coding changes on a vehicle with SFD and you fire-up the OBD11 software - the first thing that happens is that a request is made to the VW mother-ship for a coding authority called a "Token". The Token is a one-time-only-use license and it also has a time-limit.
So the important features of each individual SFD Token are: - A Token is valid ONLY for a single diagnostic session, and
- The unique coding-license will automatically lapse after a set time-period
Once generated, the Token is then wielded via the OBD11 software to the vehicle and it is validated by the module. If correctly accepted, the module is unlocked and coding changes are allowed. Note: the user identity and details of the coding changes are made available to VW - if required!
When the diagnostic session ceases -by exiting the OBD11 software, the Token is disabled and it is no longer valid. More importantly, because the Token is no longer valid - the module re-locks and coding access ceases until the SFD process is repeated and a new Token is generated/accepted by the module!
So, the suggestion in my previous reply is ostensibly about re-starting a brand new diagnostic session - which basically means repeating the entire SFD unlock process once more. This entails generating a new Token, unlocking the module again- but NOT making any coding changes. Then simply close the diagnostic session by exiting the OBD11 software! Does the error disappear, or can you clear the fault after the repeated SFD diagnostic session?
Again, I'm guessing - hence, no guarantee of success (but it is an easy try - so worth a shot, IMO of course)!!
Don
So that's the strange thing. I went through the SFD unlocking procedure. It required that I setup two factor authentication, confirmed my identity/account and then unlocked. I have subsequently disconnected and reconnected my OBDEleven several times to make other changes but it has never asked me to do the SFD unlock again. It only did it that one time but I have not seen any other screens asking me to unlock. Is there a way of confirming whether it's still unlocked and perhaps failed to lock again? I've also closed the OBDEleven app several times, but again, have never been asked to do the SFD Unlock again. Should I try clearing the app cache?
|
|
|
Post by dv52 (Australia) on Oct 8, 2024 0:13:22 GMT
As I said - I'm guessing!! Maybe contact the OBD11 support team?
Don
|
|