Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Dirk Hohndel]

> On Aug 24, 2017, at 7:06 AM, Jef Driesen  wrote:
> 
> On 2017-08-23 06:43, Dirk Hohndel wrote:
>>> On Aug 22, 2017, at 7:55 AM, Jef Driesen  wrote:
>>> I don't understand what you gain with those comments. I mean it's just 
>>> comments. Don't you need this kind of info at runtime instead?
>> Yup - I simply have a tool that parses the source to give me the
>> information that I want.
> 
> Well, that's a pretty ugly and error-prone hack. You hard-code everything in 
> the application, based on whatever version that was used at build time (which 
> may not even be the same as at runtime). But the reason why that table 
> exists, is to let applications populate the list of supported devices 
> dynamically at runtime! And by doing it this way, you also depend on some of 
> the libdivecomputer internals.
> 
> If we're adding this kind of annotations, then I prefer to make this 
> information available through the api. That will be a lot more useful, and 
> may also benefit other applications.

That's ok, I didn't expect you to take the changes, which is why I didn't 
bother sending them to the libdivecomputer mailing list.
I needed to get something that worked for our use case, and I needed it soon.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Jef Driesen]

On 2017-08-23 06:43, Dirk Hohndel wrote:
On Aug 22, 2017, at 7:55 AM, Jef Driesen  
wrote:
I don't understand what you gain with those comments. I mean it's just 
comments. Don't you need this kind of info at runtime instead?


Yup - I simply have a tool that parses the source to give me the
information that I want.


Well, that's a pretty ugly and error-prone hack. You hard-code 
everything in the application, based on whatever version that was used 
at build time (which may not even be the same as at runtime). But the 
reason why that table exists, is to let applications populate the list 
of supported devices dynamically at runtime! And by doing it this way, 
you also depend on some of the libdivecomputer internals.


If we're adding this kind of annotations, then I prefer to make this 
information available through the api. That will be a lot more useful, 
and may also benefit other applications.



Something like what I proposed for the I/O refactoring:

For the I/O refactoring, I'm already planning to add an extra field 
with the transport type. Since some devices support multiple 
transports, the transport type will need to change into a bitfield. So 
something like this:


{"Shearwater", "Petrel 2",  DC_FAMILY_SHEARWATER_PETREL, 4,
DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH | DC_TRANSPORT_BLE},


Which doesn't tell me if this is an FTDI chip - which is one of the
things that I need to know.


That's quite easy: Suunto (solution, eon, vyper and d9), Oceanic (vtpro, 
veo250 and atom2), HW (frog, ostc and ostc3) and Cressi (leonardo) 
backends use an FTDI chip. You don't need to annotate each device for 
that. Just check the family type.


Note that the usb-serial chipset is often not integrated in the dive 
computer, but in the external PC interface. So there is not always a 
nice one-to-one relationship. For example the official Suunto PC 
interface uses an FTDI chip, but there are also third-party interfaces 
available using a Silicon Labs chip (and those are quite common). And 
some really old models still have a real serial port, and thus the user 
can use any usb-serial dongle.


Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Dirk Hohndel]

> On Aug 22, 2017, at 7:55 AM, Jef Driesen  wrote:
> I don't understand what you gain with those comments. I mean it's just 
> comments. Don't you need this kind of info at runtime instead?

Yup - I simply have a tool that parses the source to give me the information 
that I want.

> Something like what I proposed for the I/O refactoring:
> 
> For the I/O refactoring, I'm already planning to add an extra field with the 
> transport type. Since some devices support multiple transports, the transport 
> type will need to change into a bitfield. So something like this:
> 
> {"Shearwater", "Petrel 2",  DC_FAMILY_SHEARWATER_PETREL, 4,
> DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH | DC_TRANSPORT_BLE},

Which doesn't tell me if this is an FTDI chip - which is one of the things that 
I need to know.

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Jef Driesen]

On 2017-08-22 05:29, Gregory Sin wrote:

Please find testing result and files/log/screens below.

DC: iX3M DEEP (Os 4.0.26/013). Clean DC, no dives logged.
Mac:10.12.4
SUBSURF:4.6.4.737
BT: Only DC and Mouse are paired, but only DC connected.

No errors reported.
Can we carefully conclude that BT comm works? ;)
I will be try same DC with dives/log after one week and revert.
Sorry, we have 3 Ratio DC here, but all pristine new w/o dives.


The last error in the logfile:

ERROR: Received NAK packet with error code 58. [in 
../../src/divesystem_idive.c:348 (divesystem_idive_packet)]


might be a bit misleading. Error code 58 means that the dive computers 
contains no dives yet. So it's completely harmless and the download was 
completed successfully.


Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Jef Driesen]

On 2017-08-21 16:51, Dirk Hohndel wrote:

BTW: I have added some annotation in the Subsurface-branch to help us
decide which dive computers to offer as choices on mobile devices
(this is in src/descriptor.c):

[...]

This basically just adds a comment at the end of every line that
follows a strict syntax: two slashes, one space, then a token. There
can be more than one such comment, e.g.:

/* Shearwater Petrel family */
{"Shearwater", "Petrel",DC_FAMILY_SHEARWATER_PETREL, 3},
// BT // BLE
{"Shearwater", "Petrel 2",  DC_FAMILY_SHEARWATER_PETREL, 4},
// BT // BLE
{"Shearwater", "Nerd",  DC_FAMILY_SHEARWATER_PETREL, 5},  
// BT

{"Shearwater", "Perdix",DC_FAMILY_SHEARWATER_PETREL, 6},
// BT // BLE
{"Shearwater", "Perdix AI", DC_FAMILY_SHEARWATER_PETREL, 7},  
// BLE


(yes, I know this looks wrong, as the Petrel has no BLE version, but
the Petrel 2 unfortunately identifies itself as Petrel).

Would you be willing to take a patch that adds this for
libdivecomputer master? This would make our lives easier and it
certainly shouldn't cause any problems on your end as this is all just
comments...
Please let me know and I'll be happy to submit one clean patch to just 
add that.


I don't understand what you gain with those comments. I mean it's just 
comments. Don't you need this kind of info at runtime instead? Something 
like what I proposed for the I/O refactoring:


For the I/O refactoring, I'm already planning to add an extra field with 
the transport type. Since some devices support multiple transports, the 
transport type will need to change into a bitfield. So something like 
this:


{"Shearwater", "Petrel 2",  DC_FAMILY_SHEARWATER_PETREL, 4,
DC_TRANSPORT_SERIAL | DC_TRANSPORT_BLUETOOTH | DC_TRANSPORT_BLE},

With this information, an application knows exactly which transport 
types are supported for each device, and can setup the appropriate I/O 
channel (built-in or custom implementation).


To find out what goes wrong, you'll need to enable the libdivecomputer 
logfile checkbox. Without the logfile, we have no idea where exactly 
it goes wrong. Screenshots are useless because they don't give the 
low-level detailed info.


I keep wanting to improve the error messages that we are able to give
- right now the useless default error that implies incorrect
permissions does a lot more harm than anything else. I just can't seem
to find the time with all the other things on my plate. A feeling that
I know you are well familiar with, Jef.

But until then, the libdivecomputer log file certainly is the correct
next step. Actually, I might be able to add a quick and dirty change
that suggests this to the user... then at least people using the test
builds would get that hint.


Just an idea: Why not always enable the logfile? Then whenever the 
download fails, you can notify the user about the error as usual, but 
also point to the log file. You probably don't want to show the contents 
of the log, but just the location of the file. That makes it very easy 
to report errors, because all the info is right there. Diving Log does 
something similar, and it works very well.


Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Dirk Hohndel]

Hi Jef,

Thanks for these clarification - this really helps.

> On Aug 21, 2017, at 7:23 AM, Jef Driesen  wrote:
> 
> I suspect the correct port should be /dev/tty.usbserial-DN02DP66. The others 
> are certainly not the correct for usb-serial adapters on Mac.

That was my assumption as well.

> In one of the screenshots, you have selected a model from the iDive series. 
> That won't work with a model from the iX3M series. This is one of the cases 
> where the actual model matters because there is a small but important 
> difference in the communication protocol! (You can still choose any model 
> from the iX3M series).
> 
> Support for the APOS4 firmware was added a few months ago, so I don't think 
> that's the problem here. (Unless you are using a subsurface build where this 
> change wasn't included yet.)

The latest binary that I made available a few hours ago 
(http://subsurface-divelog.org/downloads/test/Subsurface-4.6.4-736-g6554e4f21e4d.dmg)
 should have all changes that are in upstream libdivecomputer. We try to stay 
reasonably close to your code, as you know - it's getting increasingly 
difficult, but we'll do our best.

BTW: I have added some annotation in the Subsurface-branch to help us decide 
which dive computers to offer as choices on mobile devices (this is in 
src/descriptor.c):

static const dc_descriptor_t g_descriptors[] = {
/* Suunto Solution */
{"Suunto", "Solution", DC_FAMILY_SUUNTO_SOLUTION, 0},   // FTDI
/* Suunto Eon */
{"Suunto", "Eon", DC_FAMILY_SUUNTO_EON, 0}, // FTDI
{"Suunto", "Solution Alpha",  DC_FAMILY_SUUNTO_EON, 0},  // FTDI
{"Suunto", "Solution Nitrox", DC_FAMILY_SUUNTO_EON, 0},  // FTDI
[...]
/* Suunto EON Steel */
#ifdef USBHID
{"Suunto", "EON Steel", DC_FAMILY_SUUNTO_EONSTEEL, 0},  // BLE
#endif
/* Uwatec Aladin */
{"Uwatec", "Aladin Air Twin", DC_FAMILY_UWATEC_ALADIN, 0x1C},  // 
FTDI
{"Uwatec", "Aladin Sport Plus",   DC_FAMILY_UWATEC_ALADIN, 0x3E},  // 
FTDI
[...]
/* Uwatec Memomouse */
{"Uwatec", "Memomouse", DC_FAMILY_UWATEC_MEMOMOUSE, 0},  // FTDI
/* Uwatec Smart */
#ifdef IRDA
{"Uwatec", "Smart Pro", DC_FAMILY_UWATEC_SMART, 0x10},
{"Uwatec", "Galileo Sol",   DC_FAMILY_UWATEC_SMART, 0x11},
{"Uwatec", "Galileo Luna",  DC_FAMILY_UWATEC_SMART, 0x11},
   
etc.
This basically just adds a comment at the end of every line that follows a 
strict syntax: two slashes, one space, then a token. There can be more than one 
such comment, e.g.:

/* Shearwater Petrel family */
{"Shearwater", "Petrel",DC_FAMILY_SHEARWATER_PETREL, 3},  // BT // 
BLE
{"Shearwater", "Petrel 2",  DC_FAMILY_SHEARWATER_PETREL, 4},  // BT // 
BLE
{"Shearwater", "Nerd",  DC_FAMILY_SHEARWATER_PETREL, 5},  // BT
{"Shearwater", "Perdix",DC_FAMILY_SHEARWATER_PETREL, 6},  // BT // 
BLE
{"Shearwater", "Perdix AI", DC_FAMILY_SHEARWATER_PETREL, 7},  // BLE

(yes, I know this looks wrong, as the Petrel has no BLE version, but the Petrel 
2 unfortunately identifies itself as Petrel).

Would you be willing to take a patch that adds this for libdivecomputer master? 
This would make our lives easier and it certainly shouldn't cause any problems 
on your end as this is all just comments...
Please let me know and I'll be happy to submit one clean patch to just add that.

> To find out what goes wrong, you'll need to enable the libdivecomputer 
> logfile checkbox. Without the logfile, we have no idea where exactly it goes 
> wrong. Screenshots are useless because they don't give the low-level detailed 
> info.

I keep wanting to improve the error messages that we are able to give - right 
now the useless default error that implies incorrect permissions does a lot 
more harm than anything else. I just can't seem to find the time with all the 
other things on my plate. A feeling that I know you are well familiar with, Jef.

But until then, the libdivecomputer log file certainly is the correct next 
step. Actually, I might be able to add a quick and dirty change that suggests 
this to the user... then at least people using the test builds would get that 
hint.

Thanks

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Jef Driesen]

Greg,

I suspect the correct port should be /dev/tty.usbserial-DN02DP66. The 
others are certainly not the correct for usb-serial adapters on Mac.


In one of the screenshots, you have selected a model from the iDive 
series. That won't work with a model from the iX3M series. This is one 
of the cases where the actual model matters because there is a small but 
important difference in the communication protocol! (You can still 
choose any model from the iX3M series).


Support for the APOS4 firmware was added a few months ago, so I don't 
think that's the problem here. (Unless you are using a subsurface build 
where this change wasn't included yet.)


To find out what goes wrong, you'll need to enable the libdivecomputer 
logfile checkbox. Without the logfile, we have no idea where exactly it 
goes wrong. Screenshots are useless because they don't give the 
low-level detailed info.


Jef

On 2017-08-21 15:57, Gregory Sin wrote:

Dear Dirk,

Sorry for confusion.. perhaps its a bit complicated :)

To my understanding, issue with Os 10.9.5 is closed.
SubSurface has compatibility only 10.10 and above.

Today I did one more testing of iDive and iX3M on 10.12.6
Please find fresh screens attached.

One DC run “old” OS which is 4.0.9 and another DC run
updated/“new” OS which is 4.0.26.
Reason why I put this info up, because I’ve heard some rumors that
with latest update Ratio changed something in protocol.
By using same DC with different OS Im just trying to eliminate that
possible com-protocol issue.

Both DCs tested via USB not BT. I also deleted BT pairing to make
experiment more clean.
Both DCs were READY and shows DATA upon attempt of import or
configuration setup.
Both DCs have no data (no log yet).
SubSurf showed: usbserial-DN02DP66 port for both DC equally.
Both attempts of download showed Error Data import error.

Not sure, but may be its a good idea for time being to skip that DC
configuration feature because it is obviously not ready yet and focus
on importing data.
At least SubSurf may import data from DC log.

Screens are enclosed.
Please guide me how I can help more.

