USB connection failing with 2N and 1.90

[tjannes]

On july 17th, I last managed to download my divelog to the laptop. Yesterday I tried again, but got a message about "Unrecognised USB device". I have since tried the following:

- reboot OSTC from reset menu
- reset it with magnet
- reset it with magnet while USB was connected

I connected my OSTC to 4 different computers. On one, where I am sure it had never been connected before, it recognised it as an OSTC and installed the driver. Then it recognises two new devices. For the first (forgot what it is) it downloaded the driver online (Win 7 on all machines), the last was the USB-to-COM which gave me a failure. It is my impression that this is the same that fails on the other systems.

I tried 3 different USB cables, one of them being the original one.

Aside from this, it still performs perfectly and can still charge the battery through USB.

What can I do to solve this ?

Best regards,

Thomas

[tjannes]

Since I had to reinstall one of my computers anyway, I waited for all the updates on my Win7 64 bit to be installed, then plugged in the OSTC 2N. Again to be met with "Unrecognised USB device".

Thomas

[kobus]

You need to install 64bit Virtual Com Port Drivers. I use the FTDI ones - available here: http://www.ftdichip.com/Drivers/CDM/CDM ... tified.zip

[tjannes]

In Win7 it is supposed to pick up the drivers automatically I thought. But anyway, it fails before asking for drivers. And even if I install the drivers using the executable file, it still fails.

That's why I wonder if the problem might be physical and if there is anything left I can do with software...

[Hansjoerg]

Hey tjannes,

Though if you say that you were able to download the dives to your PC not so long ago and from your description of the problem, I suspect it rather has something to do with the PC side of things.

Can you get your hands on someone else's 2N? Maybe HW knows someone who has an N2 nearby!?

Alternatively you could install a Virtual Machine on your PC and then install WinXP and see what happens (though this is starting to get rather technical).

Cheers,

Hansjoerg

[tjannes]

Well, I am a computer-technician, so I've tested quite extensively already, but I always hesitate to say "it's broken" until I've tried all possible avenues.

And so, I dusted off the very old XP-laptop I still have lying around. Same error.

Just to be clear:

- this has now been tested on 6 different computers. 4 of them Win 7 64-bit. 1 of them Win 7 32-bit. Now one XP. One of the Win7 64-bits was reinstalled prior to testing.

- on XP the drivers were installed before connecting the OSTC. On some Win7 it was installed, on others I relied on Win7 finding them, as it should do.

- the laptop on which I managed the last download, was even restored to the date before the last export, using System Restore, because I thought Win Update or some other manipulation on my side might have been the cause.

- when I first connect the OSTC, it recognises it as HeinrichsWeikamp OSTC2, then it recognises it as a USB device, then it recognises it as a COM device. It gives me an error for this third part, stating something went wrong. If I look at the device in Device Manager, I get a this device cannot start (code 10) error.

- on any following connection attempt I see "USB device not recognised" and in the Device Manager on my reinstalled Win7 I see "Windows has stopped this device because it has reported problems. (Code 43)"

Is it safe to say my OSTC 2N is broken ? I am willing to test anything, but really think the PC side is not the issue here.

Thomas

[Hansjoerg]

Mate,

I guess your only option is to try out another unit from someone nearby or get one from HW to try out.
Send Matthias a mail and see if he can assist.

If you're anywhere near Switzerland you could try mine.


Cheers,

Hansjoerg

[Paul]

Hi,

I am having the same problem. Windows Vista x86 not recognising the device. I have downloaded the drivers from the website and extracted them as instructed but no joy. Any ideas?

[tjannes]

As I have been away on holiday, I have not further tested. In about a week, I'll be able to see a friend with the same model, we'll test eachothers dive-computers on our PCs and we'll see from there. Depending on the outcome, I'll send a mail for repair or not.

Thomas

[dmainou]

Number of q's.

Which software are you using to download the logbook?

Have you tried a Linux or a mac machine? You don not need any drivers on linux as its part of the kernel.

Have you tried with the 32bit VM within Windoze 64

Try downloading JDiveLog and selecting both the 1.8x and the 1.9x protocol.

Make sure the OSTC is ON when you plug it into the PC and when you launch the log software and when you try to make a connection/download the data.

Change the sleep CF if necessary.

Hope this helps

D

[dmainou]

Also, make sure you install the drivers BEFORE you plug the computer for the first time.

It will save you SO much pain.

D

[heinrichsweikamp]

There is a possibility of a hardware issue, of course. But every unit is tested and updated through this usb port. Maybe the cable?

Cheers,
Matthias

[Andrey]

Hello,
i have the same problem with my 2n.
I tried on my laptop and desktop, but Windows 7 even not to try find drivers.
I install drivers, instal JDiveLog but JDivelog show me error message "The specified com port could not be found".

Any advice?

P.S. When i connected usb cable the 2n charging.

[Andrey]

Andrey Wrote:
-------------------------------------------------------
> Hello,
> i have the same problem with my 2n.
> I tried on my laptop and desktop, but Windows 7
> even not to try find drivers.
> I install drivers, instal JDiveLog but JDivelog
> show me error message "The specified com port
> could not be found".
>
> Any advice?
>
> P.S. When i connected usb cable the 2n charging.

SOLVED

[tjannes]

I think I found the reason as well.... Oxidation Opened it twice to download data, thought I was careful....

[tjannes]

Contact cleaner apparently fixed my issue