- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Creating iassembly for more than 200 types of gas struts with parameter from an excel file in fast and efficient way.
I want to thank everyone in this community for your brilliant post and kind suggestions. It has helped me heaps.
I am trying to create iassembly of gas struts. I have an excel file with more than 200 types of gas struts with different part numbers, extended length, forces, diameter of piston and cylinder. I could quickly create ipart Piston file by pasting parameter from my excel file directly to the excel file generated by ipart Piston file. And derive the dimension for Cylinder Part file by linking it to parameters of ipart piston file.
However this way everytime I place the gas struts assembly I need to change the piston ipart file configuration and save the assembly with different name. I want to make the gas struts assembly as iassembly so it stays clean and easy.
However, to create an gas struts iassembly I need to create more than 200 rows individually inside the iassembly author and choose the different ipart member of the piston ipart for every iassembly member configuration. Is there a efficient way and fast way of doing it with some other techniques, ilogic or with other script?
Thank you so much really appreciate your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Is there a chance that you will need custom length for the assembly? If so I don’t believe an iAssembly will be able to handle that. Only an iPart on it’s own in a regular assembly can achieve this. Do you need to document the iAssembly in closed /open positions?
I don’t think there is a fast way to create these other than to uses incrementing member names along with iParts to quickly populated data in excel. You will likely need to come up with some kind of file naming scheme that makes sense because picking a member with random generic description like Assembly1 will make no sense.
Use the factory scope rather than member scope to select changes common across the members.
If you set your excel columns up in the correct order you can block paste your data from excel for length etc.
Ilogic can give some help to generate all members.It can also help import data like iproperties and parameters etc but this would likely be slower than organizing the data to aid with block pasting the data.
Here is a post that can create an extrusion and make an iPart in one go. You likely will not need the first half but if go you can utilize the excel creation it might speeds things up for you. I have not tried this method over regular excel population so it might gut be just a fun coding project over an increase in speed.
Have you though about the iLogic assembly route? There is some more up front work required but it may pay off in use-ability and adaptability later on especially if you need to change material and color of parts along with updating iAssembly/iPart properties etc and creating customs.
Or if this helped you, please, click (like)
Regards
Alan