Ask HN: How do you document your hardware projects?

Re:Ask HN: How do you document your hardware projects? by MountainMan1312 on Thursday January 11, 2024 @12:42PM (#38955682)

I think version control like this would work great with programmatic CAD like OpenSCAD

[ Parent | on HN ]

Re:Ask HN: How do you document your hardware projects? by nine_k on Thursday January 11, 2024 @01:03PM (#38956024)

Since OpenSCAD uses basically source code format, it already does.

I'm more interested in tracking and versioning edits to KiCAD schematics, for instance.

[ Parent | on HN ]

Re:Ask HN: How do you document your hardware projects? by bgnn on Thursday January 11, 2024 @04:39PM (#38959536)

I think you are describing something similar to Perforce Versic [1]. I use this at work to diff schematic or layout. The ugly thing is: it's perforce.. I wish there was an open source alternative.

[1] https://www.perforce.com/products/versic

[ Parent | on HN ]

Re:Ask HN: How do you document your hardware projects? by fanf2 on Thursday January 11, 2024 @05:53PM (#38960635)

KiCAD’s storage format is s-expressions, so it works OK with git (better than binary file formats). However I have not tried to merge concurrent edits by multiple people; I suspect if there is any conflict you are basically out of luck.

[ Parent | on HN ]

Re:Ask HN: How do you document your hardware projects? by lincoln20xx on Thursday January 11, 2024 @01:07PM (#38956109)

Git works great with text-based code-cad. My personal favourite flavor is build123d, which is based on cadquery.

[ Parent | on HN ]

Re:Ask HN: How do you document your hardware projects? by 533474 on Thursday January 11, 2024 @02:45PM (#38957821)

CSG is not as useful as BReps

[ Parent | on HN ]