Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

focus 40 blue do'nt works with bluetooth #2161

Closed
nvaccessAuto opened this issue Mar 13, 2012 · 10 comments
Closed

focus 40 blue do'nt works with bluetooth #2161

nvaccessAuto opened this issue Mar 13, 2012 · 10 comments

Comments

@nvaccessAuto
Copy link

Reported by paul otter on 2012-03-13 17:01
hello, we have a problem with a focus 40 braille display
the problem is this: when we connect the display with an usb cable all is working fine there is no problem and there is braille on the display.
but when we try to connect with bluetooth, nvda reports in the logfile that he can'nt find the display, while nvda is correct configured.
i've allready asked for a solution on the forum, but they tells me to create a ticket for this problem.
and when we close nvda, and starting jaws, the display will work good without any problem allso with bluetooth!
your help will great appreciated!

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2012-03-14 01:06
What is the bluetooth name of your display; i.e. how does it appear in Bluetooth Devices?

@nvaccessAuto
Copy link
Author

Comment 2 by paul otter on 2012-03-14 22:41
it presents as focus 40 bt

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2012-03-15 02:26
Is it "Focus 40 BT" or "focus 40 bt" (note the difference in capitalisation)? The distinction is important.

Please also do the following on the affected system:

  1. Start NVDA.
  2. Press NVDA+control+z.
  3. Paste the following line, ensuring there are no spaces at the start of the line:[[br]]
    import hwPortUtils; api.copyToClip(unicode(list(hwPortUtils.listComPorts(onlyAvailable=True))))
  4. Paste the clipboard into a comment in this ticket.

@nvaccessAuto
Copy link
Author

Comment 4 by orcauser on 2012-03-20 13:33
Paul is having issues logging in but he emailed me the following:
"Focus 40 BT"
waiting for the python consol output.

@nvaccessAuto
Copy link
Author

Comment 5 by orcauser on 2012-03-20 23:40
Have now received the following:

u'BT Port (COM10)', 'hardwareID': u'Bluetooth\0004&0002',
'port': u'COM10'}, {'friendlyName': u'BT Port (COM11)', 'hardwareID':
u'Bluetooth\0004&0002', 'port': u'COM11'}, {'friendlyName': u'BT Port
(COM14)', 'hardwareID': u'Bluetooth\0004&0002', 'port': u'COM14'},
{'friendlyName': u'BT Port (COM16)', 'hardwareID': u'Bluetooth\0004&0002',
'port': u'COM16'}, {'friendlyName': u'BT Port (COM17)', 'hardwareID':
u'Bluetooth\0004&0002', 'port': u'COM17'}, {'friendlyName': u'BT Port
(COM18)', 'hardwareID': u'Bluetooth\0004&0002', 'port': u'COM18'},
{'friendlyName': u'BT Port (COM20)', 'hardwareID': u'Bluetooth\0004&0002',
'port': u'COM20'}, {'friendlyName': u'BT Port (COM21)', 'hardwareID':
u'Bluetooth\0004&0002', 'port': u'COM21'}, {'friendlyName': u'BT Port
(COM22)', 'hardwareID': u'Bluetooth\0004&0002', 'port': u'COM22'},
{'friendlyName': u'BT Port (COM41)', 'hardwareID': u'Bluetooth\0004&0002',
'port': u'COM41'}, {'friendlyName': u'BT Port (COM6)', 'hardwareID':
u'Bluetooth\0004&0002', 'port': u'COM6'}, {'friendlyName': u'BT Port
(COM7)', 'hardwareID': u'Bluetooth\0004&0002', 'port': u'COM7'}

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2012-03-21 00:43
Looks like this is some sort of non-Microsoft bluetooth stack/driver. A bit of Googling suggests this is a Toshiba driver. Unfortunately, I don't know how to query this driver for the bluetooth name.

Reporter notes that this is Windows 7 32 bit. I thought everyone used the Microsoft bluetooth stack in Windows 7, but apparently not.

@nvaccessAuto
Copy link
Author

Comment 7 by nvdakor on 2014-04-29 02:09
Hi Paul and others,
Try using NVDA 2013.3 or later to see if this issue is fixed.

@bhavyashah
Copy link

@josephsl's #2161 (comment) seems to suggest that the reported issue may have been fixed in NVDA version 2013.3. Unfortunately however, the original author of this ticket did not respond to the cited comment by testing with said NVDA release and onwards, and we have no means of contacting Paul anymore. Unless we receive feedback from an NVDA user of the mentioned Braille display still confirming this ticket, I suggest closing. @ehollig

@jcsteh jcsteh removed their assignment Aug 14, 2017
@ehollig
Copy link
Collaborator

ehollig commented Aug 14, 2017

Closing, as we are unable to contact the original poster for additional information.

@ehollig ehollig closed this as completed Aug 14, 2017
@bdorer
Copy link
Sponsor

bdorer commented Sep 3, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants