Braille input suddenly stops with Braille Connect 40

[nvaccessAuto]

Reported by Alpha129 on 2013-01-13 05:02
Using NVDA brailleInput, snapshot 5681. When using the BrailleConnect 40 (using the Baum protocol), after a short period of time, inputting of text via the display is no longer possible. This is one that is hard to reproduce, as I can be doing one thing, say writing up some document in Word, and it works. If I sswitch to a different application, inputting works, and sometimes doesn't work, say into a edit field. The log shows nothing of any errors that could have happened either.
Blocked by #3541

[nvaccessAuto]

Comment 1 by jteh on 2013-01-13 23:51
Once it stops working:

1. Does it ever start working again or do you have to restart NVDA?
2. Does it report anything in input help mode?
3. What about the Braille space bar?
4. Do any other buttons on the Braille display stop working or just the Braille entry keys?

[nvaccessAuto]

Comment 2 by Alpha129 (in reply to comment 1) on 2013-01-15 04:38

1. Restarting NVDA kind of does it, but goes away after a certain period of time again.
2. In input help mode, it reports them as regular B1, B2, B3 etc.
3. The space bar becomes inactive.
4. Commands such as advancing the display still work, so just computer braille entry.

Replying to jteh:

Once it stops working:

1. Does it ever start working again or do you have to restart NVDA?
2. Does it report anything in input help mode?
3. What about the Braille space bar?
4. Do any other buttons on the Braille display stop working or just the Braille entry keys?

[nvaccessAuto]

Comment 3 by jteh (in reply to comment 2) on 2013-01-20 22:58
Replying to Alpha129:

1. Restarting NVDA kind of does it, but goes away after a certain period of time again.

So it never works again until you restart?

1. In input help mode, it reports them as regular B1, B2, B3 etc.

I think this is probably always the case, even when input is working correctly.

1. The space bar becomes inactive.

Is it reported correctly in input help when input works?

I can't think of a reason this should stop working, so unfortunately, there's probably nothing I can do unless I can get hold of a display.

[nvaccessAuto]

Comment 4 by Alpha129 (in reply to comment 3) on 2013-01-25 01:35

1. Correct, inputting stops again when NVDA is restarted.
2. The space bars are reported as B9 and B10 in input help mode.

I can't think of why it stops either. If I, for example, go to wordpad, I can type i n correctly with computer braille. If I move away from it, and come back to it (alt+tab), it stops then.

Replying to jteh:

Replying to Alpha129:

1. Restarting NVDA kind of does it, but goes away after a certain period of time again.

So it never works again until you restart?

1. In input help mode, it reports them as regular B1, B2, B3 etc.

I think this is probably always the case, even when input is working correctly.

1. The space bar becomes inactive.

Is it reported correctly in input help when input works?

I can't think of a reason this should stop working, so unfortunately, there's probably nothing I can do unless I can get hold of a display.

[nvaccessAuto]

Comment 5 by jteh on 2013-01-25 01:55
Can you please install this QWERTY Braille Input global plugin? Then, when input stops working on your display, press NVDA+z and try typing Braille on your QWERTY keyboard (e.g. press f for dot 1). Does it work with that?

[nvaccessAuto]

Comment 6 by Alpha129 (in reply to comment 5) on 2013-02-08 02:23

Replying to jteh:

Can you please install this QWERTY Braille Input global plugin? Then, when input stops working on your display, press NVDA+z and try typing Braille on your QWERTY keyboard (e.g. press f for dot 1). Does it work with that?

Yes, pressing the l letter F on the laptop keyboard emulates the letter A in braille.

[nvaccessAuto]

Comment 7 by jteh on 2014-04-14 04:09
Marking as a duplicate of #3541, as I'm pretty sure this is the same issue and that ticket has more technical info.
Changes:
Added labels: duplicate
State: closed