74 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHDurametric Communication Problem on K-Line 2
Reported or suspected cause
car (99cab)
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
Suspected cause
0
Reported fixes
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 report identifying a cause
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.
Reported cause
I had the exact same problem with the durametric cable, several emails and data logs later durametric insisted the problem was with my car (99cab).
Leading evidence: 'car (99cab)' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'car (99cab)' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check )' (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 report identifying a cause
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.
Reported cause
Short answer is the problem is with the durametric cable not your car.
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 report identifying a cause
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.
Reported cause
I emailed Durametric and asked for what turned out to the the Gen 2 cable.
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
I have checked the firmware on the cable and it is up to date.
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
I checked the wires only 3 cable are connected to the radio and the car (red, brown and yellow).
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.
74 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 · 1 adjusted by outcome qualification.
8 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
I even was asked by tech support to send it back for checking to which they replied that it worked perfectly.
Has anyone run up against this? I purchased the Durametic cable/software in order to clear the air bag light on my 1999 996. Although it read and communicated with the engine module, it kept giving me a communication message that said basically that I might not have the module available (on all the other modules). I attempted running the software on multiple occasions. After contacting Durametric Tech Support, I received the following:
Thank you for writing. The 996 models use two separate diagnostic busses, called "Kline 1" and "Kline 2".
The engine and tiptronic transmission (if installed) are on Kline 1. All other units reside on Kline 2. If you are unable to access the airbag unit or any other units beyond the engine it is likely that bus is in some way compromised. If the bus is faulty neither Durametric nor the Porsche factory tool will be able to communicate with associated modules.
The diagnostic bus can be compromised in one of several ways: shorted to ground, shorted to battery +, open circuit, or a faulty control module (such as the airbag unit). After market electronics such as a stereo may also have this effect.
You will need to check the Kline 2 bus in your car to determine the cause of the trouble.
Does anyone know how to go about checking this bus? Any help would be appreciated!
I'm not familiar with that problem, but I have had issues with the Durametric on my USB 3.0 ports.
My laptop has both USB 2.0 ports and USB 3.0 (high speed) ports. The Durametric works fine on the USB2.0, but not so much on the 3.0.
Just a thought.
From memory I've seen 4 to 5 similar cases posted but unfortunaely there was never a resolution or OP never came back to update the thread. A couple of cases the dealers/shops were able to read the 2nd K-line withouth issues with their factory scanners.
I had the exact same problem with the durametric cable, several emails and data logs later durametric insisted the problem was with my car (99cab). However the dealer insisted otherwise. A trip to the dealer, $75 and 5 mins later, they insisted everything is fine with my k2 communication line and my air bag light was shut off. Short answer is the problem is with the durametric cable not your car. FYI I tried two separate professional cables, still no luck.
This seems to be right, there are more people that have had success with the durametric cable than not, although I believe it's complete BS durametric won't admit its product won't work on all the vehicles it says it does. The problem falls 100% on their programming or lack there of. I did get them to admit it might be their fault, but they won't come out and directly state as such.
I had the same problem on my brand new durametric. I even was asked by tech support to send it back for checking to which they replied that it worked perfectly. I am an auto electrician and the k line on my car is not compromised in any way. The durametric seems to be the problem. It works perfect on the engine but as soon as you try for another module it dies and has to be closed and reopened. I tried two different laptops also. My car is a very early 98 996 model here in Australia.
My email to Durametric...
Hello,
I have purchased my durametric cable used from a prior porsche 911 owner. The cable is a second generation and I am using durametric version 6.5.1.7. My car is a 1999 911 996 VIN 622773. I am trying to get the cable to read the problems with the airbag module but it fails to initialize. The only modules the durametric cable will read is the engine DME and the tiptronic module. No other module will initialize. I have checked the firmware on the cable and it is up to date. I am using a 1 year old Toshiba laptop running windows 10 and I had it plugged in while running the durametric software. While checking the firmware, the cable did not have any VINs registered on it. Please help me read the airbag module.
Any assistance you can give me will be greatly appreciated.
Thank you,
Durametric's response...
Thank you for contacting Durametric. If the tool is unable to communicate with anything other than the engine and tiptronic units, it is likely the trouble is either with the car or the Durametric cable. In your car, the engine, tiptronic and alarm units all run on the K1 communication bus. All other units reside on the K2 bus.
A faulty control module such as the airbag unit or another bad unit on the K2 bus is capable of bringing the entire bus down. Also, any after-market electronics may have the same affect, such as a radio, GPS, phone, etc... The bus itself may be shorted to ground or the battery positive, or there may be an open circuit preventing communications between the Durametric tool and the bus in your car.
If possible, you will want to check a few things there. If you know anyone else with a Durametric tool, you might try their tool on your car. If you know anyone else with a 986 or 996 Porsche, you might try using your Durametric on their car.
You can also check your K2 bus for trouble. The K2 bus is found on pin 3 of the OBDII connector in your car. Ground pins on that connector are pins 4 & 5. Check pin 3 for any voltage; it should not have battery supply voltage. Also check for continuity to ground; there should be no continuity.
If you have no access to another Durametric tool nor to another 986 / 996 Porsche - and the checks of the K2 bus in your car appear normal - we can provide a return authorization ("RMA") number to have the cable tested here. There is no charge for this except for cost of shipping.
-------------------------------------------------------------------------------
I have not done anything because I have seen on these forums repeatedly the same problem with Durametric and the 1999 996. Durametric does not work on these cars! I will probably sell my durametric cable. Come summer time, I will take my 996 to my Indy mechanic who has PIWIS and have him fix the airbag light.
That seems backwards to me. "K2" is the Keyword 2000 protocol which is an OBD2 protocol and used in a number of vehicles, quite a few are European. Those European (and some USA) vehicles that don't use the KWP2000 use ISO-9141-2. This ignores other vehicles that use PWM or VPW and CAN. (At some point newer vehicles -- probably -- all use CAN.)
As an aside, my 2002 Boxster uses ISO-9141-2, as does my 2003 Turbo, but my 2008 Cayman S used KWP2000.
"K1" I believe refers to the Keyword 1281 protocol, which is an older pre-ODB2 protocol and is used in some vehicles (VW and Audi to name two brands but apprently Porsche too, at least in some model years) for communication with systems other than the engine controller.
I have never written any KWP1281 communication firmware so I can't tell you how it works. (I have a KWP1281 simulator though.)
I do not know if I even have any documentation on it at the office. There appears to be some "good" online documentation but it is in German and what German language skills I possessed years ago have gone away with lack of use.
This thread is very interesting to me. I've considered buying a durametric package (enthusiast) since I got my car ('99 C4) about a year and a half ago. Fortunately, I haven't had the need for it up to this point. It's not that $300 is a crazy amount of money to lay out for a useful tool - in fact, if said product works as advertised, it's a downright bargain. Then again, if said product doesn't work as advertised (as so many software based products don't) it's only natural to feel like you've been ripped off. I won't be ordering a Durametric unless there's some sort of positive resolution to this issue.
** I'd like to see a poll of users with '99 996's who have full functionality of the software
I'm hoping mine will work on my 99 C4, because I have the airbag out right now and had to run the car so the light is on. When I get the steering wheel back and connect it up, I will let you know.
I normally would think that it would work, but considering the C4 had drive by wire vs. a throttle cable and mine is a very late 99 build, I'm optimistic.
My 99 C4 conects to airbag Iff I select 993 as the vehicle, it connects to dme and tiptronic also but sometimes gives the message "module failed to respond, Abs/Psm appears to connect but shows no fault even when I know for sure there is one.
I have verified that my durametric works on my 99 airbag module....but that's because I'm guessing it's a C4 and does have the drive by wire vs. throttle cable, it is probably more like a 2000 vs. a 99.
I've got a 99 C2 and have the same issues as the OP. Tried two different cables and two laptops, all with the same result: it connects to the engine module and nothing else. Very disappointing. I may check the grounding of the pins as described, though at this point I'm inclined to send it back for a refund.
Yesterday I took my car to a local shop and they had no problems connecting to, and resetting, my airbag module with their durametric cable. I guess that's the difference between the professional vs enthusiast model? At any rate, I'm going to send mine back because it's of little use to me if I can only connect to the engine module.
If it is established that it works for Pro cables but not for Enthusiast, Durametric should fess up and exchange the cables for free for 99 owners.
Just sayin ...!
The pro cable does NOT work, I've use two different pro cables and neither would work. So the problem isn't with the pro vs enthusiast cable. The problem is they don't work on the 99, I will say I only tried it on one laptop, I'm going to try on my buddies laptop which is a top of the line and would crush 99% of the desktops out there when compared to computing powered to see if that makes a difference.
Well, the shop yesterday had no issues using their durametric on my 99. With my cable, I tried two laptops and two cables (durametric sent me an extra to try), and it didn't work in any combination (other than the engine module). Needless to say, it's all going back to durametric for a refund.
At least the shop was decent enough to only ask for a 'donation to the coffee fund' for the 5min they spent on it.
I couldn't get them to work on mine, durametric kept saying it was a problem with my car, which I knew there wasn't as it was just in the shop a month prior and they had no trouble scanning it. My solution was to take it to the dealer and within 5 minutes my airbag light was off, $75 lighter I was on my way. As it remains I am durametric free, as I've sold my cable, which coincidently works fine (non 99) to the guy I sold it to.
The OBD connector is equpped with several pins/lines for communication. The most important are the L and K lines, these are serial communication wires. The L line is mostly used for sending an addressed wake-up signal for before starting the communication on the K bus. The Porsche 993 (95-) and 996 have two K lines, on OBD pin 7 and 3. In the 993 these were called K' (K "marked") and K, and in the 996 they are called K1 and K2.
In the 993, pins 3 and 7 are interconnected in the OBD tool in order to communicate with all OBD-enabled units.
This might also be possible in the 996, it could be an idea to try to interconnect pin 3 and 7 if this isn't already done inside the OBD tool. However, I have no experience with this and don't know if this is good or not.
By the way, there is no diagnostic connection to the Litronic headlights. The only control unit that might be a a candidate is the automatic level adjustment circuit, but this is a stand-alone system.
Cheers,
Tore
Hi folks, I posted earlier that I purchased a durametric cable and it would not communicate with the airbag module. I emailed Durametric and they stated there was a problem with my K2 bus.
Well to prove there is nothing wrong with the K2 bus, I just went to my porsche mechanic and he had no problem resetting my airbag module with PIWIS proving there is nothing wrong with the K2 bus. Don't believe Durametric's advice to you that there is something wrong with your car and not their cable.
It is conclusive, Durametric does not work with a 99 C2 996. Don't buy it if you own a '99. I have a durametric for sale if anyone needs one.
Good info. Bummed about the airbag.
Although I have to admit that in true tiger dad fashion I carry my Durametric and surface2 with me in my 99 C2 everywhere I go.
Sorry to hear yours isn't working right. I'm surprised they won't replace just as a good customer support move. Mine works but often gets confused if I cycle the key while the app is running. Also, I don't think they say it in the instructions but using a usb extension cord is a big fail (just doesn't work right).
I've found I get the best customer support when I voice my problem on there Twitter feed. No company wants that kind of exposure. Good luck. Keep us posted, we're listening
I have the durametric pro-version and have a 1999 C2 (march build date) ROW specs and RHD. I was able to clear a fault code in the airbag system that I caused when removing the inner doortrim with side airbag and accidentaly switched the ignition on. I have just double checked and can confirm that my durametric talks to the airbag system. Maybe I'm very lucky?
FWIW, I have a 99' cable wire, my enthusiast edition worked for the airbag light. I was using an old laptop running win 7, I tried my 2in1 with 10 last year and it did not work.
Durametric working with 7 and not 10 happened with both the 996 and ctt.
Ya, I was just going to confirm that I can clear codes and get values on my '99 C2 (3/98 build date)as well. Haven't tried the airbag yet but all else seems to work fine.
Hi guys,
Regarding the first question of this thread, did you found a solution?
Here my issue:
No communication possible with my air-bag module (My mechanic was not able too, with pro cables...)
Air-bag light always ON
Can't lock the door.
And I have battery voltage on pin 3 of the ODB connector (between 3 and 4 and 3 and 5), when ignition ON.
My car is a Boxster 1998.
I disconnected the non-OEM auto radio... but same.
I replaced the SRS (air bag module), same issue.
Anyone could help me to find how to troubleshoot my voltage on Pin 3? or confirm that is not normal on 986? And I am on the right path to solve this air-bag light issue...
Thank you.
You may have to try the dealers. I've seen cases where the cars were not the problem and the dealers were able to read and reset the codes without problems.
Thank you Ahsai.
Currently the Porsche dealer is not close to my home.
And I need to go through the safety check first... to be "legal"... no license plate yet...
It is the reason why I am trying to do it by myself... And, I want to understand too... :-)
According my reading, my best chance is to validate if my auto-radio was the cause, is to use a short circuit detector on the ODB 2 (a VAG-Saver like tester) or use the 1k Ohm method...
This should tell me is I really have a short-circuit (with or with-out the auto-radio).
But I agree that to clear the airbag code I will not be able to do it, without pro cable... or at the dealers.
btw my cheap PIWI cable stop working some weeks ago... perhaps because of this issue... another one is on the way, but if I have still this voltage/short-circuit, I want to be sure before try again and destroy another cable...
My other standard ODB2 reader still works (but can't read air-bag module as expected, then I guess, this one is not trying to read K2 line...)
Any comments are appreciate Ahsai or anyone!
Thank you.
Yann
The airbag is on the second K-line, which is connected to pin 3 of the OBDII port. K-line idles high (bit "1"). When the scanner wants to send a bit "0", it pulls the K-line to ground using an unprotected transistor. If the K-line is shorted to +12v, that will kill the transistor when the scanner tries to pull that 12v to ground.
To test if pin 3 is shorted to the +12v, connect a ~500ohm resistor between pin 3 and +12v, then another 50ohm (5w or hgher) resistor between pin 3 and the ground. Now measure pin 3. If it only has ~1v, your K-line is fine. If it's still at 12v, the K-line is shorted to 12v. Be careful the 50ohm resistor will get hot if the K-lime is shorted to 12v.
My durametric cable never could recognize the airbag module on my 99 C2. I ended up going to my porsche mechanic who has a PIWIS and he reset my airbag light light for 20 Euro. The airbag light has never come back. He said there was nothing wrong with my K2 line as suggested by durametric. All systems in my 996 are functioning normally.
I've had to delete and reinstall the program a few times, after it wouldn't initialize using my fairly new laptop with Win10, and my old laptop with older windows versions. Other than that, I've had no issues with my 99 coupe non-egas.
Engine and Alarm at the only 2 modules that work on my two '99s with early '98 build dates. Contacted Durametric and they acknowledged it was an issue. I've also had to reinstall the software a couple of times on win10 but have had better luck in Win8.1.
I have the Durametric enthusiasts cable ,using it with an old laptop with windows XP .I haven't used the laptop for a couple years ,after doing all the updates and resetting the firewall it worked fine.I am using it on a 02 carrera,I seem to remember the instructions stated to turn the flashers on so the car won't go to "sleep" and it keeps the modules awake on the "99 models .
Hi guys,
Assai, could you confirm:
~500ohm resistor between pin 3 and
pin 16
50ohm resistor between pin 3 and
pin 4
I am following this ref for pin-out:
http://www.cb-racing.com/boxster_OBDii.html
Because I was worry to do something wrong (not sure about pin 16), I did that only:
- Test pin 3(K line 2) and pin 4(ground) ~ 11,5V
- Test pin 7(K line 1) and pin 4(ground) ~ 7 V (This line works fine because I can read it with a cheap ODB2 reader) I just wanted to confirm the value and according what I read here:
http://www.ross-tech.com/vag-com/aftermarket-radio.html
- After connect the 50ohm resistor between pin 3 and pin 4 I got ~< 1V (some mV)
- 50ohm resistor stayed cool. (not hot at all)
Of course everything ingestion ON (when OFF nothing on pin 3)
Then I reconnect the radio to see if I have deferents values. All the same.
I checked the wires only 3 cable are connected to the radio and the car (red, brown and yellow). Others are for speaker and antenna, then my guess is I have few chance that the radio cause issue if not connected on the K-Line... anyway I am not sure.
Then last test will be with the ~500ohm resistor, Assai, could you confirm my previous for pin 16?
Thank you!
Yes, those pins are ok too. Your measurement confirms your pin 3 is NOT shorted to the +12v. If you connect the 500ohm resistor too, you can confirm the line is not shorted to the ground either if it measures about 1v.
I did it.
- Ignition OFF.
- Radio connected.
- With 2 resistors connected:
~500ohm resistor between pin 3 and pin 16
50ohm resistor between pin 3 and pin 4
- I have 1v between pin 3 and pin 4. No resistors became hot.
Then that concludes your test, Ahsai, and I don't have short-circuit on K line 2.
Not sure I have to do the test ignition ON. But looks like my line is OK.
Then, my mechanic probably don't have the good cable to read my old 986... despite what he told me...
Then, I will have to find a way to have good cable or go to the dealer.
Thank you Ahsai again for this exercise, I hope my notes could be useful for someone else too.
I will let you know when I will solve my air-bag light issue... and how...
Yann
Looks like your pin 3 K-line is fine so it must be the cable. Durametric is KNOWN not to be able to communicate with that K-line on
some
earlier models. It's a well known issue.
I am glad I decided to invest in piwis 1 & 2. If anyone on this thread is in the NH, MA, ME area I am happy to plug in to confirm your Durametric is at fault. Feel free to PM me.
Fronkenstein
Hi Guys,
Just to let you know that I confirmed with the ignition ON.
Same voltage (1v), then my K line 2 is definitively in good shape.
Now the journey continue... to turn this air bag light off...
My mechanic call me back, he got new readers...
I will perhaps let him a chance ... before I do a more radical solution to resolve my air bag light issue...
Thank you.
Hi Guys,
Update:
My mechanic was finally able to read the airbag module. He did not really know why. Perhaps because I changed the SRS.
Anyway, he told me he cleared errors codes, give me my safety check, and chargerged me, of course :-)
Cleared code were:
Air bag light is on (01), Ignition driver (21), ignition circuit side airbag driver (29), Ignition circuit airbag (31), Driver belt buckle fault (45), Passenger belt bucket fault (49).
I dont why all these codes, perhaps because of my "new" used SRS module?
But the thing is: the air light is again ON...! :evil grin:
Then he cleared it, but did not check after... if the light will come back on.
This story is not done and I don't know which code is causing the light ON... return to the beginning. (except that I have my safety check :-).
I will see if my chinese cheap kiwis cable will help me to have codes...
But no error code with my standard ODB2 reader.
^^^ this person. I must track them down and kiss them!
So it went something like this. I emailed Durametric and asked for what turned out to the the Gen 2 cable. Instead they sent me a beta firmware update for my existing cable. I tried the update, no Bueno. They then told me it must be my car. I reminded them that I have two identical cars and it didn't work on either of them.
So again o asked for a Gen2 cable. So they sent me a new cable. I tried it, no Bueno. So i asked them if they had just sent me another new Gen3 cable? "Umm, yes. But we are sure it is a problem with your car." This is where I got very frustrated and informed reminded them that I had two cars and an entire thread of posts from people that were having no the same issue and that you had blamed it on their car.
OK. We'll send you a Gen2 cable. And it worked. It worked it worked it worked. I now have access to ALL modules, including air bags. Yippee!
When I get back in town I'm supposed to pull log files for both cables and send them the results. Hopefully they will be able to figure out the issue and fix the Gen3 with a legitimate firmware update. Stay tuned.
Glad it worked for you, but no way am I giving them any more business. They must clearly know the issues with the '99 and yet they kept blaming it on the car despite all evidence to the contrary. They wasted a lot of my time and $ trying to get that issue sorted.
I agree with everything you are saying. But I am going to ignore it until tomorrow and continue enjoying the fact that it finally works. Lol.
But in all seriousness, the way they have handled it is really lame.
FYI guys, I finally bought a
real
Duramtetric cable on eBay.
And now, I can read correctly everything. What a pleasure! Then that confirm that my lines were OK, and my mechanic guys not as good with Porsche as he said... And Chinese fake Porsche cables very bad...
Then here the error code from the airbag module (I have only this code), related to my Airbag light issue, I guess:
45
Belt buckle, driver
Then I am looking to buy a new belt buckle... I am hesitate to buy a used one... but as it is for safety and it is know that the 986 have connection issue with the buckle... I think I will go with a brand new one.
I hope this will finally clear this airbag light! :-)
That's me (aka "particlewave"). You can have a kiss, but I don't do tongue on the first date.
I'm glad Durametric is acknowledging this more, but they need to come right out and say it. Maybe make model/year entry specific to the ordering process so that they can provide the appropriate cable/firmware.
FYI, I changed the driver seat belt buckle. (with a used one)
And I cleared airbag codes with Durametric cable.
AirBag light gone!!! Finally!
tested multiple time, still OK, no more error code.
This is the end of my journey to resolve this airbag light!
Wish i had found this thread before i started pulling my hair out trying to get my durametric to work on my 99 996 CAB. Can connect fine to the tiptronic and DME but nothing else, so as above K1 ok, K2 not ok.
Worked fine on PIWIS 2, cable worked on a 996 previously a few years back so seems like i am out of luck.
No one worked out a hack for the cable to get it too work?
This is a source reference. Confirm exact model applicability in the original material.