Author Topic: [TMK] HHKB Alt Controller with Mini-B/Type-C connector (Read 586070 times)

jgaddi · « **Reply #100 on:** Wed, 21 October 2015, 12:33:18 »

Quote

To initialize BT module you should press LShift+RShift+ScrollLock, not Delete. LShift+RShift+Delete enters module into command mode.

Thanks for the quick reply. Is LShift+RShift+ScrollLock supposed to output anything to hid_listen? The console becomes unresponsive after that key combo.

hasu · « **Reply #101 on:** Wed, 21 October 2015, 13:03:42 »

You will see this output when BT initialize comand runs.
Note that if this command fails BT module will be configured incompletely or wrongly, you should take special care, do not touch keyboard while this until initilize command is finished. This command takes 5-10 seconds.

Code: [Select]

Entering config mode ...
CMD
Ver 6.15 04/26/2013
(c) Roving Networks
ECHO ON
SF,1
AOK
S-,TmkBT
AOK
SS,Keyboard/Mouse
AOK
SM,4
AOK
SW,8000
AOK
S~,6
AOK
SH,003C
AOK
SY,FFF4
AOK
R,1
Reboot!
Exiting config mode ...

jgaddi · « **Reply #102 on:** Wed, 21 October 2015, 13:28:19 »

Quote from: hasu on Wed, 21 October 2015, 13:03:42

You will see this output when BT initialize comand runs.
Note that if this command fails BT module will be configured incompletely or wrongly, you should take special care, do not touch keyboard while this until initilize command is finished. This command takes 5-10 seconds.
Code: [Select]
Entering config mode ... CMD Ver 6.15 04/26/2013 (c) Roving Networks ECHO ON SF,1 AOK S-,TmkBT AOK SS,Keyboard/Mouse AOK SM,4 AOK SW,8000 AOK S~,6 AOK SH,003C AOK SY,FFF4 AOK R,1 Reboot! Exiting config mode ...

It seems like something's wrong.. I don't get any output from the initialization. Any other ideas to reinitialize the bluetooth module?

hasu · « **Reply #103 on:** Wed, 21 October 2015, 13:49:49 »

You can initialize module when you are in trouble. But you should tarke care to prevent module from being cofigured incompletely or wrongly. Take the following steps.

0. Turn BT swich off and unplug USB cable.
1. open hid_listen. You can do without it but I recommend.
2. Plug USB cable and wait for keyboard to startup.
3. Press key combo LShift+RShift+ScrollLock(Fn+O).
4. Turn BT switch on. You will see output below on hid_listen.
5. Do not touch keyobard until the command completes or for twenty seconds.

Now module is configured with default setting and in pairing mode. You may need extra power cycle for pairing, try BT switch off and on.

jgaddi · « **Reply #104 on:** Wed, 21 October 2015, 14:20:39 »

Hmm, I'm still getting no output from hid_listen here. Would rebuilding from source and reflashing help here?

hasu · « **Reply #105 on:** Wed, 21 October 2015, 14:39:44 »

OK. I'd like to know your current situation exactly.

You flashed with firmware with your custom keymap, right?
Did you check the controller when it is delivered and Bluetooth worked before the reflash?
Do you think this is hardware problem or firmwre?

Assuming hardware is fine reflashing default firmware will be helpful. You should not change keymap, use default keymap until confirm your controller is fine.
You can build default firmware with "make -f Makefile.rn42" or just download it without keymap change from this page.
http://www.tmk-kbd.com/tmk_keyboard/editor/hhkb_bt/

jgaddi · « **Reply #106 on:** Wed, 21 October 2015, 16:13:27 »

Unfortunately I flashed before testing the bluetooth functionality, and I still run into the same issues with the unmodified firmware. I'm beginning to think this is a hardware issue.

hasu · « **Reply #107 on:** Wed, 21 October 2015, 16:31:42 »

OK.
I'll send another one, but it will take a week to ship, currently out of stock.
Please send your controller back with cheap carrier(maybe USPS) with tracking(insurance is not needed). I'll pay for the postage when I receive it and confirm it doesn't work.

BTW, Bluetooth LED is blinking when turn on module?

jgaddi · « **Reply #108 on:** Wed, 21 October 2015, 17:01:25 »

Great, I'll do that.

The bluetooth LED has never come on. Turning on the module only causes the battery LED (right LED) to blink red twice.

IonutZ · « **Reply #109 on:** Tue, 03 November 2015, 06:19:35 »

HASU! When's the next version coming out

Still having trouble with Fn + Shift combo when Fn = Layer 2 and on Layer 2, Shift = Layer 3

hasu · « **Reply #110 on:** Tue, 03 November 2015, 21:17:22 »

next version? no plan for Alt controller board currently and Soon(TM~~TMK~~) for TMK firmware

what's your problem exactly? we discussed it somewhere before?

Quote from: IonutZ on Tue, 03 November 2015, 06:19:35

HASU! When's the next version coming out

Still having trouble with Fn + Shift combo when Fn = Layer 2 and on Layer 2, Shift = Layer 3

IonutZ · « **Reply #111 on:** Wed, 04 November 2015, 06:59:50 »

Quote from: hasu on Tue, 03 November 2015, 21:17:22

next version? no plan for Alt controller board currently and Soon(TMK) for TMK firmware

what's your problem exactly? we discussed it somewhere before?

Quote from: IonutZ on Tue, 03 November 2015, 06:19:35
HASU! When's the next version coming out

Still having trouble with Fn + Shift combo when Fn = Layer 2 and on Layer 2, Shift = Layer 3

Here are the 2 bugs that I'm having, without which the TMK firmware would be the ultimate best:

1. My layout is the following
on Layer 0: Fn key = Momentary to Layer 1,
on Layer 1: RShift key = Momentary to Layer 2,
on Layer 2: > key = a function key.

If I hold down Fn + RShift + >, the function key is activated as expected. When I release however, if I don't release the > before release RShift and Fn, the keyboard gets stuck on Layer 2, and then I have to press Fn + RShift + > again and release them in the right order, so that the keyboard comes back to Layer 0.

2. The Next and Previous media buttons aren't the same buttons as the next and previous on the Macbook Pro's keyboard. Those keys allow me to move between songs on all the media software. The Previous and Next media buttons that I have on the HHKB, KC_MNXT, KC_MPRV, (171 and 172) only work with specific software.

Any ideas? At the same time, they might not be bugs, they might be features haha

hasu · « **Reply #112 on:** Wed, 04 November 2015, 17:10:38 »

OK.
1. Yeah, this is the biggest limitation of current TMK keymap implementation. I hope this will be fixed in next version(tm)

It will need more memory and code, this makes me hesitated.
https://github.com/tmk/tmk_keyboard/wiki/FAQ-Keymap#modifierlayer-stuck

2. See this.
https://github.com/tmk/tmk_keyboard/wiki/FAQ-Keymap#media-control-keys-in-mac-osx

hasu · « **Reply #113 on:** Sun, 08 November 2015, 21:14:41 »

Updated firmwre of keymap editor for both USB and BT. You can download the latest firmware from keymap editor now.
http://www.tmk-kbd.com/tmk_keyboard/editor/

This will fix some problems including "unneeded delay in momentary layer switch".
https://github.com/tmk/tmk_keyboard/issues/201

kaesve · « **Reply #114 on:** Sun, 22 November 2015, 00:09:36 »

Hey Hasu,

I have one of your boards, and the USB socket just broke off. My HHKB is my daily driver so I really want to fix or replace it as fast as possible. I don't have much experience with soldering or fixing PCB's, so I hope you could help me with some questions; Will every mini-USB socket fit, or do I need a specific one? Would this be doable for someone new to soldering?

