forum.heinrichsweikamp.com

I'm not able to import my last dive into jdivelog-2.15. I did not have any problems before. I had 2 dives which had not been importet while 1.88beta was installed - I only did get the second last one to be imported. Also after updating to 1.90 the last dive is not listed while importing. Changing the protocol used by jdivelog did not show any success.

Any ideas?

This could work.


Create a brand new log within Jdivelog

Import your dives, then export those two to the original one.

Will try, the reason I'm writing is more for reporting issues...

Hey Jan,

I was thinking about your issue. When you press the synch button a pop up appears with the list of downloadable dives. If you want to re download any dive simply click on it to mark it for download as well.

D

It is not in the list, will do some tests and post a pic....

See attached image for better explanation. This is tested with different computers running jdivelog-2.15 starting a whole new project. The last dive in the log book seems not to be included in the data transfer.

After doing some more dives, this specific dive is still not appearing in the download list, all dives before and afterwards are shown. It is just be visible in the internal log book but seems not be transfered to external devices....

Is there anyone interessted in this issue as long as this dive is still in my internal logbook?

I would be interested if Diving Log does download this dive? If not, it is likely a OSTC logbook issue, if it does, it is likely a JDiveLog issue. It would help identifying this problem.

Solodiver Wrote:
-------------------------------------------------------
> Is there anyone interessted in this issue as long
> as this dive is still in my internal logbook?

if you can send binary dump of the data to me, then i might
try to take a look if the the dive is visible with
my parser, which i wrote some time ago in Python.

Hi Solodiver,

> Is there anyone interessted in this issue as long as
> this dive is still in my internal logbook?

i am interested in the Divedata as Testfile for my actual Logbook Project. Can you extract the three memoryareas?
If not, send me an email and i send you a program (Windows) to extract them.
My emailadress is robert.angermayr@freenet.de.

best regards
rob

Is there any way to get the dump on a linux based computer? Rob, I'll send you a PM anyway and try to use a friends box to get the dump. I'll also try to get a copy of divinglog running there....

I managed to find someone who can afford to buy a licence from this Redmond based company. Dump sent to Rob already. wrobell - if you are also interessted in the data drop me a PM at derjan@sonnenkinder.org.

I figured out that the dive is also not visible in jdivelog running on Windows but within Diving Log 5.0. So this migth be an issue with jdivelog but there must be something different in this specific dive. Maybe Rob can figure it out...

Interessting news for me is that DivingLog is able to import dives from this crappy Shearwater desktop application. Is there any documentation on this freely available? I would like to see this in jdivelog (or any other app running on Linux) too. It would be even better to get the data directly out of the SW Predator preventing one from using the SW Desktop...

Thx,
Jan

Hi Jan

Good to hear you get this dive with Diving Log, so it is probably a JDiveLog issue and not an issue with the OSTC logbook memory. You can export that dive to UDCF to import it into JDiveLog, if you want.

The Shearwater desktop application uses a SQLite database, which can be opened with any SQLite viewer. It should be possible to add an import to JDiveLog.

Sven

Solodiver Wrote:
-------------------------------------------------------
> Is there any way to get the dump on a linux based
> computer?

you might use my application - kenozooid, which is still
in development mode and requires to install a bit of
dependencies...

http://git.savannah.gnu.org/cgit/kenozooid.git

regards,

w

I looked into Solodiver's data.

Each sample might have an event byte and one
of the samples has event byte set to 0x60,
which means that 5th and 6th bits are set.

Looking at pate 2 of 12th version of OSTC Interface document

Bit4: Manual Gas Set („Gas 6”)
Bit5: Gas Change (Gas1-5)
Bit6: unused
Bit7: unused

What is the 6th bit used for at the moment?

I sent the question to info@heinrichsweikamp.com as well.


Some more information:

sample number of the dive = 874
depth = 6.30m
profile flag byte = 0x83
size of data (see below) = 3
data: 0x60 0x04 0x78 (event byte, gas number, ???)

wrobell Wrote:
-------------------------------------------------------
> I looked into Solodiver's data.
> Bit4: Manual Gas Set („Gas 6”)
> Bit5: Gas Change (Gas1-5)
> Bit6: unused
> Bit7: unused
> What is the 6th bit used for at the moment?

SetPoint change.

> sample number of the dive = 874
> depth = 6.30m
> profile flag byte = 0x83
> size of data (see below) = 3
> data: 0x60 0x04 0x78 (event byte, gas number, ???)

SetPoint change to .120 -> 1.2bar

Cheers,
Matthias

heinrichsweikamp Wrote:
> SetPoint change to .120 -> 1.2bar

So the SetPoint is already included in the logged and transferd data?
In which firmware release has this been added? I do not change the SetPoint quite often (not in every dive, the MK2 is "just" my backup unit) but have done this in the past also where I did not have a problem afterwards. Would be nice to see this in jdivelog some day...

Thx Wrobell for your research

wrobell Wrote:
> you might use my application - kenozooid, which is
> still
> in development mode and requires to install a bit
> of
> dependencies...

Any help with the dependencies?

kenozooid $ bin/kz
Traceback (most recent call last):
File "bin/kz", line 25, in
from kenozooid.cli import ArgumentError, add_commands
ImportError: No module named kenozooid.cli

I can't find any module called kenozooid.cli in the checkout...

What is the purpose of your project? Is there any way to support a shearwater predator as well (native or at least the SQLLite based log format from their windows application)?

Solodiver Wrote:
-------------------------------------------------------
> wrobell Wrote:
> > you might use my application - kenozooid, which
> is
> > still
> > in development mode and requires to install a
> bit
> > of
> > dependencies...
>
> Any help with the dependencies?
>
> kenozooid $ bin/kz
> Traceback (most recent call last):
> File "bin/kz", line 25, in
> from kenozooid.cli import ArgumentError,
> add_commands
> ImportError: No module named kenozooid.cli
>
> I can't find any module called kenozooid.cli in
> the checkout...

I will contact you by e-mail about above if you don't mind to not
pollute this forum.

> What is the purpose of your project?

At the begining it was just dive computer support software,
but now it is evolving slowly into dive planning and dive
analysis software.

> Is there any
> way to support a shearwater predator as well
> (native or at least the SQLLite based log format
> from their windows application)?

At the moment I have parser written in Python for OSTC
(mk.1) and I do support Reefnet Sensus Ultra via
libdivecomputer library.

If libdivecomputer library supported Shearwater, then
it would be quite easy to add support for another device
in Kenozooid.

Hi,

I have the same behavior my Fedora laptop. Solodiver, did you send a bug report to Jdivelog?

No, I did not. The problem is, that I did post issues in the past and had the feeling that they are not heard. Where will you post it? Their sf.net project site seems to be dead and for their website I did not manage to find/recreate an account so far.

I really look forward to see some alternatives (like the ones from wrobel and rob) in the future and I'm for sure willing to support them...

BTW: What unit are you diving?

I'm going to send an email at this address: pellmont (at) users dot sourceforge dot net
I have a MK2 computer (not 2n).

Edit: email sent, I will post here when I will have an answer.

Stephane Wrote:
-------------------------------------------------------
> I have a MK2 computer (not 2n).

I meant your Rebreather...

Thx for taking care of this issue. Let's hope there will be soon a new release...

A hybrid rEvo3.