deskthority

Remember when I said that I would work on the KC_Media keys later? I keep trying to get them work but I cant figure out why they wont KC_MEDIA_PLAY_PAUSE outputs ] KC_MEDIA_PREV_TRACK outputs a space and what exactly KC_MEDIA_NEXT_TRACK outputs is beyond me but it does something...
I have EXTRAKEY ...

oh dear, I had a really good idea... phosphor glow esque lock lights for my ping master guess I know what I am working on next...

Besides, its not like I have any shortage of pins

@Hypersphere @swampangel thanks for all your help, Ive now got the keyboard 99.7% working to my preferences the only thing I cant seem to figure out is why the KC_MEDIA keys wont work but ill get to that another time

@Hypersphere I am but the files I download from there don't work, either they aren't compiled for my teensy or when I upload my own compiled converter and edit that keymap it wont use the new one

@swampangel Im going to take another crack at editing unimap_trans I think I have an idea to make it ...

I don't get how I am supposed to edit this, the unimap_plain keymap didn't match the keyboard and when I matched it and tried to compile it said: macro "UNIMAP" requires 128 arguments, but only 103 given
but doesn't the keyboard only have 102 keys?? where is the extra argument coming from?? why ...

How do I make a custom keymap? I have tried using the online editor to modify a compiled file but the file is still using the default map

pretty good, its incredibly different compared to my model M which I bolt modded and removed the mat for EXTRA TACTILITY lol :D

EDIT: I forgot to mention how immensely smooth this is, if there is anything smoother than this I would be so be shocked it would lead to my drive heads crashing with the ...

I just found the source of my problems; it was my wiring! I noticed that the keyboard would click every time I jiggled the wires so I used occam's razor and eliminated connection points until I soldered the wires directly to the PCB and now everything is working as it should

EDIT: Now I just have ...

@Hypersphere we have the same model number, 6112883

@swampangel strangely the makefile lists the bootloader size as 1024:
# Boot Section Size in *bytes*
# Teensy halfKay 512
# Teensy++ halfKay 1024
# Atmel DFU loader 4096
# LUFA bootloader 4096
# USBaspLoader 2048
BOOTLOADER_SIZE ?= 1024
OPT_DEFS ...

alright, changing that setting allowed it to compile but im getting the same thing as before when I plug the teensy in all I get from hid_listen is Enable break: S:48

I also forgot to mention that I have been getting the little click from the speaker when I plug it in

running that command gives me the error: ../../tmk_core/rules.mk:547: *** no ldscript for keymap section. Stop.
and if I run it with KEYMAP=kaboom1 I get: make: *** No rule to make target 'obj_ibm4704_usb_rev1_alps_unimap/unimap_kaboom1.o', needed by 'ibm4704_usb_rev1_alps_unimap.elf'. Stop.

well, there is a slight problem with that; apparently the makefile for the converter has the MCU set properly
I also booted into windows and it did recognize the controller as a HID device...

I don't have a bad keyboard do I?

yup, that fixed it I now get a nice stream of aaaaaaaaaaaaaaaaaaaaaa in kate

although I haven't gotten any notifications about setting up a USB device, its probably because im using kubuntu, ill try the converter in windows

yup, if I ever decide to hand wire a keyboard or use a PCB that requires one of these then ill probably get a 2.0 but for now I would like to make what I have work

oh sorry, I forgot to mention that I had another teensy that I put pins on, I originally bought these for another project

first I changed the MCU and the bootloader size as such:
MCU = at90usb1287
OPT_DEFS += -DBOOTLOADER_SIZE=1024

then I CD to ~/Desktop/tmk_keyboard-master/keyboard/onekey and ran ...

Looks like the hard part is going to take a bit longer, flashing it and shorting the pins didn't work, all I got was absolute silence

so, I guess, just let me know what you need to look at and ill upload it because I really have no idea what is going wrong

this is what I got after letting hid_listen run for about a minute, it does this regardless, keyboard plugged in or not actually, it speeds up if I start it without the keyboard and then plug it in

hid_listen
Waiting for device:...
Listening:
USB configured.
IBM 4704 converter
Keyboard ID: FF ...

well, after several hours of trying to wrap my tired brain around what im supposed to do I did something that resembles progress, I compiled the code following the parts of the guide that seemed relevant that swampangel posted and got something from hid_listen other than silence; a wall of the code ...

So after lurking around for a while I figure its about time I ask help from people who actually know what they are doing and not my dad, I am one of the people who have pulled the trigger on Mendelsons new listing of IBM pingmasters and naturally I want to use this on something other than the 4704 ...