I am also considering buying a bluetooth controller, especially because you have the one I need in stock. Do you have any estimation of shipping time to the US?

hasu · « **Reply #115 on:** Sun, 22 November 2015, 01:31:50 »

Hi,
Sorry to hearing that.

Could you post pic of PCB and the socket? I'm very interested in seeing how that broke.

The socket is Hirose UX60SC-MB-5ST and I can send it immediately(Tuesday) for nothing(via normal mail, probably will take a week or so to US). It is not extremely difficult but may be PITA to solder it at correct place. You can re-solder it using decent iron and flux if PCB pads are safe.

Registered mail usually take 7-10 days to US. EMS is another shipping method and 3-4 days(in their estimate but I'm not sure in real), costs around extra $6. (I cannot use DHL and Fedex practically due to their ridiculous price and poor service in Japan.)

I have bluetooth controller in stock currently and it can be shipped on Tuesday. Unfortunately this Monday(tomorrow) is holiday and Post office is closed here.

kaesve · « **Reply #116 on:** Sun, 22 November 2015, 03:13:28 »

Thanks for the quick response Hasu. I moved into a new apartment, so right now I don't even have screwdrivers to check the damage. I'll borrow tools and post a picture next week. I think I'll get the bluetooth controller -- I'll PM you with the details

Latin00032 · « **Reply #117 on:** Sun, 22 November 2015, 09:06:07 »

Any possibility of making a version of this for the fc660c?

hasu · « **Reply #118 on:** Tue, 24 November 2015, 03:52:31 »

I believe it is possible but I myself won't be deep into FC660C reverse-eng.
We are already very close to finish it, I think someone will complete this job eventually in the future. I'm happy to help and sitll keep subscribing the thread in fact.
https://geekhack.org/index.php?topic=54222.0

Vimto · « **Reply #119 on:** Thu, 26 November 2015, 01:03:17 »

Just received my board, and it's fantastic, works in Bluetooth and USB modes.
I can confirm that the adafruit 2500 mAh battery doesn't fit, as it's just a touch too large and the support post can't slot down. I may try shortening / filing the the small plastic support post by 10 mm just to try the battery, but not sure how this would impact the stability of the keyboard so am reluctant

The adafruit 2000 mAh battery fits perfectly.

I will try reprogramming it when I get home from work tonight (want to flip the windows and alt keys around).

I had one question.
If the keyboard is in USB mode, will it still charge the battery?

Vimto · « **Reply #120 on:** Thu, 26 November 2015, 08:42:45 »

I'm trying to pair the keyboard on my Alienware PC with Windows 10, and it doesn't seem to show up as a detected device.
It works fine on my iPhone, LG G3 phone and my Macbook Pro.

Has anyone else had this issue?

Vimto · « **Reply #121 on:** Thu, 26 November 2015, 13:36:17 »

Having issues trying to program my controller using dfu programmer on a Macbook Pro,

I got the following error:

Code: [Select]

make -f Makefile.rn42 KEYMAP=hhkb dfu
dfu-programmer atmega32u4 erase --force
Erasing flash...  Success
Checking memory from 0x0 to 0x6FFF...  Empty.
dfu-programmer atmega32u4 erase
Checking memory from 0x0 to 0x6FFF...  Empty.
Chip already blank, to force erase use --force.
dfu-programmer atmega32u4 flash hhkb_rn42.hex
make: *** [dfu] Error 1

This made my keyboard completely unresponsive

I then tried:

Code: [Select]

dfu-programmer atmega32u4 flash hhkb_bt_firmware.hex
with a hex file i downloaded from the keyboard editor website, but this just returned nothing

Can anyone help?

hasu · « **Reply #122 on:** Thu, 26 November 2015, 16:30:02 »

Quote from: Vimto on Thu, 26 November 2015, 13:36:17

Having issues trying to program my controller using dfu programmer on a Macbook Pro,

I got the following error:

Code: [Select]
make -f Makefile.rn42 KEYMAP=hhkb dfu dfu-programmer atmega32u4 erase --force Erasing flash... Success Checking memory from 0x0 to 0x6FFF... Empty. dfu-programmer atmega32u4 erase Checking memory from 0x0 to 0x6FFF... Empty. Chip already blank, to force erase use --force. dfu-programmer atmega32u4 flash hhkb_rn42.hex make: *** [dfu] Error 1
This made my keyboard completely unresponsive

hmm, I haven't found that erase command was executed twice in dfu target so far. On Ubuntu make doesn't stop here for some reason. Fixed it and updated the repository, use the latest source and try it again.
https://github.com/tmk/tmk_keyboard/commit/d0f174911e84be47d0f3b3d98b7d1adeb38b5411

Quote

I then tried:
Code: [Select]
dfu-programmer atmega32u4 flash hhkb_bt_firmware.hex
with a hex file i downloaded from the keyboard editor website, but this just returned nothing

Can anyone help?

I think this should work.

Code: [Select]

dfu-programmer atmega32u4 erase --force
dfu-programmer atmega32u4 flash hhkb_bt_firmware.hex
dfu-programmer atmega32u4 reset

hasu · « **Reply #123 on:** Thu, 26 November 2015, 17:12:25 »

Quote from: Vimto on Thu, 26 November 2015, 08:42:45

I'm trying to pair the keyboard on my Alienware PC with Windows 10, and it doesn't seem to show up as a detected device.
It works fine on my iPhone, LG G3 phone and my Macbook Pro.

Has anyone else had this issue?

That Alienware PC supports classic bluetooth(BT3.0 or 2.1)? HHKB Alt controller uses Bluetooth 2.1, so host has to support classic Bluetooth. These days many PC/Mac/Phones have support for both BLE(4.1/4.0) and classic but some may have only BLE. With quick browsing on dell.com it says only about BT4.1 support on the latest Alienware product but does not refer to classic BT.

And when Alt controller is connected to a host, other hosts cannot find it. You have to disconnect from the host before trying new host. Easy way to disconnect is pressing LShift+RShift+p to enter pairing mode.

hasu · « **Reply #124 on:** Thu, 26 November 2015, 17:23:36 »

Quote from: Vimto on Thu, 26 November 2015, 01:03:17

Just received my board, and it's fantastic, works in Bluetooth and USB modes.
I can confirm that the adafruit 2500 mAh battery doesn't fit, as it's just a touch too large and the support post can't slot down. I may try shortening / filing the the small plastic support post by 10 mm just to try the battery, but not sure how this would impact the stability of the keyboard so am reluctant

The adafruit 2000 mAh battery fits perfectly.

I will try reprogramming it when I get home from work tonight (want to flip the windows and alt keys around).

I had one question.
If the keyboard is in USB mode, will it still charge the battery?

Thanks for the report on batteries.

Yes, controller charges battery regardless of its mode while it is hooked up to USB port or power adapter.

Vimto · « **Reply #125 on:** Thu, 26 November 2015, 19:17:57 »

Quote from: hasu on Thu, 26 November 2015, 16:30:02

hmm, I haven't found that erase command was executed twice in dfu target so far. On Ubuntu make doesn't stop here for some reason. Fixed it and updated the repository, use the latest source and try it again.
https://github.com/tmk/tmk_keyboard/commit/d0f174911e84be47d0f3b3d98b7d1adeb38b5411

I tried this and now the erase only happens once, but I still get the same error:

Code: [Select]

Creating load file for Flash: hhkb_rn42.hex
avr-objcopy -O ihex -R .eeprom -R .fuse -R .lock -R .signature hhkb_rn42.elf hhkb_rn42.hex
dfu-programmer atmega32u4 erase --force
Erasing flash...  Success
Checking memory from 0x0 to 0x6FFF...  Empty.
dfu-programmer atmega32u4 flash hhkb_rn42.hex
make: *** [dfu] Error 1

Quote from: hasu on Thu, 26 November 2015, 16:30:02

I think this should work.
Code: [Select]
dfu-programmer atmega32u4 erase --force dfu-programmer atmega32u4 flash hhkb_bt_firmware.hex dfu-programmer atmega32u4 reset

I tried this with the .hex i downloaded and with the hex built from the command above. Got the following output both times (erase works, but flash and reset don't give any output)

Code: [Select]

dfu-programmer atmega32u4 erase --force
Erasing flash...  Success
Checking memory from 0x0 to 0x6FFF...  Empty.
dfu-programmer atmega32u4 flash hhkb_rn42.hex
dfu-programmer atmega32u4 reset

No output during the flash or the reset commands.

Is there any way to know the keyboard is in program mode or not?
What should I do once the reset command is done, i unplugged / replugged the keyboard but still no response from it on my mac

hasu · « **Reply #126 on:** Thu, 26 November 2015, 19:31:30 »

In program(bootloader) mode controller should appear as USB device with VID=03eb(Atmel) and PID=2ff4, you will find this on Mac equivalent of 'device manager'.

Probably, you don't have permission to the device enough? Try sudo.

Quote

$ sudo dfu-programmer atmega32u4 erase --force
$ sudo dfu-programmer atmega32u4 flash hhkb_rn42.hex
$ sudo dfu-programmer atmega32u4 reset

EDIT:
or

Quote

$ sudo make dfu

but I don't recommend it. To run compilation by root(admin?) is not good idea.

Vimto · « **Reply #127 on:** Thu, 26 November 2015, 20:08:36 »

Quote from: hasu on Thu, 26 November 2015, 19:31:30

In program(bootloader) mode controller should appear as USB device with VID=03eb(Atmel) and PID=2ff4, you will find this on Mac equivalent of 'device manager'.

Probably, you don't have permission to the device enough? Try sudo.

Quote
$ sudo dfu-programmer atmega32u4 erase --force
$ sudo dfu-programmer atmega32u4 flash hhkb_rn42.hex
$ sudo dfu-programmer atmega32u4 reset

EDIT:
or
Quote
$ sudo make dfu
but I don't recommend it. To run compilation by root(admin?) is not good idea.

I tried running it as sudo like you recommended and still no luck, so i increased the debug output for dfu programmer and got the following:

Code: [Select]

sudo dfu-programmer atmega32u4 flash hhkb_rn42.hex --debug 1000
     target: atmega32u4
    chip_id: 0x2ff4
  vendor_id: 0x03eb
    command: flash
      quiet: false
      debug: 1000
device_type: AVR
------ command specific below ------
   validate: true
   hex file: hhkb_rn42.hex

dfu.c:330: dfu_device_init( 1003, 12276, 0x7fff54010bd0, true, false )
dfu.c:332: dfu_device_init(000003eb, 00002ff4)
libusb: debug [libusb_get_device_list] 
libusb: debug [discovered_devs_append] need to increase capacity
libusb: debug [libusb_get_device_descriptor] 
dfu.c:347:  0: 0x03eb, 0x2ff4
dfu.c:356: found device at USB:20,10
dfu.c:595: dfu_find_interface()
libusb: debug [libusb_get_config_descriptor] index 0
dfu.c:605: config 0: maxpower=50*2 mA
dfu.c:612: interface 0
dfu.c:621: setting 0: class:0, subclass 0, protocol:0
dfu.c:634: Found DFU Interface: 0
libusb: debug [libusb_open] open 20.10
libusb: debug [darwin_open] device open for access
dfu.c:367: opened interface 0...
libusb: debug [libusb_set_configuration] configuration 1
dfu.c:369: set configuration 1...
libusb: debug [libusb_claim_interface] interface 0
libusb: debug [get_endpoints] building table of endpoints.
libusb: debug [darwin_claim_interface] interface opened
dfu.c:372: claimed interface 0...
dfu.c:301: dfu_abort( 0x7fff54010bd0 )
libusb: debug [libusb_alloc_transfer] transfer 0x7f9659c03e58
libusb: debug [libusb_submit_transfer] transfer 0x7f9659c03e58
libusb: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
libusb: debug [handle_events] poll fds modified, reallocating
libusb: debug [handle_events] poll() 1 fds with timeout in 60000ms
libusb: debug [darwin_async_io_callback] an async io operation has completed
libusb: debug [handle_events] poll() returned 1
libusb: debug [handle_events] caught a fish on the event pipe
libusb: debug [darwin_handle_transfer_completion] handling control completion with kernel status 0
libusb: debug [usbi_handle_transfer_completion] transfer 0x7f9659c03e58 has callback 0x10bc0c060
libusb: debug [sync_transfer_cb] actual_length=0
libusb: debug [libusb_free_transfer] transfer 0x7f9659c03e58
dfu.c:212: dfu_get_status( 0x7fff54010bd0, 0x7fff54010ae8 )
libusb: debug [libusb_alloc_transfer] transfer 0x7f9659f01198
libusb: debug [libusb_submit_transfer] transfer 0x7f9659f01198
libusb: debug [libusb_get_next_timeout] no URB with timeout or all handled by OS; no timeout!
libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
libusb: debug [handle_events] poll() 1 fds with timeout in 60000ms
libusb: debug [darwin_async_io_callback] an async io operation has completed
libusb: debug [handle_events] poll() returned 1
libusb: debug [handle_events] caught a fish on the event pipe
libusb: debug [darwin_handle_transfer_completion] handling control completion with kernel status 0
libusb: debug [usbi_handle_transfer_completion] transfer 0x7f9659f01198 has callback 0x10bc0c060
libusb: debug [sync_transfer_cb] actual_length=6
libusb: debug [libusb_free_transfer] transfer 0x7f9659f01198
dfu.c:238: ==============================
dfu.c:240: status->bStatus: OK (0x00)
dfu.c:241: status->bwPollTimeout: 0x0001 ms
dfu.c:243: status->bState: dfuIDLE (0x02)
dfu.c:244: status->iString: 0x00
dfu.c:245: ------------------------------
dfu.c:696: State: dfuIDLE (2)
atmel.c:287: ERROR allocating 0x10000 bytes of memory.
commands.c:238: ERROR initializing a buffer.
libusb: debug [libusb_release_interface] interface 0
libusb: debug [libusb_close] 
libusb: debug [libusb_exit] 
libusb: debug [libusb_exit] destroying default context

do you think my version of libusb or the atmel libraries is bad?

hasu · « **Reply #128 on:** Thu, 26 November 2015, 20:39:50 »

You can erase it but cannot flash?
hmm, I'm not sure what's wrong there

maybe version of tool or library?
Are you using the latest version of dfu-programmer? If not try 0.7.2. I'm using 0.7.1 on Ubuntu and it works well for me.

Quote

atmel.c:287: ERROR allocating 0x10000 bytes of memory.
commands.c:238: ERROR initializing a buffer.

Looks like it fails at malloc()? 0x10000 is just 64KB, wierd.
https://github.com/dfu-programmer/dfu-programmer/blob/v0.7.0/src/atmel.c#L287

Vimto · « **Reply #129 on:** Thu, 26 November 2015, 20:58:10 »

Thank you so much for that, i thought i was using the latest version of dfu-programmer because i clicked on the link from the dfu programmer page, but it was actually pointing to 0.7.0.
Just changed to 0.7.2 and it works (at least my keyboard is working again), thank you so much for your help.
Now to play with programming the board.

Vimto · « **Reply #130 on:** Thu, 26 November 2015, 21:49:51 »

Quote from: hasu on Thu, 26 November 2015, 17:12:25

Quote from: Vimto on Thu, 26 November 2015, 08:42:45
I'm trying to pair the keyboard on my Alienware PC with Windows 10, and it doesn't seem to show up as a detected device.
It works fine on my iPhone, LG G3 phone and my Macbook Pro.

Has anyone else had this issue?

That Alienware PC supports classic bluetooth(BT3.0 or 2.1)? HHKB Alt controller uses Bluetooth 2.1, so host has to support classic Bluetooth. These days many PC/Mac/Phones have support for both BLE(4.1/4.0) and classic but some may have only BLE. With quick browsing on dell.com it says only about BT4.1 support on the latest Alienware product but does not refer to classic BT.

And when Alt controller is connected to a host, other hosts cannot find it. You have to disconnect from the host before trying new host. Easy way to disconnect is pressing LShift+RShift+p to enter pairing mode.

My alienware is 4 years old and supports classic bluetooth as BLE was very new back then
I've seen this other post on another forum, about a similar issue someone had with the rn42 chipset and windows 10
http://www.microchip.com/forums/m892862.aspx

ccarlitos2 · « **Reply #131 on:** Fri, 27 November 2015, 08:43:24 »

Is it possible to buy a HHKB Pro 2 with the BT controller straight from you? If so how much?

hasu · « **Reply #132 on:** Fri, 27 November 2015, 09:45:57 »

Yes. See the first post of this thread.

Wait... you mean you want me to proxy HHKB? No, I can't. Use tenso.com.

kaesve · « **Reply #133 on:** Fri, 27 November 2015, 17:49:28 »

Hey Hasu,

My board arrived today and it is working perfectly. Typing this message on it right now -- I'm so happy to not have to use my laptop keyboard anymore

By the way, here's a picture of the broken board. Do you think it is still repairable? I might give it a go so I have a back-up board.

hasu · « **Reply #134 on:** Fri, 27 November 2015, 19:07:30 »

Hmmm, two big pads completely came off while five small pads seem to be safe.
If small pads are sitll there electrical connection will be ok with just resoldering. But It may be difficult to make connector stay in place firmly, you have to use glue, kind of epoxy to stick it on PCB, instead of soldering. Not sure glue is strong enough for daily usage.

EDIT:
I will think about what I can do for this. I'll PM later.

hasu · « **Reply #135 on:** Wed, 09 December 2015, 15:29:57 »

Recent buyers,
Japan Post email service is a bit iffy as of now.
Let me know if you don't get tracking number from them in three days after payment.

Thanks

bocahgundul · « **Reply #136 on:** Tue, 15 December 2015, 02:11:54 »

Bro i receive the BT controller today and when i try to test the NKRO it just dont work and just 6KRO. My Board is the BT one and i try it in USB mode

bocahgundul · « **Reply #137 on:** Wed, 16 December 2015, 02:30:32 »

And i cannot use the magic commands pls help

hasu · « **Reply #138 on:** Wed, 16 December 2015, 23:30:19 »

Ah, I missed notification mail.

Sorry, with factory default BT firmware NKRO is disabled, as it is a bit old. (I'll update it from next shippment.)
You will be able to use NKRO after program with firmware from keymap editor. And keyboard still works with 6KRO by default, to use NKRO press LShift+RShift+n.

Which magic comand did you use?
did you find you need hid_listen tool to see output from keyboard yet?
https://github.com/tmk/tmk_keyboard#debugging

bocahgundul · « **Reply #139 on:** Thu, 17 December 2015, 07:36:58 »

All fixed thank you hasu

witty · « **Reply #140 on:** Thu, 07 January 2016, 09:49:35 »

Wo! Cool!

hasu · « **Reply #141 on:** Mon, 11 January 2016, 10:58:18 »

Updated keymap editor, it supports media keys for Mac now.

http://www.tmk-kbd.com/tmk_keyboard/editor/hhkb/
https://github.com/tmk/tmk_keyboard/wiki/FAQ-Keymap#media-control-keys-in-mac-osx

hasu · « **Reply #142 on:** Mon, 11 January 2016, 17:45:46 »

Hi all,
Japan Post email service is still doubtful as of now. Let me know if you don't get tracking number in three days after payment. Sorry for this inconvenience.

ajx · « **Reply #143 on:** Tue, 12 January 2016, 13:02:22 »

Hey Hasu, i may have an issue, its pretty rare, when i barely brush the key, the key repeats several times
e.g aaaaa or wwww
Dunno if it comes from the controller

Did you meet such issue?

I have pretty standard layout (only few things have been modified, i put arrows clusters on WASD, fn is toggled)

hasu · « **Reply #144 on:** Tue, 12 January 2016, 13:27:57 »

Hi,
what do you mean with "barely brush"? you don't type the key but finger rests on the key?

capacitive sensing may be corrupted temporarily with half pressing for some period or low voltage of power.

and if you installed battery make sure it doesn't move inside case, it can prevent from sensing correctly.

ajx · « **Reply #145 on:** Tue, 12 January 2016, 14:21:34 »

Yes my fingers flying over keys or resting on the key
I use your controller without battery
I thought it was an hardware issue, potentially with the pcb or the slider itself due to my silenced mod

ajx · « **Reply #146 on:** Tue, 12 January 2016, 14:50:24 »

By the way your re right, it happens only when fingers rest on the key with half pressing after some period

Laser · « **Reply #147 on:** Fri, 15 January 2016, 11:58:01 »

I have a HHKB Pro2 and your (awesome BTW) USB controller (without BT). Question: would it be possible to attach a LED to the board, and control it through the firmware?

Reason: I would like to use permanent extra layers (toggled, not momentary), but I don't like to have these permanent layers without any form of feedback/info about which is the current layer (e.g. a bright LED, 2 bright LEDs ...).
Or, if you have another solution? How can a keyboard report visually the active layer? I think the shortcoming of having permanent layers is that the user can forget in what layer (s)he is, without any type of information offered by the keyboard (- this is the problem).

Something like a generalization of CAPS LOCK Led showing activated CAPS LOCK state, but for custom permanent FN layers.

hasu · « **Reply #148 on:** Fri, 15 January 2016, 20:55:47 »

ajx, even with TMK controller Topre chip still plays all of role in sensing capacitive switches, I think the chip has calibration process for gradual change of capacitance caused by temprature, moisture or etc. and I guess the half pressing can interfere the calibration under some conditions. Though I couldn't reproduce this problem by half pressing on my keyboard.

Laser, unfotunately TMK doesn't support any indication for layer switch at this time. But some people have added such function in some ways.
see this for example. https://github.com/tmk/tmk_keyboard/pull/198

Laser · « **Reply #149 on:** Sat, 16 January 2016, 04:30:21 »

Quote from: hasu on Fri, 15 January 2016, 20:55:47

Laser, unfotunately TMK doesn't support any indication for layer switch at this time. But some people have added such function in some ways.
see this for example. https://github.com/tmk/tmk_keyboard/pull/198

Hasu, thanks! The link seems very useful. My other half of the question was this (because I'm not an expert with this stuff):

Is it physically possible, with your "Alt Controller Board for HHKB" (USB version), to solder 2 LEDs directly where the 2 USB hub ports were (where the Bluetooth version of the controller actually has and uses 2 LEDs)?

If it is possible, what are the corresponding ports to be used in firmware?

I ask because, since the right side of the USB controller PCB has missing components (for Bluetooth), I don't know if soldering the LEDs is enough, or other resistors etc. must also be soldered in.

News:

Author Topic: [TMK] HHKB Alt Controller with Mini-B/Type-C connector (Read 586070 times)