forum.heinrichsweikamp.com

I'm having trouble downloading dives from the OSTC 2n to JDiveLog 2.17 since upgrading to v2.50 firmware (I think). Is it some problem with the protocol version in JDiveLog?

Thanks, Stephen

your configuration ?

Check -> Settings -> Divecomputer -> Protocol

Cheers,
Matthias

It has to look like this:
[img]file.php?2,file=232,filename=JdiveLogCo ... ration.jpg[/img]

Though the com port may vary.

Thanks guys. Sorry I did not provide more detail. I expected just to be told "yeah protocol mismatch - wait for next version of JDiveLog" but that looks not to be the case.

I'll provide more details this evening when I try again.

I am confident that I have the COM port set correctly and the protocol in JDiveLog is set as shown in the screenshot above.

When I attempt to download the dives, the screen on the OSTC changes and indicates that it is going through the process of handshaking and downloading the dives but nothing is recorded in my JDiveLog logbook.

I did two nice dives last weekend and they do not appear.

I'll upload some screenshots later.

Thanks again.

In this case definatly a jdivelog issue, without a question...
...really can't help as I don't Mac.
:S

smcmullan Wrote:
-------------------------------------------------------
> When I attempt to download the dives, the screen
> on the OSTC changes and indicates that it is going
> through the process of handshaking and downloading
> the dives but nothing is recorded in my JDiveLog
> logbook.

After the handshake-stuff - is there a window popping up asking you which dives (all, single, group) you want to import? Did you choose then the new dives?

That's the problem. No, nothing appears in JDiveLog asking me to import the new dives.

I'm using Windows 7 by the way but if I was to hazard a guess I'd say it was independent of the OS and is rather something between JDiveLog and OSTC. I'll check the clocks on the laptop and dive computer later to see if there is some mismatch or something also.

If all else fails I'll try re-installing JDiveLog and the drivers and try with the new beta version firmware

did you try to test with Diving Log ?
just to test connections :
if Diving Log see your OSTC and import log (just 10 dives with free licence), your windows driver is OK.

other : Did you install RTX with Jdivelog ?

This is some kind of protocol settings issue (Most likely). Try importing the dives into a new (fresh) logbook. With which firmware were the dives made?

Between 2.50 and the new beta are no changes in the protocol. Updating won't make a difference here.

regards,
Matthias

dohhh for heavens sake if you run win7 then install diving log and see if it works with that.

No idea how I thought you were using Mac...

Or just update Java JRE?

I finally figured it out.

JDiveLog didn't like my active gas (CCR diluent) of 7/75

Am having the same problem with v2.50 on mac with latest Jdive and no strange active gasses. Starting to get annoying as the dives pile up!

Ah ha! Reset CFs deco etc and undated fine, seems to be somethings strange in there somewhere.

Hope this helps!

Fraser