Unable to get my bs6 working with NVDA 2026.1.1
matthew dyer
I am currently using NVDA 2026.1.1 on a Windows 11 (25h2) desktop, with my BS6 connected via Bluetooth.
While NVDA successfully shows braille output on the display, braille input is not working at all. I have checked the logs and included the snippet with the error below. If necessary, I can replicate the issue to get a full debug log.
Is anyone else experiencing this problem with braille input?
[Insert log snippet here]
Thanks,
Matthew
--
MSN/e-mail: ilovecount...@gmail.com
AIM: mattdy1
skype: graduater2004.
Quentin Christensen
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CA%2BjagC8OdR%2B2U44fKRq8kX-Z9BDbMw_cQeiv%2B0n0rfGhqh4wOg%40mail.gmail.com.
Quentin Christensen
Richard Wells
Latest Windows 11 updates have locked out the current HIMS 2.5 USB product drivers due to signing issues. This effects Braille Sense 6, QBraille, etc. Bluetooth is the only way to use HIMS devices for now. As time allows, I will test Bluetooth Braille input to see what happens here.
Jason J.G. White
>Latest Windows 11 updates have locked out the current HIMS 2.5 USB
>product drivers due to signing issues. This effects Braille Sense 6,
>QBraille, etc. Bluetooth is the only way to use HIMS devices for now.
support braille displays. Nor does macOS. In both cases, you simply
connect a display via USB and it is detected by the appropriate software
(BRLTTY in the Linux case, and Voiceover in macOS).
Windows is the exception. I would expect adoption of the HID braille
display standard to eliminate the need for drivers, but presumably this
only applies to newer braille devices. I also worry that drivers won't
be compatible with the ARM architecture (perhaps not even with x86
emulation), and this will create difficulties for users of older
braille devices.
NVDA developers may not have the resources to implement older,
manufacturer-specific braille display protocols directly, so the
solution may well be that the problem gradually goes away as users move
to HID standard-compliant braille displays.
Steve Nutt
He did say it was connected via Bluetooth.
All the best
Steve
--
Computer Room Services
77 Exeter Close, Stevenage, Hertfordshire, SG1 4PW
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
Blog, releases & news by email: https://nvaccess.org/newsletter
User group: https://nvaccess.org/nvda-users
Mastodon: https://fosstodon.org/@NVAccess
Other socials & community: https://www.nvaccess.org/#socials
--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.