Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no stroke recognition / flashing problem? #15

Closed
Halem998 opened this issue Jun 25, 2023 · 9 comments
Closed

no stroke recognition / flashing problem? #15

Halem998 opened this issue Jun 25, 2023 · 9 comments

Comments

@Halem998
Copy link

Halem998 commented Jun 25, 2023

I think I successfully flashed the firmware, or so I thought.
My keyboard is being recognised but upon typing I don't see any output, alas. I'm wondering what could have gone wrong here

@urob
Copy link
Owner

urob commented Jun 25, 2023

It sounds like it isn't paired correctly. If you had it paired before and your previous build didn't have mouse-keys enabled, then you will need to re-set the pairing: 1. Forget bluetooth device on windows, 2. clear bluetooth connection on the 360, 3. re-pair

(This is necessary the first time you are enabling mouse keys, because the OS needs to change the driver from keyboard to keyboard + mouse)

@Halem998
Copy link
Author

unfortunately, still not working.
I'm on MacOS Catalina fwiw

maybe for some reason, my OS doesnt get to do the mouse + keyboard driver thing?

@Halem998
Copy link
Author

I just realised: it works when plugged in! it's a bluetooth thing.

@urob
Copy link
Owner

urob commented Jun 28, 2023

Another thing you could try if you haven't gotten Bluetooth to work yet:

https://zmk.dev/blog/2023/04/06/zephyr-3-2#known-issues

Afaik the official Kinesis firmware is still running on zephyr 3.0. That's why this steps may gut be necessary

@Halem998
Copy link
Author

Halem998 commented Jun 28, 2023

Oh! you just made me realise: when trying to BT_CLR I pressed the default 360-macro being mod + gui.

So when thinking of reset, I actually did not.

...
But I don't actually know how to access the sys layer yet.
How would that work?

Edit: Fn+Num it is. But still not quite sure ... I usually got a cue from the lights blinking. I must be doing it wrong

@urob
Copy link
Owner

urob commented Jun 29, 2023

I have leds disabled in my main branch. For the layout see the image in the readme.

@Halem998
Copy link
Author

I still don't get it :/

There is this line of code #define _BT_SEL_KEYS_ &bt BT_SEL 0 &bt BT_SEL 1 &bt BT_SEL 2 &bt BT_SEL 3 &bt BT_CLR

I know to Fn+Num and then the BT key. But what do I do to cycle to BT_CLR?
Sorry, I really am kinda retarded

Screenshot 2023-06-30 at 17 06 52

@urob
Copy link
Owner

urob commented Jun 30, 2023

I still don't get it :/

There is this line of code `#define BT_SEL_KEYS &bt BT_SEL 0 &bt BT_SEL 1 &bt BT_SEL 2 &bt BT_SEL 3 &bt BT_CLR

`

I know to Fn+Num and then the BT key. But what do I do to cycle to BT_CLR?

Sorry, I really am kinda retarded

Screenshot 2023-06-30 at 17 06 52

BT_SEL_KEYS expands to the definition above. So BT_CLR is on the inner index position in that row.

@Halem998
Copy link
Author

Halem998 commented Jul 9, 2023

BT_SEL_KEYS expands to the definition above. So BT_CLR is on the inner index position in that row.

What exactly do you mean by that?
Could you possibly give an example where for example BT_2 is being cleared? I pressed the BT_SEL key and the key right to that simultaneously but I failed once again ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants