Support for Aqualung i200, coming?

[PaqKILLER]

Support for Aqualung i200, coming?

[Vinnie S]

So no one is looking in to this?

[Anton Lundin]

Don't think so.

You cloud try to create a libdivecomputer dump file of the device. I guess it will work if you choose aqualung i300. From that it might be possible to figure out how the i200 works.

//Anton

[Jef Driesen]

I added support for the i200 to libdivecomputer a few days ago.

PS: New Oceanic based devices almost never work out of the box. Downloading
memory dumps should work, but for the dives and the parsing libdivecomputer
needs to know which memory layout to use and that is different for every model.
The default fallback for unknown models is rarely correct. It's just enough to
be able do download a memory dump, but everything else will be wrong.

Jef

[Vinnie S]

Awesome! So, what next? 

During the i300 enabling, I saw someone who was using the dctool to download the dives and then imports the files into subsurface. For the time being (until subsurface picked up the new libdivecomputer), I was going to try and grab a daily build of the mac dctool and do the same, but I don't see where to do that. 

I did notice that the protocol appears to be the same as the other Aqualung because it downloaded the dives, but the dive details were all messed up.

Thanks!

[Dirk Hohndel]

Depends on how impatient you are.
I'm on family vacation. Sadly that will end soon.
It shouldn't take us too long to have a test build with an updated libdivecomputer. My guess would be less than a week...

/D

--
from my phone.

[Vinnie S]

Enjoy your vacation!! It's far more important. ;-)

Thanks for your work on the project!

[Jef Driesen]

On 19-08-17 21:28, Vinnie S wrote:
> Awesome! So, what next?
>
> During the i300 enabling, I saw someone who was using the dctool to download the
> dives and then imports the files into subsurface. For the time being (until
> subsurface picked up the new libdivecomputer), I was going to try and grab a
> daily build of the mac dctool and do the same, but I don't see where to do that.

Use these options to download the dives and output an xml file:

./dctool -v -l atom2.log -f atom2 download -o atom2.xml <serialport>

I believe subsurface can import the xml file.

> I did notice that the protocol appears to be the same as the other Aqualung
> because it downloaded the dives, but the dive details were all messed up.

Yes, that's exactly what I explained in my previous email :-)

Jef

[Vinnie S]

> Use these options to download the dives and output an xml file: 

> 

> ./dctool -v -l atom2.log -f atom2 download -o atom2.xml <serialport> 

> 
> I believe subsurface can import the xml file. 

This has the same effect as directly importing them into subsurface. All the dives import, but the dates are wrong, depths are wrong, etc. Also seems to think there are air pressure readings, which i200 doesn't have.

>> I did notice that the protocol appears to be the same as the other Aqualung 

>> because it downloaded the dives, but the dive details were all messed up. 

>
> Yes, that's exactly what I explained in my previous email :-)

That's because it was supposed to be. ;-) I was confirming that I was experiencing the behavior you said I would.

Thanks, Vinnie

[Jef Driesen]

On 19-08-17 22:25, Vinnie S wrote:
>> Use these options to download the dives and output an xml file:
>>
>> ./dctool -v -l atom2.log -f atom2 download -o atom2.xml <serialport>
>>
>> I believe subsurface can import the xml file.
>>
> This has the same effect as directly importing them into subsurface. All
> the dives import, but the dates are wrong, depths are wrong, etc. Also
> seems to think there are air pressure readings, which i200 doesn't have.

That probably means that the build you tried didn't include the i200 support
yet. I have uploaded a new build now. Try again with the new build.

Jef

[Linus Torvalds]

On Sat, Aug 19, 2017 at 12:28 PM, Vinnie S <vinsan...@gmail.com> wrote:
>
> During the i300 enabling, I saw someone who was using the dctool to download
> the dives and then imports the files into subsurface. For the time being
> (until subsurface picked up the new libdivecomputer)

Well, if you build your own binaries, I have a sync-ed up libdivecomputer at

git://github.com/torvalds/libdc-for-dirk.git Subsurface-branch

which does require a (small) patch to subsurface (attached) to handle
the new timesync changes.

There are a few more things I want to do to that libdivecomputer
branch, but they don't affect the Aqualung i200.

Further small things I need to fix up:

- the HIDAPI changes that Jef did do *not* work for the Scubapro G2,
since they break BLE - he didn't see that because he doesn't use the
generic IO layer and only tested USB HID

- I'll wire up the EON Steel timesync update too. I've got the code,
and it's actually pushed out too, but it's not tested in the new form
since subsurface doesn't *use* the new timesync code yet.

Linus

[Vinnie S]

> That probably means that the build you tried didn't include the i200 support 

> yet. I have uploaded a new build now. Try again with the new build. 

Grabbed the new one. Worked perfectly!! 

> Well, if you build your own binaries, I have a sync-ed up libdivecomputer at 

I don't have a build environment set up on my Mac. With my dive frequency, dctool + import will work plenty fine until a new binary release comes out. 

THANKS guys!! You rock! :-)

[Dirk Hohndel]

Would you mind testing our latest test build?

http://subsurface-divelog.org/downloads/test/Subsurface-4.6.4-736-g6554e4f21e4d.dmg

This should support the Aqualing i200

Thanks

/D

[Vinnie S]

Would you mind testing our latest test build?

http://subsurface-divelog.org/downloads/test/Subsurface-4.6.4-736-g6554e4f21e4d.dmg

This should support the Aqualing i200

Thumbs up for Mac OS 10.12.6. Imported smoothly and data is confirmed accurate.

Thanks!!! 

[fe...@masias.net]

Sorry for my lack of participation lately (new job in a new industry is really kicking my butt) but I finally found some time to dive this week... and can also confirm that download support for i200 works on macOS 10.11.6, and the data matches that of the official software.

-Federico