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

Already on GitHub? Sign in to your account

Freedom Scientific Focus Series' input aren't received when port is set to USB #3662

nvaccessAuto opened this Issue Nov 26, 2013 · 8 comments


None yet
2 participants

Reported by twynn92 on 2013-11-26 07:28
When you set the port to USB in NVDA --> Preferences --> Braille settings, buttons on the display work only until the next restart of NVDA. From that point on, output appears on the display, but no keys are registered by NVDA.

Steps to reproduce:

  1. Start NVDA, and load the Focus display with the port set to USB, not Automatic.
  2. Press a few keys.
    • Note; In my example, I typed the equals key (dots 1-2-3-4-5-6) four times.
  3. Restart NVDA. You will notice that the Focus display is no longer loaded. Go into the Braille settings again, and attempt to change to the Focus display with USB as its port. You'll notice that you cant. Change to the port Automatic instead, and it will load.
  4. Once it has loaded, try and type a few keys.
    • Note: NVDA doesn't log this, but I again typed equals four times.
  5. Restart NVDA again. You'll notice this time that the Focus display loads.
  6. Type a few keys, and you notice they work.
    • Note: Again, I proceeded with typing equals four times.


  1. If the port is set to USB, input will only work for that session. If NVDA is restarted, it can't load the display unless you set the port to Automatic, but input will not register. You can then choose USB as the port and it will once again work, but input will still be broken. If you restarted having the port set to USB, again the same scenario will occur - no input or loading of display.
    • Note: I actually did this in earlier tests, but didn't log them.
  2. If the port is set to Automatic, input works fine. When restarting, input still works fine and the display is loaded on startup.

Logs for each startup of NVDA are attached.

Attachment 01.log added by twynn92 on 2013-11-26 07:29

Attachment 03.log added by twynn92 on 2013-11-26 07:30

Attachment 02.log added by twynn92 on 2013-11-26 07:35

Comment 1 by jteh on 2013-11-26 07:58
Do you also have the display paired via Bluetooth? Automatic just tries USB then Bluetooth; it's the same code path for USB as far as I can see. If you do have it paired, it's probably falling back to Bluetooth at startup for automatic.
Exactly which display do you have?
Which USB driver are you using: the one listed in the NVDA User guide or the more recent driver? (See #3585.)

Comment 2 by twynn92 on 2013-11-26 08:24
My display is not currently paired via Bluetooth. The Bluetooth dongle isn't even connected, and switching to Bluetooth as the Port results in an error. Also, checking the status (a feature in the display) while in Automatic port mode, it says USB on the right.

I have the Focus 14 Blue, firmware 5.49. The driver I use is version 1.0.2028, found on the new download page referred to in the aforementioned ticket.

Update: I connected my display via Bluetooth, and connection is established, though input doesn't register. If I go back, and choose the display again, the connection is lost entirely. I would have to go into Toshiba's Bluetooth's settings, disconnect from the display, and reconnect to it. I can then connect to the display again, but input still doesn't register (whether I choose Bluetooth or automatic as the port).

Update: On my PC, which essentially runs the same configuration, the USB connection always works no matter what I choose as the port. Bluetooth, using the same stack and dongle, only works once, but input registers fine. If I wish to use the Bluetooth connection a second time, I'd have to disconnect and reconnect from the Bluetooth settings. Same driver is used for the Braille Display.

Comment 8 by James Teh <jamie@... on 2013-11-28 03:14
In [84fc046]:

Freedom Scientific Braille display driver:  make sure to give port strings to fbOpen as ANSI rather than unicode. Specifically USB could fail as  it could be unicode when coming from the config. Re #3662 Re #3509

Comment 9 by James Teh <jamie@... on 2013-11-28 03:14
In [9dee70e]:

Freedom Scientific braille display driver: if  the driver cannot be initialized with any of the ports, make sure to clean up our message window and its window class. this this is not done, subsiquent successful initializations will fail to get braille display input as the message window could not be properly registered. Re #3662 Re #3401

Comment 10 by jteh on 2013-11-28 03:19
This should now be fixed. The fix has been committed to the rc branch, so it will be in 2013.3rc4.
Milestone changed from None to 2013.3
State: closed

@nvaccessAuto nvaccessAuto added this to the 2013.3 milestone Nov 10, 2015

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