pcmhacking.net

antus wrote:Let me guess, your laptop is a toshiba? If not, probably other vendors do their own thing also to replace Microsofts BT stack as well. My memory and experience with BT on windows is that its not very good. From back in the early days when it wasnt supported at all (yet it was on apple macs), and laptop companies shipped their own 3rd party stack, then later they did add their own but it never worked well. Even now on current windows 10 I still have problems with my bluetooth headphones pairing properly. I often have to turn them on, let them pair, tell windows to disconnect and remove the device, then pair again before I can get any audio coming out despite the fact windows is saying the headphones are the speakers. Then the next time it'll work first try. Its quite frustrating The same headphones pair fine automatically to my work mac every time.

Good guess!!! Its my trusty Toshiba! Last of their released line in Aus

My laptop is a Toshiba, but my wife's laptop is a Dell, and get basically the same behavior on both, except for the numbering of the COM ports.

@tazzi - that link specifically says Toshibas only provide one port with their own stack, so thats why your not seeing the same. If you can you might need to fire up a W10 VM, and use vmwares BT passthrough. That might maybe kinda give you the same behaviour, but with a virtual shared BT port, so whether its useful or not, hard to say. Maybe Toshiba didnt do the same across all models.

Well I went around to my workshop after my day job with my tuning laptop and put the xpro vt through its paces. Lets see what Tazzi says, but it looks like it might be a hardware problem after all that. But I think we still need to test with lsdroid to confirm. Mine works with lsdroid and pcmhammer on win 10 with 2 com ports (using the first one). I guess the 2 ports is a windows oddity on the stock non-oem BT stack thats no more than a red herring.

Well least its good to see its working happily on Windows for you

I have only just got home too so about to test here

Ok so I have managed to get the same issues that draz is getting.
The bluetooth works perfectly on my android device, but my windows installation is having problems.

So, windows pairs, but then instantly disconnects from the device. I can tell as the blue LED goes back to flashing quickly. When then using pcmhammer with either comport, it does into appear windows tries to reconnect to the device.

Wow what a nightmare that is with windows.
Ok so after about 20 attempts, finally got windows to actually connect then read with pcmhammer.

So, I paired up then entered the pin when prompted. I then disconnected the OBDX from the OBD port, then reconnected and in PCMHammer I selected the Bluetooth comport thats associated as the OUTGOING bluetooth connection.. and it seems to have connected.

I also set my computers bluetooth to "discoverable" and "allow bluetooth devices to find this PC".

I cant get it to work any other way, app either hangs or crashes.

*Edit
I have to repeat that exact process every single time since windows doesnt seem to just reconnect.

Wow so its a Windows race condition over which port is which when starting up with two! ugh... Microsoft... And if we are to fix it properly and support windows we'll need to find a way to identify which port is which and find the device. Or maybe scan all scannable com ports and see which one answers as the device. Auto hardware detection would be nice but it wont be the smallest change.

antus wrote:Wow so its a Windows race condition over which port is which when starting up with two! ugh... Microsoft... And if we are to fix it properly and support windows we'll need to find a way to identify which port is which and find the device. Or maybe scan all scannable com ports and see which one answers as the device. Auto hardware detection would be nice but it wont be the smallest change.

I recall reading something about a dedicated bluetooth library to use.... ahh here we go:
https://docs.microsoft.com/en-us/uwp/ap ... inrt-19041

Maybe would have better luck using the dedicated bluetooth library instead of relying on windows to auto connect.

Tazzi wrote: So, I paired up then entered the pin when prompted. I then disconnected the OBDX from the OBD port, then reconnected and in PCMHammer I selected the Bluetooth comport thats associated as the OUTGOING bluetooth connection.. and it seems to have connected.

There's supposed to be a pin? I've just been leaving that blank, and it does pair. I will try the disconnect/reconnect.

Re the LEDs, can't tell what they're really doing (except they're on) because it's in the car and they're right up against the underside of the dash.

Update: I note that I now have COM3 as incoming, COM4 as outgoing, the opposite of what it was the last time I checked, so confirming the COM initialization race condition idea.

Update 2: Can't get it to work just by disconnecting / reconnecting the OBDX. One thing I noticed is that when the device is powered on and paired for the first time, windows will quickly say it's "connected". If I then power off / power on the device, windows will say it's "paired" but won't change it to "connected". Anyway pcmhammer still says "can't initialize" whether it's connected or just paired.''

Update 3: Works great on windows in USB mode! And faster than I expected.