Atopile – Design circuit boards with code
1–10 of 32 posts
Re: Atopile – Design circuit boards with code
#2[deleted]
Re: Atopile – Design circuit boards with code
#3If the important thing is "with code" then show me the code.
I gave up hunting through your website because I never managed to find an example of what the code for a real circuit looks like. That should be front and center on the first page.
Re: Atopile – Design circuit boards with code
#4Previously:
Show HN: Atopile – Design circuit boards with code - https://news.ycombinator.com/item?id=39263854 - Feb 2024 (292 comments)
Re: Atopile – Design circuit boards with code
#5title says design circuit boards, but it looks to just be netlist generation which is used as input to an external layout tool. step 5 is to use kicad to do lay out.
https://atopile.io/atopile/quickstart#a-typical-workflow
A typical workflow
1. Sketch your circuit on paper.
2. Search https://packages.atopile.io and GitHub for pre-existing modules you need, and use ato install to install them.
3. Design a module and do its calculations using ato code.
4. Run ato build to compile your project, choose components to suit your design, and update your layout (PCB) file.
5. Use KiCAD to lay out any changes
6. Repeat steps 3-5 until you’re happy with your design.
7. When you’re done with your design, push your changes to your repo.
8. CI will automatically build and test your project, and generate the manufacturing files you need to order your PCBs.
9. Take these manufacturing files to your PCB manufacturer to get your PCBAs.
Re: Atopile – Design circuit boards with code
#6If the important thing is "with code" then show me the code. I gave up hunting through your website because I never managed to find an example of what the code for a real circuit looks like. That should be front and center on the first page.
You must have given up pretty quick."ato Language" in the left-hand navigator under "Essentials" is pretty obvious.
Re: Atopile – Design circuit boards with code
#7If the important thing is "with code" then show me the code. I gave up hunting through your website because I never managed to find an example of what the code for a real circuit looks like. That should be front and center on the first page.
You must have given up pretty quick."ato Language" in the left-hand navigator under "Essentials" is pretty obvious. https://atopile.io/atopile/essentials/1-the-ato-language
That's a language definition not an example of what a real circuit looks like in code.
Re: Atopile – Design circuit boards with code
#8title says design circuit boards, but it looks to just be netlist generation which is used as input to an external layout tool. step 5 is to use kicad to do lay out. https://atopile.io/atopile/quickstart#a-typical-workflow A typical workflow 1. Sketch your circuit on paper. 2. Search https://packages.atopile.io and GitHub for pre-existing modules you need, and use ato install to install them. 3. Design a module and d…
It still makes sense though. In many cases, especially in digital design, circuits look like islands of isolated components where the labels are actually defining the connections between them.
Re: Atopile – Design circuit boards with code
#9Previously: Show HN: Atopile – Design circuit boards with code - https://news.ycombinator.com/item?id=39263854 - Feb 2024 (292 comments)
My reaction to the first comment would be that for more flexibility you could write a Python script to generate the .ato netlist.
Re: Atopile – Design circuit boards with code
#10title says design circuit boards, but it looks to just be netlist generation which is used as input to an external layout tool. step 5 is to use kicad to do lay out. https://atopile.io/atopile/quickstart#a-typical-workflow A typical workflow 1. Sketch your circuit on paper. 2. Search https://packages.atopile.io and GitHub for pre-existing modules you need, and use ato install to install them. 3. Design a module and d…
It still makes sense though. In many cases, especially in digital design, circuits look like islands of isolated components where the labels are actually defining the connections between them.
I would agree if manufacturers bothered to provide machine readable data sheets [0]. If you have to read the data sheet and manually write your component definitions, then this won't be much faster than doing it with a GUI.
[0] To be fair I'm not a professional electrical engineer, maybe there are expensive databases that I don't have access to. I personally always thought that EDA tools have a natural business opportunity where they give you the razor for free (the EDA software) and sell you the razor blades (e.g. part libraries).