Everything You Need to Know About Model States | KETIV Virtual Academy
HTML-код
- Опубликовано: 1 авг 2024
- Subscribe to KETIV Virtual Academy ►► ketiv.com/ketiv-virtual-academy
Subscribe to our session for manufacturing leaders and innovators, KETIV Digital Manufacturing Series ►► ketiv.com/ketiv-digital-manuf...
In a recent KETIV Virtual Academy, we taught how to create customized model states in a sheet metal environment and how to control it using iLogic. To continue on the Model State topic, we will be looking at how to use model states to manipulate parts, assemblies, and drawings to give an accurate depiction of how these models will react in a real-life situation. Along with this, we will be going over some tips and tricks that I discovered while using the Model State tool.
In this session we will be going over:
- Creating Model States at a part and assembly level
- Different workflows when creating new model states within parts
- Tips about Model States that everyone should know
Follow us:
Facebook ►► / ketivtech
Twitter ►► / ketivtech
LinkedIn ►► / ketiv-technologies-inc
Blog ►► ketiv.com/blog/subscribe/
#KETIV #KVA 
Наука
A massive drawback is any part or assembly that has model state is not possible to edit in place. Do you can not see your changes in the assembly in real time.
Out of curiosity why are you manually typing in values that you already have as dimensions? Linking them is a far better workflow, shouldn't you be showing best practices?
Hi Richard, linking dimensions through parameters is definitely a great workflow, especially if you are going to be calling on those dimensions multiple times. Linking the parameters so they can be controlled in an assembly is excellent as well. In these examples, we are using them as static models, so it wasn't necessary to link since workflow length would be the same. Thank you!
aren't appearances stored in representations - anything visual is stored in representation - anything affecting geometry/properties is stored in model states?