Great Video to start with the possibilities. I just start with iLogic in an assembly and I think this video is very helpful. Now I search a assembly for trying by myself.
Very informative video. Thank you. Couple of questions/suggestions.. 1. Why are you adding both a mate and an insert? an insert does the same job as a mate, no? 2. For the constraints, you could rename the occurrence in the assembly browser. then, seeing as your feature names are the same, adding the ilogic script would be a simple copy and paste job for all the variants. 3. I think a replace command may do this job a bit quicker as you wouldn't need to specify the deletion of the unused components. Below is my script which seems to be working well. If component = "Insert A" Then Dim componentA = Components.Add("Fitting 1:1", "Insert A.ipt", position := Nothing, grounded := False, visible := True, appearance := Nothing) Component.Replace("Fitting 1:1", "Insert A.ipt", True) Constraints.AddInsert("Insert1", "Fixed Boss:1", "INSERT_EDGE", "Fitting 1:1", "INSERT_EDGE", axesOpposed := True, distance := 0.0, lockRotation := False, biasPoint1 := Nothing, biasPoint2 := Nothing)
ElseIf component = "Insert B" Then Dim componentA = Components.Add("Fitting 1:1", "Insert A.ipt", position := Nothing, grounded := False, visible := True, appearance := Nothing) Component.Replace("Fitting 1:1", "Insert B.ipt", True) Constraints.AddInsert("Insert1", "Fixed Boss:1", "INSERT_EDGE", "Fitting 1:1", "INSERT_EDGE", axesOpposed := True, distance := 0.0, lockRotation := False, biasPoint1 := Nothing, biasPoint2 := Nothing) End If Would like your thoughts on these comments. Really appreciate your video though as it set me on the right track of what works best for me.
i started doing something like this today. The problem with the supressed version is the parts still show up on the BoM. This was they should be removed. very informative, thanks
This is brilliant. Instead of specifying the name of the components and mating faces many many times, is there a way you could specify a string variable to define the parts and geometry once in a list at the start of the script
Is it possible to have an video on how to insert your cylinder in an assembly by choosing the configuration and being able to change it like a "iassembly".
Advantages: 1. To create an array of parts parametrized by .xls sheet - you wan constraint them as you insert them... say - touch the same surface, at different distance. 2. To send the assembly for simulations. The "hidden" objects are still detected, and you got to disable them all one by one... super touchy.
I'm just about to start working on an assembly using this exact iLogic rule. My assembly will end up having 20-30 parts in it, with all but 4 being deleted per the parameter choice. I use Autodesk Vault so my components and iLogic assembly will exist in a separate folder from the finished unit assembly. When you initially set up your assembly, are each of the components saved in the same folder so they can be properly referenced by the rule or can they exist in different places?
I need to use Washer Plains in Content Center File for a bolted joint, between two plate have oval holes, so I have to use the Constraints.Addmate function. they are stitched together on the XZ plane. I want the two planes face down, and there is an offset equal to the thickness of the joint. But they are on the same side, that action makes 2 Washer Plain on the same side. I think I just need to fix the parameters below to reverse the plane. But I do not understand deeply about Function. Please help me.
I have not tried the code in a previous version but my first guess would be, No. The first issue in Constraining Components, the Naming of faces and edges, is not available in the 2018 release which would prohibit the code from running. I would think that that is just the beginning of the code problems if you would try to use it in 2018.
@@davebreiner2744 That's true, I have tried to test it and naming of faces and edges is new functionality in 2019 and that part of code doesn't work for 2018. I am not sure but Autodesk might release a update/service pack later to add those options for 2018.
Good tutorial man, my newly acuired cad manager thinks we can build an air handling unit in 3D from spreadsheet, hes going to shit his pants when he sees this, there are infinate posibilities
Great Video to start with the possibilities. I just start with iLogic in an assembly and I think this video is very helpful. Now I search a assembly for trying by myself.
Very informative video. Thank you.
Couple of questions/suggestions..
1. Why are you adding both a mate and an insert? an insert does the same job as a mate, no?
2. For the constraints, you could rename the occurrence in the assembly browser. then, seeing as your feature names are the same, adding the ilogic script would be a simple copy and paste job for all the variants.
3. I think a replace command may do this job a bit quicker as you wouldn't need to specify the deletion of the unused components. Below is my script which seems to be working well.
If component = "Insert A" Then
Dim componentA = Components.Add("Fitting 1:1", "Insert A.ipt", position := Nothing, grounded := False, visible := True, appearance := Nothing)
Component.Replace("Fitting 1:1", "Insert A.ipt", True)
Constraints.AddInsert("Insert1", "Fixed Boss:1", "INSERT_EDGE", "Fitting 1:1", "INSERT_EDGE",
axesOpposed := True, distance := 0.0, lockRotation := False, biasPoint1 := Nothing, biasPoint2 := Nothing)
ElseIf component = "Insert B" Then
Dim componentA = Components.Add("Fitting 1:1", "Insert A.ipt", position := Nothing, grounded := False, visible := True, appearance := Nothing)
Component.Replace("Fitting 1:1", "Insert B.ipt", True)
Constraints.AddInsert("Insert1", "Fixed Boss:1", "INSERT_EDGE", "Fitting 1:1", "INSERT_EDGE",
axesOpposed := True, distance := 0.0, lockRotation := False, biasPoint1 := Nothing, biasPoint2 := Nothing)
End If
Would like your thoughts on these comments. Really appreciate your video though as it set me on the right track of what works best for me.
I was looking for just this type of example. Thanks, this has been very helpful.
Be sure to subscribe to our channel. MANY more short, features-based tutorials and Tips & Tricks to come!
i started doing something like this today. The problem with the supressed version is the parts still show up on the BoM. This was they should be removed. very informative, thanks
You can filter the BOM so only the visible part populate the list.
Brilliant video. Really helpful. Thanks.
We are glad that you found it helpful! Be sure to subscribe so you don't miss our future tips & tricks and tutorial videos!
This is brilliant. Instead of specifying the name of the components and mating faces many many times, is there a way you could specify a string variable to define the parts and geometry once in a list at the start of the script
Is it possible to have an video on how to insert your cylinder in an assembly by choosing the configuration and being able to change it like a "iassembly".
Advantages:
1. To create an array of parts parametrized by .xls sheet - you wan constraint them as you insert them... say - touch the same surface, at different distance.
2. To send the assembly for simulations. The "hidden" objects are still detected, and you got to disable them all one by one... super touchy.
I'm just about to start working on an assembly using this exact iLogic rule. My assembly will end up having 20-30 parts in it, with all but 4 being deleted per the parameter choice. I use Autodesk Vault so my components and iLogic assembly will exist in a separate folder from the finished unit assembly. When you initially set up your assembly, are each of the components saved in the same folder so they can be properly referenced by the rule or can they exist in different places?
Would like to know this too. It would be good if it could pull parts from Vault.
I need to use Washer Plains in Content Center File for a bolted joint, between two plate have oval holes, so I have to use the Constraints.Addmate function. they are stitched together on the XZ plane. I want the two planes face down, and there is an offset equal to the thickness of the joint. But they are on the same side, that action makes 2 Washer Plain on the same side. I think I just need to fix the parameters below to reverse the plane. But I do not understand deeply about Function. Please help me.
Does this iLogic coding also work in the 2018 release even when the snippets are not there in the older release?
I have not tried the code in a previous version but my first guess would be, No. The first issue in Constraining Components, the Naming of faces and edges, is not available in the 2018 release which would prohibit the code from running. I would think that that is just the beginning of the code problems if you would try to use it in 2018.
@@davebreiner2744 That's true, I have tried to test it and naming of faces and edges is new functionality in 2019 and that part of code doesn't work for 2018. I am not sure but Autodesk might release a update/service pack later to add those options for 2018.
Good tutorial man, my newly acuired cad manager thinks we can build an air handling unit in 3D from spreadsheet, hes going to shit his pants when he sees this, there are infinate posibilities
Thanks for watching!
There is a commercial every 4 minutes...
We appreciate your support!