makotokurauchi / helix Goto Github PK

去年10月の MakotoKurauchi/qmk_firmware#20 で、Helix のファームウェアのビルド時の指定オプションが、ビルド結果のバイナリファイル名に反映するようにしました。
半年近く運用してみての経験に基づいて、今後どうしたほうがより良いのか再検討を要すると思われます。

From a quick look on the PCB layout it seems like both Pro Micros are connected together using the TRS cable by pin number two (The RX pin of the serial port).
If it's true then the right (slave) side won't be able to send data to the left (master) side.

Hi, I didn't know where else to post this. I'm not getting any output from the keyboard when plugging the Pro Micro into the PC.

If I remove the Pro Micro from the keyboard, it is detected by QMK toolbox.

Do you have any ideas of things I can test to try to get this keyboard working?

I've posted some photos of the work-in-progress here: https://imgur.com/a/3gnFJrw

Any help is greatly appreciated, I'm stuck and don't know what else to try!

What was the reason behind those LED cutouts? Are they for reverse mount LEDs? I was under impression there are no reverse mount adressable LEDS. Why did you make those cutouts? Are they for compatibility with non-RGB switches only? The board will be better without cutouts and will support SMD reflow process without soldering each LED with individual solder bridges. Was there even a real reason?

recently made pcbs from the provided kicad files and three keys on row 4 of the pcb activate the entire column. if using the pcb as left side, Z, X, and B activate the whole column

Most of the European languages have additional characters and a 75% keyboard would have enough keys to accommodate dedicated keys for those, without having to change the keyboard layout. Another use case can be developers can have dedicated keys for {}() to make life lot easier.

Even without these a 75% keyboard would be a nice addition.

Linking: .build/helix_rev2_oled_default.elf [ERRORS] | | /usr/bin/avr-ld: .build/obj_helix_rev2_oled_default/keyboards/helix/rev2/rev2.o:/home/draven/qmk_firmware/keyboards/helix/local_drivers/ssd1306.h:69: multiple definition of display'; .build/obj_helix_rev2_oled_default/local_drivers/ssd1306.o:/home/draven/qmk_firmware/keyboards/helix/local_drivers/ssd1306.h:69: first defined here
| /usr/bin/avr-ld: .build/obj_helix_rev2_oled_default/keyboards/helix/rev2/keymaps/default/keymap.o:/home/draven/qmk_firmware/keyboards/helix/local_drivers/ssd1306.h:69: multiple definition of display'; .build/obj_helix_rev2_oled_default/local_drivers/ssd1306.o:/home/draven/qmk_firmware/keyboards/helix/local_drivers/ssd1306.h:69: first defined here | collect2: error: ld returned 1 exit status | make[1]: *** [tmk_core/rules.mk:306: .build/helix_rev2_oled_default.elf] Error 1 Make finished with errors make: *** [Makefile:584: helix/rev2/oled:default:flash] Error 1

When compiling firmware on QMK configurator, repeated errors occur with Helix builds. This prevents the firmware from being downloaded. The following is the error reported in the command window:

|
| .build/obj_helix_rev2_back_oled_default_583be4a/keyboards/helix/rev2/rev2.o: In function matrix_init_kb': | /qmk_compiler/qmk_firmware/keyboards/helix/rev2/rev2.c:25: undefined reference to is_helix_master'
| collect2: error: ld returned 1 exit status
|
makek:300: .build/helix_rev2_back_oled_default_583be4a.elf] Error 1
make: *** akefile:579: helix/rev2/back/oled:default_583be4a] Error 1
�ake finished with errors
�

More of a preemptive question than an issue: I'm currently in the process of assembling my Helix and have followed a few guides. Is it correct to assume that I can only enable backlighting OR underglow, but not do both simultaneously? I know the Corne has the ability to do both, I was not sure if it was similar in that regard.

The problem I'm running in to is that if I power the left side then only the left side works, but if I power the right side then both sides work but the keymap is (understandably) flipped. Is there anything I need to do to fix this?

Any plans on upgrading the PCB schematics with Kailh Hot Swappable sockets?

I'm sorry this is not a real issue-- I'm just enchanted with the keycaps shown in the picture. What keycaps are these?

Thanks!

Hi @MakotoKurauchi,

Just wanted to say thank you for designing such a beautiful looking board.

I wanted to ask if you think you could use through-hole diodes in place of SMD diodes and still be able to complete this build with kailh choc switches.

Thank you.

I've been attempting to flash a custom keymap, but I haven't been able to accomplish this.

