Bootloader

[Patrik]

Hi!

Having problems connecting to the OSTC Mk.2 from both Windows XP and Ubuntu 9.10. Both machines recognise the computer and finds the comport but when using the bootloader in windows it just says Searching for PIC.... Not found (have tried to go through all com ports several times and using different USB ports). I have also tried the JDiveLog without success, "No protocol found".

In Linux I tried to use the JDiveLog only, but it says Protocol not set. If I change the version from "auto" to the latest version (-1.44 I believe is the latest you can choose) then the program hangs or crashes. Tried it both as root and user.

Any thoughts?

[Patrik]

I am able to update the firmware, but still have problems with transfering logs and stuff.

[heinrichsweikamp]

Hi,

Set the protocol version to 1.44 manually, auto seems to be faulty. With Jdivelog 2.13 and OSTC Mk.2 firmware 1.60 I can download the dives without problems. The new color setting custom functions are not yet supported from JDivelog but this will be available in the future.

regards,
Matthias

[Patrik]

I got it to work with the new stable firmware (1.6), but I need to tap the load and save button a few times and get an error between tries before it actually loads or saves the settings. Will test if it works with my Linux when I get home, that is more important then windows Downloading the logs works every time.

I think I was just too slow when I rebooted the computer when connecting with the bootloader before.

Cheers
Patrik

[Jan_Arild]

Having problems connecting the OSTC Mk.2 ver 1.60 from Windows XP Jdivelog 2.13.
PC finds new device and install, but canot download the dive from OSTC.

In Jdivelog, going to File/downoad from divecomputer, gets error message "Transfer failed, Driver not set".

Jan

[heinrichsweikamp]

Hallo Jan,

Check "File" -> "Settings" -> "Divecomputer" and select OSTC with protocol "OSTC 1.19 - 1.44" (Works better then "Auto"). Select correct COM port, sometimes the additional RXTX library is required.

Regards,
Matthias

[Jan_Arild]

Thanks Matthias.
Config is made, but do not get any comports to select from?
Com port scrolldown menu is blank.

[Stephen McMullan]

I'm having the same issues myself with Windows XP and Ubuntu 10.04. Tried bootloader on windows after installing the drivers and JDivelog on ubuntu with similar experience as above. I work as pro software engineer so not a complete dummy

Great service by the way - was about to report a bug and noticed its already fixed in next beta.

Great product - have done three CCR trimix dives so far since purchase 70m, 80m and 65m and compares well against Inspiration Vision computer. Excellent in the water - changing set points, dils, bailout to OC and back again etc. Well done.

Stephen

[heinrichsweikamp]

Hello,

When the OSTC does not show up in the COM ports the problem is the missing driver, either the RXTX Libary (Which requires administrator rights to install) or the FDTI driver. We have MAC OSX, Ubuntu, Windows XP and 7 here with working OSTC connection. So, it's possible

regards,
Matthias

[Jan_Arild]

I'm also sure it's posible Matthias

Tonight i installed the FDTI driver ver. 2.06.02 for the desired com port according to installation guide at http://www.ftdichip.com/Drivers/VCP.htm but still just blank com selection menu.

I also already got a com port configurated for a RS232-USB converter from before wich also use a FTDI driver.

Any ideas what to do?
Whats the deal with RXTX Libary ?

Jan

[Jan_Arild]

Finally got the communication working.
After upgrading to Jdive 2.14 and setting file/settings/divecomputer to driver: OSTC, Com port: highest number, Protocol version: OSTC Mk.2 1.50-1.70.

Great !

[Stephen McMullan]

Likewise, I was able to update the firmware with the bootloader (my personal stupidity was responsible after all).

I was able to download the dive profiles with the latest version of JDiveLog

Nice one. Totally happy now.