Re: Bluetooth blues solved (sort of)

2015-10-29 Thread Ivan Wagner
>> The problem I encountered is OS-specific to the Ubuntu bluetooth >> interface. After loading external software and not using the built-in >> Ubuntu tool, I am able to download the Petrel reliably. Dear Willem, I'm facting similar issues. What external software are you actually using at the

Re: Bluetooth blues solved (sort of)

2015-10-29 Thread Willem Ferguson
On 29/10/2015 09:19, Ivan Wagner wrote: Dear Willem, I'm facting similar issues. What external software are you actually using at the moment? I'm on ubuntu LTS 14.04. Thank you for the info, ivan The problem I encountered is OS-specific to the Ubuntu bluetooth interface. After loading

Bluetooth blues

2015-10-23 Thread Willem Ferguson
I try to download from a Petrel 2 using Bluetooth, but encounter problems. I do: Import from dive computer -> Choose Bluetooth download scan When I rightclick to pair I get error: local device error: Pairing error (see attached image) Below is the terminal output.

Re: Bluetooth blues

2015-10-23 Thread Miika Turkia
try pairing using OS tools if u need pin code, then dl should work miika > On 23 Oct 2015, at 11:57, Willem Ferguson > wrote: > > I try to download from a Petrel 2 using Bluetooth, but encounter problems. > > I do: > Import from dive computer -> Choose

Re: Bluetooth blues

2015-10-23 Thread Claudiu Olteanu
> I was under the impression that the Petrel 2 and the Uemis were your test > devices when coding the Bluetooth interface and that access to the Petrel 2 > has more or less been sorted out?? Am I mistaken? I have only two devices: OSTCs and OSTC 2. Rick helped me to test the connectivity with a

Re: Bluetooth blues

2015-10-23 Thread Rick Walsh
On 24 Oct 2015 00:51, "Claudiu Olteanu" wrote: > > > I was under the impression that the Petrel 2 and the Uemis were your test > > devices when coding the Bluetooth interface and that access to the Petrel 2 > > has more or less been sorted out?? Am I mistaken?

Re: Bluetooth blues

2015-10-23 Thread Anton Lundin
I took a look at qt parring interfaces, shouldn't there be a way to test a couple of standard parring codes? //Anton On October 23, 2015 12:02:19 PM GMT+02:00, Claudiu Olteanu wrote: >Hi there, > >If your remote device requests a custom PIN code for the

Re: Bluetooth blues

2015-10-23 Thread Claudiu Olteanu
Unfortunately the API doesn't allow you to specify a PIN code. There is a bug [1] reported and also a partial implementation for an agent[2] which could be used to pass the PIN code, [1] - https://bugreports.qt.io/browse/QTBUG-42740 [2] - https://codereview.qt-project.org/#/c/85595/ On Fri, Oct

Bluetooth blues

2015-10-23 Thread Claudiu Olteanu
Hi there, If your remote device requests a custom PIN code for the pairing process, your should pair the devices using a different tool. Currently QtBluetooth doesn't have support for custom PIN codes. A workaround could be to use bluetoothctl, register an agent using the following commands,

Bluetooth blues

2015-09-09 Thread Willem Ferguson
I was trying to document the Bluetooth interface using a Shearwater Petrel. Below is the console output of the three attempts. I had three sessions: 1) Ubuntu 15.04 2) Fedora 22 3) Fedora 22 On Ubuntu, the first four of 37 dives were downloaded. On Fedora it resulted in a segfault both times

Re: Bluetooth blues

2015-09-09 Thread Willem Ferguson
On 09/09/2015 16:56, Claudiu Olteanu wrote: Hi there, It seems that it doesn't use our custom implementation for the open method. It should use *shearwater_common_custom_open *to open the device. This means that your libdivecomputer version is incorrect or the SSRF_CUSTOM_SERIAL wasn't cached