Remain at your disposal.
Greg

On 21 Aug, 2017, at 20:36, Dirk Hohndel  wrote:


It is also cant see USB unless you purposely put USB0 in the port
settings.


So if you put USB0 it works, but with /dev/tty.USB0 it doesn't? I'm
confused.


I tried iDive with old OS and iX3M with new.


I don't understand, I thought the old OS (10.9) didn't allow you to
run the new Subsurface build at all?

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Dirk Hohndel]

> On Aug 20, 2017, at 10:28 PM, Gregory Sin  wrote:
> 
> Dear Dirk,
> 
> Please find attached.
> It crashes on 10.9.5. (report is in the file).

Yes, we need to update our documentation. Because of a dependency in the latest 
Qt version, Subsurface now requires MacOS 10.10.

> It tried to connect on 10.12 via BT but failed (errors in the file).

Lots of screen shots, a bit hard to figure out which one shows which situation.
From what I can tell in the screen shots, you tried to run "configure dive 
computer" - that only supports some Suunto and Heinrichs Weikamp devices, not 
your RATIO dive computers

Then the download screen with BT doesn't seem to have BT checked. Is that a 
mistake?

> It is also cant see USB unless you purposely put USB0 in the port settings.

So if you put USB0 it works, but with /dev/tty.USB0 it doesn't? I'm confused.

> I tried iDive with old OS and iX3M with new.

I don't understand, I thought the old OS (10.9) didn't allow you to run the new 
Subsurface build at all?

Thanks

/D
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Dirk Hohndel]

> On Aug 20, 2017, at 8:43 PM, Gregory Sin  wrote:
> 
> On the stable release (4.6.4) it does not work neither BT or USB.
> Checked yesterday on iDive and IX3M computers and on different Mac/OS.
> iDive is OS 4.0.9/011 and iX3M is OS 4.0.26/013

Let's deal with one problem at a time. I just created a new test build from
the latest sources - this one includes the library that was missing from the
previous build.

Please try

http://subsurface-divelog.org/downloads/test/Subsurface-4.6.4-735-g0bb93c76fd91.dmg

/D


___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Gregory Sin]

On the stable release (4.6.4) it does not work neither BT or USB.
Checked yesterday on iDive and IX3M computers and on different Mac/OS.
iDive is OS 4.0.9/011 and iX3M is OS 4.0.26/013

Guide me please how I can help further.

kind regards
Gregory


On 21 Aug, 2017, at 11:30, Linus Torvalds  wrote:

> On Sun, Aug 20, 2017 at 8:14 PM, Benjamin  wrote:
>> 
>> *whistling quietly*
>> 
>> I may need the instructions on the boot-heel to empty the water out of the 
>> boot, but I do try to read the manual when I can't get things to work... :)
> 
> Ok, you have that box checked.,
> 
> This may be some OS X issue - or alternatively a iX3M one. I just
> checked the two dive computers I have that do BT, and they both work
> (both USB and BT). But I don't have a rfcomm device, and I don't have
> OS X..
> 
>Linus



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Linus Torvalds]

On Sun, Aug 20, 2017 at 8:14 PM, Benjamin  wrote:
>
> *whistling quietly*
>
> I may need the instructions on the boot-heel to empty the water out of the 
> boot, but I do try to read the manual when I can't get things to work... :)

Ok, you have that box checked.,

This may be some OS X issue - or alternatively a iX3M one. I just
checked the two dive computers I have that do BT, and they both work
(both USB and BT). But I don't have a rfcomm device, and I don't have
OS X..

Linus
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Benjamin]

What should be passed there for a bluetooth connection? Because it used to
work up until the G2 support was added to Subsurface :(

On 20 August 2017 at 13:46, Jef Driesen  wrote:

> On 19-08-17 12:00, Benjamin wrote:
>
>> So, after a few trials, I'm getting the following in the subsurface.log
>> file:
>>
>> INFO: Open: name=00:13:43:0C:56:29
>>
>> ERROR: Failed to open the serial port. [in ../../src/shearwater_common.c:46
>> (shearwater_common_open)]
>>
>
> This shows exactly what the problem is! A bluetooth MAC address
> (00:13:43:0C:56:29) is being passed to the dc_serial_open() function. And
> of course that doesn't work!
>
> Jef
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Gregory Sin]

Hi Robert

Hope you are not in Papua ;) to my memory internet is second issue there, after 
Malaria of course ;)

Ok, let me try it on 3 macs (with different OS) and 2 iX3M (DEEP and Easy 
models), by using BT and cable.
I think its Ratio  OS version, what can make a difference… got some rumors that 
after recent update of their OS, client SW also need to be updated.
Are we talking about this version Subsurface-4.6.4-709-gd77de11a1d2e.dmg?

