UHK80 connected via USB sometimes seems not to send keypress information after being idle

[ilya-sarantsev]

I have a UHK80 connected via USB (no Bluetooth, no battery) to a MacBook Pro 16-inch, Nov 2024. It works fine most of the time, but sometimes when it has been idle for a while (even a couple of minutes while I'm off in the kitchen making tea) it stops sending any keypress information. What I mean is that it correctly turns the backlight on when I type, but nothing appears on the screen, and no control buttons work. It never happens during active typing.

Firmware 15.3.1. Reconnecting the USB cable fixes the problem.

[ilya-sarantsev]

Maybe it was incorrect to say "no Bluetooth", as it is always enabled right? I just didn't even try it out, I only use the keyboard via cable.

[kareltucek]

When this happens, does the oled react to layer switching?

[ilya-sarantsev]

@kareltucek hi! I'll make sure to check.

[ilya-sarantsev]

@kareltucek hi! Has just happened again while I was actively using the keyboard, so not even while being idle. It continues to light up, modes light up accordingly, but nothing happens when I press keys.

Fn -> Function layer lights up -> Press buttons -> Nothing happens (expected to increase/decrease sound for example)
Mouse -> Mouse layer lights up -> Press movement buttons -> Nothing happens (expected the cursor to move)

Re-connect USB, and above mentioned scenarios start working.

[ilya-sarantsev]

@kareltucek hi! Do you have any update? I have to re-connect my keyboard multiple times a day, this is really suboptimal 🥲

[kareltucek]

@ilya-sarantsev thanks for headups and sorry for forgetting about this!

Unfortunately no. We will need to have Benedek take a look, but first we need to pinpoint the issue better.

The above tells me that the keyboard is alive and responsive, but some or all usb interfaces stopped functioning. Is Agent functional in this state?

If yes, please try keeping agent open with right half logs enabled ( https://uhk.io/knowledgebase/how-to-report-firmware-issues ) and see if there are any c2usb logs when this happens.

If you are up to it, it may be useful to capture wireshark log of the usb interface.

Also please try to plug the UHK into a different port. It is a lame advice, but it turns out that in some cases it actually makes a difference.

[ilya-sarantsev]

@kareltucek yeah, it seems like when the issue occurs, it disconnects it completely

btw, when you say different port, do you mean a different laptop port, or a different port keyboard port (as in left/right half ports)?

[kareltucek]

I mean different laptop port.

With 16.1.1 firmware, you should be able to get some logs out of UHK even when usb is out of order. Please follow this guide and improvise a bit: https://github.com/UltimateHackingKeyboard/firmware/blob/master/doc-dev/other/troubleshooting_c2usb.md My guess is that the most interesting will be a snaplog issued right after the usb stops working. Then reconnect and open agent to retrieve it.

[ilya-sarantsev]

@kareltucek hi! I'm reading the instructions.

Reproduce the issue.
Run the snaplog macro. This will export the usb log buffer into the persistent status buffer.

Not sure I understand, how do I run a macro when the keyboard is unresponsive?

Bring usb back to life. If need be, restart uhk using its reset button, but do not powercycle it.

I assume powercycling means unplugging it from the USB and plugging it back in? And reset will erase all my custom settings and macros, right?

[kareltucek]

It continues to light up, modes light up accordingly, but nothing happens when I press keys.

This means that the keyboard is still operating fine, except its usb stack. Macros run on the keyboard, so you just tap the relevant key.

I assume powercycling means unplugging it from the USB and plugging it back in? And reset will erase all my custom settings and macros, right?

In case you don't have batteries, yes 🤦. I assumed you had one.

Pressing the reset button will just reboot the board. All settings remains in place.

Let me check a few things and get back to you.

[kareltucek]

One more thing you need to have in $onInit - otherwise the log will get deleted when initializing buffers:

set devMode true

Without pulling usb/power, you can reboot the uhk by either the reset button or by a reboot macro, whichever is more comfortable for you.

That's all that comes to mind.

[ilya-sarantsev]

@kareltucek hi! I wanted to go over this again to make sure I understand everything. I need help with printStatus.

1. I have created the $onInit macros:

set devMode true
zephyr uhk logs 1
zephyr log enable wrn Battery
zephyr log enable wrn Bt
zephyr log enable wrn StateSync
zephyr log enable inf udc
zephyr log enable wrn udc_nrf
zephyr log enable inf hogp
zephyr log enable dbg c2usb

It now prints a bunch of information in the Advanced settings window:

2. I have also created macros to run reboot, zephyr uhk snaplog and printStatus:

reboot works as expected
zephyr uhk snaplog apparently does something, but I'm not sure what it does. It prints in the Advanced settings log:

Executing following command from macro: 'uhk snaplog'
Log snapped to status buffer.

printStatus doesn't seem to do anything. I search in manual and still don't quite understand how to use it. Could you help here?

And when everything is up and running, the idea is to:

1. Wait till the issue occurs
2. Run zephyr uhk snaplog
3. Run reboot
4. Run printStatus to get the logs

Is it right?

[kareltucek]

Ah, sorry, there is a trap. Agent consumes the log buffer periodically, so when you use the snaplog command while Agent is running, you get a snap of an empty buffer.

To test the function:

• close Agent
• wait a couple minutes until some logs accumulate or just use some macros that produce logs
• run the zephyr uhk snaplog macro
• open Agent
• you should see a yellow bar

[ilya-sarantsev]

@kareltucek does this say anything? I followed the instructions and pressed snap logs when the keyboard was unresponsive, then restarted, and found this in the Agent (yellow block):

.1.1 / 6cf33b1813f6bf84474b4618824dd9e4)
StateSync: Setting battery mode to 0
Allocating unregistered bonds
StateSync: Resetting left right link! Unidirectional
User config applied
Enabling UART
NusServer: NUS Server module initialized.
Scan module initialized
NusClient: NUS Client module initialized
Bt: Starting bluetooth services.
Bt: BtManager: Start 'advertising and scanning' (0).
Bt: filling scan filters
executing over shell_bt_nus
Executing following command from macro: 'uhk logs 1'
Usb logging enabled: 1
Has log: 0
Usb log buffer fill: 0 / 2048
executing over shell_bt_nus
Executing following command from macro: 'log enable wrn Battery'
executing over shell_bt_nus
Executing following command from macro: 'log enable wrn Bt'
executing over shell_bt_nus
Executing following command from macro: 'log enable wrn StateSync'
executing over shell_bt_nus
Executing following command from macro: 'log enable inf udc'
executing over shell_bt_nus
Executing following command from macro: 'log enable wrn udc_nrf'
executing over shell_bt_nus
Executing following command from macro: 'log enable inf hogp'
executing over shell_bt_nus
Executing following command from macro: 'log enable dbg c2usb'
USB config changing to Hid_NoGamepad
StateSync: Batteries: 0% 0% (0 0)
Conn: UartLeft: (Ready)
StateSync: