dcpedit / redherring Goto Github PK

so yeah, when I put in the OLED screen for my board, it fails to recognize it in windows, but if I don't solder it in, it is getting recognized. I wonder if people can help me out here, as I really want an OLED screen working

Why do many people use 75R instead of 68R to link D+ and D- in the design of many people,
what I saw in the official document is 68R,
will there be any difference between these two resistors,
this has puzzled me for a long time

The 4 pin OLED header link in the bom points to a part that looks different than the part used in the build guide.
Does the BOM link point to the correct part? If not, can you point me to the correct part?
Mouse part
Build guide image

Hello,
It's a really interesting keyboard, it's a really nice piece of work, I'm especially interested in his solenoids, "da da da", sounds great, but the best I can find on my local shopping site The parameters of the solenoid valve are DC3V 0.5A; DC5V (0.83A, 0.41A), I want to know which one should I choose, I am looking forward to your answer, thank you

It seems like the current PCB mounting hole diameter is only 1.47mm, which I think make it near impossible to insert the Mill-Max hotswap socket due to the same thickness without accounting for drilling tolerance/error.

Like for example the 0305 has the follow specs:

• Diameter: 1.47 mm
• Recommended PCB mounting hole diameter: 1.50-1.55 mm
• Flange thickness: 0.64 mm
• Flange diameter: 1.93 mm

EDIT: Is the reason due to the switch being raised higher (than sitting flushed) causing issue with the acrylic layers?

Is there any plan to support this? Or strictly pure soldered board only? Thanks!

10k resistor in BOM has long lead times at both Mouser and digi-key. Can you recommend an alternative?
BOM 10k resistor
I think this might be a viable replacement, but I'm not sure about the whole carbon vs metal and the different % bit.
Possible alternative

Hello, I have a problem when I flashing the vial firmware. What should I do, please? These are the qmk tookbox output:

*** USBasp device disconnected (WinUSB): Van Ooijen Technische Informatica USBasp (16C0:05DC:0102)
*** AVRISP device connected (usbser): Microsoft USB 串行设备 (COM38) (16C0:0483:0100) [COM38]
*** USBasp device connected (WinUSB): Van Ooijen Technische Informatica USBasp (16C0:05DC:0102)
*** USBasp device connected (WinUSB): Van Ooijen Technische Informatica USBasp (16C0:05DC:0102)
*** Attempting to flash, please don't remove device
>>> avrdude.exe -p atmega32a -c avrisp -U flash:w:"D:\Program Files\avrdude-v7.0-rc1-windows-x64\redherring_vial.hex":i -P COM38
    
    avrdude.exe: AVR device initialized and ready to accept instructions
    
    Reading | ################################################## | 100% 0.01s
    
    avrdude.exe: Device signature = 0x000001
    avrdude.exe: Expected signature for ATmega32A is 1E 95 02
                 Double check chip, or use -F to override this check.
    
    avrdude.exe done.  Thank you.
*** Flash complete
    
>>> avrdude.exe -p atmega32a -c usbasp -U flash:w:"D:\Program Files\avrdude-v7.0-rc1-windows-x64\redherring_vial.hex":i
    avrdude.exe: error: could not find USB device with vid=0x16c0 pid=0x5dc vendor='www.fischl.de' product='USBasp'
    
*** Flash complete
    avrdude.exe done.  Thank you.

4.7uF Capacitor in BOM is scheduled for obsolescence and will be discontinued by the manufacturer. I'd like to find an alternative - but I was unable to find one with similar specs for the form factor.
If there's a good alternative, I'll update the BOM.

This is an eye-opening design, thanks to the author's dedication and selfless dedication.
I'm a keyboard lover, but just a beginner.
May I ask if there is a finished product to refer to, or better yet, I can just buy a sample, which may sound a bit low-level, lol.

The left shift and backslash for ISO needs spacing out.
MX501.225 overlaps with MX501 such that two switches cannot be physically placed to conform to ISO layout.

Would it be possible for you to commit the source files for redherring_vial.hex? The one with solenoid support that you most recently committed in this repository? I would like to edit the keymap to support tap-mod shift keys on the spacebars, but vial doesn't support that function, so I’d have to compile new firmware. I found some files you posted at https://github.com/dcpedit/vial-qmk/tree/dcpedit/keyboards/dcpedit/redherring, but I suspect those don’t correspond to the published hex. I recompiled it to test this theory by cloning the found files to qmk_firmware/keyboards/redherring and running 'make redherring:vial' in QMK MSYS. I was able to compile a new hex and flash it to the board, but there are three distinct differences in function:

1. OLED font and logo are no longer displaying (I just get garbled noise).
2. Rotary encoder won't control volume or page up/down as expected.
3. Vial no longer recognizes the keyboard.

Everything else works fine but I'm hoping with the right source files I can avoid loosing those functions.