jpconstantineau / ergotravel Goto Github PK

Check with EasyEDA and other fabs to see what label to put for them to replace for the job ID.

Job ID should be between switches so that it does not show up when KB is fully assembled.

I’ve tried to insert the Zealios switch to the PCB and it is very hard going. I’ve measured the diameter of the switch’s pins as 1.7 mm.

There are generic labels that are present on the silkscreen. These are not necessary.

the smaller holes makes it easer to keep diodes in place when soldering, but you have to bend the legs exactly right.

Hi,

I'm eager to order and assemble my first split keyboard. I've ended up here after trying to make up my mind for a while. I was about to attempt to port the layout to choc switches but it would seem a fresh commit's been made. Is this a finished layout and has it been tested?

Most kind of you to share what you create! Please share if any help is needed.

/ Jona

This will help everyone in troubleshooting connection issues.

Help by measuring the thickness of your sockets and document how much room there is left between the arduino and the bottom plate.

I'm looking to have an acrylic/steel combo case cut for an ErgoTravel build but I have some questions about the case files in the repo:

1. Are the files in acryliccase/jpconstantineau/ compatible with the middle section defined in the grogdor folder?

2. What are the dimensions and path lengths for the top1u1u, middle and bottom plates defined in the grogdor folder (or is there some way to determine these values from the svg files provided)?

3. What thickness of acrylic should be used when getting the middle section cut (assuming the top and bottom are both acrylic)?

It is poor design to use 90 degree line bends.

Hiya! Please let me know if you prefer that questions be in a thread on reddit, I'm happy to oblige and move this to wherever makes sense.

I opted for the partially built keyboard, which means that the diodes and Pro Micro headers were already on the board (thank you).

Looking at the guide, it looks like you solder diode pins to the pro-micro rather than the header pins I got. I got header pins in my kit and I just want to verify before I goof up my build:

• Are header pins intended to be soldered onto the pro micro / do they fit into the pro-micro headers?
• Should I get and use diode legs instead?

I tested individual header pins and it doesn't seem like they stick in the sockets, though I could just not be trying hard enough.

The V1.03 pcb gerber is not recognised by JLCPCB. It cannot detect dimensions or give a visual preview of the board. This makes me concerned that the gerber may be defective and so I am hesitant to order.

Please can you take a look?

I was looking at your code as a friend is making their own ErgoTravel keyboard, and something's puzzling me a little.

So as far as I understand, to link the two halves of the keyboard, either I2C or "regular" serial is used (with a TRRS cable). I see the defines in the code to choose between the two protocols, but the files for serial seem to be missing in this repository? I did find them in this merge commit: https://github.com/qmk/qmk_firmware/pull/3129/files

Now I might be misinterpreting things, but from the serial.c and serial.h I can see there, it looks like software serial is used (bitbanging) on port PD0. Why? I'd assume hardware serial (on PD2/PD3) would be preferred, since that makes timing a lot easier and it saves you some instructions. I wouldn't be surprised if you could push that to greater speeds too, thus reducing latency (on the slave half).

One reason I can think of, but this is just speculation, is that I2C was implemented first (of which the pins are on PD0/PD1) and serial support was added later, and that one wanted to keep pin compatibility between the two. Is this it, is there another reason, or did I completely misinterpret the serial operation?

Hello,

First of all, thanks for making this board available for us all! I loved the Cherry MX variant and printed a choc variant, but I have some questions.

I printed ErgoTravelLight v3.01 by/for myself without even checking #29 (I built the cherry version back then and I wanted to make a choc variant), while ordering other stuff from JLCPCB, and I'm currently a bit confused:

Is this version even checked and confirmed working? I received the boards this week from JLC and when I check now I'm a bit confused. Are there any guides available ?

1. Are the orientation of Pro micros same with Cherry variant, as in build guide?
2. What is the diodes' orientation? I cannot discriminate it on the PCB silk screen. Any photos available to check ? Or, Is the diodes' orientation same as the Cherry MX guide, where the zener diodes' black lines are in same orientation as SMD ones' vertical lines?
3. Which LEDs would you prefer for soldering ? I have ws2812b 3535, but I believe it'd be impossible to solder these with iron, so cream flux + heat would be required since the foot print is too small.

Thanks in advance!

Instead of having generic large switch labels on the silkscreen, we can number them to match the diode IDs

moving the diode will ease diode install and would allow for all diodes to be installed underneath the PCB

Silkscreen has a few extra lines around the serial header.

A lot of the files here are repetitive and from glancing the code, the keyboard could use the split_common library in QMK. Recently did a PR for the Iris for this exact thing, however I can't verify the PR would work until my ErgoTravel comes in whenever from the GB. If you can't get around to it, I can work on it when I get my ErgoTravel in from the GB.

Link to PR for reference: qmk/qmk_firmware#3458

VCC passes through the TRRS connector and may power WS2812 RGB LEDs on the other side. As such resistance of thin VSS lines may affect brightness of LEDs.