Hi All,
I have an assembly containg Sub-Assemblies and Parts.
I have made User Parameters in the Assembly Top Level which are numeric.
When I try to "Link" Parameters in the Parts and select the Top Level Assembly file when prompted I get this "Tip".
Does anyone know if it is not good practice or not possible or what...???
For info I have stripped out all of the iLogic from all parts and am trying to start with a fresh set of rules starting by controlling the parts from the Top Level.
Cheers!
Steve Glover
Inventor Pro 2014 64-Bit Build: 170
Solved! Go to Solution.
Solved by PaulMunford. Go to Solution.
Solved by mrattray. Go to Solution.
Solved by rdyson. Go to Solution.
Hello Steve,
don't start to link parameters out of the top-level assembly.
Do it out of a part file with just this aim - just a container of parameters.
Lothar
Thanks for the posts.
I'm not sure how to reply to all but hope this gets somewhere.
The empty part with only the iLogic Form & User Parameters works pretty well.
I'm finding it pretty useful to open the Form in the "empty" part then open the assembly tab which enables me to see the assembly updating as I change the options in the iLogic Form.
After watching the video herein attached I noticed this chap has his iLogic Form in the Assembly working down the parts.
But this is only possible using iLogic to actually have a filename in the VB code.
This falls over when doing a "Copy Design" in Vault as the new set of files are looking for the original filename in the iLogic code which has been changed in the copy design process.
( Blimey, I hope that makes sense )
I will give it another few days before I tick the solved button.
Again, many thanks for all the replies.
I hope this helps a few users.
@SteveGlover8744 wrote:
But this is only possible using iLogic to actually have a filename in the VB code.This falls over when doing a "Copy Design" in Vault as the new set of files are looking for the original filename in the iLogic code which has been changed in the copy design process.
I've solved this in the past by using a parameter to hold the file name and path of the "master" part and having it be an option on the form.
Logic uses the name it sees in the model browser. You can 'stabilize' this name by over riding it (change it to something eles then change it back).