Aqualung i300 support?

[Philippe Massart]

Hello,

I would like to know if the support of the new Aqualung i300 is planned.

Thanks 

[Jef Driesen]

On 2016-03-03 08:03, Philippe Massart wrote:
> I would like to know if the support of the new Aqualung i300 is
> planned.

Since it's supported by Pelagic's Diverlog software, I assume it's also
using the atom2 communication protocol. I suggest you try the following:
In the subsurface download dialog choose "Oceanic Atom 2.0", and enable
both the libdivecomputer logfile and memory dump check boxes. Start the
download. It may fail, but that's fine at this stage. Send back the log
file and memory dump.

Jef

[Philippe Massart]

Thanks. At this time, I do not own a computer yet, but before choosing one, I needed to know if it would be supported.

Philippe

[Sean Fao]

Hi Jef,

I do have an Aqualung i300 and tried the above recommendations. Unfortunately, I get the following error when attempting:

Error

Unable to open /dev/tty.Bluetooth-Incoming-Port Oceanic (Atom 2.0)

No log files are generated.

Any help with this would be greatly appreciated.

-- 

Sean

[Jef Driesen]

On 2016-05-04 00:48, Sean Fao wrote:
> On Thursday, March 3, 2016 at 2:43:09 AM UTC-5, Jef Driesen wrote:
>>
>> On 2016-03-03 08:03, Philippe Massart wrote:
>> > I would like to know if the support of the new Aqualung i300 is
>> > planned.
>>
>> Since it's supported by Pelagic's Diverlog software, I assume it's
>> also
>> using the atom2 communication protocol. I suggest you try the
>> following:
>> In the subsurface download dialog choose "Oceanic Atom 2.0", and
>> enable
>> both the libdivecomputer logfile and memory dump check boxes. Start
>> the
>> download. It may fail, but that's fine at this stage. Send back the
>> log
>> file and memory dump.
>

> I do have an Aqualung i300 and tried the above recommendations.
> Unfortunately, I get the following error when attempting:
>
> Error
> Unable to open /dev/tty.Bluetooth-Incoming-Port Oceanic (Atom 2.0)

You used the wrong serial port. Normally it should be something like
/dev/tty.usbserial-XXX. The /dev/tty.Bluetooth-Incoming-Port belongs to
some bluetooth device, not your dive computer. Have you installed the
USB driver? Usually it gets installed along with manufacturer's
software.

Jef

[Sean Fao]

Hi Jef,

I had actually noticed it was using a Bluetooth port, which seemed odd to me. Strangely, I believe my Suunto Zoop (also USB) connects via the same port, but I'll verify for sure when I get home this evening. I did try to select a USB port, but only Bluetooth is available for this device (other devices allow me to select between USB and Bluetooth). I haven't been able to locate a driver for the i300, but Diver Log doesn't seem to have any problem communicating with it (maybe because I'm on a Mac?).

Thank you again,

Sean

[Justin Visser]

I actually just got an i3000 and would really like to use Subsurface and do not have the Mac so I cannot use the Diverlog software that the i3000 uses for a Mac. 

I have no logged dives on it, however on the coming Thursday I will try to take it in a pool to get a test dive. Hopefully I can provide some kind of log data if it won't import. 

[Jef Driesen]

I suggest you also try the following: In the subsurface download dialog

choose "Oceanic Atom 2.0", and enable both the libdivecomputer logfile
and memory dump check boxes. Start the download. It may fail, but that's
fine at this stage. Send back the log file and memory dump.

It doesn't matter whether you try on Linux, Windows or Mac. Just make
sure you install the usb driver (which usually gets installed along with
the software from the manufacturer).

Jef

[Justin Visser]

Apologies for the late reply. I finally got to go to the pool and use the computer. I will attach both of the logs you requested. I was unable to get the data to import into subsurface. Kept giving a header error. Use AquaLungs software "DiverLog" on Windows, I was able to successfully log the data in their program. 

In subsurface it does seem like it picked up the device. As without it plugged in it gave an error about not being able to connect (makes sense), but when I connected it and tried com3 subsurface did seem to get the data, and the dive computer indicated that the computer did use it. So my hunch here is that the format is maybe slightly different. 

Let me know if you need anymore information.

[Justin Visser]

If subsurface supports the formats that DiverLog uses for exports I could just import my logs that way: http://ediverlog.com/faq.py?CAT=Backup/Import/Export

