Hi,When you get the chance can you post the mod you made to ali's case, I have that case :p
most of the testers have already received the GH60 rev. B. The faster we test everything, the earlier we'll produce the final boards.
Let's not hurry too much though, we need well-tested boards.
There are a couple of things that have to be tested: compatibility with various layouts (ISO, ANSI, HHKB, etc), compatibility with extension modules, etc.
We also need to make sure that it's possible to implement full backlighting with the extension module and that the board fits various cases.
I've already tested alixinhzai's case and it fits nearly ok. It was necessary to scrape a thin layer of the USB receptacle's cutout to fit the acrylic plates, but other than that, it's okay.
I'd be very interested in getting a report about how the USB looks in various cases - whether it's centered or shifted.
Here's the current firmware, version 0.2, for rev. B only: (Attachment Link)
The layout or GUI have not changed. Remember about programming the layout after flashing. The firmware comes with no layout.
I got my GH60 soldered up in a poker layout. However, the 8 column seemed not to work. I did try loading different firmware on it a couple of time, and nothing seemed to work. :(
I got my GH60 soldered up in a poker layout. However, the 8 column seemed not to work. I did try loading different firmware on it a couple of time, and nothing seemed to work. :(
Which keys didn't work?
I got my GH60 soldered up in a poker layout. However, the 8 column seemed not to work. I did try loading different firmware on it a couple of time, and nothing seemed to work. :(
Which keys didn't work?
If I remember correctly, it was 8, u, j, n
I'll double check when I get home.
I got my GH60 soldered up in a poker layout. However, the 8 column seemed not to work. I did try loading different firmware on it a couple of time, and nothing seemed to work. :(
Which keys didn't work?
If I remember correctly, it was 8, u, j, n
I'll double check when I get home.
Did you use the firmware from this topic?
It looks like you used the rev. A firmware!
The keys that didn't work should've been 8, i, k, m.
If it was different keys, there's something wrong with your board:/
You are using the "new" TMK firmware, right? I think hasu updated it for Rev B support.
When you get the chance can you post the mod you made to ali's case, I have that case :p
Using Linux (Ubuntu) I was able to successfully flash the version 0.2 firmware onto the 32U4. Now I just need to compile and flash a working layout onto it. Oh yeah, and assemble the board with switches, case, etc. :)
Thanks komar!When you get the chance can you post the mod you made to ali's case, I have that case :p
I scraped about 0.5mm of this plastic edge:
(Attachment Link)
You are using the "new" TMK firmware, right? I think hasu updated it for Rev B support.
I'll try that out, but as of right now, this is my Rev B:Show Image(http://i.imgur.com/0VmYSj2.png)
Looks great!
Did you use the firmware from the top of this thread? It should work fine with my layout (as for the column).
As for split backspace, I've yet to add support to the firmware...
As for tkinter, you need python3-tk
Could always give mine a shot *wink wink*
+ Flashed the new base firmware in Lunix using dfu-programmer.Thanks for the report.
+ Installed the new GUI in Linux/Ubuntu. Had to copy the USB directory from the previous version for it to work.
+ New layout file is brilliant. Used it with the GUI to output a new .hex file with my HHKB layout.
- Could not get the GUI to program the GH60 in bootloader mode. "No device present." Used dfu-programmer to flash .hex to keyboard.
- Still need to debug issue with "-" key, and intermittent issue with APP key. I installed used switches (Clears), so the problem may be with the switches I used, or maybe I need to reflow those diodes, etc.
?? What scancode can I use for numpad_plus, numpad_minus, etc.?
I like to use my keypuller to short the switch contacts. It's the perfect size to reach from the switch post to the diode contact. Real good for pinpointing the issue between switch/diode/software.I use my tweezers for this;)
I updated my source to support Rev.B as well as Rev.A by one firmware binary.
jdcarpe, can you try this? Or someone?
(Attachment Link)
Let me know whether these keys work; 8, U, I, K and M.
Thank you, jdcarpe.
I updated my firmware tmk_keyboard to support Rev.B PCB as well as Rev.A. Now one firmware binary works on both PCBs. And some keymap files(HHKB and spaceFN) were added and fixed README.
https://github.com/tmk/tmk_keyboard/tree/master/keyboard/gh60
tmk_keyboard/keyboard/gh60[master]% make KEYMAP=poker
...
Size after:
text data bss dec hex filename
23406 56 178 23640 5c58 gh60_lufa.elf
tmk_keyboard/keyboard/gh60[master]% make dfu
dfu-programmer atmega32u4 erase
dfu-programmer atmega32u4 flash gh60_lufa.hex
Validating...
23462 bytes used (81.83%)
dfu-programmer atmega32u4 reset
Thank you, jdcarpe.
I updated my firmware tmk_keyboard to support Rev.B PCB as well as Rev.A. Now one firmware binary works on both PCBs. And some keymap files(HHKB and spaceFN) were added and fixed README.
https://github.com/tmk/tmk_keyboard/tree/master/keyboard/gh60
I'm trying to flash your tmk firmware to a rev A on mac os x.
I was able to use homebrew to install avr (https://github.com/larsimmisch/homebrew-avr), and 'dfu-programmer'.
I'm not sure how to flash a layout though? I can run this with any keymap and I always get the same layout after it flashes. (I was previously running komars firmware with an iso layout.)Code: [Select]tmk_keyboard/keyboard/gh60[master]% make KEYMAP=poker
...
Size after:
text data bss dec hexfilename
23406 56 178 23640 5c58gh60_lufa.elf
tmk_keyboard/keyboard/gh60[master]% make dfu
dfu-programmer atmega32u4 erase
dfu-programmer atmega32u4 flash gh60_lufa.hex
Validating...
23462 bytes used (81.83%)
dfu-programmer atmega32u4 reset
edit: fixed code quote
If you're going to flash the TMK firmware on there, you'll need to edit the layout file and compile it to .hex first, before flashing your new firmware .hex to the GH60.
You can download the TMK firmware from hasu's Github. The readme will tell you how to edit the layout file for your platform (GH60) and compile it.
3. Make
Build firmware using GNU make command. You'll see <project>_<variant>.hex file in that directory unless something unexpected occurs in build process.
mkae -f Makefile.<variant> clean
make -f Makefile.<variant>Has anyone built the GH60 rev. B prototype with all the LEDs on?Hi komar007! you means WASD, poker arrows fn and esc's? I soldered it with LEDs on and it works~I use the tmk's firmware.
I can buy some and solder them myself, but I thought if someone has already done it, they could test it...
I would like to see if I can get a bit more information on a few things about this pcb. Some questions may seem strange, but help me out if you can.- yes,
- Is the controller soldered on the underside of the pcb?
- Are all of the LED resistors SMD and which side of the pcb are they soldered on?
- Is the USB connection soldered onto the underside of the pcb?
- Do I see a reset button under the caps lock key? Which side is that on?
- I see about a dozen through hole resistors, which side are they mounted on?
If you have a pcb soldered up, would you mind looking at the profile (thickness) and tell me which of the components are raised away from the pcb the most? I am assuming it would probably be the usb connector, maybe the reset button (if thats what that is) and potentially the controller.Here it is, in order:
And for the final and most important question. How raised away from the pcb is the tallest component that is soldered on? If you have a pair of calipers and can give me a pretty detailed number that would be ideal.Assuming the extension module is not soldered, than probably the tallest will be the LED resistors, if they are mounted on the underside. Unfortunately, this depends on what resistors are used. I can't tell you now which we'll ship in the set, because I haven't chosen them yet.
I am trying to figure out what my relative bounds are for the thickness of the silicon sheet in my case design (http://geekhack.org/index.php?topic=51872.msg1144912#msg1144912). I will have cutouts in the silicon for the components that are very raised (like the usb connector and the controller).
Has anyone built the GH60 rev. B prototype with all the LEDs on?Hi komar007! you means WASD, poker arrows fn and esc's? I soldered it with LEDs on and it works~I use the tmk's firmware.
I can buy some and solder them myself, but I thought if someone has already done it, they could test it...
This is my GH60 rev B version
(Attachment Link)
Is there some information about the LED extension module somewhere in a thread that I don't know about/can't find?
If you have a pcb soldered up, would you mind looking at the profile (thickness) and tell me which of the components are raised away from the pcb the most? I am assuming it would probably be the usb connector, maybe the reset button (if thats what that is) and potentially the controller.Here it is, in order:
USB receptacle - 4.1mm
reset switch - 3.1mm
capacitors C3 and C8 - 1.3mm
controller - 1.1mmAnd for the final and most important question. How raised away from the pcb is the tallest component that is soldered on? If you have a pair of calipers and can give me a pretty detailed number that would be ideal.Assuming the extension module is not soldered, than probably the tallest will be the LED resistors, if they are mounted on the underside. Unfortunately, this depends on what resistors are used. I can't tell you now which we'll ship in the set, because I haven't chosen them yet.
I am trying to figure out what my relative bounds are for the thickness of the silicon sheet in my case design (http://geekhack.org/index.php?topic=51872.msg1144912#msg1144912). I will have cutouts in the silicon for the components that are very raised (like the usb connector and the controller).
Congratulations on the case design. It looks very good so far. I like thin cases which don't have space inside. It reduces the noise significantly. Currently using Ali's acrylic case, I wouldn't change it for anything else, even pretty aluminum cases.
Okay, I think you're right. We should start ASAP. The final files are not in the repo yet. And I think, to make it more fair to the participants, I won't publish them until production is complete, keeping the rev. B's status "faulty". This way I can be sure the GH people will get the finished boards first, before somebody else produces them on their own. Not that I mind if someone produces GH60 alone at all of course. But this way we'll give priority to the participants who have paid for prototyping and other stuff.I can totally understand your thought and I found my use of the word "buyers" in previous post was improper. We all participants are taking risks of development and production to make this great thing happen, and should be proud of this. We are not just buyers or consumers.
I hope that the lack of bug information in this thread means lack of bugs, and not that those who got their prototypes didn't have the time to test them. Anyway, if someone has found something, please say it now or never!;DBetatesters, please!
- My main idea is to keep everything simple and modular as possible. I'll need two pins from the atmega (tx/rx) to send/receive AT commands - I think we already reserved these pins some time ago.Not that ATmega hardware UART RXD/TXD pins(PD2/PD3) are reserved for matrix, we should use software UART with GPIO pins to interface BT module. From my experience with WT12 this is not a problem, but I've not tried RN42 with software UART yet.
- Hasu mentioned the power source selection - most probably we will need to make some hack to power feed the board but we can do it later ...Yes, I agree.
Yes, unfortunately I used those pins before I knew we would have an extension module, and then I didn't want to change too much before production. Then it appeared we did another run of prototypes, so I could have changed it then, but I didn't think about it. Now it's too late again, I want as little changes as possible, because there will be no prototypes anymore.- My main idea is to keep everything simple and modular as possible. I'll need two pins from the atmega (tx/rx) to send/receive AT commands - I think we already reserved these pins some time ago.Not that ATmega hardware UART RXD/TXD pins(PD2/PD3) are reserved for matrix, we should use software UART with GPIO pins to interface BT module. From my experience with WT12 this is not a problem, but I've not tried RN42 with software UART yet.
http://geekhack.org/index.php?topic=40514.msg859852#msg859852 (http://geekhack.org/index.php?topic=40514.msg859852#msg859852)
What I'm slightly concerned about is powering the board from the extension module and charging from USB. While just feeding power through VCC and GND pins on he ext' module is not a problem, it can be tricky if we want the possibility to connect USB at the same time to charge the battery. I haven't thought about it, but I do hope it'll be possible to do this without modifications to the mainboard's design.Quote- Hasu mentioned the power source selection - most probably we will need to make some hack to power feed the board but we can do it later ...Yes, I agree.
... On the other hand, I think I'm going to use atmega8a for the backlight module for example, and this means I'll have just one pin left for communication ...
We did mentioned it previously here (http://geekhack.org/index.php?topic=40514.msg820823#msg820823).
Using the RN-42 I think we are okay with software UART (I don't know about the WT giga - mine never went home, sniff)... On the other hand, I think I'm going to use atmega8a for the backlight module for example, and this means I'll have just one pin left for communication ...This guy does not have support for USB, we will have to use some firmware-only usb driver ...
The tmk firmware works on it? Your firmware will work on it?
IMHO, it's not a good moment to change the uC.
-1 atmega8a, sry.
Would not be easier to add one shift register like the mcp23017 or mcp23018??
Found some problems when I tried to set up a ISO GH60 rev.C in Windows:
- ukbdc_gui crashed when I tried to program a layout. I have put up a pull request on GitHub with a fix.
- mnemonics.py is missing: 100: "europe_2" which is needed on ISO layouts for the key right to left shift "<"
- shift is not working together with the key right to left shift and the key right to enter. Feels like a problem with modifiers in firmware.
- Space bar is not working, could be a hardware problem with my board, have to check
Now I need some sleep :p
I think I found the problem. I measured PB6, the pin connected to the column and it appear to be floating so I temporarily added an external pull up resistor and than space started to work! I'm going to test some more and than maybe add a patch, a real physical one that is ;-)