Re: Device mount point is disabled (and fixed to wrong device)

2018-02-03 Thread Rob Mason 
Hi Jef

Yes, I think I may be having issues with irda and Mint rather than
Subsurface.  Here's what I can see from dmesg:

usb 2-1.2: new full-speed USB device number 3 using ehci-pci
usb 2-1.2: New USB device found, idVendor=066f, idProduct=4200
usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.2: Product:  IrDA/USB Bridge
usb 2-1.2: Manufacturer:  Sigmatel Inc
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver option
usbserial: USB Serial support registered for GSM modem (1-port)
option 2-1.2:1.0: GSM modem (1-port) converter detected
usb 2-1.2: GSM modem (1-port) converter now attached to ttyUSB0
usbcore: registered new interface driver stir4200

Here's the libdivecomputer logfile:

Subsurface: v4.7.6, built with libdivecomputer
v0.7.0-devel-Subsurface-branch (8ae735a4d70307ebe2a42d315697f02ce71dbe88)
ERROR: No dive computer found. [in uwatec_smart.c:182
(uwatec_smart_device_open)]

I assume subsurface needs to find irda0??




On 3 February 2018 at 20:00, Jef Driesen  wrote:

> On 03-02-18 18:05, Berthold Stoeger wrote:
>
>> On Samstag, 3. Februar 2018 17:46:10 CET Rob Mason wrote:
>>
>>> Hi Berthold - the subgear is irda, not bluetooth. It has worked
>>> previously
>>> on older versions, but unable to connect on 4.7.6-1 on Mint Linux 18.3.
>>> --
>>>
>>
>> Yes I know. Nevertheless, the "interface consistency fix" in commit
>> d23bd46
>> enables the device field only for serial transport.
>>
>> To my defense - I just copied old buggy code, but made it more
>> noticeable. I
>> pushed a fix to github. If you can compile from source, you can use this.
>> If
>> not, there is a workaround: Select a dive computer with serial transport
>> (I
>> think the XP-Air is), change the device and then go back to the XP-10.
>> This
>> should be saved to the preferences, so you only have to do it once (until
>> you
>> change dive computer).
>>
>
> The reason why the dropdown is disabled is because IrDA communication
> doesn't use a device node at all. Libdivecomputer will automatically
> discover the IrDA device address. So it doesn't matter what is shown in the
> dropdown box, because it's not used for anything.
>
> If the download fails because no dive computer is found, that means the
> discovery did not found any IrDA device (or at least not one that matches a
> known dive computer). Enable the libdivecomputer logfile checkbox and send
> us the log. That should tell us what is going on.
>
> Jef
>
> ___
> 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: Device mount point is disabled (and fixed to wrong device)

2018-02-03 Thread Jef Driesen 

On 03-02-18 18:05, Berthold Stoeger wrote:

On Samstag, 3. Februar 2018 17:46:10 CET Rob Mason wrote:

Hi Berthold - the subgear is irda, not bluetooth. It has worked previously
on older versions, but unable to connect on 4.7.6-1 on Mint Linux 18.3. --


Yes I know. Nevertheless, the "interface consistency fix" in commit  d23bd46
enables the device field only for serial transport.

To my defense - I just copied old buggy code, but made it more noticeable. I
pushed a fix to github. If you can compile from source, you can use this. If
not, there is a workaround: Select a dive computer with serial transport (I
think the XP-Air is), change the device and then go back to the XP-10. This
should be saved to the preferences, so you only have to do it once (until you
change dive computer).


The reason why the dropdown is disabled is because IrDA communication doesn't 
use a device node at all. Libdivecomputer will automatically discover the IrDA 
device address. So it doesn't matter what is shown in the dropdown box, because 
it's not used for anything.


If the download fails because no dive computer is found, that means the 
discovery did not found any IrDA device (or at least not one that matches a 
known dive computer). Enable the libdivecomputer logfile checkbox and send us 
the log. That should tell us what is going on.


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

Re: Device mount point is disabled (and fixed to wrong device)

2018-02-03 Thread Rob Mason 
Hi Berthold - the subgear is irda, not bluetooth. It has worked previously on 
older versions, but unable to connect on 4.7.6-1 on Mint Linux 18.3.
--
Rob Mason
07770 578764

On 3 February 2018 16:43:14 GMT+00:00, Berthold Stoeger 
 wrote:

Hi Rob,

On Samstag, 3. Februar 2018 12:57:18 CET Rob Mason wrote:
 Hi,

 I'm running Version 4.7.6 on linux Mint 18.3 - using a Subgear XP-10
 (infrared).

 My infrared adapter is found on /dev/ttyUSB1, but the 'Device or Mount
 Point' drop down list is disabled and fixed to /dev/ttyS30. Dive computer
 is not found. How can I changed this to /dev/ttyUSB1 ???

