Incorrect tank info.

[Jef Driesen]

On 24-08-12 11:03, Jef Driesen wrote:
> What exactly happens if you set the device to air mode? Can you still
> configure the gasmixes, or is access to the gasmix settings 
> completely
> disabled? I'm just trying to understand the logic used by the device.
> Then we can fix the libdivecomputer code to match that logic.
>
> Based on the comments so far, this seems to be what is happening:
>
> if (air) {
>      Ignore the gasmix settings, and assume a single mix with air. 
> The
> gasmix settings retain their previous (non-air) values only as a
> convenience, so you don't have to adjust the settings for your next
> nitrox and/or multigas dive, but they are not used.
> } else {
>      Use the gasmix settings.
> }

I would like to fix this issue before the 0.2.0 release. I have 
attached a work-in-progress patch that needs some testing. I think it's 
correct for the older generation models (Vyper 2, D9, etc), but I 
suspect that for the newer models (Helo2, D4i, D6i, D9tx, etc) the gas 
model byte is stored at a different offset.

Normally I can easily test this kind of stuff myself, but for some 
reason the latest Suunto Dive Manager (SDM) doesn't accept arbitrary 
serial ports anymore. I guess there is some kind of check for the USB 
VID/PID, or the FTDI driver. I used to have a linux kernel module to 
emulate an FTDI usb-serial chip (using the usb gadget interface), but it 
doesn't compile anymore with recent kernels :-( So for now, I can't get 
my test data into SDM to confirm the patch is correct, and thus I need 
some testing with real hardware.

Jef
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wip_d9_gasmodel.patch
Type: text/x-patch
Size: 1623 bytes
Desc: not available
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20120919/6fc8f7a1/attachment.bin>