Inventor - Methods for Controlling Frame Generator Filenames and Part Numbers

Поделиться
HTML-код
  • Опубликовано: 1 июн 2021
  • This is a more unique situation based on a user question from previous video and the user wanted to know how to control the file names and part numbers for Frame Generator components, based on a particular naming scheme they wished to use.
    Pete will solve this with two sets of tools combined, some out-of-the-box naming options and an iLogic rule to completely control the Part Number.
    Link to Video and Comment: • Inventor - Editing the...
    Link to Jhoel Forshav's super helpful video: knowledge.autodesk.com/suppor...
    #TeamD3 #D3InventorTips
    For more information about this and other topics, check out our website www.TeamD3.com
  • НаукаНаука

Комментарии • 19

  • @BuffaloBluesBand
    @BuffaloBluesBand Год назад +1

    @Jhoal,
    I never did thank you for you doing this video. It truly helped me. I extended this concept to do a lot more auto-configuration, including creating segregated folder hierarchy based on the naming convention. I even tried to Save to Frame template to a new Frame Skeleton with a SK+name that matches the Assembly name. However, that aspect didn't work.
    Unfortunately, I no longer work for that employer and no longer need Frame Generator models. But a great lesson on several aspects of Inventor and iLogic.

    • @Team-D3
      @Team-D3  11 месяцев назад

      So glad that you found the video helpful and please let us know if there's anything else that we can assist with. Hope all is going well with your new employer and have a most blessed day!

  • @wesfky
    @wesfky 2 года назад +1

    Your user should call their project file (ipj) the job number and then in the frame generator default names use which calls the project file. I didn't have a line to discriminate between content center part and others, I just ran the script in the phantom frame assembly. The next thing I'm trying to work out is getting to count across the project. Because if you have 2 frames in one project, the part numbers will double up.

    • @Team-D3
      @Team-D3  2 года назад +2

      William, thanks for reaching out! I have many users who only have a single project file, who use Vault for example, so using the project file won't help those situations. This is why I typically use one frame per subassembly and use that assembly name as the name driver. For example, if I have a project ABCD and there are two subassemblies "-100" and "-200", I would have the following frame assembly names: "ABCD-100_Frame" & "ABCD-200_Frame". I'm not saying your approach is incorrect, by no means, just wanted to share my thoughts.
      Please let us know if you have any other questions and have a most blessed day!
      - Pete

  • @aaronhendricks4352
    @aaronhendricks4352 2 года назад

    Have you seen any issue arise with the warning about potentially creating files with the same name? I want to switch mine to an index number because the unique number is 13 digits long and I think I'm getting errors with having a file path that is to long when I download the frame to the local machine. I've heard there are some issues with using frame generator and vault when there are frame files with the same name. I use separate ipj files for each project and in my experience frames usually point to a specific frame folder.

    • @Team-D3
      @Team-D3  2 года назад +1

      Aaron, excellent question! When I'm using the Index number, I typically couple that with the assembly name. That has kept me out of trouble, as long as I don't reuse the assembly name. If you have Vault professional, you could also use Naming Schemes module to help avoid using the same assembly names, but the risk is generally low (especially for a smaller design team). Please let me know if you have any other questions, I'd be happy to help! Have an awesome and most blessed day!
      - Pete

  • @waltjenkins6241
    @waltjenkins6241 Год назад

    Hello Pete, I have a pretty simple question around frame generator (I think) and it has to do with Pack-N-Go from Inventor to a new location. The issue seems to be that the association with the skeleton model in the frame assembly seems to remain in the origin location that Pack-N-Go was initiated from, and makes the new frame location and assembly model un-editable ?
    Can you advise on this and or best practices of not only Pack-N-Go, but also "Make from" where you may want to make another frame very similar to an origin frame but with minor modifications (this seems to be an issue more so when copying or make from, or Pack-N-Go) - any help is greatly appreciated
    Thanks a bunch
    Walt J. Ecolab/Nalco Water

    • @Team-D3
      @Team-D3  11 месяцев назад

      @waltjenkins6241, so sorry to have missed this comment somehow! I'll have to do some testing on the Pack-N-Go concept to see what can be done. Unfortunately, it doesn't rename the files, so there could still be some issues there. You could explore using Design Assistant, which is a bit old, but does have to the capability of renaming components. My advice is to use Vault and the Copy Design tool. We just released a video showing how this process could work with a single skeletal model driving frame variations, which has been working well. Please check out that video link below. Thanks for your patience, hope this helps and have a most blessed day!
      ruclips.net/video/np87r_q4Iss/видео.html
      - Pete

  • @webb.industries
    @webb.industries Год назад

    Thanks, Pete.
    I wanted to know whether this type of thing would work if you save the assembly as another number but then change some parts and remove others with welded components. I tried something like this, but when I returned to the original file, I realised that the changes I made to the new one were also affected to the old part's generated frame. How do you change the structure to not refer to the original one? Because I tried to replace the frame with a different sketch, except I changed one dimension.
    There may be an easier way to create a rectangular type frame - e.g. with all dimensions the same, except for one. E.g. 1000 x 1000, and then base the next one on 1000 x 600 and the next to 1000 x 400 - something like that. I want to use the same design but change one dimension every time. But the biggest one may contain extra components to strengthen the structure.
    Do you think this makes sense?

    • @Team-D3
      @Team-D3  Год назад +1

      @webb.industries thanks for reaching out! This is a really interesting question and I've been giving it some thought, but unfortunately haven't had time to formulate a solution. My initial thought is to try and use Model States and see if I can have "unique" variations of the skeletal model. That way each new design assembly can be tied back to a central sketch model and you can components as desired. This may also work within an iAssembly workflow.
      Please note that I haven't had any time to test, so it's all a bit theoretical at this point. However, I've noted this and will revisit it as soon as I'm able and see if I can knock out a video (provided there's a good solution.)
      Really appreciate the question, apologize for the delayed response, and have a most blessed day!
      - Pete

    • @Team-D3
      @Team-D3  11 месяцев назад

      @webb.industries, it looks like Model States did work well for this process. Please check out the blog post and video link below. Also, if you need help with anything else, please do not hesitate to reach back out. Have an awesome and most blessed day!
      hubs.li/Q01Y2s1G0 (Blog Post)
      ruclips.net/video/np87r_q4Iss/видео.html (Video Link)

  • @e1f910
    @e1f910 3 года назад +1

    Thank you for this great way to sync filenames and part numbers. I just have a question: Is there a way to apply this same code in Inventor 2019? I cannot find a way to do it. all the filenames are still called per frame members . If possible can you please point me to a link of yours, or to somebody else who already did this? Appreciate. Thanks

    • @Team-D3
      @Team-D3  3 года назад +1

      Eric S, out apologies for the delay in getting back to you! Yes, this should be possible in 2019 Inventor, but you'll have to update to the 2019.2 or later release to access the File Naming Defaults. Give that a try and let us know if you have additional questions.

    • @e1f910
      @e1f910 3 года назад +1

      @@Team-D3
      Thank you, we installed 2022 to take full advantage of all those new features, including this method you’ve explained, thanks again for your great work!

  • @andrisvitus4086
    @andrisvitus4086 2 года назад

    Hi, why when I try to run this code it shows me that syntax error in line 13, 15 and 17. Did I do something wrong there?

    • @Team-D3
      @Team-D3  2 года назад

      Andris, sorry to hear that you've had issues with the code. In my original code, line 13 is a comment line and shouldn't even run anything, so I would double check the code on your side. Be careful about the string: {AC211AE0-A7A5-4589-916D-81C529DA6D17} which identifies the Frame Generator components. There could be some errors that occur, if that's not correct. Please let me know if this helps and thanks for reaching out! Have an awesome and most blessed day!
      - Pete

    • @andrisvitus4086
      @andrisvitus4086 2 года назад +1

      @@Team-D3 Thank You! All working now PERFECT!

  • @lehongson416
    @lehongson416 2 года назад

    Error on Line 13 : Syntax error.
    Error on Line 15 : Syntax error.
    Error on Line 17 : Syntax error.
    I run this Code and show error. Please help me!!. I use Inventor 2021 pro

    • @Team-D3
      @Team-D3  2 года назад

      LÊ HỒNG SƠN thanks for reaching out and our apologies for the delay in getting back to you. Can you please double check your code? Line 13 should be just a comment line, Line 15 should be the End If line and there isn't a Line 17 (at least with the way it's written). Have you combined this with other code? Is this being done in an iLogic rule? If you're trying to code this into an add-in, you may have to tweak some of the code you're building. Hope this helps to clarify and please reach out with any questions.