Software engineers take for granted that every change can be diffed, reviewed and rolled back. Hardware engineers usually can't. Most PCB tools store designs in binary formats, so "what changed between rev B and rev C?" means opening two files and squinting.
System ET is an open-source ECAD tool that takes the opposite approach. Modules, symbols, packages and devices are all plain-text files. The training repo shows what they look like: https://github.com/Blunk-electronic/ET_training
Three things follow from that:
- Version control works. Branches, diffs and code review apply to hardware.
- Automation works. A script processor drives the design, so repeated changes become scripts instead of clicking.
- Other tools can read the design. Simulators and checkers don't need an export step.
ET also models multi-board "rigs", checking connector and cable pinouts between boards, which is where a lot of integration bugs live.
It's written in Ada and runs on Linux: https://github.com/Blunk-electronic/ET
Disclosure: I'm helping the maintainer find testers. Feedback goes straight to him.
Top comments (0)