Windows 10 and the unability to use a Freedom Scientific braille display through bluetooth

[nvaccessAuto]

Reported by tyrylu on 2015-08-08 19:46 Hello, after the upgrade to Win 10 i'm unable to use the Pac mate 40 blue display with NVDA through bluetooth. The device shows as paired in the device list, but i just get the RuntimeError no device found in the log. Is it causet by Freedom's driver incompatibility or can something be done with that? Note that an older Focus 40 (not blue) through USB works just fine. Unfortunately, i can't try it with the newer, but it worked in Windows 7 just fine as well.

[nvaccessAuto]

Comment 1 by jteh on 2015-08-09 23:28 Unfortunately, we don't have a Bluetooth Focus display, so aren't able to test this.

If you are able, please do the following to provide us with further details:

1. Press NVDA+control+z to open the NVDA Python console.
2. Paste the following line into the console:

 import hwPortUtils as h; list(h.listComPorts())

1. Press enter.
2. Press f6.
3. Press control+a to select all, then control+c to copy.
4. Paste what you copied into your reply.

[nvaccessAuto]

Comment 2 by tyrylu on 2015-08-10 06:06 There's the output. The correct COM port it's there as COM7, but the fbOpen call still fails. I tried pairing the device a few times and rebooting just for sure.

import hwPortUtils as h; list(h.listComPorts())

u'Agere Systems HDA Modem', 'hardwareID': u'HDAUDIO\FUNC_02&VEN_11C1&DEV_1040&SUBSYS_103C3066&REV_1002', 'port': u'COM3'}, {'friendlyName': u'Intel(R) Active Management Technology - SOL (COM4) ', 'hardwareID': u'PCI\VEN_8086&DEV_1C3D&SUBSYS_161C103C&REV_04', 'port': u'COM4'}, {'friendlyName': u'Standardn\xed s\xe9riov\xe1 linka pomoc\xed protokolu Bluetooth (COM7) ', 'bluetoothName': u'Focus 40 BT', 'hardwareID': u'BTHENUM{00001101-0000-1000-8000-00805f9b34fb}_LOCALMFG&000f', 'bluetoothAddress': 17596091135363L, 'port': u'COM7'}, {'friendlyName': u'Standardn\xed s\xe9riov\xe1 linka pomoc\xed protokolu Bluetooth (COM6) ', 'hardwareID': u'BTHENUM{00001101-0000-1000-8000-00805f9b34fb}_LOCALMFG&0000', 'bluetoothAddress': 0, 'port': u'COM6'} Regards, L. T.

[nvaccessAuto]

Comment 3 by jteh on 2015-08-10 06:10 In that case, I unfortunately have no idea why this isn't working and I can't do much more without a device to test with. It does seem as if there might be some issue with the Freedom Scientific dll, though.

[nvaccessAuto]

Comment 4 by jteh on 2015-08-10 06:13 Actually, since it seems you're using a language other than English, there's one other thing you can try for me. What do you get if you type this into the Python console?

u'COM7'.encode("mbcs")

I'm guessing you'll get 'COM7', which is correct, but just checking.

[nvaccessAuto]

Comment 5 by tyrylu on 2015-08-10 06:29 I was afraid of something like that. What sort of testing would you do with a device except testing that it isn't a local anomaly? Anything i could test?

[nvaccessAuto]

Comment 6 by tyrylu on 2015-08-10 06:32 And to the last comment, i unfortunately get 'COM7' e. g. a python 2 str with the correct content.

[nvaccessAuto]

Comment 7 by jteh on 2015-08-10 06:33 Honestly, I'm not sure without further thought. I'd first make sure the right port was being passed to fbOpen, but it sounds like you've already done that. I might then try opening the device directly and talking the raw protocol, but that'd either require getting the tech docs from FS or figuring it out from the BRLTTY driver. I might also try watching with WinDBG to see what calls are being made and where it fails.

[nvaccessAuto]

Comment 8 by jteh on 2015-08-10 06:36 Btw, we've also had reports of Bluetooth not working with a Brailliant BI in Windows 10 (#5195). That driver talks raw protocol; it doesn't use a dll. I'm not sure why that one is failing; I'm waiting on further info.

Note that the Baum driver seems to work just fine for me in Windows 10 with Bluetooth. It too talks raw protocol.

[nvaccessAuto]

Comment 9 by tyrylu on 2015-08-10 07:04 Unfortunately, the issue is not caused by the PC Bluetooth stack, other devices work. :-(

[nvaccessAuto]

Comment 10 by Brendon22 on 2015-08-10 10:11 Hello, I would like to advise that the Freedom Scientific DLL is not compatible with Windows 10. This should be compatible at the release of JAWS 17 in November.

Thank you and kind regards,

Brendon 22.

[nvaccessAuto]

Comment 11 by Brendon22 on 2015-08-10 10:11 Changes: Changed title from "Windows 10 and the unability to use an Freedom Scientific braille display through bluetooth" to "Windows 10 and the unability to use a Freedom Scientific braille display through bluetooth"

[LeonarddeR]

cc @bramd

[bramd]

I was able to use a Focus 40 blue over Bluetooth a few weeks ago in Windows 10, both through the DLL and with my new driver in bramd/nvda/freedomscientific-native branch, which uses the protocol directly.

[Adriani90]

@tyrylu are you still having the issue?

[tyrylu]

Excluding some october update pairing issues, no, the issue is resolved and likely can be closed.

[Adriani90]

Closing as works for me. Thanks for your fast reply.