45
0
Fork
You've already forked project-issues
0

Decide on CAD software standardization #55

Open
opened 2026年05月11日 21:41:14 +02:00 by songtech-0912 · 3 comments

Currently, our team uses a variety of different CAD software, many of which are proprietary and save proprietary file formats. We have no native CAD drawings in our repositories; only STEP files that have terrible data fidelity, even if they are in theory a suitable file exchange format. As a compromise solution given the issues with file interchange with CAD models, I propose the following plan:

  • The recommended CAD software will be Fusion 360, since it has a free version and RPI also gives an educational license. Ideally, everyone should use it*.
  • However, everyone is allowed to use any CAD software they are most familiar with (the native file format of Fusion 360 are F3D files), and store the files in the Source Models folder in the model drafts folder in the laser repo. Each file must be documented in the README in the folder.
  • Whenever anyone makes a change, they should export a STEP file for their models
  • This way, people can use program-native files for CAD (hence avoiding data loss during file interchange/export), while keeping our models open-source and not locked-in by proprietary file formats

While I don’t want to promote proprietary software, FreeCAD is just not very user-friendly at all and extremely frustrating to use. By using this composite approach, we are able to still ensure that our CAD files can be loaded in FreeCAD/another open-source CAD software (since they can generally all import STEP files) while avoiding the inevitable data loss that comes from using a non-native file format.

*: There are a few exceptions; for instance, the solar mirror uses OpenSCAD since it is a simple geometry, has a high degree of symmetry, and requires easily-adjustable parameters for rapid iteration.

Currently, our team uses a variety of different CAD software, many of which are proprietary and save proprietary file formats. We have no native CAD drawings in our repositories; only STEP files that have terrible data fidelity, even if they are in theory a suitable file exchange format. As a compromise solution given the issues with file interchange with CAD models, I propose the following plan: - The recommended CAD software will be Fusion 360, since it has a free version and RPI also gives an educational license. Ideally, everyone should use it\*. - However, everyone is allowed to use any CAD software they are most familiar with (the native file format of Fusion 360 are F3D files), and store the files in the `Source Models` folder in the model drafts folder in the [laser repo](https://codeberg.org/elaraproject/laser-research/). Each file must be **documented** in the README in the folder. - Whenever anyone makes a change, they should export a STEP file for their models - This way, people can use program-native files for CAD (hence avoiding data loss during file interchange/export), while keeping our models open-source and not locked-in by proprietary file formats While I don’t want to promote proprietary software, FreeCAD is just not very user-friendly at all and extremely frustrating to use. By using this composite approach, we are able to still ensure that our CAD files can be loaded in FreeCAD/another open-source CAD software (since they can generally all import STEP files) while avoiding the inevitable data loss that comes from using a non-native file format. \*: There are a few exceptions; for instance, the solar mirror uses OpenSCAD since it is a simple geometry, has a high degree of symmetry, and requires easily-adjustable parameters for rapid iteration.
Author
Owner
Copy link

CAD software comparison in Jacky's opinionated judgement:

Software Advantages Disadvantages
FreeCAD FOSS*, has a reasonable number of features(?) Not particularly user-friendly, quite buggy
Blender FOSS, actually delightful, lots of tutorials, has CAD plugins Isn't really capable of CAD work without plugins
Autodesk Inventor Industry-standard & widely used, supports DXF**, has free educational version Non-FOSS, educational access is complicated, ridiculously expensive otherwise, non-FOSS
Solidworks Industry-standard & widely used, supports DXF** Non-FOSS, educational version costs 60ドル/year
Fusion 360 Widely used, some of the team already uses it, free for personal use, supports DXF* Non-FOSS, native file format (F3D) is proprietary
Siemens NX RPI offers it free via student license It has many negative reviews
OpenSCAD FOSS, highly-programmable, code-based is useful for some tasks Everything has to be done with its programming language (hence very tedious & slow)
Onshape Free for 6 months, reasonably widely-used by hobbyists Non-FOSS, less features than Autodesk stuff/Solidworks
Rhino Not sure? But seems widely used Non-FOSS, Educational version costs 195ドル
Sketchup Very very widely-used, supports DXF Non-FOSS, meant more for architecture than CAD, costs 55ドル/year even with student discount, can’t export to STEP

*: FOSS means "Free & open-source". We want to support open-source!
**: DXF is AutoCAD's CAD interchange file format and supported by most commercial CAD software. It is a partially-open standard that can be loaded via open-source tools (e.g. FreeCAD has an importer)

A more complete and unopinionated list is given on this Wikipedia article.

CAD software comparison in Jacky's opinionated judgement: | Software | Advantages | Disadvantages | | ----------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- | | FreeCAD | FOSS\*, has a reasonable number of features(?) | Not particularly user-friendly, quite buggy | | Blender | FOSS, actually delightful, lots of tutorials, has CAD plugins | Isn't really capable of CAD work without plugins | | Autodesk Inventor | Industry-standard & widely used, supports DXF\*\*, has free educational version | Non-FOSS, educational access is complicated, ridiculously expensive otherwise, non-FOSS | | Solidworks | Industry-standard & widely used, supports DXF\*\* | Non-FOSS, educational version costs 60ドル/year | | Fusion 360 | Widely used, some of the team already uses it, free for personal use, supports DXF\* | Non-FOSS, native file format (F3D) is proprietary | | Siemens NX | RPI offers it free via student license | It has many negative reviews | | OpenSCAD | FOSS, highly-programmable, code-based is useful for some tasks | Everything has to be done with its programming language (hence very tedious & slow) | | Onshape | Free for 6 months, reasonably widely-used by hobbyists | Non-FOSS, less features than Autodesk stuff/Solidworks | | Rhino | Not sure? But seems widely used | Non-FOSS, Educational version costs 195ドル | | Sketchup | Very very widely-used, supports DXF | Non-FOSS, meant more for architecture than CAD, costs 55ドル/year even with student discount, can’t export to STEP | \*: FOSS means "Free & open-source". We want to support open-source! \*\*: DXF is AutoCAD's CAD interchange file format and supported by most commercial CAD software. It is a partially-open standard that can be loaded via open-source tools (e.g. FreeCAD has an importer) A more complete and unopinionated list is given [on this Wikipedia article](https://en.wikipedia.org/wiki/Comparison_of_computer-aided_design_software).
songtech-0912 changed title from (削除) Decide on CAD software policy (削除ここまで) to Decide on CAD software standardization 2026年05月14日 21:12:33 +02:00
Author
Owner
Copy link

In addition, Dune3D seems interesting but probably too unstable for our use.

In addition, [Dune3D](https://github.com/dune3d/dune3d) seems interesting but probably too unstable for our use.
Author
Owner
Copy link

Should mention that Onshape is web-based hence cross-platform, and reasonably cheap. Might work well for us for those reasons.

Should mention that Onshape is web-based hence cross-platform, and reasonably cheap. Might work well for us for those reasons.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
elaraproject/project-issues#55
Reference in a new issue
elaraproject/project-issues
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?