The fastest message board... ever.
OSTC's running hwOS 
OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 20, 2015 01:02PM

Hallo ich bin neuer Besitzer eines OSTC 2. Und wie hier im Forum auch schon öfters gesehen, ich habe massive Probleme mit der Bluetooth Verbindung zu jedem Programm. Sei es Subsurface, Divelog oder der Companion. Als Betriebssystem nutze ich Windows 10. Probiert habe ich es auf einem Dell Laptop und einem normalen PC. Beim Laptop mit integriertem Bluetooth und beim PC mit einem USB Dongle.
Wenn ich den OSTC kopple erscheint er mit der Seriennummer in den Einstellungen. Es werden zwei Com Ports angelegt(ein und ausgehend). Ich werde nicht! nach dem Pin wie im Handbuch aufgeführt gefragt und sehe nirgends eine Einstellung dafür.
Probleme mit Subsurface:
Wähle ich den ausgehenden Port kommt die Fehlermeldung Fehler beim Öffnen von Com5 Heinrich Weikamp (Ostc2).Wähle ich den eingehenden friert Subsurface ein und ich muß es per Taskmanager schließen. Egal was ich mache, die Protokolldatei wird nicht beschrieben.

Probleme mit Divlog:
Wähle ich den ausgehenden Port kommt die Meldung: DC_Status_IO. Wähle ich den eingehenden kommt passiert gar nichts. Der OSTC beendet die Bluetoothverbindung und nichts kommt.
Probleme mit dem Companion:
Bei der eingehenden: Unable to open Port. Bei der ausgehenden: Write Block Timeout.
Alle drei Programme wurden im Administratormode ausgeführt. Bei allen drei Programmen wurde vorher Bluetooth beim OSTC aktiviert und ich muß sagen dieser Befehl ist an einer sehr bescheidenen Stelle wenn man hier oft durch das Menue geht.

Bei Subsurface konnte ich keine Protokolldateien erstellen. Bei Divlog kommt folgendes beim ausgehenden Port:
Beim eingehenden erscheint kein Fehlerprotokoll da hier einfach nichts passiert.
System.Reflection.TargetInvocationException: Während des Vorgangs ist eine Ausnahme aufgetreten, sodass das Ergebnis ungültig ist. Weitere Ausnahmedetails finden Sie in InnerException.

bei System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
bei Divinglog.Download.Libdivecomputer.BWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
bei System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
bei System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.

bei Divinglog.Download.Libdivecomputer.dc_device_open(IntPtr& device, IntPtr context, IntPtr descriptor, String name)
bei Divinglog.Download.Libdivecomputer.DLUniversal(LibdivecomputerDescriptor Desc)
bei Divinglog.Download.Libdivecomputer.BWorker_DoWork(Object sender, DoWorkEventArgs e)
bei System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Diving Log Version: 6.0.0.1
Windows Version: Windows 10


Viele Grüße

Christof



Edited 1 time(s). Last edit at 08/20/2015 01:06PM by ChristofM.

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: heinrichsweikamp ()
Date: August 20, 2015 04:08PM

ChristofM Wrote:
> Com Ports angelegt(ein und ausgehend). Ich werde
> nicht! nach dem Pin wie im Handbuch aufgeführt
> gefragt und sehe nirgends eine Einstellung dafür.

Das ist egal. Entweder es geht direkt ohne Pin oder dieser lautet "0000".

> Probleme mit Subsurface:
> Wähle ich den ausgehenden Port kommt die
> Fehlermeldung Fehler beim Öffnen von Com5
> Heinrich Weikamp (Ostc2).Wähle ich den

Nur der ausgehende ist richtig, also der mit der normalerweise niedrigeren Nummer.

Ist das Bluetooth denn auch am OSTC aktiviert, wenn das Auslesen stattfinden soll?

Gruß,
Matthias

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 20, 2015 04:55PM

Quote

Ist das Bluetooth denn auch am OSTC aktiviert, wenn das Auslesen stattfinden soll?
Ja das ist es.

Momentan habe ich folgendes Errorlog beim Diving Log
INFO: Open: name=COM5
ERROR: Element nicht gefunden (1168) [in serial_win32.c:152 (serial_open)]
ERROR: Failed to open the serial port. [in hw_ostc3.c:275 (hw_ostc3_device_open)]


INFO: libdivecomputer-0.dll version: 0.5.0-devel



Edited 1 time(s). Last edit at 08/20/2015 04:59PM by ChristofM.

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 20, 2015 05:38PM

