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
BrailleNote: Support for BrailleNote Touch via USB HID/new protocol #6524
Comments
I've been in contact with HumanWare about this already.
Thanks! P3 because we want to support as many braille displays as possible, but this is new enough that it's also not urgent. |
Hi. |
Hi, last time I talked to Greg Stilson from HumanWare, a Touch should emulate newer Brailliant models. Thanks.
From: Nicklas Tegner [mailto:notifications@github.com]
Sent: Thursday, August 31, 2017 12:27 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Author <author@noreply.github.com>
Subject: Re: [nvaccess/nvda] BrailleNote: Support for BrailleNote Touch via USB HID/new protocol (#6524)
Hi.
Are there any plans as to when the Braillenote Touch is going to be supported.
I've tested the support with NVDA version 2017.3, tried to connect it with every type of Humanware display in "braille settings" but it didn't work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#6524 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkGg3tGL5ZVN71c-zctfL2QzyCPtUks5sdmBQgaJpZM4KlODM> .
|
Hi. |
Sorry, but you realy have selected Papenmeyer Braille displays?
Brailliant is a Humanware model...
Rui Fontes
…-----Mensagem Original-----
De: Nicklas Tegner
Data: 31 de agosto de 2017 13:54
Para: nvaccess/nvda
Cc: Subscribed
Assunto: Re: [nvaccess/nvda] BrailleNote: Support for BrailleNote Touch via
USB HID/new protocol (#6524)
Hi.
I can confirm that, that isn't the case.
When I connect my bnt with the provided usb cable, install the usb serial
drivers from humanware's website and go and try to set it up with nvda it
just gives the following message:
Could not load the papenmeier display.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I have a branch (brailliantBtHid) which updates the Brailliant B driver to support the BN Touch, among other things. Unfortunately, despite using the correct protocol, etc., it apparently doesn't work, even though it works just fine with the Brailliant via USB (and is the same protocol). I suspect some weirdness with either the HumanWare firmware or some Windows driver. In any case, we're going to need to debug this with a display. I won't have time to do this before I leave, so @michaelDCurran will work with HumanWare to take care of this when he is able (though that may take some time given the transition at NV Access). @NicklasMCHD, I'm not sure what serial driver you're referring to, but as far as HumanWare have told me, the BN Touch does not use USB serial. Instead, it uses USB HID, which does not need a driver installed. |
Has anyone tried this driver from Humanware? See http://support.humanware.com/index.php?Action=Page.Link&PageLink=11541&To=http%3A%2F%2Fwww.humanware.ca%2Fweb%2FHumanWare%2FBrailleDrivers%2FBrailleTerminalTools2_1_0_6.exe |
Humanware have finally managed to get me a BrailleNote Touch so I can continue work on the driver. I now have it and am getting used to its layout and settings before I start looking into debugging / fixing the USB HID driver in the next few days. Bluetooth is working okay for me. |
@michaelDCurran: Are you going to base this on @jcsteh's (brailliantBtHid branch (i.e. does it also implement Bluetooth HID)? |
I'd recommend basing any further work on that branch, as it includes other changes necessary to support these newer HumanWare displays as well.
|
I haven't properly looked into this yet, but I'm not quite sure what you
mean about bluetooth HID... Current versions of NVDA seem to work fine
with this device via Bluetooth and I did not need to install any
drivers. Is it Bluetooth serial by default and I'm just lucky Windows 10
supports this Bluetooth device? Or is it already Bluetooth HID. I have
not yet seen any settings on the Device to change what kind of Bluetooth
it is. I only see a choice of Bluetooth or USB.
I'll start looking at Jamie's branch tomorrow.
|
Only the Brailliant uses Bluetooth HID and only in OpenBraille mode. Other displays use USB HID and Bluetooth serial.
|
Ah. After resetting the device, Brailliant driver in NVDA no longer
shows up. There must be settings somewhere on the device then.
|
I believe the BrailleNote can emulate the Bluetooth name of the Brailliant in order to support older screen readers. However, it's still Bluetooth serial regardless, even in native mode.
|
Now using Jamie's branch Bluetooth is working well. I am guessing that when I received the device it was still on an older version where the bluetooth name had Brailliant in it. It now just says BrailleNote Touch after I reset / updated the device. |
What happens if you disable reading? My hypothesis is that the device
doesn't like us waiting on a read for some reason while we're also writing.
This doesn't make sense, since reading is actually just retrieving from a
circular buffer that Windows maintains as it receives HID input reports,
but maybe there's some weird interaction I'm not understanding.
|
@michaelDCurran commented on 21 feb. 2018 12:04 CET:
May be instead of using two hwIo.Hid instances, you need to use different endpoints for I/O. I belief I pointed that out as an idea to @jcsteh before he left. See the Hims driver as an example, however that uses Bulk instead of HID. |
Hi,
I haven't forgotten about my work on supporting Apex's scroll wheel and others...
According to a HumanWare staff, BrailleNote Touch firmware 2.0 includes a braille display mode to allow it to act as a braille display, with the Touch using USB HID and a new protocol (no more need for a custom USB serial driver). I plan to ask HumanWare AU to let @jcsteh have a demo unit so he can investigate this further.
Thanks.
The text was updated successfully, but these errors were encountered: