forum.heinrichsweikamp.com

The new Version of JDiveLog is now online: http://www.jdivelog.org/ - it supports the new logbook format and new Custom Functions.

In time for the next stable...

regards,
Matthias

Sorry to say Matthias, but there seems to be something wrong still. My last 4 dives will not get imported, I'm quite sure I did not change the setpoint in them (at least not in all 4 dives). Checking the internal logbook I can clearly see, that the unit hangs for around 5 seconds after displaying these first 4 dives in the overview list before showing the 5th and Exit. Any ideas? I did not have the abibilty to test this with divinglog yet. Anybody interested in getting a dump for analyzing?

Thx,
Jan

@ Solodiver:

I found the same behaviour,the last 3 dives didn't get imported.after a couple of attempts I tried to do the obvious and looked at the settings.Simply changing in Settings>Divecomputer>Firmware to OSTC Mk2 1.9x- everything worked as supposed.Well,the dives are being imported,although the depth differs by 1something meter on 30 m dives,I guess it is due to salinity set to 1.04 on OSTC.The internal logbook lags a little after displaying the dives made with 1.93 beta,that i would suppose to be due to to the older dives having been recalculated from 1.90 stable(the old format).

Good dives,
Richard
OSTC MK2 385

Sorry for typo,of course protocol,not firmware.
It's kinda late.

Richard

OSTC MK2 385

Oh dear, sorry guys. The thing is, I got a couple of (older) dives imported in the same session so I didn't thought it could be something like this.

So, does this mean, the earlier dives stored in the logbook have a different format than the newer ones?

Thx,
Jan

Hi,

The format structure is the same, but there is more data recorded in the header (GF settings, etc.) and more profiles stored (CNS, GF).
All software should be able to read and interpret both old and new binary formats (once updated).

JeanDo Wrote:
> All software should be able to read and interpret
> both old and new binary formats (once updated).

And JDiveLog does exactly that. When set to protocol "1.91-x" (Settings -> Divecomputer) JDiveLog 2.16 imports dives in the new and old format. The protocol is downwards compatible.

Regards,
Matthias

I also can't import dives with that version of Jdivelog. My MK2 is under french firmware 1.90, PC is under Linux 64bits (RxTx is fine).
When I set the transfer protocol to 1.91 it starts to transfer datas (blue led is on) but stops with a Comm Timeout message. Same behaviour under WinXP 32bits.
I'm going to report this to Pascal Pellmont

Stephane Wrote:
-------------------------------------------------------
> I also can't import dives with that version of
> Jdivelog. My MK2 is under french firmware 1.90, PC
> is under Linux 64bits (RxTx is fine).
> When I set the transfer protocol to 1.91 it starts
> to transfer datas (blue led is on) but stops with
> a Comm Timeout message. Same behaviour under WinXP
> 32bits.

Ok, it's a bit more complicated:
- Dives made with the 1.90 but downloaded when firmware 1.91 or later is installed on OSTC will be imported fine with protocol setting 1.91-X
- When there is V1.90 installed on the OSTC you need to select 1.90-x

Regards,
Matthias

Thank you Matthias.
Result is the same: no dives imported. But I don't have the timeout message anymore!

OK, I found where the problem is: Jdivelog doesn't like mixes with low oxygen.

[pre]
Exception in thread "Thread-4" java.lang.IllegalArgumentException: oxygenPercent is not a valid Percentage value '7'
at net.sf.jdivelog.ci.ostc.OSTCMix.(Unknown Source)
at net.sf.jdivelog.ci.ostc.OSTCProtocol100801Mk2.parseSettings(Unknown Source)
at net.sf.jdivelog.ci.ostc.OSTCProtocol080121.parseAll(Unknown Source)
at net.sf.jdivelog.ci.ostc.AbstractOSTCProtocol.download(Unknown Source)
at net.sf.jdivelog.ci.OSTCInterface.transfer(Unknown Source)
at net.sf.jdivelog.gui.MainWindow$11.run(Unknown Source)

[/pre]

Diluent was Tx7/72 for a 117m CCR dive.

Stephane Wrote:
-------------------------------------------------------
> OK, I found where the problem is: Jdivelog doesn't
> like mixes with low oxygen.



Thx Stephane for figuring this out,
Jan