You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have successfully updated my DIY Soarer converter to use the new firmware and initial testing showed it was okay. (even got to configure a few things in VIAL)
However, after a few days of light usage, I noticed the keyboard frequently (every 30-60 seconds) becomes unresponsive for a second or two, after which it flashes the Num Lock LED and then starts operating normally again.
I have reverted to Soarer’s firmware and it works fine, so there appears to be no hardware issues (Arduino Pro Micro USB-C – ATMEGA32U4 )
This is the command I used for the flash the firmware (relatively the same as I initially used for soarer's converter firmware)
I do not have another keyboard to test this but I have tested it with Soarer's converter firmware without issue for several months
I believe that the problem is unlikely to be related to a hardware issue.
I can try compiling with fewer features, though I am not sure which ones would be good candidates.
If you have recommendations, let me know
I have successfully updated my DIY Soarer converter to use the new firmware and initial testing showed it was okay. (even got to configure a few things in VIAL)
However, after a few days of light usage, I noticed the keyboard frequently (every 30-60 seconds) becomes unresponsive for a second or two, after which it flashes the Num Lock LED and then starts operating normally again.
I have reverted to Soarer’s firmware and it works fine, so there appears to be no hardware issues (Arduino Pro Micro USB-C – ATMEGA32U4 )
This is the command I used for the flash the firmware (relatively the same as I initially used for soarer's converter firmware)
Have any idea what could be going wrong?
The text was updated successfully, but these errors were encountered: