Inventor iLogic Troubleshooting


Inventor’s iLogic can be an incredibly powerful tool and when implemented correctly will make your life an absolute dream.  You are also able to find an incredible amount of coding snippets on the internet as what you are trying to achieve has probably already been tried by someone else.  If it has not then there is always someone to help on the autodesk forums and discussion groups.   There are a lot of helpful people out there, which include both Autodesk users and employees.

This help will sometimes come in the form of VB coding and the Inventor API which is what iLogic can also utilise but if you are not a coder then sometimes the help can be confusing as it is coming from a user that understands the language and you have not even taken a basic course.

I do not know VB but I am slowly starting to get to grips with it.  I really should do a course or get a manual but I will do that when I have time.  So with my limited knowledge I have come up with a system to help me trouble shoot the coding.  I comment out everything from the bottom and then start uncommenting one line at a time to see what it does.  Very Inventor like when trying to see how a part was created that you have downloaded from the Internet.  You take the EOP (end of part) all the way to the top and then you pull it down one feature at a time to see how that bad boy was created.  (please note that this does not always work when there is coding that you do not understand)

Another method that I use to troubleshoot what I want to do is to write everything down on a piece of paper (yes very old school) and then try and figure out how to do each step and then put the code together.