What do you use Ilogic and VBA for?

[Darkforce_the_ilogic_guy]

Hope it ok to ask this questing?  what are you using customization for ? most video i find online is about changing a model with ilogic.. but sind most of the thing we working is too customization for our costumes for project to project  it is hard for us to do .. but I have use it for add Miter as properties so , surface as properties , raw materiel number , add bend note to drawing , sorte partlist ... and colour to part and assambly after the surface.

but that do you use it for .. hope you can inspire me to make new greate feature to our cad system

[frederik_vollbrecht]

Hi,

what I use the most is a script which exports all common formats of a part or assembly to a directory with stockfiles.
These will then pushed into or ERP-System (either over night or direct with a tool).

iLogic checks some properties (like approval and time stamps) befor export.

Another one I use is a "titleblock switcher". This is used if i need to translate a drawing file from ger-eng.

As I most of the time work with Multi-Bodys, I have a script which renames all bodys in this format:
"Projektnumber of the File" "-" "running number"
so I don't need to rename them manual.

I also yesterday wrote a thread where I was showing my newest script:
https://forums.autodesk.com/t5/inventor-customization/ilogic-to-send-create-a-e-mail/m-p/8951873/hig...

I guess i need to bring some order to my iLogic mess 😄

[frederik_vollbrecht]

Oh, what I forgot.

If I find myself doing the same task:

The third time a day

The forth time a week

The fifth time a month

I try to get this task automated 😊

Was the solution helpful? Please mark as accepted or kudo

[pball]

I mostly use iLogic for setting up properties inside of parts, assemblies, and drawings. I have a script create a detailed material description for sheet metal parts depending on the material and thickness for example. All of these scripts auto run when files are saved.

As for VBA or the VB.net addin I've converted to a few years back. This contains all my scripts for exporting and editing groups of files and some other scripts that are always manually run. I have an iProperties script with all the properties we use on dialog and some extra automation added. There are also batch printing and exporting scripts that can be run on all open files or all components inside an open assembly.

My addin also has a few commands that mimic built in commands but better (in my opinion at least). For example I have an update browser names script that requires no input and just renames browser nodes to the part number. Another favorite is save and replace all, which saves and replaces a part/assembly plus every instance of it in the assemble which the built in command does not do.

[Darkforce_the_ilogic_guy]

The renames browser script how have you made it ? could you guide me to make my own ? my colleagues have been asking for it.. but have have not fundt the right way to do that jet

[tdant]

Any time notice myself doing a task I've already done before, I add that task to a to-do list of automation projects. Any spare time I have goes toward knocking out that to-do list, and I find that anything I put on that list can be via programming. Some examples: exporting all the .idws I have open to .pdfs; changing the format of drawings and parts from the corporate standard template to local standards; selecting multiple faces based on a selected appearance; creating custom properties in all parts of an assembly; creating cover drawings for master drawing lists; master fabricated parts lists, master purchased parts lists, fastener lists, etc.; querying what part numbers have already been used in an assembly; and probably most helpful, assigning part numbers based on BOM structure, folder structure, etc. That last one has probably saved me 100 hours over the past year.

[JMGunnar]

Check this 

http://inventortrenches.blogspot.com

http://inventortrenches.blogspot.com/search/label/Autodesk%20Inventor%20iLogic?updated-max=2012-03-0...

[JMGunnar]

http://inventortrenches.blogspot.com

[pball]

@Darkforce_the_ilogic_guy 

Here is the basic VBA version. filename_noext() is a function I made to return just the filename of something and the split() is to get the number in the current occurrence name. There will be an error if you try to name two browser nodes the same. Hope this helps out.

    Dim oAssydoc As AssemblyDocument
    Set oAssydoc = ThisApplication.ActiveEditDocument
    
    Dim oOcc As ComponentOccurrence
    For Each oOcc In oAssydoc.ComponentDefinition.Occurrences
        Dim oOccDoc As Document
        Set oOccDoc = oOcc.Definition.Document
    
        oOcc.Name = filename_noext(oOccDoc.fullFilename) & ":" & Split(oOcc.Name, ":")(1)
    Next

[doug.johnston]

I use ilogic to simplify the whole modeling / drawing process.

Setting up user forms, mainly to eliminate having to go to the parameters and iproperties to modify models and fill in required fields.

Example - I have created a sheet metal template user form where I can build 95% of the sheet metal parts we manufacture, including adding flanges and holes.

Using the form, I can create a new part from scratch, create drawings and create a derived dxf file to waterjet in under 10 minutes !!  This usually took approx. 30+ minutes before I created the template, by having to go through all the different commands (sheet metal, parameters, iproperties, modeling).

[JamieVJohnson2]

I use iLogic for common run calculations to be rerun on save.  I use iLogic to update a custom save stamp for the drawing.  I use VB.NET to perform MANY custom simple to complex design tools.  Simple as adding a few common constraints, complex as a complete automatic processing drawing tool with LOTS of decisions and calculations being performed in short order.

For your custom projects, you need to work a few by hand, and perhaps you will find a common task list.  We always do A, then B, and then C.  That is where you can jump in as a developer.  Even if A requires 30 decisions to be made, your code can help the user make those decisions, and process the design much faster.  That usually requires things like custom windows to display many controls, buttons, text boxes, and the like so the user can verify values before hitting the 'wammy' button that does the work while they get coffee!  (yes I actually called a button Wammy once in 1996 to save an accountant 1 weeks worth of work condensing it to just a few minutes).

[philip1009]

It all depends on how standard you can make designs.  The more variability in a design adds to the complexity almost to the point where automating it isn't much faster than the manual work.  My work has a standard frame design with cover plates on the sides and back with all of the equipment presented on the front.  The framework can be easily automated as most of it's pretty standard and controlled with a form, and then I have a basic interface to add equipment to the front.

Since yours is pretty custom, I'd start looking at the steps of your design process that are the most tedious or problematic.  Doing something simple such as automatic PDF or flat pattern DXF exports can save so much time.