Give me few days please. Will revert soon.

Have a good trip.

kind regards
Greg



On 20 Aug, 2017, at 18:40, Robert C. Helling  
wrote:

> Gregory,
> 
> I am currently traveling and only rarely have internet connectivity.
> 
>> Am 20.08.2017 um 10:58 schrieb Gregory Sin :
>> 
>> unable to run that test version due to immediate crash on both Mac).
> 
> I tried the latest test version and have no problem to run it. Upon crashing, 
> the mac should offer to send a crash report (to apple not us). Could you 
> please copy and paste that report so we can try to figure out what is going 
> on?
> 
> Best
> Robert
> 
> PS: the ratio computers work for others. So it Must be an unfortunate 
> combination with your setup.



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Jef Driesen]

On 19-08-17 12:00, Benjamin wrote:

So, after a few trials, I'm getting the following in the subsurface.log file:

INFO: Open: name=00:13:43:0C:56:29

ERROR: Failed to open the serial port. [in ../../src/shearwater_common.c:46 
(shearwater_common_open)]


This shows exactly what the problem is! A bluetooth MAC address 
(00:13:43:0C:56:29) is being passed to the dc_serial_open() function. And of 
course that doesn't work!


Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Robert C. Helling]

Gregory,

I am currently traveling and only rarely have internet connectivity. 

> Am 20.08.2017 um 10:58 schrieb Gregory Sin :
> 
> unable to run that test version due to immediate crash on both Mac).

I tried the latest test version and have no problem to run it. Upon crashing, 
the mac should offer to send a crash report (to apple not us). Could you please 
copy and paste that report so we can try to figure out what is going on?

Best
Robert

PS: the ratio computers work for others. So it Must be an unfortunate 
combination with your setup. 
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Gregory Sin]

In my case it just crashes.. I mean that version.
Mac data is in the file.

On 19 Aug, 2017, at 18:00, Benjamin  wrote:

> So, after a few trials, I'm getting the following in the subsurface.log file:
> INFO: Open: name=00:13:43:0C:56:29
> 
> ERROR: Failed to open the serial port. [in ../../src/shearwater_common.c:46 
> (shearwater_common_open)]
> 
> Currently running Macos 10.13 Beta (17A344b) (updated since my last email). 
> Running Subsurface 4.6.4-709-gd77de11a1d2e from the "test" folder on the 
> offical download site.
> 
> When using the latest version from the git server, compiling against Qt 5.9.1 
> using the -build-deps switch, I get the exact same error in the log file.
> 
> I'm lost as to how to proceed from here :(
> 
> 
> 
> Benjamin
> 
> 
> On 18 August 2017 at 09:32, Benjamin  wrote:
> Good morning
> I just checked with the latest version in test (709), and on Macos version 
> 10.13 Beta (17A330h), I still get the "Insufficient permissions" when trying 
> to download from my Petrel 2.
> I'll do another download with a log later on today and hopefully will be able 
> to say something slightly more useful thanmy current "I can't see what is 
> wrong"
> Benjamin
> 
> On 18 August 2017 at 03:04, Gregory Sin  wrote:
> Dear Robert,
> 
> I tried last version Subsurface-4.6.4-709-gd77de11a1d2e , but it crashes on 
> startup, see screen attached.
> Was no such things with 4.6.4 release.
> 
> Can you help?  Please.
> 
> thanks
> Gregory
> 
> On 16 Aug, 2017, at 16:32, Robert Helling  wrote:
> 
>> Gregory,
>> 
>>> On 16. Aug 2017, at 10:15, Gregory Sin  wrote:
>>> 
>>> Dear Miika, gentlemen
>>> 
>>> Actually here is 2 problems.
>>> One is no connectivity with DEEP (via BT or USB) and second is lack of 
>>> configuration functionality for iX3M computers.
>>> 
>>> May be I can start from main problem- connectivity.
>>> 
>>> Mac 10.9.5
>>> iX3M DEEP Gps APOS 4.0.26/013 (works well with Ratio SW via USB).
>>> 
>>> CONNECTIVITY
>>> 
>>> Perhaps screens saying more than words.
>>> In case of BT, Mac and DEEP are paired and connected.
>>> In case of USB you can see USB0 interface availability.
>>> Of course computer is in PC mode and showing CONNECTED in case of BT.
>> 
>> The problem is that the error message about „Insufficient privileges“ 
>> actually only means „there is a problem, I cannot talk to the device“. But 
>> we recently fixed some problems regarding BT connectivity on Macs (which at 
>> least solved a problem for my mac talking to an OSTC), so unless you are 
>> already doing that, you should try with the latest version from 
>> http://subsurface-divelog.org/downloads/test/
>> 
>>> 
>>> CONFIGURATION
>>> 
>>> To my understanding this feature not yet implemented?
>>> At least computer is not visible (USB/BT) on that screen.
>>> Any attempt to press CONNECT button returned w/o any reaction.
>>> 
>>> Last week I was asking if SS and RATIO can be used together, I think Robert 
>>> said it is ok.
>>> Appreciate if you may guide me what went wrong on my side. I will follow.
>>> 
>>> Please accept my thanks for your kind effort and time.
>> 
>> Indeed, configuring dive computers in Subsurface is so far only implemented 
>> for OSTCs and Suuntos (as you can see from the device selection on the left).
>> 
>> Best
>> Robert
>> 
> 
> 
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Benjamin]

