deskthority

it will generate a matrix based on the layout, you would need to manually edit each switch to make sure it matched the matrix that you drew out. otherwise you would get errors like a f when should be a g etc

the code you get from keyboardlayouteditor.com would need to be pasted into kbfirmware.com, you will need to set up your matrix, teensy pins, cps lock pin, keymap etc then further edit those files for your ctrl 1= F1 before compiling into a .hex file. Then you would need to flash that file to the te...

that can be soldered to any pin, you will probably need to add a resistor though

here is the pinout of the teensy2++ https://www.pjrc.com/teensy/pinout4a.png you will want to keep pins D0 and D1 free if you are going to be using a screen as it will need those pins As has been mentioned D6 does have an on board LED which can cause errors so best to avoid that pin other then that ...

well you are in luck, this has been done, however the programming needed is above my level so unfortunately i will not be able to help you out directly but this is where you need to start https://www.reddit.com/r/MechanicalKeyb ... amic_info/

you will not be able to get that screen working along with having the programmable keyboard as you want it. It is possible to have an OLED screen however again it would need programming which is beyond my expertise. what exactly were you wanting to use the screen for in any case?

that code from the keyboard layout editor site is then input into the kbfirmware.com site in order to then make the files that would be needed. the code i linked would need to be added to one of the files that is generated by kbfirmware.com

it will i think be possible, however it would need writing code for it to work so i will see what i can find. Ok it looks like this can be done, assuming the code on the following still works https://www.reddit.com/r/olkb/comments/9eohzf/qmk_using_ctrl_as_fnkey_only_for_a_few_keys/ as this is a cust...

For that you would set up a dedicated FN key so you would hold down that key that would change the layer. It is best not to use modifiers as these functions are already hard coded to what keys they operate on.

I guess you would put the | key in the bottom right, though it will not matter for generating the keymap as that key itself is just seen as KC_GRAVE where the `~ key would be if on a US board. Windows would then translate that key into the regional graph.

for the Teensy, i said i would send you one, just pm me your address and i will post it this evening after i get home from work. As for the cable, why don't you ask Saintgo himself via pm he is on this forum, along with other keyboard communities also.

Also had a look at the links you posted and i don't think there is a keyboard template that matches mine :cry: you would need to take the layout of something like a full size and then move, delete and adjust the keys to fit what you want. click the key you want to change and there box below allows ...

you will generate the .hex file from the kbfirmware.com website but you need info on what controller you will use as well as what pin on the controller corresponds woith what row/column.

you just need the controller. i mean you can make the .hex file without as long as you solder the controller the same pins as in the hex file

The problem limiting you is going to be the pins available to use. The sorers converter that you speak of basically just converted the protocol xt to usb rather then directly hooking into the matrix. you will need one pin per row and 1 pin per column if the pro micro supports enough pins then you ca...

i always use QMK have never used TMK

looks fine, anything goes as long as you are happy with it

Yes that looks very good. Last thing you would need to do is to make a kle of the layout that you want and also if you want any layers.

A drawing of the matrix will indeed help as you can then use it to refer to when you create the matrix in the website. Thank you for your insight Muirium, the reason why i suggest the website kbfirmware.com as it makes it easier ,at least for me, especially when the matrices are different from each ...

The easy part is indeed soldering the rows and columns to the Teensy pins yes, but in order to create the .hex file needed to flash the teensy you will need to construct both a physical matrix (physical layout of the switches on the board) and the electrical matrix (layout of connected switches). Th...

No charge for the Teensy, though you can help me in other ways. I am going to be making a presentation on converting vintage boards for the meetup happening in Leeds next month. I would appreciate using some of the photos and also asking if I have explained things correctly so that my presentation w...

Well done, it would be easier to now arrange the table by the order of the keys on the board and also convert the pin numbers to correspond to the physical row/column numbers starting from 0 e.g. Columns 0, 1, 2 etc so that Esc = Column 0, Row 0, F1 = Row 0, Column 1 etc. Before getting the conversi...

ok sorry if you know how a diode works but i am going to repeat it anyway. The diode is like a one way system, it allows current to flow in one direction only from + to -ve. Assuming you placed the probes of the multimeter in the correct polarity e.g. the -ve probe was soldered to position 2 and you...

if you have established that the far right is for the rows, then the other 2 with traces going down will be for the columns so it is those pins that you would need to probe with the other end on side 1 of the diode

I tried getting the other half of the matrix but found that the other pins just connected to the diode pin below the image below shows what I mean. Sorry if my description is bad I am new to this sort of thing please let me know what I am doing wrong. Thanks.15692695081141968231378354124626.jpg If ...

measure with multimeter on continuity between the diode and the switch pin above it. Once you establish the side that is connected to the switch measure the other end of the diode to the shift register the same way as you did the switch pins.

the diodes are designed to prevent ghosting see here wiki/Rollover,_blocking_and_ghosting so the matrix can only be scanned in the direction of the diode as its basically a one way system.

maybe photos of the board itself to judge condition along with a timestamp to prove ownership of the board?

There may be traces like that because the pcb is not isolated to just the keyboard matrix. it may need the unnecessary traces to be cut for it to work correctly. You only need to wire upp the pins that correspond to the matrix itself

if that controller has enough pins to cover both of the ribbon cables then you are ok. the reason to go with a Teensy++ is just the amount of pins that you have access to. if you are wireing a full sized board then often the matrix would have a greater number of pins that the smaller controller boar...