JDiveLog not seeing my OSTC

[Regthing]

Hello.
Sorry if this has been covered already but I can't seem to get JDive to see my OSTC.

I've not dived it yet so I don't have anything to download but I'm expecting to be able to change CFs through JDive.

The error I'm getting is that it can't find the port. I've downloaded and I'm running Windows XP with Oracle Java RTE 5.0 (I believe this is SUN). I've installed the Virtual Com Port driver and set up the protocol to Auto but still nothing? The JDive manual does not make any reference to the OSTC.

Cheers.
Scott.

[divinglog]

Hi Scott

You can try to use Diving Log. With the free demo you can configure the CF without limitations.

Cheers,
Sven

[heinrichsweikamp]

Hi Scott,

> port. I've downloaded and I'm running Windows XP
> with Oracle Java RTE 5.0 (I believe this is SUN).
> I've installed the Virtual Com Port driver and set
> up the protocol to Auto but still nothing? The
> JDive manual does not make any reference to the
> OSTC.

We had some discussions about JDiveLog installation routines in our forum:

http://www.heinrichsweikamp.com/read.php?2,3026
http://www.heinrichsweikamp.com/read.php?2,3300

As you are using Windows XP, you need to have the USB driver installed, see: http://www.ftdichip.com/Drivers/VCP.htm

Windows XP does not automatically install the driver (Windows 7 does).

regards,
Matthias

[Regthing]

Hi Matthias.
When I fist plugged the OSTC into my PC it did recognise it and installed some drivers, then told me it was ready to use.

I then tried JDive setting the 'Settings -> Divecomputer -> Protocol -> Auto' but still I got the message saying that the port wasn't set.

Restarted the PC, same again.

Installed the usb driver from ftdichip, restarted the PC and still the same.

[heinrichsweikamp]

Find out which virtual COM port the OSTC has (With the windows device manager) and select this port.

Try Protocol "1.50 - 1.70" and don't forget to turn the unit on.

Regards,
Matthias

[Regthing]

I'm not seeing it in device manager. Had a look through the ftdi install guide and the driver selected by windows may be taking precedence over the installed ftdi driver and preventing it from being properly recognised.

Apparently when the search for driver window appear you should direct it to the ftdi driver and not allow windows to search for an alternative. The removal of the windows driver looks quite involved as they no longer supply a removal tool

[heinrichsweikamp]

"FTCLEAN" can be downloaded here: http://www.ftdichip.com/Support/Utilities.htm

Cheers,
Matthias