RE: Atmospheric pressure for Ratio iX3M

[Steve]

-Original Message-
From: Jef Driesen [mailto:j...@libdivecomputer.org] 
Sent: Thursday, 17 August 2017 1:46 AM
To: Robert Helling 
Cc: subsurface@subsurface-divelog.org; Steve

Subject: Re: Atmospheric pressure for Ratio iX3M

On 2017-07-13 10:11, Robert Helling wrote:
> we have a user report on the forum that gets incredibly low SAC rates 
> for dives downloaded from a newly acquired Ratio iX3M. Looking at the 
> xml I see there surface pressure values of above 9bar. Does anybody 
> have an idea how those come about? Maybe there is something wrong in 
> the parser.

According to the documentation, the atmospheric pressure is stored in
millibar. That appears to be correct for the older models (Orca and iDive).
But for all the newer models (iX3M) the result is indeed a factor 10 too
large. Probably a mistake in the documentation (or a bug in the firmware).
I'll take care of fixing that.

Jef


While you are making the surface pressure change can you also add the fixed
set point data.
I am manually adding the initial fixed setpoint ppo2 to the xml file and I
also don't think that the setpoint changes get added.
You should have my ix3m-reb data from our last testing that is using fixed
setpoint and without.

Steve

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

Re: Adding a DC for mobile download

[Anton Lundin]

On 21 August, 2017 - Dirk Hohndel wrote:

> 
> > On Aug 21, 2017, at 8:50 AM, John Van Ostrand  wrote:
> > 
> > I've been meaning to test the Cochran computers on  my android device for 
> > download but I can't see it on the list of vendors in the latest app.
> > 
> > It uses FTDI and has the same vid (1027) and pid (24577) as some other DCs. 
> > I've tried finding where it might be filtered in the code and it's not 
> > apparent. 
The vid / pid is the ftdi "standard" ones so they are already added to
the manifest. Android should suggest that you open Subsurface when you
plug in the device.

> > 
> > How do I add it?
> 
> Right now this is done by adding a comment in the src/descriptor.c file in 
> libdivecomputer and then running a tool that creates our lists in 
> core/downloadfromdcthread.cpp:
> scripts/dcTransport.pl
> 
> > Secondly, is it likely to work? All current models use two different baud 
> > rates.  They use 9600 for issuing commands and for small reads but after 
> > issuing a read command for dive data it switches to either 115200 
> > (Commander) or ~800,000 (EMC) to receive data. It switches back to 9600 
> > afterwards. 
> 
> That I don't know.

Yepp. It should work. You can compile the desktop with FTDISUPPORT=ON
and test it there. Just write the magic string ftdi in the "Device or
mount point" and click download. Its easier to debug there.


I've tested the ftdi serial code against a OSTC3 which runs 115200 baud
and a Suunto Vyper which runs at 9600 baud. There might be a issue with
the "extensive" switching but "regular" switching works.


//Anton


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

Re: Adding a DC for mobile download

[Dirk Hohndel]

> On Aug 21, 2017, at 8:50 AM, John Van Ostrand  wrote:
> 
> I've been meaning to test the Cochran computers on  my android device for 
> download but I can't see it on the list of vendors in the latest app.
> 
> It uses FTDI and has the same vid (1027) and pid (24577) as some other DCs. 
> I've tried finding where it might be filtered in the code and it's not 
> apparent. 
> 
> How do I add it?

Right now this is done by adding a comment in the src/descriptor.c file in 
libdivecomputer and then running a tool that creates our lists in 
core/downloadfromdcthread.cpp:
scripts/dcTransport.pl

> Secondly, is it likely to work? All current models use two different baud 
> rates.  They use 9600 for issuing commands and for small reads but after 
> issuing a read command for dive data it switches to either 115200 (Commander) 
> or ~800,000 (EMC) to receive data. It switches back to 9600 afterwards. 

That I don't know.

/D

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

Adding a DC for mobile download

[John Van Ostrand]

I've been meaning to test the Cochran computers on  my android device for
download but I can't see it on the list of vendors in the latest app.

It uses FTDI and has the same vid (1027) and pid (24577) as some other DCs.
I've tried finding where it might be filtered in the code and it's not
apparent.

How do I add it?

Secondly, is it likely to work? All current models use two different baud
rates.  They use 9600 for issuing commands and for small reads but after
issuing a read command for dive data it switches to either 115200
(Commander) or ~800,000 (EMC) to receive data. It switches back to 9600
afterwards.


-- 
John Van Ostrand
At large on sabbatical
___
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