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
Freedom Scientific Focus Series' input aren't received when port is set to USB #3662
Comments
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 |
Comment 2 by twynn92 on 2013-11-26 08:24 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
|
Comment 9 by James Teh <jamie@... on 2013-11-28 03:14
|
Comment 10 by jteh on 2013-11-28 03:19 |
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:
Conclusions:
Logs for each startup of NVDA are attached.
The text was updated successfully, but these errors were encountered: