Hi Dave: That log output was exactly what brltty provided when using
both the inpkts and brlkeys flags to -l. I didn't modify it in any
way.
I don't know about hci or what the manual says because the manual
which came with the unit on it's build-in ramstick got blown away by
mistake quite a few
[quoted lines by Kirk Reiser on 2023/10/13 at 10:05 -0400]
Do you happen to know (perhaps from the manual) if the keyboard emulates a PC
HID keyboard? If so, it mightn't be sending data that brltty can see.
>Here is the combined log from my last experimentation if you folks
>might be kind
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
[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,
