Hi Dave and Mario: This journey seems to get a bit stranger as I dig
into the problem. I did as both of you suggested and in the end used
both the inpkts and brlkeys arguments to the -l flag. I'm afraid I
couldn't make much sense out of the inpkts data because I don't
understand the format. In either case I didn't see much in the way of
output related directly to the braille keyboard but as I said that
maybe because i don't understand the format of the inpkts flag. What I
can say which is more confusing is that the braille keyboard did
provide up-arrow, down-arrow, left and right arrow keys along with the
enter and space bar. I could move up, down and so forth on the bash
command line and in an editor. None of the other keys seem to have had
any affect. To be clear that was using chord-1, chord-4, chord-2 and
chord-5 combinations.
Here is the combined log from my last experimentation if you folks
might be kind enough to have a gander to see if I missed anything
significant.
https://reisers.ca/brl.log
Kirk
On Thu, 12 Oct 2023, Dave Mielke wrote:
[quoted lines by Kirk Reiser on 2023/10/11 at 12:17 -0400]
if someone could tell me how to troubleshoot to figure out if it is in
fact a hardware problem or software problem.
You could capture a brltty debug log. You can use the -L (uppercase) option to
specify the file to write the log to, and the -linpkts (this -l is lowercase)
to tell it to log input packets from the device. Then press keys and see what
shows up.
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty
