iAssembly error: while publishing factory table in the main assembly

[kevin.machadoUXS5W]

Hi Community,

Please see below the error which I faced during inserting iAssembly into the main assembly.

Application – Inserting number of variations of Handrails into the main structure.

We would prefer iAssembly over iPart as we extract the MTO of all assemblies and subassemblies.

Details of Standard Handrail-

Two types of Handrails – Double Panel and Single Panel with variations of Fixed & Removable type of each panel. In Double Panel, the handrail length remains fixed whereas in Single Panel it varies.

Procedure of creation of iAssembly-

• In the Double Panel, the design remains much simpler than the Single Panel. Hence I depict the creation of iAssembly of the single panel.
• 
• Factory Table in which all the parameters (STIFF_LG, STIFF_HT, SGP_LG etc.) are sought from Parts associated with assembly (Linked Parameters from Part)
• 
• To get those linked Parameters, a small iLogic code was added.

Till this level, everything remains smooth and that iAssembly runs flawlessly with all variations.

However when I start pushing this assembly in the main structural model to have different variations of the lengths, the problem starts popping up.

The lengths of panels should be 3000mm and 2200mm respectively as per the factory table however those remains identical.

All my efforts remain futile till now, hence writing this email to you to get any further assistance from your side, if possible.

[A.Acheson]

Unfortunately iassemblies cannot be used with custom iparts, It is a limitation. The family table requires all data to be fully defined. You could in a rather convoluted method create a new iassembly row for each new custom ipart then regenerate the assembly but I'm not sure it would be a robust method. 

You may need to try an ilogic assembly where you use place ilogic component to create a new length of railing. This  would have the benefit of eliminating the need for custom iparts also as they can be tricky to store and change after. 

See video of a very similar railing product here with that method 

[johnsonshiue]

Hi Kevin,

I suspect this could be a limitation in the iAssembly + iLogic workflow. Personally, I think iLogic rules work the best with iAssembly/iPart when the intent is to perform "change component" workflow on a consumed iAssembly/iPart member. I don't think attempting to alter iAssembly/iPart author table would yield desirable results (depending on what change is made).

If possible, please share the files in zip here or send it to me directly johnson.shiue@autodesk.com. I would like to understand the behavior better and see if this is a bug or a limitation, and also if there is a better workflow.

Many thanks!

[kevin.machadoUXS5W]

Resending

From: Kevin Machado
Sent: Tuesday, November 29, 2022 8:20 PM
To: Johnson.shiue@autodesk.com
Subject: FW: Autodesk Inventor - iAssembly error

Hi Johnson,

Greetings!!

With regards to your reply on Autodesk Community, I am attaching herewith the zip file comprising the iAssembly Handrail model for your further study. It also contains iLogic code.

I tried placing this iAssembly in the main assembly so as to get different iterations of handrails in lengths /Bolted& welded cleats.

Please review and advise on the same.

Thanks and Regards

Kevin Machado
Sr. Designer
	T. +91 (0)7738742016 E.  Kevin.machado@kentplc.com W. www.kentplc.com

From: Kevin Machado
Sent: Monday, November 28, 2022 10:07 PM
To: paul.munford@autodesk.com
Subject: Autodesk Inventor - iAssembly error

Hi Paul,

Greetings!!

This is Kevin here once again. Please see below the error which I faced during inserting iAssembly into the main assembly.

Application – Inserting number of variations of Handrails into the main structure.

We would prefer iAssembly over iPart as we extract the MTO of all assemblies and subassemblies.

Details of Standard Handrail-

Two types of Handrails – Double Panel and Single Panel with variations of Fixed & Removable type of each panel. In Double Panel, the handrail length remains fixed whereas in Single Panel it varies.

Procedure of creation of iAssembly-

• In the Double Panel, the design remains much simpler than the Single Panel. Hence I depict the creation of iAssembly of the single panel.
• 
• Factory Table in which all the parameters (STIFF_LG, STIFF_HT, SGP_LG etc.) are sought from Parts associated with assembly (Linked Parameters from Part)
• 
• To get those linked Parameters, a small iLogic code was added.

Till this level, everything remains smooth and that iAssembly runs flawlessly with all variations.

However when I start pushing this assembly in the main structural model to have different variations of the lengths, the problem starts popping up.

The lengths of panels should be 3000mm and 2200mm respectively as per the factory table however those remains identical

All my efforts remain futile till now, hence writing this email to you to get any further assistance from your side, if possible.

Thanks and Regards

Kevin Machado

Sr. Designer

[johnsonshiue]

Hi Kevin,

I took a quick look at the files. I think I know where the problem is. The iLogic rule in this case is to push assembly (iAssembly table) parameters to individual parts within the assembly. However, such parts are shared by multiple iAssembly members. Since there are the same parts (files), the parameter values can only be unique. For example, when the length is 2000mm and all the parts are adjusted accordingly. Then when the length is 3000mm, the parts will also be adjusted. But, when both 2000mm and 3000mm exist, these parts can only have one value set.

Instead of generating iAssembly members regularly, you need to use iLogic Design Copy to spawn the variation. Here is the workflow.

1. The project isn’t set up properly. Please go to Project settings -> Workspace -> add a workspace -> remove Workgroup Search path.
2. Move the files to the \Workspace.
3. Open 7201275-ALG-SGPANEL.iam -> activate a desirable member -> make sure everything is updated -> Save -> Close.
4. iLogic Design Copy -> pick 7201275-ALG-SGPANEL.iam -> select a target folder -> add a prefix or subfix. A new variation needs to have different file names.
5. After the new variation is created. Open the top-level assembly and delete the iAssembly table (optional).

Many thanks!

[John_L_Hermosa]

I just created a macro to make a handrail. It makes the skeleton or the model, the user can select the best of the options.

https://youtu.be/sPhljXibVSo?feature=shared