Hi HN, still making progress on Circuitscript, a Python-inspired language for describing electronic schematics: https://circuitscript.net/. You can try it in the browser via the Bench IDE: https://bench.circuitscript.net/
The biggest addition in the past month is initial support for ngspice netlist export — you can now take a Circuitscript design and export it to a SPICE netlist for ngspice simulation. This is a step toward closing the loop between describing a circuit and verifying its behavior, all from the same source file.
I have also added bus support, which makes wide parallel connections like data/interface (I2C, SPI, etc.) lines much less tedious to connect up.
Recently I produced and tested a 161-LED charlieplexed array in Circuitscript, using nested for-loops to generate the array instead of copy-pasting every LED and connection by hand. I plan to write a blog post soon to document this design.
As always, the motivation is to describe schematics as code rather than by clicking around graphical CAD tools (KiCad, Allegro, Altium, etc.). I want to spend time on the design itself, with code expressing the intentions clearly and reviewable in text.
Feedback welcome, especially from anyone frustrated with graphical schematic tools! If you have a KiCad design you'd like to convert to Circuitscript, please reach out to me. I'm looking to test the limits of the language and happy to help with the conversion.
The biggest addition in the past month is initial support for ngspice netlist export — you can now take a Circuitscript design and export it to a SPICE netlist for ngspice simulation. This is a step toward closing the loop between describing a circuit and verifying its behavior, all from the same source file.
I have also added bus support, which makes wide parallel connections like data/interface (I2C, SPI, etc.) lines much less tedious to connect up.
Recently I produced and tested a 161-LED charlieplexed array in Circuitscript, using nested for-loops to generate the array instead of copy-pasting every LED and connection by hand. I plan to write a blog post soon to document this design.
As always, the motivation is to describe schematics as code rather than by clicking around graphical CAD tools (KiCad, Allegro, Altium, etc.). I want to spend time on the design itself, with code expressing the intentions clearly and reviewable in text.
Feedback welcome, especially from anyone frustrated with graphical schematic tools! If you have a KiCad design you'd like to convert to Circuitscript, please reach out to me. I'm looking to test the limits of the language and happy to help with the conversion.