Jon89
Veteran Member
close
- Join DateJan 2009
- LocationRaleigh, NC
- Posts:13,072
-
Likes:2,339
-
Liked:4,722 Times in 3,062 Posts
2006 XK8. The airbag system amber indicator light on the dash began flashing while we were headed out to dinner tonight. It flashed many times, perhaps as many as 25 or 30, before going solid on. I read somewhere that this flashing sequence is actually a code for what component within the airbag system is triggering the fault. I assume you must count the individual flashings before the light turns solid on and interpret them somehow. Is this true, and if so, how do you figure out the code and relate it to a component needing attention?
WhiteXKR
Veteran Member
close
- Join DateApr 2010
- LocationArlington VA USA
- Posts:7,657
-
Likes:533
-
Liked:3,019 Times in 2,141 Posts
Count the flashes until a pause, that is the first digit. Count again until a second longer pause, that is the second digit. It repeats the sequence a few times after ignition then goes solid.
Here is the decoder ring: https://www.jaguarforums.com/forum/a...lash-codes-pdf
Here is the decoder ring: https://www.jaguarforums.com/forum/a...lash-codes-pdf
Jon89
Veteran Member
close
- Join DateJan 2009
- LocationRaleigh, NC
- Posts:13,072
-
Likes:2,339
-
Liked:4,722 Times in 3,062 Posts
Thanks for breaking the code for me. So the flashing code is always just a two-digit number that is repeated several times before the warning light goes solid?
Does the car's air bag warning system also generate an OBDII code that my neighbor's generic-but-relatively-sophisticated OBDII code reader can recognize and interpret?
Does the car's air bag warning system also generate an OBDII code that my neighbor's generic-but-relatively-sophisticated OBDII code reader can recognize and interpret?
WhiteXKR
Veteran Member
close
- Join DateApr 2010
- LocationArlington VA USA
- Posts:7,657
-
Likes:533
-
Liked:3,019 Times in 2,141 Posts
Quote:
Does the car's air bag warning system also generate an OBDII code that my neighbor's generic-but-relatively-sophisticated OBDII code reader can recognize and interpret?
Yes.Originally Posted by Jon89
Thanks for breaking the code for me. So the flashing code is always just a two-digit number that is repeated several times before the warning light goes solid? Does the car's air bag warning system also generate an OBDII code that my neighbor's generic-but-relatively-sophisticated OBDII code reader can recognize and interpret?
I do not think a generic code reader will pick up the air-bag OBDII codes, but the flashing lights should give you pretty good info.
Jon89
Veteran Member
close
- Join DateJan 2009
- LocationRaleigh, NC
- Posts:13,072
-
Likes:2,339
-
Liked:4,722 Times in 3,062 Posts
Just came back inside from starting the car after it sat overnight locked and therefore in sleep mode. No air bag warning light now - after the usual system self-check procedure, all is well. Drove the car around the neighborhood. No issues now, so I returned home and locked it. The only difference compared to last night is that I was alone in the drivers seat this morning. So the system has obviously cleared and re-set....
I've read that the proximity sensors on the passenger side can be fussy and may not like the way the passenger is leaning or positioned in relation to the airbag locations on that side. I wonder if my wife's movements set off the air bag warning light last night....
Thoughts and suggestions? Since the air bag warning light did indeed flash many times and eventually go solid last night, would an OBDII code have been stored as a result?
I've read that the proximity sensors on the passenger side can be fussy and may not like the way the passenger is leaning or positioned in relation to the airbag locations on that side. I wonder if my wife's movements set off the air bag warning light last night....
Thoughts and suggestions? Since the air bag warning light did indeed flash many times and eventually go solid last night, would an OBDII code have been stored as a result?
WhiteXKR
Veteran Member
close
- Join DateApr 2010
- LocationArlington VA USA
- Posts:7,657
-
Likes:533
-
Liked:3,019 Times in 2,141 Posts
Wait until it happens again and get the code. Most likely culprit is a connector that needs cleaning (use Radio Snack Tuner cleaner), and the code will help you isolate where.
Jon89
Veteran Member
close
- Join DateJan 2009
- LocationRaleigh, NC
- Posts:13,072
-
Likes:2,339
-
Liked:4,722 Times in 3,062 Posts
Will do. As always, thanks for your expertise....
GGG

close
- Join DateDec 2011
- LocationDurham, UK
- Posts:120,439
-
Likes:7,142
-
Liked:17,003 Times in 12,221 Posts
Quote:
Here is the decoder ring: https://www.jaguarforums.com/forum/a...lash-codes-pdf
Flashing airbag warning started yesterday and is still there today. Following the above procedure, I get [One Flash - pause - Seven Flashes]. This repeats three times before becoming a permanent light.Originally Posted by WhiteXKR
Count the flashes until a pause, that is the first digit. Count again until a second longer pause, that is the second digit. It repeats the sequence a few times after ignition then goes solid.Here is the decoder ring: https://www.jaguarforums.com/forum/a...lash-codes-pdf
From the Decoder Diagnostic TSB, code 17 indicates OPS sensor fault either on the B Pillar or the overhead Console. Alternatively it could be an OCS calibration error.
I've cleaned the connectors on the B Pillar and the Console but the error is still there. It looks as if I need the DTC's read to get any further.
My AutoEnginuity is the older version which isn't compatible with the Jaguar enhancement. To update means buying the entire package of scantool and enhancement. Before I do this, can anyone confirm the AE version ST06 with Jaguar enhancement allows reading and clearing airbag 'B' codes?
Graham