That looks like a change concerning the Bluetooth interface, which I made some
time ago. :( I'm looking into it.

Berthold

Acasta Ltd - A Crown Commercial Service Supplier. CyberEssentials Certified 
QGCE013.
Registered in England 6619191. 42 Pitt Street, Barnsley, S70 1BB. VAT 
Registered 934 6797 75.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Device mount point is disabled (and fixed to wrong device)

2018-02-03 Thread Rob Mason 
Thanks - will give that a try.
--
Rob Mason
07770 578764

On 3 February 2018 17:05:00 GMT+00:00, Berthold Stoeger 
 wrote:

Hi,

On Samstag, 3. Februar 2018 17:46:10 CET Rob Mason wrote:
 Hi Berthold - the subgear is irda, not bluetooth. It has worked previously
 on older versions, but unable to connect on 4.7.6-1 on Mint Linux 18.3. --

Yes I know. Nevertheless, the "interface consistency fix" in commit  d23bd46
enables the device field only for serial transport.

To my defense - I just copied old buggy code, but made it more noticeable. I
pushed a fix to github. If you can compile from source, you can use this. If
not, there is a workaround: Select a dive computer with serial transport (I
think the XP-Air is), change the device and then go back to the XP-10. This
should be saved to the preferences, so you only have to do it once (until you
change dive computer).

Berthold

 Rob Mason
 07770 578764

 On 3 February 2018 16:43:14 GMT+00:00, Berthold Stoeger
  wrote:

 Hi Rob,

 On Samstag, 3. Februar 2018 12:57:18 CET Rob Mason wrote:
  Hi,

  I'm running Version 4.7.6 on linux Mint 18.3 - using a Subgear XP-10
  (infrared).

  My infrared adapter is found on /dev/ttyUSB1, but the 'Device or Mount
  Point' drop down list is disabled and fixed to /dev/ttyS30. Dive computer
  is not found. How can I changed this to /dev/ttyUSB1 ???

 That looks like a change concerning the Bluetooth interface, which I made
 some time ago. :( I'm looking into it.

 Berthold

 Acasta Ltd - A Crown Commercial Service Supplier. CyberEssentials Certified
 QGCE013. Registered in England 6619191. 42 Pitt Street, Barnsley, S70 1BB.
 VAT Registered 934 6797 75.



Acasta Ltd - A Crown Commercial Service Supplier. CyberEssentials Certified 
QGCE013.
Registered in England 6619191. 42 Pitt Street, Barnsley, S70 1BB. VAT 
Registered 934 6797 75.
___
subsurface mailing list
subsurface@subsurface-divelog.org
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Re: Device mount point is disabled (and fixed to wrong device)

2018-02-03 Thread Berthold Stoeger 
Hi,

On Samstag, 3. Februar 2018 17:46:10 CET Rob Mason wrote:
> Hi Berthold - the subgear is irda, not bluetooth. It has worked previously
> on older versions, but unable to connect on 4.7.6-1 on Mint Linux 18.3. --

Yes I know. Nevertheless, the "interface consistency fix" in commit  d23bd46 
enables the device field only for serial transport.

To my defense - I just copied old buggy code, but made it more noticeable. I 
pushed a fix to github. If you can compile from source, you can use this. If 
not, there is a workaround: Select a dive computer with serial transport (I 
think the XP-Air is), change the device and then go back to the XP-10. This 
should be saved to the preferences, so you only have to do it once (until you 
change dive computer).

Berthold

> Rob Mason
> 07770 578764
> 
> On 3 February 2018 16:43:14 GMT+00:00, Berthold Stoeger
>  wrote:
> 
> Hi Rob,
> 
> On Samstag, 3. Februar 2018 12:57:18 CET Rob Mason wrote:
>  Hi,
> 
>  I'm running Version 4.7.6 on linux Mint 18.3 - using a Subgear XP-10
>  (infrared).
> 
>  My infrared adapter is found on /dev/ttyUSB1, but the 'Device or Mount
>  Point' drop down list is disabled and fixed to /dev/ttyS30. Dive computer
>  is not found. How can I changed this to /dev/ttyUSB1 ???
> 
> That looks like a change concerning the Bluetooth interface, which I made
> some time ago. :( I'm looking into it.
> 
> Berthold
> 
> Acasta Ltd - A Crown Commercial Service Supplier. CyberEssentials Certified
> QGCE013. Registered in England 6619191. 42 Pitt Street, Barnsley, S70 1BB.
> VAT Registered 934 6797 75.


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

Re: Device mount point is disabled (and fixed to wrong device)

2018-02-03 Thread Berthold Stoeger 
Hi Rob,

On Samstag, 3. Februar 2018 12:57:18 CET Rob Mason wrote:
> Hi,
> 
> I'm running Version 4.7.6 on linux Mint 18.3 - using a Subgear XP-10
> (infrared).
> 
> My infrared adapter is found on /dev/ttyUSB1, but the 'Device or Mount
> Point' drop down list is disabled and fixed to /dev/ttyS30. Dive computer
> is not found. How can I changed this to /dev/ttyUSB1 ???

That looks like a change concerning the Bluetooth interface, which I made some 
time ago. :( I'm looking into it.

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

Device mount point is disabled (and fixed to wrong device)

2018-02-03 Thread Rob Mason 
Hi,

I'm running Version 4.7.6 on linux Mint 18.3 - using a Subgear XP-10
(infrared).

My infrared adapter is found on /dev/ttyUSB1, but the 'Device or Mount
Point' drop down list is disabled and fixed to /dev/ttyS30. Dive computer
is not found. How can I changed this to /dev/ttyUSB1 ???

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