So, after a few trials, I'm getting the following in the subsurface.log
file:

INFO: Open: name=00:13:43:0C:56:29

ERROR: Failed to open the serial port. [in ../../src/shearwater_common.c:46
(shearwater_common_open)]

Currently running Macos 10.13 Beta (17A344b) (updated since my last email).
Running Subsurface 4.6.4-709-gd77de11a1d2e from the "test" folder on the
offical download site.

When using the latest version from the git server, compiling against Qt
5.9.1 using the -build-deps switch, I get the exact same error in the log
file.

I'm lost as to how to proceed from here :(


Benjamin

On 18 August 2017 at 09:32, Benjamin  wrote:

> Good morning
> I just checked with the latest version in test (709), and on Macos
> version 10.13 Beta (17A330h), I still get the "Insufficient permissions"
> when trying to download from my Petrel 2.
> I'll do another download with a log later on today and hopefully will be
> able to say something slightly more useful than my current "I can't see
> what is wrong"
> Benjamin
>
> On 18 August 2017 at 03:04, Gregory Sin  wrote:
>
>> Dear Robert,
>>
>> I tried last version Subsurface-4.6.4-709-gd77de11a1d2e , but it crashes
>> on startup, see screen attached.
>> Was no such things with 4.6.4 release.
>>
>> Can you help?  Please.
>>
>> thanks
>> Gregory
>>
>> On 16 Aug, 2017, at 16:32, Robert Helling  wrote:
>>
>> Gregory,
>>
>> On 16. Aug 2017, at 10:15, Gregory Sin  wrote:
>>
>> Dear Miika, gentlemen
>>
>> Actually here is 2 problems.
>> One is no connectivity with DEEP (via BT or USB) and second is lack of
>> configuration functionality for iX3M computers.
>>
>> May be I can start from main problem- connectivity.
>>
>> Mac 10.9.5
>> iX3M DEEP Gps APOS 4.0.26/013 (works well with Ratio SW via USB).
>>
>> CONNECTIVITY
>>
>> Perhaps screens saying more than words.
>>
>> In case of BT, Mac and DEEP are paired and connected.
>> In case of USB you can see USB0 interface availability.
>> Of course computer is in PC mode and showing CONNECTED in case of BT.
>>
>>
>> The problem is that the error message about „Insufficient privileges“
>> actually only means „there is a problem, I cannot talk to the device“. But
>> we recently fixed some problems regarding BT connectivity on Macs (which at
>> least solved a problem for my mac talking to an OSTC), so unless you are
>> already doing that, you should try with the latest version from
>> http://subsurface-divelog.org/downloads/test/
>>
>>
>> CONFIGURATION
>>
>> To my understanding this feature not yet implemented?
>> At least computer is not visible (USB/BT) on that screen.
>> Any attempt to press CONNECT button returned w/o any reaction.
>>
>> Last week I was asking if SS and RATIO can be used together, I think
>> Robert said it is ok.
>> Appreciate if you may guide me what went wrong on my side. I will follow.
>>
>> Please accept my thanks for your kind effort and time.
>>
>>
>> Indeed, configuring dive computers in Subsurface is so far only
>> implemented for OSTCs and Suuntos (as you can see from the device selection
>> on the left).
>>
>> Best
>> Robert
>>
>>
>>
>> ___
>> subsurface mailing list
>> subsurface@subsurface-divelog.org
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>>
>>
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Benjamin]

Good morning
I just checked with the latest version in test (709), and on Macos
version 10.13 Beta (17A330h), I still get the "Insufficient permissions"
when trying to download from my Petrel 2.
I'll do another download with a log later on today and hopefully will be
able to say something slightly more useful than my current "I can't see
what is wrong"
Benjamin

On 18 August 2017 at 03:04, Gregory Sin  wrote:

