What was the reason for creating the "Eric" User Parameter?
@Leroyteam5 жыл бұрын
Todd Barnett In 2019 Eric Units are more popular compared to the imperial system
@antichris69994 жыл бұрын
I'm attempting to use iLogic to get weights on a drawing. The drawing contains one assembly but I need multiple assemblies. How would I go about getting the total weights of the number of assemblies I need rather than just the weight of one assembly? Autodesk called me about this issue but they just told me to put multiple assemblies on the assembly file but turn off the visibility. This will make the files huge. That method is out of the question so I'm trying to figure out the iLogic. Any help would be appreciated.
@KETIVTechnologies4 жыл бұрын
Hi Antichris6999, The workflow provided by Autodesk would be the best, you can bring in those sub-assemblies and then create LOD's for each. Once you suppress these LOD's to your desired assembly you can extract the weights within the iProperties. I hope this helps out!
@rihabmaaloul76973 жыл бұрын
Hi KETIV team, I have a problem I cant solve its similar to the part 1 model with the holes. Lets say I have holes and I want them to start at 1 inch from the left side and I have a fixed spacing between them Yet I want to keep atleast 2 inches from the right side without holes. using three parameters here (fixed spacing between holes and start point and end point) isnt possible... I hope you get what I mean ... its complicated...
@KETIVTechnologies3 жыл бұрын
Hi Rihab. I believe I understand your question. When trying to annotate a distance (START-MIDDLE-END), one of those parameters will end up being a driven parameter, which could possibly be the source of some of your issues. You can still make calls to the driven parameter in your ilogic like with regular parameters (ie "suppress feature if END distance is =/ 2" or so). Feel free to reach out to support@ketiv.com for more information though.
@AbbasIdris5 жыл бұрын
Is the iLogic code case sensitive?
@KETIVTechnologies5 жыл бұрын
Abbas, absolutely. That's definitely something you need to keep in mind when writing code for automation.
@AbbasIdris5 жыл бұрын
@@KETIVTechnologies Thanks!
@ajamit0074 жыл бұрын
Your "HoleSpacing" Equation should be (Length-(d16*2ul))/(NumOfHoles-1ul)
@KETIVTechnologies4 жыл бұрын
Thanks!
@oddbarnett5 жыл бұрын
Can the User Parameter "Length" be a Model Parameter?
@Leroyteam5 жыл бұрын
Todd Barnett ofcourse not
4 жыл бұрын
Cool !! keep doing
@KETIVTechnologies3 жыл бұрын
Thank you!
@Calacene5 жыл бұрын
42:25 It's driving me crazy that you put a space between the first section and the first else if, but no space between the second section and second else if
@KETIVTechnologies5 жыл бұрын
Thanks for catching that Calacene! We'll look out for that in the future.
@stephenm63344 жыл бұрын
you have issues
@Leroyteam5 жыл бұрын
Link to the Past 👀
@davidewing90884 жыл бұрын
really too wordy. this could have probably been done in a relatively short period of time.
@KETIVTechnologies4 жыл бұрын
We have longer and shorter content videos on iLogic, sorry you found this one too long. Feel free to use our timestamps in the description to skip to the parts you are most interested in.
@davidewing90884 жыл бұрын
@@KETIVTechnologies It is not often that I complain. As a newbie, I was looking for a focused means of answering questions. I want to learn.
@czr7j95 жыл бұрын
I don't know, I just find Solidworks easier to use, less complicated and more logical.