noroadsleft / qmk_firmware

keyboard controller firmware for Atmel AVR and ARM USB families
http://qmk.fm
GNU General Public License v2.0
2 stars 2 forks source link

[Feature Request] Rotary Encoder #1

Closed jolo2020 closed 2 years ago

jolo2020 commented 3 years ago

Feature Request Type

Description

I don't think, that I've chosen the right issue type, sorry about that. Attached you'll find a picture of soldering work done on an Iris PCB. Is there a way to use the unused pins of the atmega in a similar way (solder the wire of an encoder to holes in the PCB) or do I have to solder directly on the microcontroller (since the wings board has an integrated chip)?

20210306_082734

(Image by jhelvy)

noroadsleft commented 3 years ago

Sorry, but I'm greatly confused by your post.

Well first your post is super helpful!

You reference a "super helpful" first post that apparently I made, but have started a new issue on my qmk_firmware fork; so there's no included context. I don't know what post to which you are referring – if you can link me to the post you're referring to that would be a big help.

But is it possible to describe which pins are unused? I am new to the qmk language and want to go straight for a big project (adding a encoder to ymdk wings).

I don't know offhand, but it probably wouldn't be hard to determine.

Furthermore, do you have any actual keymapping after the definition of variables to share?

Not sure what variables you're referring to here. Do you mean for setting up the rotary encoder?

jolo2020 commented 3 years ago

Sorry my bad it's this post:

https://github.com/noroadsleft/qmk_firmware/blob/master/keyboards/ymdk/wings/config.h

I am quite new to everything so please excuse my stupid questions :).

I would really appreciate some guidance to programming the encoder, where to solder on the atmega32u4 and furthermore a normal keymap (qwerty), because I failed last time programming the keymap :(.

Thank you already!!

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

github-actions[bot] commented 2 years ago

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know. // [stale-action-closed]