> Dear Robert,
>
> I tried last version Subsurface-4.6.4-709-gd77de11a1d2e , but it crashes
> on startup, see screen attached.
> Was no such things with 4.6.4 release.
>
> Can you help?  Please.
>
> thanks
> Gregory
>
> On 16 Aug, 2017, at 16:32, Robert Helling  wrote:
>
> Gregory,
>
> On 16. Aug 2017, at 10:15, Gregory Sin  wrote:
>
> Dear Miika, gentlemen
>
> Actually here is 2 problems.
> One is no connectivity with DEEP (via BT or USB) and second is lack of
> configuration functionality for iX3M computers.
>
> May be I can start from main problem- connectivity.
>
> Mac 10.9.5
> iX3M DEEP Gps APOS 4.0.26/013 (works well with Ratio SW via USB).
>
> CONNECTIVITY
>
> Perhaps screens saying more than words.
>
> In case of BT, Mac and DEEP are paired and connected.
> In case of USB you can see USB0 interface availability.
> Of course computer is in PC mode and showing CONNECTED in case of BT.
>
>
> The problem is that the error message about „Insufficient privileges“
> actually only means „there is a problem, I cannot talk to the device“. But
> we recently fixed some problems regarding BT connectivity on Macs (which at
> least solved a problem for my mac talking to an OSTC), so unless you are
> already doing that, you should try with the latest version from
> http://subsurface-divelog.org/downloads/test/
>
>
> CONFIGURATION
>
> To my understanding this feature not yet implemented?
> At least computer is not visible (USB/BT) on that screen.
> Any attempt to press CONNECT button returned w/o any reaction.
>
> Last week I was asking if SS and RATIO can be used together, I think
> Robert said it is ok.
> Appreciate if you may guide me what went wrong on my side. I will follow.
>
> Please accept my thanks for your kind effort and time.
>
>
> Indeed, configuring dive computers in Subsurface is so far only
> implemented for OSTCs and Suuntos (as you can see from the device selection
> on the left).
>
> Best
> Robert
>
>
>
> ___
> subsurface mailing list
> subsurface@subsurface-divelog.org
> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
>
>
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Jef Driesen]

On 2017-08-16 11:46, Anton Lundin wrote:

Step one would be some documentation. How to read and write settings
to the computer. Whats the protocol? Which settings are there and how 
to

interpret the data.
The information doesn't need to be "public", but the code we write 
based
on it will be. As far as I know there is only one manufacturer which 
has

public documentation, and thats HeinrichsWeikamp. We have "non public"
documentation from more manufacturers, but its best if Ratio would be
willing to publish their documentation.


I already have access to official documentation from Ratio/Divesystem. 
But it only contains information for downloading the dives (which I have 
implemented). It does not contain any info on settings or anything else.



Step two would be a device to test it against. It doesn't need to be a
"full production" device, it could just as well be a device that failed
QA for reasons irellevant to program and test the code against. IE
consmetic defects, a couple of dead pixels on the display, uneven
backlight or such.


I don't have a test device either.

Jef
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Davide DB]

On Aug 16, 2017 11:46 AM, "Anton Lundin"  wrote:




Step one would be some documentation. How to read and write settings
to the computer. Whats the protocol? Which settings are there and how to
interpret the data.
The information doesn't need to be "public", but the code we write based
on it will be. As far as I know there is only one manufacturer which has
public documentation, and thats HeinrichsWeikamp. We have "non public"
documentation from more manufacturers, but its best if Ratio would be
willing to publish their documentario



Hi Anton,

Months ago I wrote to them to get documentation about their dc (they are
Italian) and they replied to me that they are pleased to give us support
but they asked to be officially contacted by a Subsurface representative.
I stepped back because someone here (I have to dig through the archives)
wrote that developers here already have a contact with them.
If you like I can just forward you and Dirk my email exchange and then you
will continue with them.

Bye
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Gregory Sin]

Dear Anton,

Ok, let me see what I can do with Step 1 :)
I will try to help.

On 16 Aug, 2017, at 17:46, Anton Lundin  wrote:

> On 16 August, 2017 - Gregory Sin wrote:
> 
>> Dear Anton
>> 
>> Could you please guide me what data do you need from RATIO.
>> We are their distributors and have a good relation with them.
>> Personally, I think this product is very well made and gaining more and more 
>> popularity.
>> It could be good match between SubSurf and Ratio, I think.
> 
> Step zero. Find one or more people with the time to get it done.
> Subsurface is written by a group of volunteers, doing this in their free
> time. I could probably eventually get it done, but there's no guarantee
> when.
> 
> 
> Step one would be some documentation. How to read and write settings
> to the computer. Whats the protocol? Which settings are there and how to
> interpret the data.
> The information doesn't need to be "public", but the code we write based
> on it will be. As far as I know there is only one manufacturer which has
> public documentation, and thats HeinrichsWeikamp. We have "non public"
> documentation from more manufacturers, but its best if Ratio would be
> willing to publish their documentation.
> 
> 
> Step two would be a device to test it against. It doesn't need to be a
> "full production" device, it could just as well be a device that failed
> QA for reasons irellevant to program and test the code against. IE
> consmetic defects, a couple of dead pixels on the display, uneven
> backlight or such.
> 
> 
> 
> 
> 
> //Anton
> 
> 
> --
> Anton Lundin  +46702-161604



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Anton Lundin]

On 16 August, 2017 - Gregory Sin wrote:

> Dear Anton
> 
> Could you please guide me what data do you need from RATIO.
> We are their distributors and have a good relation with them.
> Personally, I think this product is very well made and gaining more and more 
> popularity.
> It could be good match between SubSurf and Ratio, I think.

Step zero. Find one or more people with the time to get it done.
Subsurface is written by a group of volunteers, doing this in their free
time. I could probably eventually get it done, but there's no guarantee
when.


Step one would be some documentation. How to read and write settings
to the computer. Whats the protocol? Which settings are there and how to
interpret the data.
The information doesn't need to be "public", but the code we write based
on it will be. As far as I know there is only one manufacturer which has
public documentation, and thats HeinrichsWeikamp. We have "non public"
documentation from more manufacturers, but its best if Ratio would be
willing to publish their documentation.


Step two would be a device to test it against. It doesn't need to be a
"full production" device, it could just as well be a device that failed
QA for reasons irellevant to program and test the code against. IE
consmetic defects, a couple of dead pixels on the display, uneven
backlight or such.





//Anton


-- 
Anton Lundin+46702-161604
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Gregory Sin]

Im trying to install test version Subsurface-4.6.4-709-gd77de11a1d2e.dmg
However, installer saying file is corrupted. See attached.

Please help.


On 16 Aug, 2017, at 16:32, Robert Helling  wrote:

> Gregory,
> 
>> On 16. Aug 2017, at 10:15, Gregory Sin  wrote:
>> 
>> Dear Miika, gentlemen
>> 
>> Actually here is 2 problems.
>> One is no connectivity with DEEP (via BT or USB) and second is lack of 
>> configuration functionality for iX3M computers.
>> 
>> May be I can start from main problem- connectivity.
>> 
>> Mac 10.9.5
>> iX3M DEEP Gps APOS 4.0.26/013 (works well with Ratio SW via USB).
>> 
>> CONNECTIVITY
>> 
>> Perhaps screens saying more than words.
>> In case of BT, Mac and DEEP are paired and connected.
>> In case of USB you can see USB0 interface availability.
>> Of course computer is in PC mode and showing CONNECTED in case of BT.
> 
> The problem is that the error message about „Insufficient privileges“ 
> actually only means „there is a problem, I cannot talk to the device“. But we 
> recently fixed some problems regarding BT connectivity on Macs (which at 
> least solved a problem for my mac talking to an OSTC), so unless you are 
> already doing that, you should try with the latest version from 
> http://subsurface-divelog.org/downloads/test/
> 
>> 
>> CONFIGURATION
>> 
>> To my understanding this feature not yet implemented?
>> At least computer is not visible (USB/BT) on that screen.
>> Any attempt to press CONNECT button returned w/o any reaction.
>> 
>> Last week I was asking if SS and RATIO can be used together, I think Robert 
>> said it is ok.
>> Appreciate if you may guide me what went wrong on my side. I will follow.
>> 
>> Please accept my thanks for your kind effort and time.
> 
> Indeed, configuring dive computers in Subsurface is so far only implemented 
> for OSTCs and Suuntos (as you can see from the device selection on the left).
> 
> Best
> Robert
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: RATIO iX3M DEEP computers compatibility and connection/configuration problem

[Anton Lundin]

On 16 August, 2017 - Robert Helling wrote:

> > On 16. Aug 2017, at 10:15, Gregory Sin  wrote:
> > 
> > CONFIGURATION
> > 
> > To my understanding this feature not yet implemented?
> > At least computer is not visible (USB/BT) on that screen.
> > Any attempt to press CONNECT button returned w/o any reaction.
> > 
> > Last week I was asking if SS and RATIO can be used together, I think Robert 
> > said it is ok.
> > Appreciate if you may guide me what went wrong on my side. I will follow.
> > 
> > Please accept my thanks for your kind effort and time.
> 
> Indeed, configuring dive computers in Subsurface is so far only implemented 
> for OSTCs and Suuntos (as you can see from the device selection on the left).

Its even more specific than that. Its just implemented for certain
OSTC models, and one Suunto model, the old Vyper series.


Its because those are the ones we have either documentation for (OSTC's)
or good reverse engineered information (Suunto Vyper), and I have access
to those devices and can test the code.


It's always going to be a selective subset of computer models which we
can configure and firmware update.


If anyone else have information about other computers and are willing to
spend some time with it, its just a bunch of coding to add support for
more computer models.


//Anton


-- 
Anton Lundin+46702-161604
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface