Re: Perdix AI import error
What about to try a x64 Windows compile? Sometimes there are less problems with compatibility layers using x64 apps on x64 OS. I don’t have the knowledge to do it, otherwise I would try. Il giorno dom 10 nov 2019 alle 17:32 Dirk Hohndel ha scritto: > > > On Nov 10, 2019, at 8:06 AM, Lubomir I. Ivanov > wrote: > > > > On Sun, 10 Nov 2019 at 12:17, Dean Murray wrote: > >> > >> I used a workaround for Bluetooth in Windows 10 and have never looked > back. I described it here > https://github.com/Subsurface-divelog/subsurface/issues/2117 > >> > > > > Dean, your method does not work for me and the Perdix AI. > > Correct, because your Perdix AI is BLE-only. > This workaround using a COM port only works for older BT-rfcomm > divecomputers. > > /D > > ___ > 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: Perdix AI import error
> On Nov 10, 2019, at 8:06 AM, Lubomir I. Ivanov wrote: > > On Sun, 10 Nov 2019 at 12:17, Dean Murray wrote: >> >> I used a workaround for Bluetooth in Windows 10 and have never looked back. >> I described it here >> https://github.com/Subsurface-divelog/subsurface/issues/2117 >> > > Dean, your method does not work for me and the Perdix AI. Correct, because your Perdix AI is BLE-only. This workaround using a COM port only works for older BT-rfcomm divecomputers. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Perdix AI import error
>> yes, OSTC+ got quite stable after the latest Windows 10 updates. >> the Perdix AI still has problems with the native backend. On Sun, 10 Nov 2019 at 12:08, tormento wrote: > > Which brand/model of BT dongle? > without a dongle. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Perdix AI import error
Which brand/model of BT dongle? Il giorno sab 9 nov 2019 alle ore 17:39 Lubomir I. Ivanov < neolit...@gmail.com> ha scritto: > On Sat, 9 Nov 2019 at 18:20, tormento wrote: > > > > OSTC uses BT LE as Perdix? > > > > yes, OSTC+ got quite stable after the latest Windows 10 updates. > the Perdix AI still has problems with the native backend. > > lubomir > -- > ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Perdix AI import error
On Sat, 9 Nov 2019 at 18:20, tormento wrote: > > OSTC uses BT LE as Perdix? > yes, OSTC+ got quite stable after the latest Windows 10 updates. the Perdix AI still has problems with the native backend. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Perdix AI import error
I am using the included dongle and I really don’t know which brand / model it is to find the updated driver. Windows uses a “generic BT” driver. OSTC uses BT LE as Perdix? Il giorno sab 9 nov 2019 alle 16:41 Lubomir I. Ivanov ha scritto: > > I tried whatever kind of trick. > > the un-pair, pair trick works for me. > make sure you have the latest BT chip drivers too. > > > I have no problem at all with Shearwater Cloud and that’s strange. > > The Shearwater Cloud is using a different Windows backend called Windows > RT. > Subsurface is using the native Windows backend. > > There is no way for us to fix that unless we re-write Subsurface as a > Universal Windows Platform app in C#, which is no-go. > Windows 10 needs to sort their flakiness for some chipsets on the > native backend. > > For instance the OSTC+ with latest Windows 10, connected fine each > time and does not need the un-pair, pair trick. > > lubomir > -- > > On Sat, 9 Nov 2019 at 17:28, tormento wrote: > > > > I tried whatever kind of trick. > > > > I have no problem at all with Shearwater Cloud and that’s strange. > > > > If a Windows issue, how can it be solved or worked around? > > > > Alberto > > > > P.S I’d like to know if other Perdix have same issues. > > > > Il giorno sab 9 nov 2019 alle 15:12 Lubomir I. Ivanov < > neolit...@gmail.com> ha scritto: > >> > >> on Windows, try unpairing and pairing the Perdix before each downlioad > >> from Subsurface. > >> the status of the device in the Control Panel should turn from Paired > >> to Connected if successful. > >> please note, this is a Windows issue and not a Subsurface issue. > >> > >> lubomir > >> -- > >> > >> On Mon, 4 Nov 2019 at 11:28, tormento wrote: > >> > > >> > Ok, I tried to download dive on another laptop with integrated BT > with or without dongle and don't work there too. > >> > > >> > In the meantime I have done it with newest Testflight build on iOS > but I'd like to be able to download from Windows version too. > >> > > >> > Alberto > >> > > >> > Il giorno sab 2 nov 2019 alle ore 07:48 Jef Driesen < > j...@libdivecomputer.org> ha scritto: > >> >> > >> >> On 2/11/19 07:41, tormento wrote: > >> >> > I am getting errors while importing dives from Perdix AI with its > BT dongle (I > >> >> > don't hava any other to try) while it's own software can import > dives correctly. > >> >> > > >> >> > I select choose Bluetooth mode, find the Perdix and save. > >> >> > > >> >> > When I try to import, I get: > >> >> > > >> >> > Connecting to BLE device > >> >> > Connecting > >> >> > > >> >> > Then a error windows pops up with "Dive data import error". > >> >> > > >> >> > image.png > >> >> > > >> >> > The log tells: > >> >> > > >> >> > Subsurface: v4.9.3-242-g9c8fbe494db2, built with libdivecomputer > >> >> > v0.7.0-devel-Subsurface-NG > (426a39fc7378cac3f5b1d3983be38d56ab526e78) > >> >> > INFO: Open: transport=32 > >> >> > INFO: Configure: baudrate=115200, databits=8, parity=0, > stopbits=0, flowcontrol=0 > >> >> > INFO: Timeout: value=3000 > >> >> > INFO: Sleep: value=300 > >> >> > INFO: Purge: direction=3 > >> >> > INFO: Write: size=11, data=0100FF0105002E902000C0 > >> >> > > >> >> > No .bin is generated. > >> >> > >> >> Uncheck the "Save libdivecomputer dumpfile" checkbox. The Shearwater > Perdix AI > >> >> communication protocol doesn't support memory dumps. Trying to > download a memory > >> >> dump will always fail with DC_STATUS_UNSUPPORTED. > >> >> > >> >> For the diagnostics purposes, the log file is sufficient for these > models. > >> >> > >> >> 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 > ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Perdix AI import error
> I tried whatever kind of trick. the un-pair, pair trick works for me. make sure you have the latest BT chip drivers too. > I have no problem at all with Shearwater Cloud and that’s strange. The Shearwater Cloud is using a different Windows backend called Windows RT. Subsurface is using the native Windows backend. There is no way for us to fix that unless we re-write Subsurface as a Universal Windows Platform app in C#, which is no-go. Windows 10 needs to sort their flakiness for some chipsets on the native backend. For instance the OSTC+ with latest Windows 10, connected fine each time and does not need the un-pair, pair trick. lubomir -- On Sat, 9 Nov 2019 at 17:28, tormento wrote: > > I tried whatever kind of trick. > > I have no problem at all with Shearwater Cloud and that’s strange. > > If a Windows issue, how can it be solved or worked around? > > Alberto > > P.S I’d like to know if other Perdix have same issues. > > Il giorno sab 9 nov 2019 alle 15:12 Lubomir I. Ivanov > ha scritto: >> >> on Windows, try unpairing and pairing the Perdix before each downlioad >> from Subsurface. >> the status of the device in the Control Panel should turn from Paired >> to Connected if successful. >> please note, this is a Windows issue and not a Subsurface issue. >> >> lubomir >> -- >> >> On Mon, 4 Nov 2019 at 11:28, tormento wrote: >> > >> > Ok, I tried to download dive on another laptop with integrated BT with or >> > without dongle and don't work there too. >> > >> > In the meantime I have done it with newest Testflight build on iOS but I'd >> > like to be able to download from Windows version too. >> > >> > Alberto >> > >> > Il giorno sab 2 nov 2019 alle ore 07:48 Jef Driesen >> > ha scritto: >> >> >> >> On 2/11/19 07:41, tormento wrote: >> >> > I am getting errors while importing dives from Perdix AI with its BT >> >> > dongle (I >> >> > don't hava any other to try) while it's own software can import dives >> >> > correctly. >> >> > >> >> > I select choose Bluetooth mode, find the Perdix and save. >> >> > >> >> > When I try to import, I get: >> >> > >> >> > Connecting to BLE device >> >> > Connecting >> >> > >> >> > Then a error windows pops up with "Dive data import error". >> >> > >> >> > image.png >> >> > >> >> > The log tells: >> >> > >> >> > Subsurface: v4.9.3-242-g9c8fbe494db2, built with libdivecomputer >> >> > v0.7.0-devel-Subsurface-NG (426a39fc7378cac3f5b1d3983be38d56ab526e78) >> >> > INFO: Open: transport=32 >> >> > INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, >> >> > flowcontrol=0 >> >> > INFO: Timeout: value=3000 >> >> > INFO: Sleep: value=300 >> >> > INFO: Purge: direction=3 >> >> > INFO: Write: size=11, data=0100FF0105002E902000C0 >> >> > >> >> > No .bin is generated. >> >> >> >> Uncheck the "Save libdivecomputer dumpfile" checkbox. The Shearwater >> >> Perdix AI >> >> communication protocol doesn't support memory dumps. Trying to download a >> >> memory >> >> dump will always fail with DC_STATUS_UNSUPPORTED. >> >> >> >> For the diagnostics purposes, the log file is sufficient for these models. >> >> >> >> 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 ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Perdix AI import error
I tried whatever kind of trick. I have no problem at all with Shearwater Cloud and that’s strange. If a Windows issue, how can it be solved or worked around? Alberto P.S I’d like to know if other Perdix have same issues. Il giorno sab 9 nov 2019 alle 15:12 Lubomir I. Ivanov ha scritto: > on Windows, try unpairing and pairing the Perdix before each downlioad > from Subsurface. > the status of the device in the Control Panel should turn from Paired > to Connected if successful. > please note, this is a Windows issue and not a Subsurface issue. > > lubomir > -- > > On Mon, 4 Nov 2019 at 11:28, tormento wrote: > > > > Ok, I tried to download dive on another laptop with integrated BT with > or without dongle and don't work there too. > > > > In the meantime I have done it with newest Testflight build on iOS but > I'd like to be able to download from Windows version too. > > > > Alberto > > > > Il giorno sab 2 nov 2019 alle ore 07:48 Jef Driesen < > j...@libdivecomputer.org> ha scritto: > >> > >> On 2/11/19 07:41, tormento wrote: > >> > I am getting errors while importing dives from Perdix AI with its BT > dongle (I > >> > don't hava any other to try) while it's own software can import dives > correctly. > >> > > >> > I select choose Bluetooth mode, find the Perdix and save. > >> > > >> > When I try to import, I get: > >> > > >> > Connecting to BLE device > >> > Connecting > >> > > >> > Then a error windows pops up with "Dive data import error". > >> > > >> > image.png > >> > > >> > The log tells: > >> > > >> > Subsurface: v4.9.3-242-g9c8fbe494db2, built with libdivecomputer > >> > v0.7.0-devel-Subsurface-NG (426a39fc7378cac3f5b1d3983be38d56ab526e78) > >> > INFO: Open: transport=32 > >> > INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, > flowcontrol=0 > >> > INFO: Timeout: value=3000 > >> > INFO: Sleep: value=300 > >> > INFO: Purge: direction=3 > >> > INFO: Write: size=11, data=0100FF0105002E902000C0 > >> > > >> > No .bin is generated. > >> > >> Uncheck the "Save libdivecomputer dumpfile" checkbox. The Shearwater > Perdix AI > >> communication protocol doesn't support memory dumps. Trying to download > a memory > >> dump will always fail with DC_STATUS_UNSUPPORTED. > >> > >> For the diagnostics purposes, the log file is sufficient for these > models. > >> > >> 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: Perdix AI import error
on Windows, try unpairing and pairing the Perdix before each downlioad from Subsurface. the status of the device in the Control Panel should turn from Paired to Connected if successful. please note, this is a Windows issue and not a Subsurface issue. lubomir -- On Mon, 4 Nov 2019 at 11:28, tormento wrote: > > Ok, I tried to download dive on another laptop with integrated BT with or > without dongle and don't work there too. > > In the meantime I have done it with newest Testflight build on iOS but I'd > like to be able to download from Windows version too. > > Alberto > > Il giorno sab 2 nov 2019 alle ore 07:48 Jef Driesen > ha scritto: >> >> On 2/11/19 07:41, tormento wrote: >> > I am getting errors while importing dives from Perdix AI with its BT >> > dongle (I >> > don't hava any other to try) while it's own software can import dives >> > correctly. >> > >> > I select choose Bluetooth mode, find the Perdix and save. >> > >> > When I try to import, I get: >> > >> > Connecting to BLE device >> > Connecting >> > >> > Then a error windows pops up with "Dive data import error". >> > >> > image.png >> > >> > The log tells: >> > >> > Subsurface: v4.9.3-242-g9c8fbe494db2, built with libdivecomputer >> > v0.7.0-devel-Subsurface-NG (426a39fc7378cac3f5b1d3983be38d56ab526e78) >> > INFO: Open: transport=32 >> > INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, >> > flowcontrol=0 >> > INFO: Timeout: value=3000 >> > INFO: Sleep: value=300 >> > INFO: Purge: direction=3 >> > INFO: Write: size=11, data=0100FF0105002E902000C0 >> > >> > No .bin is generated. >> >> Uncheck the "Save libdivecomputer dumpfile" checkbox. The Shearwater Perdix >> AI >> communication protocol doesn't support memory dumps. Trying to download a >> memory >> dump will always fail with DC_STATUS_UNSUPPORTED. >> >> For the diagnostics purposes, the log file is sufficient for these models. >> >> 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: Perdix AI import error
Ok, I tried to download dive on another laptop with integrated BT with or without dongle and don't work there too. In the meantime I have done it with newest Testflight build on iOS but I'd like to be able to download from Windows version too. Alberto Il giorno sab 2 nov 2019 alle ore 07:48 Jef Driesen ha scritto: > On 2/11/19 07:41, tormento wrote: > > I am getting errors while importing dives from Perdix AI with its BT > dongle (I > > don't hava any other to try) while it's own software can import dives > correctly. > > > > I select choose Bluetooth mode, find the Perdix and save. > > > > When I try to import, I get: > > > > Connecting to BLE device > > Connecting > > > > Then a error windows pops up with "Dive data import error". > > > > image.png > > > > The log tells: > > > > Subsurface: v4.9.3-242-g9c8fbe494db2, built with libdivecomputer > > v0.7.0-devel-Subsurface-NG (426a39fc7378cac3f5b1d3983be38d56ab526e78) > > INFO: Open: transport=32 > > INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, > flowcontrol=0 > > INFO: Timeout: value=3000 > > INFO: Sleep: value=300 > > INFO: Purge: direction=3 > > INFO: Write: size=11, data=0100FF0105002E902000C0 > > > > No .bin is generated. > > Uncheck the "Save libdivecomputer dumpfile" checkbox. The Shearwater > Perdix AI > communication protocol doesn't support memory dumps. Trying to download a > memory > dump will always fail with DC_STATUS_UNSUPPORTED. > > For the diagnostics purposes, the log file is sufficient for these models. > > Jef > ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: Perdix AI import error
On 2/11/19 07:41, tormento wrote: I am getting errors while importing dives from Perdix AI with its BT dongle (I don't hava any other to try) while it's own software can import dives correctly. I select choose Bluetooth mode, find the Perdix and save. When I try to import, I get: Connecting to BLE device Connecting Then a error windows pops up with "Dive data import error". image.png The log tells: Subsurface: v4.9.3-242-g9c8fbe494db2, built with libdivecomputer v0.7.0-devel-Subsurface-NG (426a39fc7378cac3f5b1d3983be38d56ab526e78) INFO: Open: transport=32 INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, flowcontrol=0 INFO: Timeout: value=3000 INFO: Sleep: value=300 INFO: Purge: direction=3 INFO: Write: size=11, data=0100FF0105002E902000C0 No .bin is generated. Uncheck the "Save libdivecomputer dumpfile" checkbox. The Shearwater Perdix AI communication protocol doesn't support memory dumps. Trying to download a memory dump will always fail with DC_STATUS_UNSUPPORTED. For the diagnostics purposes, the log file is sufficient for these models. Jef ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Perdix AI import error
I am getting errors while importing dives from Perdix AI with its BT dongle (I don't hava any other to try) while it's own software can import dives correctly. I select choose Bluetooth mode, find the Perdix and save. When I try to import, I get: Connecting to BLE device Connecting Then a error windows pops up with "Dive data import error". [image: image.png] The log tells: Subsurface: v4.9.3-242-g9c8fbe494db2, built with libdivecomputer v0.7.0-devel-Subsurface-NG (426a39fc7378cac3f5b1d3983be38d56ab526e78) INFO: Open: transport=32 INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=0, flowcontrol=0 INFO: Timeout: value=3000 INFO: Sleep: value=300 INFO: Purge: direction=3 INFO: Write: size=11, data=0100FF0105002E902000C0 No .bin is generated. I am using Windows 10 x64, latest build. *Alberto* P.S: Is there a way to delete previous computer "buttons" from import window? ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