I attempted using QMK Configuartor initially, but I'm always met by the error:

Linking: .build/helix_rev2_back_oled_layout_mine.elf �
|
| .build/obj_helix_rev2_back_oled_layout_mine/keyboards/helix/rev2/rev2.o: In function matrix_init_kb': | /qmk_compiler/qmk_firmware/keyboards/helix/rev2/rev2.c:25: undefined reference to is_helix_master'
| collect2: error: ld returned 1 exit status
|
makeine.elf] Error 1
make: *** ine] Error 1
�ake finished with errors
�

If I do it in MSYS I'm met by the same issue:
Linking: .build/helix_rev2_mandydeth.elf [ERRORS]
|
| c:/msys64/home/mandy/qmk_utils/avr8-gnu-toolchain/bin/../lib/gcc/avr/8.3.0/../../../../avr/bin/ld.exe: .build/obj_helix_rev2_mandydeth/keyboards/helix/rev2/rev2.o: in function matrix_init_kb': | C:\Users\Mandy\qmk_firmware/keyboards/helix/rev2/rev2.c:25: undefined reference to is_helix_master'
| collect2.exe: error: ld returned 1 exit status
|
make[1]: *** [tmk_core/rules.mk:306: .build/helix_rev2_mandydeth.elf] Error 1
Make finished with errors
make: *** [Makefile:584: helix:mandydeth:flash] Error 1

Update:
I was able to successfully compile via QMK Configurator, but only by using the split_common option. Unfortunately does not appear to be functional with OLED or backlighting even while using helix/rev2/sc/oledback

Is there a way to have my cake and eat it while enabling oled/backlighting and a custom keymap?

Hello there.

I'd like to build a Helix and order lasercut plates locally. However I do not know what the required thickness is. I'm assuming that the build has some thickness in mind as it recommends certain heights of standoffs.

What is the recommended thickness for plates? Should a recommendation be made in the guide?

Hi, I recently was able to flash my Helix halves with LED testing firmware as I was building it. Once each half was flashed, I had about a month of not flashing them as bit-by-bit I finished the build. (Note: I have never flashed both halves when they were connected.) I continued building and finally had them complete and connected both halves for the first time in a long time, but did not flash them. I proceeded to plug each half in at a time with the intention of flashing them with useful firmware other than the LED test firmware so that I may finally type with it. The two windows machines that I have tried on do not recognise the presence of either halves neither in QMK Toolbox nor in Device Manager. I am not getting the chimes as you would usually get when plugging or unplugging a USB device, and the reset button hasn't made made a difference either. Also, interestingly, if a Helix module is plugged in, it receives power and the OLED and LED presets work and I can cycle through them as expected, however this continues even when my windows machines are asleep or even shut down but still powered ! (I noted that this does not happen if the computer had not been booted but is shut down and powered) This behavior is similar to the LED's on my motherboard which stay on when the machine is shut down etc.
I have tried communicating with the pro micro using Arduino IDE but it was still undetectable and I didn't have any new ideas.
Someone mentioned "IPS programming to get the bootloader" but I'm not sure where to start with this.
Sidenote: I should mention that when the halves are connected, there is a slight difference in the lighting/hue/colors of LED's between the halves for LED presets apart from a few.

It is rather frustrating not being able to communicate with the pro micro's even though I was once able to...

Anyone who can help with this problem is much appreciated.

Guide calls for m2 7mm standoffs for mx switches. I'm measuring 6mm when assembled. Is it possible to switch to 6mm standoffs? thanks

I can't find the same pro micro as in the picture. which manufacturer you sourced it from?

Any chance we can get the build guide translated to English?

The controller has two columns you can insert the pins into and it is not symmetrical between the two halves so I suggest an additional explanation:
The pins should go into the columns outlined by the silk on the top side of the board. If you are not sure you can match the labels on the board with the labels on the controller.

Best would be to have a picture showing the marking right before the controller part of the guide.

This was the only major issue I had when following the guide which required me to turn for help elsewhere

Hey,

Would it be possible to make the exact measurements of the holes, switch openings and distance between them available?

Thanks!

Edit: Didn't know these could be read using Adobe Illustrator
Problem solved!

Hello, I collected everything, I asked for it, but the right side does not work, if I change the cable in places, the left side does not work. How do I fix the problem? I ran the firmware on both sides.

qmk setting

What's the model number or where can I find the OLED modules to purchase?

Hi

Quick question; does the Pro Micro need to be flipped on the right pad? Or can the bottom side also face upwards like on the left side?

Thanks a lot.