NumLock point does't work anymore

[necsoiu]

Describe the bug NumLock point does't work anymore

To Reproduce Press point (.) on NumLock

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Chrysalis Version: 0.11.8

chrysalis-debug.json.txt

[obra]

If you map that physical key to another key (like the regular period key), does it work?

Do you know what caused it to stop working? (What changed that caused it to stop working)?

Best, jesse

On Sat, Oct 22, 2022 at 1:48 AM necsoiu @.***> wrote:

Describe the bug NumLock point does't work anymore

To Reproduce Press point (.) on NumLock

Expected behavior A clear and concise description of what you expected to happen.

Screenshots [image: numlock point] https://user-images.githubusercontent.com/1866443/197330209-d5100730-d65c-439f-96c4-d5a4172784dd.png

Desktop (please complete the following information):

• OS: Windows 11
• Chrysalis Version: 0.11.8

chrysalis-debug.json.txt https://github.com/keyboardio/Chrysalis/files/9843905/chrysalis-debug.json.txt

— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1193, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2BPC32LR7OGQ3LZBLTWEOS4BANCNFSM6AAAAAARLYHTQQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[necsoiu]

" If you map that physical key to another key (like the regular period key), does it work?" YES it works. " Do you know what caused it to stop working? (What changed that caused it to stop working)? It stopped working after the firmware update.

În lun., 24 oct. 2022 la 19:42, Jesse Vincent @.***> a scris:

If you map that physical key to another key (like the regular period key), does it work?

Do you know what caused it to stop working? (What changed that caused it to stop working)?

Best, jesse

On Sat, Oct 22, 2022 at 1:48 AM necsoiu @.***> wrote:

Describe the bug NumLock point does't work anymore

To Reproduce Press point (.) on NumLock

Expected behavior A clear and concise description of what you expected to happen.

Screenshots [image: numlock point] < https://user-images.githubusercontent.com/1866443/197330209-d5100730-d65c-439f-96c4-d5a4172784dd.png

Desktop (please complete the following information):

• OS: Windows 11
• Chrysalis Version: 0.11.8

chrysalis-debug.json.txt < https://github.com/keyboardio/Chrysalis/files/9843905/chrysalis-debug.json.txt

— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1193, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAALC2BPC32LR7OGQ3LZBLTWEOS4BANCNFSM6AAAAAARLYHTQQ

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/keyboardio/Chrysalis/issues/1193#issuecomment-1289306231, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOHVS2QHFKOEMKYLAUQRMLWE236ZANCNFSM6AAAAAARLYHTQQ . You are receiving this because you authored the thread.Message ID: @.***>

-- O zi cât mai plăcută! Paul Necșoiu Tel: 0721 36 75 33 E-mail: @.***

[necsoiu]

If you map that physical key to another key (like the regular period key), does it work? Do you know what caused it to stop working? (What changed that caused it to stop working)? Best, jesse … On Sat, Oct 22, 2022 at 1:48 AM necsoiu @.> wrote: Describe the bug NumLock point does't work anymore To Reproduce Press point (.) on NumLock Expected behavior A clear and concise description of what you expected to happen. Screenshots [image: numlock point] https://user-images.githubusercontent.com/1866443/197330209-d5100730-d65c-439f-96c4-d5a4172784dd.png Desktop (please complete the following information): - OS: Windows 11 - Chrysalis Version: 0.11.8 chrysalis-debug.json.txt https://github.com/keyboardio/Chrysalis/files/9843905/chrysalis-debug.json.txt — Reply to this email directly, view it on GitHub <#1193>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2BPC32LR7OGQ3LZBLTWEOS4BANCNFSM6AAAAAARLYHTQQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

We really need to solve this issue. Strange thing is that on other Atreus with the same firmware version and same configuration it works. If needed I can provide debug files for both keyboards. In this moment both have version 0.12 of Firmware and are on the same SO (Windows 11).

Curios thing is that on the computer where it does't work I have other problem too which is reported here [https://github.com/keyboardio/Chrysalis/issues/733]. I think they may be related and should be investigated together.

Another aspect is that one of the keyboards is older and another newer. Has something changed in the keyboard hardware that could lead to these two problems?

[obra]

if you swap the two keyboards, what happens?On Jan 6, 2023, at 7:20 AM, necsoiu @.***> wrote:

If you map that physical key to another key (like the regular period key), does it work? Do you know what caused it to stop working? (What changed that caused it to stop working)? Best, jesse … On Sat, Oct 22, 2022 at 1:48 AM necsoiu @.> wrote: Describe the bug NumLock point does't work anymore To Reproduce Press point (.) on NumLock Expected behavior A clear and concise description of what you expected to happen. Screenshots [image: numlock point] https://user-images.githubusercontent.com/1866443/197330209-d5100730-d65c-439f-96c4-d5a4172784dd.png Desktop (please complete the following information): - OS: Windows 11 - Chrysalis Version: 0.11.8 chrysalis-debug.json.txt https://github.com/keyboardio/Chrysalis/files/9843905/chrysalis-debug.json.txt — Reply to this email directly, view it on GitHub <#1193>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALC2BPC32LR7OGQ3LZBLTWEOS4BANCNFSM6AAAAAARLYHTQQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

We really need to solve this issue. Strange thing is that on other Atreus with the same firmware version and same configuration it works. If needed I can provide debug files for both keyboards. In this moment both have version 0.12 of Firmware and are on the same SO (Windows 11). Curios thing is that on the computer where it does't work I have other problem too which is reported here [https://github.com//issues/733]. I think they may be related and should be investigated together. Another aspect is that one of the keyboards is older and another newer. Has something changed in the keyboard hardware that could lead to these two problems?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[necsoiu]

On the HP computer both keyboards seems to work fine. So I guess it may be something that is not compatible with ASUS motherboards. Do you think it can be solved?

[necsoiu]

OK. So today I solved the problem, but I haven't fully identified what caused the problem to be solved so I will detail the steps I took.

1. I made a motherboard BIOS update. (then I tested but the problem still exists).
2. I pluged a comercial keyboard to test if works (with this keyboard everything worked well, but with Atreus still don't)
3. I locked the Atreus to first level to test if on this level the numpad dot works (surprise, it worked).
4. Reverted back Atreus to layer 0 and surprise, surprise, it worked here too.

So in the end I think it could be the

1. The BIOS
2. Or the comercial keyboard somehow unlocked something
3. Or changing Atreus on layer 1 somehow unlocked something. I mention that on layer 0 the numpead keys ar accessed by pressing a layer shift key (to the leyer 1).

Anyway I'm super happy that this problem was solved.