Durametric Won't Connect
 

I did a google search, but none of the results addressed my issue.

I had a Gen1 cable and version 5 of the software, both of which worked fine. I sold that cable and bought a used Gen2.

Now the Gen2 Cable and latest version of the software won't connect to anything but the alarm module.
Laptop specs meet and exceed recommendations, tried it with the power adapter plugged in, tried reseating the cable, restarting computer, checked drivers...all good.

Any ideas before I contact Durametric?

Last one...

Just tried it on a different laptop with better specs and got the same result...program will not connect to any modules (except alarm)!

I would contact Durametric. I purchased a used cable that had a similar issue. They were helpful, they reset the cable by sending me a file if I recall correctly. It was a few years ago, so forgive my memory. Said they would only do this once. I purchased the cable from someone on eBay that said it only used one VIN. When it wouldn't work I thought I bought a counterfeit so I contacted Durametric and they verified it was a legitimate cable. After I told them how I got the cable they told me they could reset it but only once. Now it works fine.

Particlewave: I had a similar problem with mine. I bought a new Durametric from Pelican about 6 months ago. Was driving me crazy. It would occasionally connect and then fail. I sent back to Durametric for analysis, they found nothing wrong with the one I had but said they had some issues with some from another batch. Long story short, I finally found that the .NET Framework 3.5 sp1, they said it needed did not contain .Net Framework 2.0. I downloaded the 2.0 and it has been working fine since. Good Luck

Thanks for the suggestions. :)
I ran some updates on the laptop last night and will try again shortly. My guess is that I'll have to contact Durametric.

Edit: the windows updates didn't solve the issue.

Just a thought, the USB ports on my Laptop have multiple standards ie USB3 and USB2 which can operate at different speeds.

You might want to try all your USB ports just on the outside chance that some ports may stand a better chance of working than others.

Particlewave,

Did you get this resolved? I am having issues with my alarm and ran the durametric last night and although I don't get the error you are seeing, it appears that my durametric is not communicating.

Here is a pic of what I see with the alarm module.

Attachment 20117

Attachment 20118

I noticed that I did not have .NET 2.0 downloaded so I am now downloading it and will try again.

EDIT - The install said I already had it so now I am at a loss.

John

Got a new durametric last night installed and it wouldn't initially work. I had to uninstall and then re-install to get it working. I think it had to do with the drivers....

I've been communicating with Durametric all week and unfortunately, still no luck. :(

A couple things to note:
1) The first time I connected the cable to the computer, I got a message stating that it required a firmware update, which it did on its own immediately.

2) One time when I connected the cable, it auto-detected my car and ECU. However, I could still not connect to the modules.

3) One time the cars info showed up on the ECU module (VIN, ignition range 1/2, etc).

The above leads me to believe that the cable and software do work, but that they don't work consistently. This could be a software issue or a connection issue, so I've checked all my connections and everything looks good.

I got it to work finally and now have a bunch of alarm faults to figure out.

Nice customer service :cool:
:dance::dance::dance:

