deskthority

• ] (above right shift, next to return)
• Send Line (above numpad 8)
• Unmarked / SetUp (front printed, top right key in numblock)

• Print
• Print Line
• Hold

r53 +32 d32 
rF0 r53 -32 u32 
r7E +47 d47 
rF0 r7E -47 u47 
r84 +C2 dC2 
rF0 r84 -C2 uC2 
r57 +72 d72 a
rF0 r57 -72 u72 
r5F +73 d73 a
rF0 r5F -73 u73 
r62 +93 d93 a
rF0 r62 -93 u93

layerblock
	FN1 		1
	FN2 		1
	FN1 FN2		1
endblock

ifset set3
# My config for RJ45 cabled AT layout Model M
remapblock
layer 0
	caps_lock	fn1
	lalt		lgui
	# lctrl		lalt			# Since only the left Control is labelled as such
	# ralt		rgui			# And Alt Gr is the only "Alt" / Option
	rctrl		rgui			# "Send" can be the other Command
	f13			esc
	europe_2	back_quote
	back_quote	europe_2
	pad_plus	pad_enter
endblock

ifset set3
remapblock
layer 1
# 	HHKB Arrows
	LEFT_BRACE 	UP
	SEMICOLON 	LEFT
	SLASH 		DOWN
	QUOTE 		RIGHT
	L 			PAGE_UP
	PERIOD 		PAGE_DOWN
	K 			HOME
	COMMA 		END
	H 			PAD_ASTERIX
	J 			PAD_SLASH
	N			PAD_PLUS
	M			PAD_MINUS
	
# 	ESDF Arrows	
	E			UP
	S			LEFT
	D			DOWN
	F			RIGHT
	R			PAGE_UP
	V			PAGE_DOWN
	A			HOME
	G			END
	
# 	Media keys across the number row	
	1			F14					# Decrease Display Brightness 
	2			F15					# Increase Display Brightness
	3			F10					# Exposé: All App Windows
	4			F12					# Dashboard
	5			F11					# Exposé: Show Desktop
	6			F9					# Exposé: All Windows in All Apps
	7			MEDIA_PREV_TRACK	# iTunes / media playback controls
	8			MEDIA_PLAY_PAUSE
	9			MEDIA_NEXT_TRACK
	0			MEDIA_MUTE			# Volume controls
	MINUS		MEDIA_VOLUME_DOWN
	EQUAL		MEDIA_VOLUME_UP
endblock

ifset set3
macroblock 
	# Soarer's Double Shift Caps Lock
	macro lshift rshift
	press caps_lock
	endmacro
	
	macro rshift lshift
	press caps_lock
	endmacro
endblock

Muirium wrote:The diagram may be the mirror image of what you're expecting. All five wires in my RJ45 solder to something. Shield I just connected to my external converter's metal case. I remember it was indeed the bare looking wire.

• Vcc = Black
• Data = Red
• Clock = Yellow
• Ground = White

Muirium wrote:Odd. Both of my RJ45 connected terminal Model Ms detect as code set 3 automatically. They can be a bit strange though, these old terminal boards. You've probably got the connections you need. I doubt the keyboard could type at all without all four.

My notes from the soldering job say:

• Vcc = Black
• Data = Red
• Clock = Yellow
• Ground = White

Although I checked everything first with a continuity tester, I still made a mistake when soldering. I put data on another pin on the RJ45 socket. Fortunately it was just unused and didn't do any harm. But interestingly, the keyboard did send events via the converter which I could read with hid_listen. No actual useable keystrokes (all signals were the same) but the converter could see something was there at least, while flashing the Teensy's light on every key press! That's what a missed connection looks like.

Soldering up sockets is the hardest part of making an external version of the converter. Mini Din especially (aka PS/2) is a little horror! I found my way around the first RJ45 socket I did just fine, but the second one I took two takes to get right. Those staggered pins are made to confuse.

Muirium wrote:I just bought a bare Mini Din socket, clipped wires and soldered those minuscule buggers on while cursing and melting plastic! There's an easier way? I should learn to solder sometime. It's always so dramatic!

Muirium wrote:True story: I also bought a Mini USB jack and a USB B socket, soldered some very small, insanely fiddly wires between them, with a great deal of cursing the like no one beyond these shores would even understand. Continuity tester says my homemade lead is fine. And my brief test with a memory card reader says it works on the computer too. (I didn't dare to blow my one and only Teensy…) But whenever I plug it into a USB port, every Bluetooth device in the house drops its connection and even the Wi-Fi gets mighty choppy.

Apparently I've built a USB powered 2.4 GHz jammer. Hmm. Well, it didn't cost much, and is pretty small at least. Maybe it'll come in useful someday!

beltet wrote:

Muirium wrote:I just bought a bare Mini Din socket, clipped wires and soldered those minuscule buggers on while cursing and melting plastic! There's an easier way? I should learn to solder sometime. It's always so dramatic!

I feel the same, much cursing...
You can use a old cable, strip the wires and solder them on other wires and the put shrinking tube on them, little easier in my opinion.

EDIT: Yeah I would like one of these aswell to put inside the keyboard.

Here´s a pick of the inside:


I bought a network outlet and took away the pins for the network cable. and soldered on cables between teensy and rj45 jack, modded the case and hotglued the teensy on the other board. Isolated the soldering with hot glue aswell.

fruktstund wrote:

beltet wrote:

Muirium wrote:I just bought a bare Mini Din socket, clipped wires and soldered those minuscule buggers on while cursing and melting plastic! There's an easier way? I should learn to solder sometime. It's always so dramatic!

I feel the same, much cursing...
You can use a old cable, strip the wires and solder them on other wires and the put shrinking tube on them, little easier in my opinion.

EDIT: Yeah I would like one of these aswell to put inside the keyboard.

Here´s a pick of the inside:


I bought a network outlet and took away the pins for the network cable. and soldered on cables between teensy and rj45 jack, modded the case and hotglued the teensy on the other board. Isolated the soldering with hot glue aswell.

I find the most interesting part of this picture being the "i avföring" written on the Post-it.

Muirium wrote:Layers are sneaky. The way I'd do it is to remap Extra_F2 to some nonexistent key in layer 1. There's a bunch of ones like language_1 etc. that even terminal Model Ms don't have. Then use that fake key to trigger the macro.

Right now, your code isn't using any layer (beyond the default layer 0) at all. You need to put a layer 1 instruction into the remap block. I use separate remap blocks for each layer, not sure if this is necessary but it keeps things clean in any case.

Also, both your function keys FN1 and FN2 just engage the same layer: that's what layerblock is saying. This is standard practice, but watch out if you want layers beyond 0 and 1. You'll need to modify that bit to allow them to exist.

Soarer wrote:Yeah, that - sneakiness FN keys can't be used as modifiers in macro triggers directly yet - I might put that in when get round to revamping the trigger logic - until then there's a fairly easy workaround: in the FN layer, remap the key to some HID code you don't use elsewhere, and then trigger the macro on that...