Ich habe jetzt ein wirklich altes Vista Programm heruntergeladen das die Windows 10 Treiber ersetzt. Hier kommt etwas neues und beim OSTC ist er im Download Modus. Da danach aber das Divinglog sowie Windows 10 abstürzt, ist das defintiv keine Möglichkeit.

Beim Diving Log erscheint folgendes:

System.Reflection.TargetInvocationException: Während des Vorgangs ist eine Ausnahme aufgetreten, sodass das Ergebnis ungültig ist. Weitere Ausnahmedetails finden Sie in InnerException.

bei System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
bei Divinglog.Download.Libdivecomputer.BWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
bei System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
bei System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.

bei Divinglog.Download.Libdivecomputer.dc_device_foreach(IntPtr device, dive_callback callback, IntPtr userdata)
bei Divinglog.Download.Libdivecomputer.DLUniversal(LibdivecomputerDescriptor Desc)
bei Divinglog.Download.Libdivecomputer.BWorker_DoWork(Object sender, DoWorkEventArgs e)
bei System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Diving Log Version: 6.0.0.1
Windows Version: Windows 10

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: divinglog ()
Date: August 20, 2015 05:55PM

Hallo Christof

Lade dir bitte dieses Update herunter und entpacke es in den Diving Log Programmordner:

[www.divinglog.com]

Lass es mich wissen ob das Problem immer noch auftritt.

Schöne Grüße,
Sven

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 20, 2015 06:10PM

Mit dem Companion habe ich mit den Vista Treibern ein Update durchführen können. Divinglog findet allerdings immer noch nicht den OSTC oder stürzt ab.
Hier die Meldung die bei einem nicht finden auftritt

INFO: Open: name=COM8
INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=1, flowcontrol=0
INFO: Timeout: value=3000
INFO: Sleep: value=300
INFO: Flush: queue=3, input=2358, output=0
INFO: Write: size=1, data=BB
INFO: Read: size=1, data=FF
ERROR: Unexpected echo. [in hw_ostc3.c:186 (hw_ostc3_transfer)]
ERROR: Failed to send the command. [in hw_ostc3.c:318 (hw_ostc3_device_init_download)]


INFO: libdivecomputer-0.dll version: 0.5.0-develERROR: Das Handle ist ungültig (6) [in serial_win32.c:187 (serial_close)]

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 20, 2015 06:14PM

Und hier noch einmal eine neuere Fehlermeldung:
INFO: Open: name=COM8
INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=1, flowcontrol=0
INFO: Timeout: value=3000
INFO: Sleep: value=300
INFO: Flush: queue=3, input=0, output=0
INFO: Write: size=1, data=BB
INFO: Read: size=1, data=BB
INFO: Read: size=1, data=4D
INFO: Write: size=1, data=69
INFO: Read: size=1, data=69
INFO: Read: size=64, data=132801564857204F5354430000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
INFO: Read: size=1, data=4D
INFO: Write: size=1, data=6A
INFO: Read: size=1, data=6A
INFO: Read: size=1, data=11
INFO: Read: size=1, data=4D
INFO: Write: size=1, data=61
INFO: Read: size=1, data=61
INFO: Read: size=261, data=FAFA000000591600235616000F08050A19881A1E0024C000DC0332071500000115000000150000001500000015000000015113100200007FB30000FF46005A00640078008C000012003F1458081E5501010000AFC2C5C4C0BBB4ACA49D969089827B74BE61DD3F9D062940ED4D39402562344096AD2340EEA30F40E0F5F63FA704D33F3776B53FC17FA13F6BC5933F27AB883F397D7F3F2910713F2BA5653F0FA65C3F5050505050505050505050505050505000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000030A000000B5AA56040000FBFBFAFA791600
ERROR: Failed to receive the answer. [in hw_ostc3.c:218 (hw_ostc3_transfer)]
ERROR: Failed to read the header. [in hw_ostc3.c:550 (hw_ostc3_device_foreach)]
INFO: Write: size=1, data=FF
INFO: Read: size=1, data=24
ERROR: Unexpected echo. [in hw_ostc3.c:186 (hw_ostc3_transfer)]
ERROR: Failed to send the command. [in hw_ostc3.c:410 (hw_ostc3_device_close)]


INFO: libdivecomputer-0.dll version: 0.5.0-develERROR: Das Handle ist ungültig (6) [in serial_win32.c:437 (serial_write)]
ERROR: Failed to send the command. [in hw_ostc3.c:168 (hw_ostc3_transfer)]
ERROR: Failed to send the command. [in hw_ostc3.c:410 (hw_ostc3_device_close)]
ERROR: Das Handle ist ungültig (6) [in serial_win32.c:187 (serial_close)]

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: divinglog ()
Date: August 20, 2015 10:07PM

