We sat down to talk to Macrofab Engineering Podcast hosts Parker Dillmann and Stephen Kraig. Macrofab is a PCB and Electronics Manufacturing platform.
Need to organize schematic, PCB and supporting files? Here are some ways to do so more easily by setting up your Altium project on Git.
Over the last 6 months, the global semiconductor shortage has been consistently making news for the wave of resulting disruption across the hardware world. From automotive to consumer electronics, virtually every hardware industry has had to scramble to find component replacements ranging from sophisticated ICs to simple microcontrollers.
We live at the dawn of a golden age of hardware development. The tools being built are powerful, fast, and focused on saving money and time but not necessarily with an intuitive user interface. Git has a reputation for being clunky and severe, but everyone participating in the tool-building ecosystem has taken Git a long way from its command line only roots.
Most electronics designs are more complicated than a single PCBA. Very often, designs are compartmentalized into multiple interconnected PCBAs, wiring harnesses, enclosures, mechanical fasteners, labels, packaging, and anything else necessary to run the design.
One of the biggest differences between using Git for software vs Git for hardware is that software tends to use Git as source control whereas hardware tends to use Git as version control.
Every hardware engineer is familiar with traditional design review. In the past, it made sense to gather a group of people in a room, staring at a projector screen, and manually walk through the schematics and PCB layout. Every person has a chance to voice their input and create action items.
In a previous post, we covered git for hardware commit best practices. To review, changes to the files are captured in commits to your local filesystem. Commits should collect small, purposeful, and related changes to the files.
Revision control can be overwhelming when first starting out. Engineers used to releasing files once per PCBA revision can be daunted by commits. It’s very easy to finish working on a section of a schematic and instantly jump to another. Keeping the development momentum flowing is important.