Hi Fellows,
This post presents a simple (or not) approach to address the challenges of dense patterning in F360. The issue is particularly pronounced in the parametric design mode. The example does not venture into API-driven methods that could be more efficient. Still, for obvious reasons, they are not available for everyday CADmortals (how to change the status? … just pray API .. until enlightenment strike).
So let's go:
- The hardware must be up to the challenge imposed by an envisaged pattern. For this example, the design contains three parameter-driven machine tables (only in their early design stages), each featuring 40x80 pattern's elements. (altogether 9600).
- Do not make the mistake of designing a patterned component in situ in your final design. Do it in a separate file. (I did three in one! … me bad! … the computer with 32GB RAM/ 4GB GpuRAM has had a problem chewing through it!)
- Simplify the topological steps leading to the pattern. The comparison of Table_B and Table_C is a good example here. The same design was achieved in two different ways. The creation of Table_B is more straightforward and faster.
- Use double patterning. Compose a pattern's sub-segment first and then pattern it to complete the design (e.g., Table_C).
- Use well-optimized pattern elements (not shown in this example)
- While undertaking steps towards building necessary elements, successively convert the latter to direct modelling (DM) bodies as you go. It will significantly alleviate the burden on the computing resources required in terms of time and memory. This is illustrated in timelines of Table_C in files <MachineTable Frivolous> and <MachineTable SimplifyAsYouGo> (2*patternFeats and 3*CombineFeats are left not DMed still, but they should). Compare the respective timeLines!
- Strip the parametric envelope from your patterned component by converting it to a direct modelling mode and save it as a separate file. You might also dissolve features. It will take some considerable processing time… go to bed and check the next day. The algorithm here is suspiciously slow, and even it utilizes all processors cores!!!. It might be ill... I would not recommend dissolving…unless they are swim shorts 🏖.
- You might also elect to remove the respective user parameters used to build the component (depend upon circumstances), and this will be the final 'product.'
- Only this DM form of a component should be included in your successive design steps.
- Finally, if the pattern is friendly enough and you have access to a machine shop and a guy there with thick oiled fingers, he will write a couple of lines of lazy G-code to perform the task without a need to resort to the 'maca geegee' described above.
- He might also spare you the possible formidable challenges of running CAM generation of the model.
- On the individual part's drawing, just show a pattern element and mark the pattern parameters and instruction for the part's machinist (possibly as a graphical tool path marking - note for TF360).
- However, if you are a rendering artist and, even worst … the animation one … craft F360 model!
Related Posts:
Attachments:
MachineTable_Frivolous.f3d model (94KB) https://a360.co/34C1qZi
MachineTable_SimplifyAsYouGo.f3d model (94KB) https://a360.co/3icHu7k
MachineTable_C_DirectModelling.f3d model (12KB) https://a360.co/3fHEQoD
Videos:
MachineTable _mono.mp4 4K_mono (71MB) https://a360.co/3yQP5OZ
MachineTable _arcd.mp4 4K_stereo (357MB) https://a360.co/3fICRQN
To be viewed on 4K media devices (monitors, UHD TVs, projectors...) of reasonable performance. For the best experience, use stand-alone media applications and the native resolution 3840x2160 – full screen. The stereo file requires an anaglyph red/cyan glasses. Download the files over a network, where the cost of doing so is not a concern. The files are to be used for private, non-commercial purposes only.
WARNING:
MachineTable_Frivolous.f3d and MachineTable_SimplifyAsYouGo.f3d are not very responsive. In any circumstances, do not change parameters when the whole timeLine is in effect. Suppose you want to modify the design, separate tables to individual files and change the userParameters rolling back timeLine first. Make sure that you have the proper hardware for the task. Certain algorithms in the process use a vast amount of memory. In case there is not enough of it, page.sys will be utilized, resulting in slowing down the process considerably. MachineTable_C_DirectModelling.f3d is relatively safe.
Regards
MichaelT