The alarm fault screen worked once. :( It now shows no errors again.

This sounds a lot like the behavior I was experiencing. The DME showed up once, now nothing. The alarm module will read, but only intermittently.
What OS are you using? CPU and RAM?

Windows 7 - 64 bit
8GB Ram
i7 processor

I am not sure if other functions are having this problem but I saw it on Alarm for sure.

I sent mine in to Durametric today, so I will report back when I hear something from them (probably middle of next week).

Durametric has had my cable for 4 days and still no response from them (was quoted 1-2 days). :(

I'm not getting impatient and I really appreciate their help, the suspense is just killing me! :eek:

Durametric found nothing wrong with the cable...not really sure where to go from here. I guess I'll have a cable for sale soon. :(

They found nothing wrong with mine also. They sent a new one that worked no better. When I tried after free upgrade to windows 10 the .Net framework was identified, installed and now works. Downside is Windows 10.

How do you do this? am not a computer wizard, but I could figure this out with some help. I am having the same problems connects to engine, but not airbag?

Krieger: If your Durametric cable is able to auto select your DME then your .Net framework version is likely fine. Basically this is language that allows the application to run. Do you have a seatbelt fault? I believe this would prevent access to the airbag.

Mine had .net 4.2 or something, so I deleted that and got it back to 3.5, but that did not fix the issue. I can't install anything previous to 3.5 because it's a part of Windows 7.

It does not auto-detect DME. :(

First, .Net Framework isn't part of normal Windows updates unless it's already installed. So, Install .Net Framework 2.0 and I guess 3.5 and 3.5 SP1. Or start with 2.0 and 3.5, then run Windows updates to get the service packs.

.Net 2.0 x64 (unsure if you'll need the 32-bit version...you're running a 64-bit OS - which honestly could be part of the problem, see below.)
.Net 3.5
.Net 3.5 SP1 (these are both 32-bit)

Like I said above, a lot of OBDII software wasn't designed for 64-bit OS's and may or may not have 64-bit drivers, I haven't gotten my Durametric yet. If you have an older laptop around, I'd try that. You're both running mid-to-high-end machines that are more than capable of running the software, but could possibly be *too advanced*, depending on the software developer.

edit: per their system requirements, your 64-bit-ness shouldn't be a problem, but you'll want to verify that you have the .Net Framework. I'd try an older laptop if all else fails...not a newer one.

My garage computer is a Dell e6400 that was previously running a 32 bit windows 7 OS with the .Net framework 3.5sp1 which Durametric claims is not required in Windows 7. My Durametric ver 6.5 would occasionally auto detect but was limited and would soon fail. According to Durametric windows 7 32 and 64 bit are compatible. I spent a lot of time going through the computer running diagnostics and sent cable back for testing, nothing found, however they replaced the cable. After a couple months of frustration in a fit I wiped the HD clean and installed the free Windows 10. So long DELL. Hooked DM cable up and a pop up window reported I needed .Net Framework 2.0. Installed and I now have a working cable. Wonder if I would have had as much enjoyment if I had simply used my MAC!!

Without running a VM (which can introduce many problems), a Mac is not the best computer for this kind of work, and I say this as an avid Mac user of 20+ years. My garage computer is a Dell Latitude D620 dual booting Windows XP and Windows 7. It was cheap (free, actually) and I don't care if it gets maimed by a tool or run over.

Had Win 10 not worked on my computer it was going to get maimed AND run over!!!:o

Downloading the free Windows 10 upgrade now. I hope that fixes it.

I think what he's saying is that .Net Framework 2.0 was the solution to the problem. No reason to install the privacy nightmare that is Windows 10.

You can't install .net 2.0 on a Windows 7 PC.
Windows 7 comes with .net 3.5. If you try to install 2.0, you'll get an error since you already have 3.5.

Try this. It's the 32-bit version, but it does install (which I just verified, see screenshot) and may be what's needed. If not, uninstall if you wish.

I have the same connection issue with a Durametric Cable. I had a vague memory of someone mentioning the cable not seating well, which caused some issue.... I never found the inormation when it became relevant. I remember it was mentiond that little grinding on the cables connection helped it seat better.

Instead, I sent mine to Durametric, it passed their tests. As an IT guy, I did a fresh build with a suitable laptop, stepped through various versions of .net - testing functionanlity at each point. Durametric had reported timing issue with some USB version - i used a known good chip version. Never had success.

Grounding issues seems to be related to many troublehooting tips/suggestions on Durametrics website. Hearing that after market electronics can cause grounding issues the original radio was installed, the on board radar detector removed, even disconnected the IMS Guardian. Still no Joy.

One day, the ODBD connector from under the dash was removed and the Durametric plugged directly into it. It all worked. Mounted the ODBD connector back into the dash - and it never connected again. Even when removing the connector from the dash a second time.

My next step will be ensuring that my cable is seating properly in the ODBD connector. I have a note that mentions one of the ODBD pins can cause connection problems if not seated well.

I do have a seat belt fault. I had the seat out and figured it would be easy to reset. How do you reset it? I just figured in the Durametric it was in the airbag file.

Oh shiat! I just plugged in cord to my computer (not car). I ASSumed seat memory file in Durametric was for eletric seats that had a memory position for adjusting seats to the drivers desired position...Okay not a lot of time has past since my last post. My brain is mostly functional sometimes

Okay, I gave it a try again. I can connect to the Engine and the alarm, but I get the connection error "unable to connect to this module" when I try to connect to the ABS, Airbag, A/C and Seat Memory. I try a different usb port in the computer and the same results. My Boxster is a 99, so I didn't try parking assist or xenon.

I've got that. Your screenshot looks just like mine. :confused:

The Windows 10 install failed. Had to do a Windows 7 repair, so now I'm back to square one. I tried running the software on 2 older desktops with no luck (Durametric 6 failed to open after install).
Trying for the Windows 10 update again. Not sure what else to do. I've tried every computer I own.

I guess I'll check my port as a last resort, but the generation 1 Durametric cable and OBDII readers work fine...

I finally got Windows 10 downloaded and installed, hoping that would fix something. No change.

I read on rennlist that others were having similar issues and it seemed to be primarily with '99s. Looks like it's probably a software issue.

http://rennlist.com/forums/996-forum/915821-durametric-communication-problem-on-k-line-2-a.html

Well just for data my build date is 4/98.

..................

I know how you feel. I may have just been lucky with mine, like you I was ready to run it over. If I was closer I'd connect to my computer just to determine it could work. Hope the new laptop works for you, I tried the same thing with no luck. Obviously my frustration level was at max boil to take a perfect functioning Dell running Win 7 and in a final act of desperation Install Win 10! Now it might as well be an ACER. But it did work. Good Luck

If you go the Chinese knock-off Durametric, you'll need a computer running XP. It's possible that it'll run okay on Windows 7 32-bit, but it definitely won't run on anything 64-bit. Just an FYI.