Braille Display Problem
|
Christopher Gray
I just updated my NVDA to the current version. My braille display now fails. Is this a known problem?
I set my com port to the humanware setting for the port and get an error when I press OK.
Chris
|
|
|
|
Abbie Taylor
Which Braille display are you using? It might need a new driver
in order to be compatible with the latest version of NVDA. Have
you tried connecting it via USB? Also, this may be too obvious,
but is your Braille display set to Automatic in the NVDA Braille
settings? Good luck. On 1/16/2023 3:16 PM, Christopher Gray
wrote:
-- Abbie Johnson Taylor, Author https://www.abbiejohnsontaylor.com abbietaylor945@... |
|
|
|
Quentin Christensen
Have you fully restarted the PC since updating? The main Braille changes in 2022.4 are an update to LibLouis (the software we use which converts text into Braille) and a fix for password suppression in terminal in Visual Studio. Although this shouldn't have changed, it might be worth double checking the advice for your display in our user guide. You mentioned Humanware but not which display you have. If it's a "Baum/Humanware/APH/Orbit Braille Display": https://www.nvaccess.org/files/nvda/documentation/userGuide.html#Baum or if it's a "HumanWare Brailliant BI/B Series / BrailleNote Touch": https://www.nvaccess.org/files/nvda/documentation/userGuide.html#HumanWareBrailliant or if it's a HumanWare BrailleNote: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#HumanWareBrailleNote On Tue, Jan 17, 2023 at 9:28 AM Abbie Taylor <abbietaylor945@...> wrote:
--
Quentin Christensen Training and Support Manager Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|
|
Hi, In addition to what Quentin is asking, can you:
Thanks. Cheers, Joseph |
|
|
|
Christopher Gray
I have used Automatic and the Baum/Humanware settings and can get no braille on either. I'm using a USB connection. The display clears when NVDA starts, but I get no braille.
So, is there a new driver I need to be using? Chris |
|
|
|
Christopher Gray
Hi:
My braille display is a Brailliant BI 40 from Humanware. I'm connecting it to my PC via USB. The overall setting is Automatic. I tried using the Humanware/Baum/etc setting but that only offers serial connectivity and did not work.
Just to reiterate, when I start NVDA the display clears so I know the connection is active. But, I see no braille. This happened when I updated to the most recent version of NVDA a couple of days ago.
If a new driver is required, can you provide a link?
How do I generate a debug log for you? I'll be happy to send one.
Chris
Hi,
In addition to what Quentin is asking, can you:
Tell us which connection technology you are using (USB, bluetooth, automatic, etc.)? Send a debug log to NV Access (info@...) so folks can diagnose it?
Thanks.
Cheers,
Joseph
|
|
|
|
hurrikennyandopo ...
Hi
Are you using a serial to usb cable? In my case I had to instal a serial to usb driver.
Then after the braille display was turned on and plugged in I had to go into the settings of nvda locate the braille section and then change it to human ware braille note. The next time I tabbed there was a combo box where I could change it from serial to serial to usb done some changes and up it come.
I can not remember if in the braille note I had to set it to some thing like use with a screen reader or terminal.
I did do a tutorial on it when I set it up for others who are new even to a old braille display at it is called connecting a braille display to nvda and can be found off the following page at Petrus' It might help.
You might need the driver for your braille display to run it?
Gene nz On 18/01/2023 15:55, Christopher Gray
wrote:
I have used Automatic and the Baum/Humanware settings and can get no braille on either. I'm using a USB connection. The display clears when NVDA starts, but I get no braille. |
|
|
|
Christopher Gray
I am not using a serial to USB cable.
Chris ]
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Tuesday, January 17, 2023 7:32 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Braille Display Problem
Hi
Are you using a serial to usb cable? In my case I had to instal a serial to usb driver.
Then after the braille display was turned on and plugged in I had to go into the settings of nvda locate the braille section and then change it to human ware braille note. The next time I tabbed there was a combo box where I could change it from serial to serial to usb done some changes and up it come.
I can not remember if in the braille note I had to set it to some thing like use with a screen reader or terminal.
I did do a tutorial on it when I set it up for others who are new even to a old braille display at it is called connecting a braille display to nvda and can be found off the following page at Petrus' It might help.
You might need the driver for your braille display to run it?
Gene nz
On 18/01/2023 15:55, Christopher Gray wrote:
|
|
|
|
Christopher Gray
Below are the log entries at the end of the log that appear to address the braille display.
HTH,
Chris
WARNING - mathPres.initialize (19:10:35.724) - MainThread (14228): MathPlayer 4 not available INFO - core.main (19:10:35.724) - MainThread (14228): Using wx version 4.1.1 msw (phoenix) wxWidgets 3.1.5 with six version 1.16.0 INFO - brailleInput.initialize (19:10:35.725) - MainThread (14228): Braille input initialized INFO - braille.initialize (19:10:35.726) - MainThread (14228): Using liblouis version 3.23.0 INFO - braille.initialize (19:10:35.728) - MainThread (14228): Using pySerial version 3.5 INFO - braille.BrailleHandler.setDisplayByName (19:10:35.738) - MainThread (14228): Loaded braille display driver noBraille, current display has 0 cells. INFO - core.main (19:10:35.952) - MainThread (14228): Java Access Bridge support initialized INFO - UIAHandler.UIAHandler.MTAThreadFunc (19:10:36.036) - UIAHandler.UIAHandler.MTAThread (508): UIAutomation: IUIAutomation6 INFO - core.main (19:10:36.324) - MainThread (14228): NVDA initialized INFO - braille.BrailleHandler.setDisplayByName (19:10:37.802) - braille._BgThread (2896): Loaded braille display driver noBraille, current display has 0 cells. INFO - braille.BrailleHandler.setDisplayByName (19:13:14.112) - braille._BgThread (2896): Loaded braille display driver noBraille, current display has 0 cells. ERROR - unhandled exception (19:14:54.299) - braille._BgThread (2896): Traceback (most recent call last): File "_ctypes/callbacks.c", line 232, in 'calling callback function' File "hwIo\base.pyc", line 150, in _ioDone OSError: [WinError 995] The I/O operation has been aborted because of either a thread exit or an application request. INFO - braille.BrailleHandler.setDisplayByName (19:22:38.655) - braille._BgThread (2896): Loaded braille display driver noBraille, current display has 0 cells. INFO - braille.BrailleHandler.setDisplayByName (19:22:38.699) - braille._BgThread (2896): Loaded braille display driver noBraille, current display has 0 cells. ERROR - stderr (19:22:38.705) - braille._BgThread (2896): Exception in thread braille._BgThread: Traceback (most recent call last): File "threading.pyc", line 926, in _bootstrap_inner File "threading.pyc", line 870, in run File "braille.pyc", line 2371, in func OSError: exception: access violation writing 0xF66A6D9E
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Christopher Gray
Sent: Tuesday, January 17, 2023 9:03 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Braille Display Problem
I am not using a serial to USB cable.
Chris ]
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Hi
Are you using a serial to usb cable? In my case I had to instal a serial to usb driver.
Then after the braille display was turned on and plugged in I had to go into the settings of nvda locate the braille section and then change it to human ware braille note. The next time I tabbed there was a combo box where I could change it from serial to serial to usb done some changes and up it come.
I can not remember if in the braille note I had to set it to some thing like use with a screen reader or terminal.
I did do a tutorial on it when I set it up for others who are new even to a old braille display at it is called connecting a braille display to nvda and can be found off the following page at Petrus' It might help.
You might need the driver for your braille display to run it?
Gene nz
On 18/01/2023 15:55, Christopher Gray wrote:
|
|
|
|
Hi, Sounds like the braille display detector and background output task (BG thread) are getting confusing data... Some more questions:
Cheers, Joseph |
|
|
|
Abbie Taylor
The issue could be with the Brailliant. You might want to contact Humanware about it before sending a bug report to NV Access.
On 1/17/2023 8:22 PM, Christopher Gray
wrote:
-- Abbie Johnson Taylor, Author https://www.abbiejohnsontaylor.com abbietaylor945@... |
|
|
|
Travis Siegel
I'm sorry. How is this a braille display problem? The original poster clearly stated that it works with a previous version of NVDA. Updating NVDA broke the display driver, how is that the manufacturer's fault? You know the response of the manufacturer is simply going to be to either downgrade the NVDA version, or use another screen reader, because it's not their problem. That's assuming of course that they bother to offer a solution at all. Once they hear that a new version of software broke it, their first response is going to be the famous. It's a software problem. And, Honestly, I'm sitting here trying not to laugh, because what did the software folks say? It's a hardware problem.
Chris, downgrade to NVDA 22.3, and see if the proper behavior returns. If it does, there's no problem with the display. If it doesn't, then perhaps it's worth checking with the manufacturer, though even then it's no guarantee, because it could simply be something that 22.4 changed during it's upgrade that doesn't revert with a new install of 22.3.
On 1/18/2023 10:04 AM, Abbie Taylor
wrote:
|
|
|
|
Gene
If something doesn't revert, you could completely remove NVDA and
reinstall it, but before you try that, creating a portable version
of the 22.3 should tell you if the display will continue to work
with that version.
toggle quoted message
Show quoted text
This discussion illustrates a useful feature that I think should be implemented in the NVDA update process. The user could specify that a backup of the current version be made and a command could be implemented in NVDA to allow the user to completely revert, if desired. I really don't like the user updating, in such a way that that the older version becomes unavailable. Gene On 1/18/2023 9:41 AM, Travis Siegel
wrote:
|
|
|
|
Christopher Gray
Is there a way to downgrade to 22.3? I do not see such an option in NVDA. I suppose I could revert to an earlier version of Windows before installing 22.4, but really don’t want to do that.
Chris
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Travis Siegel
Sent: Wednesday, January 18, 2023 7:42 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Braille Display Problem
I'm sorry. How is this a braille display problem? The original poster clearly stated that it works with a previous version of NVDA. Updating NVDA broke the display driver, how is that the manufacturer's fault? You know the response of the manufacturer is simply going to be to either downgrade the NVDA version, or use another screen reader, because it's not their problem. That's assuming of course that they bother to offer a solution at all. Once they hear that a new version of software broke it, their first response is going to be the famous. It's a software problem. And, Honestly, I'm sitting here trying not to laugh, because what did the software folks say? It's a hardware problem.
Chris, downgrade to NVDA 22.3, and see if the proper behavior returns. If it does, there's no problem with the display. If it doesn't, then perhaps it's worth checking with the manufacturer, though even then it's no guarantee, because it could simply be something that 22.4 changed during it's upgrade that doesn't revert with a new install of 22.3.
On 1/18/2023 10:04 AM, Abbie Taylor wrote:
|
|
|
|
Download the older installer, then install, it should downgrade for yhou, or download the old installer and tuirn it into a portable copoy so you can use both.
Good luck.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Christopher Gray
Sent: Wednesday, January 18, 2023 9:46 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Braille Display Problem
Is there a way to downgrade to 22.3? I do not see such an option in NVDA. I suppose I could revert to an earlier version of Windows before installing 22.4, but really don’t want to do that.
Chris
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Travis Siegel
I'm sorry. How is this a braille display problem? The original poster clearly stated that it works with a previous version of NVDA. Updating NVDA broke the display driver, how is that the manufacturer's fault? You know the response of the manufacturer is simply going to be to either downgrade the NVDA version, or use another screen reader, because it's not their problem. That's assuming of course that they bother to offer a solution at all. Once they hear that a new version of software broke it, their first response is going to be the famous. It's a software problem. And, Honestly, I'm sitting here trying not to laugh, because what did the software folks say? It's a hardware problem.
Chris, downgrade to NVDA 22.3, and see if the proper behavior returns. If it does, there's no problem with the display. If it doesn't, then perhaps it's worth checking with the manufacturer, though even then it's no guarantee, because it could simply be something that 22.4 changed during it's upgrade that doesn't revert with a new install of 22.3.
On 1/18/2023 10:04 AM, Abbie Taylor wrote:
-- ---------- Sarah Alawami, owner of flying Blind. Visit my website to read my story. Windows 11 22H2 (x64) build 22621.963 NVDA Version: 2022.3.3 Microsoft 365 MSO (Version 2211 Build 16.0.15831.20098) 64-bit |
|
|
|
Abbie Taylor
Well, my Brailliant 20 works fine with the latest version of
NVDA. I subscribe to the Brailliant list, and I haven't heard of
anyone witha Brailliant 40 having this issue. That's why I suggest
contacting Humanware. The problem could be with the unit itself.
I'd hate to see Chris go through the process of downgrading or
un-installing and re-installing to find out that still doesn't
solve the problem. Also, if another driver is needed for the
Brailliant BI 40, a technical support representative from
Humanware would know where it can be downloaded. Downloading a
driver would be a lot easier than downgrading NVDA. On 1/18/2023 8:41 AM, Travis Siegel
wrote:
-- Abbie Johnson Taylor, Author https://www.abbiejohnsontaylor.com abbietaylor945@... |
|
|
|
Deenadayalan Moodley
Hi,
I also use a Humanware Brailliant with NVDA 2022.4. I am not experiencing any problems. I have the display using the automatic setting.
Thanks.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Christopher Gray
Sent: Wednesday, 18 January 2023 05:23 To: nvda@groups.io Subject: [nvda] Braille Display Issue
Hi:
My braille display is a Brailliant BI 40 from Humanware. I'm connecting it to my PC via USB. The overall setting is Automatic. I tried using the Humanware/Baum/etc setting but that only offers serial connectivity and did not work.
Just to reiterate, when I start NVDA the display clears so I know the connection is active. But, I see no braille. This happened when I updated to the most recent version of NVDA a couple of days ago.
If a new driver is required, can you provide a link?
How do I generate a debug log for you? I'll be happy to send one.
Chris
Hi,
In addition to what Quentin is asking, can you:
Tell us which connection technology you are using (USB, bluetooth, automatic, etc.)? Send a debug log to NV Access (info@...) so folks can diagnose it?
Thanks.
Cheers,
Joseph
|
|
|
|
Travis Siegel
Best to wait and see what Chris wants to do, but seriously, installing another version of NVDA literally took me like 2 minutes when I downgraded because of the Kindle desktop app reading problem. If you're not willing to invest 2 minutes into possibly solving your problem, then I'm not sure why you'd post on the list in the first place. You have to remember that not every machine/hardware combination
is the same. Just because 500 people run the same software setup,
doesn't mean that all 500 people are having identical experiences
with their software/hardware setups. This is a simple easy to implement check that will verify that the update to 2022.4 is indeed the culprit or not. If he installs 22.3, and the problem persists, then it's likely the update to 22.4 wasn't the cause of the error. mind you, that doesn't rule it out entirely, but it's a pretty good bet.
On 1/18/2023 1:53 PM, Abbie Taylor
wrote:
|
|
|
|
Gene
This workaround may help not just in this case, but in others where
an upgrade causes problems but you don't want to revert.
toggle quoted message
Show quoted text
It may be that the best work around for the problem is to use the installer for 2022.3 and use the continue running option instead of creating a portable copy or downgrading. You can start with the current version running, then run the installer which will shut down the currently running version and run the 2022.3 version. You would then check the I agree license and tab to continue running and press the space bar, it's a button. When you have an installed version and you run another version in this way, all your settings are used from the installed version and all add-ons are used unless they are incompatible. And since there already is an installed version, when you get a message from UAC and/or have to use a secure desktop screen, the installed version will automatically run so you have just as much access as if you were only running the installed version. When you return to the usual screens, the version you were running from the installer automatically runs again. If you downgrade, I don't know if there could be any problems but, assuming this problem will be fixed if it is one that is a general problem and not something on this one machine, my work around allows you to leave the current version installed while using the previous version as though it were installed. You could create a shortcut on the desktop for the installer and a short cut command so you could run it conveniently once the installed version automatically runs after boot up . I am running 2022.3 as I described because of the Kindle problem, discussed a number of days ago, probably on the main list. Since the 2022.3 version does everything I want, but I don't want to revert, I run 2022.3 at the start of a session and let it run. Gene On 1/18/2023 11:50 PM, Travis Siegel
wrote:
|
|
|