Hallo Christof

Mein Update sollte nur die unten stehende Fehlermeldung beheben, die neue Fehlermeldung hat eine andere Ursache.


System.Reflection.TargetInvocationException: Während des Vorgangs ist eine Ausnahme aufgetreten, sodass das Ergebnis ungültig ist. Weitere Ausnahmedetails finden Sie in InnerException.

bei System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
bei Divinglog.Download.Libdivecomputer.BWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
bei System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
bei System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.

bei Divinglog.Download.Libdivecomputer.dc_device_foreach(IntPtr device, dive_callback callback, IntPtr userdata)
bei Divinglog.Download.Libdivecomputer.DLUniversal(LibdivecomputerDescriptor Desc)
bei Divinglog.Download.Libdivecomputer.BWorker_DoWork(Object sender, DoWorkEventArgs e)
bei System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)



Edited 1 time(s). Last edit at 08/20/2015 10:07PM by divinglog.

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: TnT ()
Date: August 21, 2015 10:05AM

ChristofM Wrote:
-------------------------------------------------------
> INFO: Write: size=1, data=61
> INFO: Read: size=1, data=61
> INFO: Read: size=261, data=<omitted>
> ERROR: Failed to receive the answer. [in
> hw_ostc3.c:218 (hw_ostc3_transfer)]
> ERROR: Failed to read the header. [in
> hw_ostc3.c:550 (hw_ostc3_device_foreach)]

We get a timeout while reading the dive headers. We only get 261 bytes instead of the expected 1024 bytes (first chunk of the full 64K). I received a very similar report from another user (see topic), where the read operation does timeout too quickly. Instead of waiting the full timeout (default 3 seconds) it returns after less then a millisecond. So it appears the driver ignores the configured timeout.