It wouldn't be ideal as I would need to pay $20 to get the full version, however if that would allow me to get my logs into sub-surface I could bite the bullet on that fee.

On Monday, May 9, 2016 at 4:59:11 AM UTC-4, Jef Driesen wrote:

[Jef Driesen]

On 2016-05-17 07:19, Justin Visser wrote:
> Apologies for the late reply. I finally got to go to the pool and use
> the
> computer. I will attach both of the logs you requested. I was unable to
> get
> the data to import into subsurface. Kept giving a header error. Use
> AquaLungs software "DiverLog" on Windows, I was able to successfully
> log
> the data in their program.
>
> In subsurface it does seem like it picked up the device. As without it
> plugged in it gave an error about not being able to connect (makes
> sense),
> but when I connected it and tried com3 subsurface did seem to get the
> data,
> and the dive computer indicated that the computer did use it. So my
> hunch
> here is that the format is maybe slightly different.

The data format is indeed different. That explains why the communication
with the dive computer works fine, but downloading and parsing the dives
fails.

> Let me know if you need anymore information.

I have everything I need. Even better, support for the i300 is already
available in libdivecomputer master. I received some data from another
i300 owner a few days ago, and my fixes appear to work for your data
too.

Just wait for the next subsurface release.

Jef

[Miika Turkia]

I would use the native download since the protocol is already
supported by libdivecomputer, as Jef just informed in another mail. I
just don't know when new version is released.

There is also DL7 import on development version of Subsurface. But as
said, I would download natively, as that will most likely include more
details than the DL7 import.

> --
> You received this message because you are subscribed to the Google Groups
> "Subsurface Divelog" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to subsurface-dive...@googlegroups.com.
> To post to this group, send email to subsurfac...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/subsurface-divelog/e6c67efb-21fa-4fd9-b126-1ddf6aaf39e6%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

[Justin Visser]

That is great to hear! I haven't used the computer for any OW dives yet so I have nothing I care to have imported from it yet, so I am quite happy to hear that there is support added for it that will be in subsurface soon!

Justin V

[Justin Visser]

Hello,

It has been a while since the last message in this conversation, however I would like to mention that I still am not seeing the i300 in the release version of subsurface, or in any of the daily builds.

I have still been just using the method of using the dctool.exe file to create the xml file from the command line, and then import this as a "log file" into subsurface, however this process is a lot more tedious and has become somewhat annoying, especially since this method means old dives still stored on the computer that are already logged get inserted again.

I am wondering if there is any news on implementing this library updates yet?

Justin V

On Tue, Jun 14, 2016 at 10:45 PM, Justin Visser <foge...@gmail.com> wrote:

I am not seeing a i300 in the Aqua lung section. Still just the same one as before. I tried to use the Oceanic Atom 2.0 again just to see if that was changed and it is not. It reads it in, just parses it incorrectly. Same problem as before. Just for kicks I also tried some of the other dive computers under the Oceanic vendor and the ones I tried also showed the same symptoms as the Atom 2.0. 

Overall it just seems like the i300 support is not there yet, unless I am missing something.

I just downloaded the build from today, which is Subsurface 4.5.2-1427-gda052967c263 for Windows. 

Justin V

On Tue, Jun 14, 2016 at 8:22 AM, Justin Visser <foge...@gmail.com> wrote:

It is the morning here and I'm at work. I'll also be doing a dive later on today, so I'll have to test this out when I get home tonight! I will let you know how the test goes! *crosses fingers*.

Thanks for replying despite travelling!

Justin V

On Tue, Jun 14, 2016 at 1:59 AM, Miika Turkia <miika....@gmail.com> wrote:

I am currently traveling, so cannot test or verify this, but Dirk did attempt to fix this on Subsurface daily builds yesterday. Can you try the latest daily build and see if it works.

miika

On 13 Jun 2016, at 04:51, Justin Visser <foge...@gmail.com> wrote:

I can use Linux as well if needed. Is there anywhere that has examples of these commands being run or some kind of documentation? Just something so that I can figure out what is expected in each parameter? Because I now have 6 dives on my computer and according to the manual depending on the sample rate I may only get 15 logs stored if I'm lucky at the sample rate I'm using. 

Justin V

On Sun, Jun 5, 2016 at 11:17 PM, Miika Turkia <miika....@gmail.com> wrote:

IIRC the -d parameter should be device, like com3 or what is used by
the DC. I am not exactly sure how it is in Windows...

miika

On Sun, Jun 5, 2016 at 10:41 PM, Justin Visser <foge...@gmail.com> wrote:
> From looking at the commit
> (http://git.libdivecomputer.org/?p=libdivecomputer.git;a=commitdiff;h=8f776cc55e720883bb92caf17c9c5d30898d53c7;hp=d1aa9478a4e692254fb09d52ae6e0bbf855aaff1)
> I am having a hard time figuring out what the family, device, and model
> number are suppose to be. Here is my guess below, but it seems incorrect:
>
> ./dctool -f Aqualung -d i300 -m i300 download
> No supported device found: i300
>
>
> Justin V
>
>
> On Sat, Jun 4, 2016 at 2:43 PM, Miika Turkia <miika....@gmail.com> wrote:
>>
>> I know the feeling :(  Anyway, it just occurred to me that you should
>> be able to use libdivecomputer's dctool to grab your logs and import
>> that to subsurface. Just as a workaround until Dirk manages to create
>> a new daily build with the latest fixes from libdivecomputer included.
>>
>> http://www.libdivecomputer.org/builds/windows/
>>
>> The dctool is a command line application and figuring out the proper
>> parameters might take a bit of an effort, but IIRC if you download the
>> dives to XML format with dctool, we should be able to import them to
>> Subsurface. And if you spot anything missing or incorrect, I should be
>> able to fix the import of dctool produced XML. This way, you should
>> not be loosing any dives completely.
>>
>> HTH,
>> miika
>>
>> On Fri, Jun 3, 2016 at 7:33 PM, Justin Visser <foge...@gmail.com> wrote:
>> > Well the only reason I'm so anxious for the support in subsurface is
>> > because
>> > my dive computer will only keep ~15 past dives stored and past that it
>> > will
>> > start overwriting. So I am just worried about losing some dive data
>> > since I
>> > couldn't log it.
>> >
>> > Justin V
>> >
>> >
>> > On Fri, Jun 3, 2016 at 12:02 PM, Miika Turkia <miika....@gmail.com>
>> > wrote:
>> >>
>> >> you can try, but I don't think it will work. We have changed some API
>> >> and
>> >> that might cause problems. Withaout this difference, there shouldn't be
>> >> any
>> >> need for code changes, but now I suspect the official libdivecomputer
>> >> is
>> >> incompatible.
>> >>
>> >> miika
>> >>
>> >> On 03 Jun 2016, at 18:11, Justin Visser <foge...@gmail.com> wrote:
>> >>
>> >> To confirm though, will replacing the current libdivecomputer in
>> >> subsurfaces directory with the new libdivecomputer provide the support?
>> >> Or
>> >> does there need to be additional code added on the subsurface side to
>> >> support this?
>> >>
>> >> Justin V
>> >>
>> >>
>> >> On Fri, Jun 3, 2016 at 11:09 AM, Miika Turkia <miika....@gmail.com>
>> >> wrote:
>> >>>
>> >>> Ah, it looks like the i300 support is not yet included in our daily
>> >>> builds. We use own branch of libdivecomputer and Dirk will need to
>> >>> merge the latest commits from master to our branch. Unfortunately he
>> >>> has been extremely busy lately so I am not sure how soon that will
>> >>> happen.
>> >>>
>> >>> miika
>> >>>
>> >>> On Fri, Jun 3, 2016 at 6:00 PM, Justin Visser <foge...@gmail.com>
>> >>> wrote:
>> >>> > Looking at the commit for the addition it would seem like I should
>> >>> > probably
>> >>> > be seeing an option for my dive computer under the Vendor of
>> >>> > Aqualung
>> >>> > and
>> >>> > the dive computer of i300:
>> >>> >
>> >>> >
>> >>> > http://git.libdivecomputer.org/?p=libdivecomputer.git;a=commit;h=8f776cc55e720883bb92caf17c9c5d30898d53c7
>> >>> >
>> >>> > I am not seeing it in there.
>> >>> >
>> >>> > Justin V
>> >>> >
>> >>> >
>> >>> > On Fri, Jun 3, 2016 at 10:40 AM, Miika Turkia
>> >>> > <miika....@gmail.com>
>> >>> > wrote:
>> >>> >>
>> >>> >> Since you are anxious to get going, how about grabbing our "daily"
>> >>> >> build and testing with that. Was it so that you are using Windows?
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> https://subsurface-divelog.org/downloads/daily/subsurface-4.5.2-1406-g7a77569019ad.exe
>> >>> >>
>> >>> >> Even though the version states 4.5.2-1406, that is more resent than
>> >>> >> the released 4.5.6.
>> >>> >>
>> >>> >> miika
>> >>> >>
>> >>> >> On Fri, Jun 3, 2016 at 5:34 PM, Justin Visser <foge...@gmail.com>
>> >>> >> wrote:
>> >>> >> > I'm assuming just replacing the current lib file in the
>> >>> >> > Subsurface
>> >>> >> > directory
>> >>> >> > with the new one isn't enough is it?

>> >>> >> >
>> >>> >> > Justin V
>> >>> >> >
>> >>> >> >
>> >>> >> > On Tue, May 17, 2016 at 5:16 AM, Miika Turkia
>> >>> >> > <miika....@gmail.com>
>> >>> >> > wrote:
>> >>> >> >>

[Dirk Hohndel]

On Jul 25, 2016, at 6:58 PM, Justin Visser <foge...@gmail.com> wrote:

Hello,

It has been a while since the last message in this conversation, however I would like to mention that I still am not seeing the i300 in the release version of subsurface, or in any of the daily builds.

The subsurface-4.5.2-1496-g177e21076b98.exe daily build should support the i300.

http://subsurface-divelog.org/downloads/daily/subsurface-4.5.2-1496-g177e21076b98.exe

Are you sure you have tried this version?

/D

[Justin Visser]

I just downloaded the build 30 minutes ago. I do not see any i300 under the "Aqualung" vendor, nor do I see it in the Oceanic vendor. 

Am I looking in the wrong place? 

Justin V

--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/cJUI40tRXZc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to subsurface-dive...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/279189FD-AB32-41B7-A646-3326BD422C52%40hohndel.org.

[Dirk Hohndel]

Grr. Silly me. I copied the file before the build finished, i.e., I copied the previous build. 

I hate it when I do that :-(

This time I tested things :-)

http://subsurface-divelog.org/downloads/daily/subsurface-4.5.2-1501-g8c2668a6b1d3.exe

/D

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-dive...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/CAHBoyw_fx1V2shwwR6-FnnBy5nYcsnx8ZCr6w9sU43tXe%3DFZbg%40mail.gmail.com.

[Justin Visser]

Not a problem. I just tested the new build and it appears to be working as expected now. Importing works smoothly and correctly detects my old dives versus the new dives. 

Thanks for the work. I appreciate it! 

Justin V

To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/576475CA-94C7-4334-A8D0-2D8F8C7BD827%40hohndel.org.

[Kyle Patac]

Hello,

I am trying to get my i300 to work and this is the error I recieved. I did download the newest driver for it before I tried to connect it. Any help would be much appreciated.

Subsurface: v4.7.8, built with libdivecomputer v0.7.0-devel-Subsurface-branch (d02f1c3cdcc6a04d085538578d872ec6e3282382)

INFO: Open: name=COM3

INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, flowcontrol=0

INFO: Timeout: value=4000

INFO: Sleep: value=100

INFO: Purge: direction=3

INFO: Write: size=1, data=67

INFO: Read: size=3, data=1CE0FE

ERROR: Failed to receive the answer. [in /home/travis/build/Subsurface-divelog/subsurface/libdivecomputer/src/hw_ostc.c:434 (hw_ostc_device_eeprom_read)]

Justin V

Justin V

To unsubscribe from this group and all its topics, send an email to subsurface-divelog+unsub...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/279189FD-AB32-41B7-A646-3326BD422C52%40hohndel.org.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Subsurface Divelog" group.

To unsubscribe from this group and stop receiving emails from it, send an email to subsurface-divelog+unsub...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/subsurface-divelog/CAHBoyw_fx1V2shwwR6-FnnBy5nYcsnx8ZCr6w9sU43tXe%3DFZbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Subsurface Divelog" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/subsurface-divelog/cJUI40tRXZc/unsubscribe.

To unsubscribe from this group and all its topics, send an email to subsurface-divelog+unsub...@googlegroups.com.

To post to this group, send email to subsurfac...@googlegroups.com.