CAD workflow for internal cooling channels in CuCrZr additive parts
I am comparing CAD strategies for a compact CuCrZr heat-transfer component with curved internal channels. In BricsCAD, would you keep each channel as a separate solid until the final Boolean subtraction, or build the channel network as one swept solid first? My priorities are avoiding self-intersections at branch junctions, preserving a minimum wall thickness, and making later design changes without rebuilding the whole feature tree.
For additive-oriented CAD, I would also appreciate practical advice on checking unsupported channel angles and exporting a clean STEP model for downstream thermal simulation. I am interested in the modeling workflow rather than machine process settings.
The geometry class is similar to the copper alloy thermal parts in this engineering reference: https://copper3dp.com/cucrzr-3d-printing/
Comments
-
Hello.
When modeling complex solids, it is better to start by creating separate parts.
This approach requires more work but:- Avoids self-intersecting solids, like when using sweeps.
- Ensures further analysis on how separate parts could best be joined together.
Bricscad doesn't include any 3D printing related tools, like the ones included in slicing applications.
So, an automatic analysis in this regard - checking unsupported channel angles - is not possible.0 -
Wouldn’t NTop be more suited for this?
0 -
BricsCAD has clash/intersecting detection analysis (interference command) so that would help for part of the checking. The analysis for channel angles for 3D printing could probably done in another program provided there is a suitable export format.
Unless one is working on projects that are restricted to a certain kind of work(flow) it is unlikely that there is a single program that can do all the things necessary and retain a fast error/crash free performance. At some point you have to use more than one program.
Imagine what it would be if BricsCAD could to structural analysis, strength analysis etc. like Ansys. They made a start in V25 or V26 when it was launched and since then I don't recall seeing any development on it in the release notes so it may have been abandoned for the time being.
0