![]() The dropdown list includes all iMate connections created for the published assembly. Selecting the iMate connection for the front part. The dropdown list includes all parameters stored in the skeleton file.ĥ. Selecting the parameter that controls the height of the skeleton. The dropdown list includes all parameters stored in the skeleton file.Ĥ. Selecting the parameter that controls the depth of the skeleton. The dropdown list includes all parameters stored in the skeleton file.ģ. Selecting the parameter that controls the width of the skeleton. These basic components are candidates to become the skeleton body of the created iBox component. The command automatically scans assembly parts and searches for basic components, from which parts are derived. Selection of Skeleton Body Here, the skeleton body controlling the geometry of the iBox component is selected. To publish the component, open the file of the assembly which will be transformed into the iBox component. they allow displaying accurately the component in the context of the interior.įor Woodwork for Inventor to see such an assembly as an iBox component, it has to be published. All other iMate connections are set depending on the user’s needs and are auxiliary in nature, i.e. One connection has to define the orientation of the front and top part of the iBox component. In this case, such parameter can be created as a dummy parameter that has no effects on the geometry of the door skeleton.Īnother requirement for the iBox component: the assembly created based on the skeleton must have at least two iMate connections. Width and height parameters are important for such component, while depth parameter may have no effect on the doors, since the door depth does not change regardless of the measurements of the interior skeleton body. For example, a block of facade doors with hinges. It is possible that changing one of the parameters does not result in changes to the overall skeleton geometry. Please enable JavaScript if you would like to comment on this blog.The parameter names can be freely chosen to make them easy to read and understand for the user. Here is the Inventor 2020 model I used: Download Chain_with_MatchList View the entire comment thread. Here is the Inventor 2020 model I used: Download Chain_with_MatchList The above code only works well if inside the assembly each iMate has a unique name and should only be matched with a specific other iMate. When the code finishes, the parts will be on top of each other - I described the same thing in the other article.īest thing is to ground one of the components and then you can move around the others so they come apart and end up like shown in the picture on the top. If MatchiMate(cd, imate, imates, item) Then Set res = Ĭall cd.iMateResults.AddByTwoiMates(imate, imateMatch)ĭebug.Print "Matching " + imate.name + " with " + imateMatch.name + " // " + Err.Description NET / iLogic Function GetAlliMates(cd As Assembl圜omponentDefinition) As NameValueMap NET / iLogic instead have a look at Convert VBA to. Here is the VBA code I used - if you want to use. Instead, we can just place all the components in the assembly at the same time without automatic iMate resolution and then use the API to match the iMates. Unfortunately, as I mentioned above, simply relying on the " Automatically generate iMates on place" option in the " Place Component" dialog will not work as it will also match Insert1a to Insert3b and Mate1a to Mate3b when adding the second part to the assembly. Insert1a will be matching Insert1b, and Insert1b will be matching nothing, etc Insert2bĮach iMate will have a MatchList containing the same iMate type for the same connection point but for the opposite part type: IMates will be named following this pattern: "", e.g. ![]() So we'll have an a type part with connections for points 1 and 2 named chain_a_1-2.ipt, one b type part with connections for point 2 and 3 named chain_b_2-3.ipt, etc There will be four connection points as shown in the above image. We have 4 parts based on 2 types of models: a and b. This is what I thought of doing as a test: ![]() Inventor Idea Station: Match list for imates ![]() if there are unresolved/unpaired iMates left then they will be matched even if there is no appropriate name in the MatchList) I did not realize that they over-match □ In theory, when using a MatchList, the iMates in the various components should be matched automatically when using the " Automatically generate iMates on place" option in the " Place Component" dialog, based on the names provided in the list. I already had a blog post on Hook up a chain using iMate's, but I was recently asked about more iMate related API samples, so I thought I could also demonstrate the usage of iMate MatchList.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |