forum.heinrichsweikamp.com

Solved
My comuter FTI driver was lost some while back.
Reinstalled, then COM 9 was avelible by USB again, the V2.01 became avelible in Settings -> Divecomputer, and download was sucessful.

Also madae an up grade V2.21 all good

Thanks Matthias.

Matthias
You may have a point.
"Settings -> Divecomputer" is protocol version OSTC Mk2 1.50-1.70. Divecomputer is upgraded to 1.90 i think, will check this tonight.

By the way, after upgrade to 1.90? I really miss the ability to be able to reset the stopwach without the need of going into the menu.

Hi scubatinoo.
This is exactly what I do, but dives made after 12. feb 2012 will not show in the new window. Even if I can se them directly at the OSTC.

Checked date and time on the computer and on the dives who will not import, all looks good.
Last dive which uploads to the PC is made 12. feb 2012, the next dive later same day and on will not upload.

I'm using JDiveLog 2.16 to download from OSTC firmware 2.01.

Connection to the divecomputer works and I'm also able to do setup. When trying to download dives, latest 18 dives do not show in the PC import window, only previus dives which is already imported show.

Ideas anyone?

When checking my PC for correct com, OSTC is com9, in the Bootloader I can only choose form com1-4.

Is there a way around this?

Hi Matthias
From what I'm understand I use Bootloader V1.9.5
But when checking PIC I got error, see attach

Nope, still no go.. the OSTC screen says

Buliding MD2 harse
Please wait....

Then black screen and orange led blinking only

Hi Matthias, you are correct.
Now new error

Connected to \\.\COM3 at 115200
HEX: 0 min old, INHX32,18Fcode+cfg, total=81556 bytes.
Searching for PIC ...Not found,
ERROR!

I did the following:
-Installed bootloader V1
-Downloaded HEX file ver 2.01 to lockal directory
-Choose HEX file ver 2.01 in the bootloader file dialog: "Browse"
-Choose COM-Port 3 in the bootloader
-OSTC Mk.2 Reset Menu, choose "Reboot OSTC"
-Pressed "write" at the bootloader

OSTC returned to ...

Great, I will give it a go

I will need to opgrade from ver 1.7

From what I understand I need to first upgrade to ver1.8, where is this avelible for download?

Second, I will be able to upgrade directly from ver 1.8 to ver2.01 by using Botloader V2.

Jan

How do you do that?

Instaled ver.1.70.
In dive mode, active gases is still not taken in account to calculate the decompression forecast.

Instaled ver.1.70 stable and noticed ther is still no easy way of reseting the stopwatch. Only way is to go into the menue twice!

This will be my request for future changes.

Serial No.835 is displayed in the unitdisplay.
Serial No.832 is displayed in JDivelog 2.14/OSTC settings, what is corect?

Jan

Is there a complete list available of changes made or added in 1.70 Stable.

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 !

Anyone else getting an "Error" message when trying to install JDiveLog 2.14

Made anothe install without the RXTX Libary and everything whent well. But I think I got the same problem as "Sepp", can you please write in English.

Jan

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 ...

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

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

Modified Iphone screenprotector works fine, and easy to purchase.

I think your depth maybe to shallow for GF to make anny affect.

Jan

Simple is great!
If you do demanding dives you do not want a computer flashing in different colors and biping every other minute giving some mystique code.

Information already given in the display do not need an alarm.
My personal opinion only.