To confirm this, can you try with the libdivecomputer test application? You can download it here. It's a command-line application, which you need to run with the following options:
ostc3-timeout.exe -v -l ostc3.log -d ostc3.xml -b ostc3 <COMx>
Replace <COMx> with the correct serial port (e.g. COM8). When done, send me the ostc3.log file. It will be in the same directory as the ostc3-timeout.exe file. (If it's short you can also post in the forum.)

Jef

--
libdivecomputer developer
[www.libdivecomputer.org]

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 21, 2015 12:10PM

Hi Jef,

When I run the application I get the error message that Windows 10 can not find the file. The file extension display is turned on. The file names match.

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: TnT ()
Date: August 21, 2015 05:47PM

When you start the Command Prompt, you are probably in a different directory then the one where the exe is located. Either you move the exe to the same directory, or you change the current directory of the Command Prompt.

--
libdivecomputer developer
[www.libdivecomputer.org]

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 22, 2015 12:58PM

[0.000011] DATETIME 2015-08-22T09:57:28Z (1440237448)
[0.000155] VERSION 0.5.0-devel (922d219bdc01eba71941dcc3d3f325b31cdd3b33)
[0.000537] Opening the device (Heinrichs Weikamp OSTC 2, com8).
[0.000825] INFO: Open: name=com8
[0.001152] INFO: Configure: baudrate=115200, databits=8, parity=0, stopbits=1, flowcontrol=0
[0.001389] INFO: Timeout: value=20000
[0.001576] INFO: Sleep: value=300
[0.302371] INFO: Flush: queue=3, input=0, output=0
[0.302989] Registering the event handler.
[0.304130] Registering the cancellation handler.
[0.306159] Downloading the dives.
[0.306487] Event: progress 0.00% (0/4194304)
[0.307773] INFO: Write: size=1, data=BB
[0.364082] INFO: Read: size=1, data=BB
[0.364450] INFO: Read: size=1, data=4D
[0.365696] INFO: Write: size=1, data=69
[0.384021] INFO: Read: size=1, data=69
[0.384439] INFO: Read: size=64, data=132801564857204F5354430000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[0.385933] INFO: Read: size=1, data=4D
[0.386703] INFO: Write: size=1, data=6A
[0.412011] INFO: Read: size=1, data=6A
[0.412441] INFO: Read: size=1, data=11
[0.413511] INFO: Read: size=1, data=4D
[0.414432] Event: model=17 (0x00000011), firmware=342 (0x00000156), serial=10259 (0x00002813)
[0.415721] INFO: Write: size=1, data=6D
[0.512096] INFO: Read: size=1, data=6D
[0.512553] INFO: Read: size=328, data=5616000F08050A19881A1E00240100FFA829000F080C1515D2093F00030200FF481B000F081514145F0427001E0300FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
[0.514642] ERROR: Failed to receive the answer. [in ../../source/src/hw_ostc3.c:241 (hw_ostc3_transfer)]
[0.515081] ERROR: Failed to read the header. [in ../../source/src/hw_ostc3.c:581 (hw_ostc3_device_foreach)]
[0.515487] ../../source/examples/universal.c:840: Error downloading the dives.
[0.519265] INFO: Write: size=1, data=FF
[0.520004] INFO: Read: size=1, data=FF
[0.520623] Result: Timeout

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 28, 2015 03:46PM

The problem still exists sad smiley

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: TnT ()
Date: August 29, 2015 01:15PM

This appears to be the same problem as in this topic. Allthough we have configured a timeout of 20 seconds, the read operation already returns after less than a millisecond:

[0.001389] INFO: Timeout: value=20000
...
[0.415721] INFO: Write: size=1, data=6D
[0.512096] INFO: Read: size=1, data=6D
[0.512553] INFO: Read: size=328, data=<omitted>
[0.514642] ERROR: Failed to receive the answer. [in ../../source/src/hw_ostc3.c:241 (hw_ostc3_transfer)]

So it's no surprise we get only a part of the expected response packet. This is probably a bluetooth driver or hardware problem. In the other topic the problem was solved by using another bluetooth adapter.

--
libdivecomputer developer
[www.libdivecomputer.org]

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 31, 2015 10:37AM

I´m able to update the OSTC 2 with the companion, so i don´t understand the problem on hardware or driver site. Only the Logbook Import doesn´t work on a fresh installed Windows 10 Dell Laptop and it dont work on a fresh installed Windows 10 Desktop PC. Every other Bluetooth device worked with these two Computers without any problems and the Windows 10 Bluetooth drivers.

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: Guignome ()
Date: August 31, 2015 02:08PM

Hello,

Similar problem for me

I have the new OSTC 2.

I have two computers without problem under windows Seven.

Since updgrade the two computer to Windows 10, OSTC Companion and Divelod doesnt work. The bluetooth's link with OSTC is OK but i can't transfer or update firmware.

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: TnT ()
Date: August 31, 2015 03:01PM

ChristofM Wrote:
-------------------------------------------------------
> I´m able to update the OSTC 2 with the companion,

On the exact same Windows 10 system? Or another one?

--
libdivecomputer developer
[www.libdivecomputer.org]

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ChristofM ()
Date: August 31, 2015 06:30PM

On exact the same system.

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: ijdod ()
Date: September 08, 2015 12:26AM

I think it's very likely a driver problem. I had similar issues with Win7, using the 'latest' Dell drivers for the Broadcom BCM2070 Bluetooth chipset in my Dell laptop. I installed some more recent drivers from another laptop vendor, which solved my problems with Win7. With Win10, however, those drivers were replaced, and the BT connectivity stopped working. A couple of weeks ago the Win10 BCM2070 drivers were updated by Microsoft, which changed the error messages, but didn't actually solve the problem. Luckily I have another system which does work, so I can update my OSTC2.

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: heinrichsweikamp ()
Date: September 09, 2015 04:06PM

Hello,

It seems that there is some incompatibility with the new Windows 10 Bluetooth stack and the current OSTC PC Programs: [answers.microsoft.com]

While the described work-around worked here on a WIN10 PC, it failed on another. So there definitely is some issue here we need to fix.

We're already discussing this with PC program developers and ask for your patience here.

regards,
Matthias

Options: ReplyQuote
Re: OSTC2 Bluetooth Windows 10 Problems
Posted by: hosebei ()
Date: October 20, 2015 07:02PM

Thanks to providing more information to this Problem! smiling smiley
In the answers Link you provided on the last page:
answers.microsoft.com
They talk about an Update, that has to be installed on your Windows 10 machine (KB3093266). I checked mine, and recognized, that it is already installed. But my OSTC 2 would still not connect. I had to go to the Device Manager and let me list the Hidden Devices aswell. After Deleting the hidden OSTC 2 Device, I started the Bluetooth mode on the OSTC 2 again. After a successful Pair with the Computer, I could use OSTC companion and also subsurface to export the Dives.
Finally I can use the OSTC 2 on my Windows 10 x64 Machine. I assume that we have to blame Microsoft rather than Heinrichs Weikamp.

Options: ReplyQuote


Sorry, only registered users may post in this forum.
This forum powered by Phorum.