Giter Club home page Giter Club logo

avalanche's People

Contributors

climent avatar vlkv avatar winder avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

avalanche's Issues

Split Communication Issues

I've been struggling for around a week trying to get either serial or i2c working between the halves.

To try and get i2c working, I've added through hole resisters to the left side using the holes above and below the SMD pads for R1 and R2, and jumpers between the P1/2 holes and the bottom through holes for R1/2 on the right half. I tried adding #define USE_I2C in both the v4 config.h as well as my keymap's config.h, but I could never get it to work.

I gave up on i2c and tried to at least get serial working by bridging the W1 pad on both sides' PCBs and then adding #define USE_SERIAL in both the v4 config.h as well as my keymap's config.h, but I could never get it to work.

I've built 4x PCBs, swapped out microcontrollers, verified continuity between the TRRS jacks with a multimeter, and tried a different TRRS cable (both cables worked fine with my dactyl manuform). No matter what I tried, I can't seem to get it to work.

The only thing that kind of worked was setting #define EE_HANDS and flashing each half as specifically the right or left side. If I then hook USB cables from each side's microcontroller to my computer (without a TRRS cable, of course), it kinda works though it's super laggy.

I tried not to bother you, but I've been stuck for around a week at this point and I REALLY like the V4's design. Anything you can suggest to help me get this working, preferably using i2c, would be sincerely appreciated.

[v4.2] Shorting the SW34 pads for the OLED causes a short on the Pro Micro

I'm not sure if I'm doing something incorrectly, but when I bridge the SW34 pads to try to enable the OLED, my pro micro doesn't start. Desoldering the bridge fixes the issue. I have LEDS installed if that would affect anything.

Edit: Must have been an issue with the LEDs. I de-soldered them and it appears to work properly now.

Problems after breaking-off the numbers row

Thanks to Brent Stromberg, he discovered that on a 40% avalanche (after you break off the numbers row):

However the encoder twists do not register. 
They send KC on press, but no knob turns. 
Also the reset button does not work

And the problem is in the PCB, see image: https://imgur.com/a/KO09Qfu

P.S. Workaround - connect with a wire GND to the reset button (see pink trace drawing on the image above).

v4.2 JLCPCB Order

I'm ordering some v4.2 PCBs and JLCPCB sent the following question. From the image it looks like the holes are green, does this mean the hotswap sockets and spring housing hole are missing?

As shown below, it seems this is a working gerber ready for production, is that right?

Shall we fabricate as per this gerber without further compensation and optimization?

image

Differences between v3 and v4

The only differences are the microcontroller and OLED position? the layout for keys has not been changed?

Thanks in advance

v4.2 compatible QMK firmware

Following up on #19. Have you released a v4.2 compatible QMK fork, or any info on where to find/obtain that? The QMK repo linked to in the readme only has v3. I had hoped the firmware wouldn't require many changes but flashing v3 onto a v4.2 pcb doesn't seem to work at all (OLEDs are garbled, no LEDs, no keystrokes worked). I found a functional .hex file by beekeeb which does work, so someone somewhere has it working. Any help or pointers would be appreciated, thank you!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.