8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHDurmetric help
Leading reported evidence
Check codes, the software didn't display anything
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
Anyway, checked for codes, the software didn't display anything.
Leading evidence: 'Check codes, the software didn't display anything' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check codes, the software didn't display anything' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
You might check your manual, I seem to recall a note stating that the airbags are disabled with an active system fault.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
They normally throw a code between 44 and 50, and be sure to check under the seat that they're properly plugged into the harness.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
So, recently had my airbag light come on (actually over x-mas on my way to my parents house) and picked up the durametric software to reset the light.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Reset the light, light went out, came back on a few hundred miles later.
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
odd, are you sure the software properly connected with the car?(does it pull up the car ID's?...EDIT, perhaps the airbag module has a hardware connection problem..?)...have you tried going under 'functions' and doing the 'short test all modules'?
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
8 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T183130Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
So, recently had my airbag light come on (actually over x-mas on my way to my parents house) and picked up the durametric software to reset the light. Anyway, checked for codes, the software didn't display anything. Reset the light, light went out, came back on a few hundred miles later.
Anyway, plugged back in and want to figure out what the heck is going on. Still get nothing under any of the identification, information or fault code windows on any module. Though I can read live values off the ECU and mess with dash lights. Since it's saturday, and I doubt i'll get an answer from durametric anytime soon, was wondering if you guys had anything. Now i'm gonna go back inside and get my fingers to work again. brrr
That's odd. My airbag light comes on a few times a year. I get the code on the durametric. I forget number of the code thrown, but it us my driver side seatbelt sensor (common problem). It is my understanding that the airbag is still operable when the code is thrown. Weird that you are not seeing it on the software. Durametric support has always been good, I'm sure they can answer.
odd, are you sure the software properly connected with the car?(does it pull up the car ID's?...EDIT, perhaps the airbag module has a hardware connection problem..?)...have you tried going under 'functions' and doing the 'short test all modules'?
When I get the occasional airbag light, I spray some electronic contact cleaner in the seat belt receptacle before resetting with the durametric. That helps me to avoid the light for another 9-12 months.
So is it not connecting to any module, or just the airbag module? If it connects to everything but the airbag module, it may be an issue with the module or wiring harness. If your airbag light is on, it should pull codes.
You might check your manual, I seem to recall a note stating that the airbags are disabled with an active system fault.
+1 as others have said, the first place to check is the seat belt buckles and electric harness (driver and passenger). They normally throw a code between 44 and 50, and be sure to check under the seat that they're properly plugged into the harness.
If you're new to Durametric and the airbag light is steadily lit, I suspect that you are getting the code and just don't yet know where to look in the software to read it.
This is a source reference. Confirm exact model applicability in the original material.
