Discovery Import

Discovery Import

Replace reference error

TAGGED: 

    • rg
      Subscriber

      Why after the save as of the component in one of sub-assembly the reference is missing?

       

      Regards

      ūüõą This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions
    • Naresh Patre
      Ansys Employee

      Hello Roberto

      Is it possible for you to share the assembly (and all its sub assemblies) that you shown in the video, for investigating this issue?

      • rg
        Subscriber

        Naresh Patre 

        we can send them to you, the subgroups have all been created by the same component

    • Naresh Patre
      Ansys Employee

      Hello Roberto Can you attach the model(s) here? I guess those are generic and can be uploaded here. If not, let me know and I will send you a separate link for uploading.

    • rg
      Subscriber

      Hi, I can attach them right away.
      Thank you

       

      🛈This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions

      • Naresh Patre
        Ansys Employee

        Roberto 

        Thanks for sharing the model. The reason behind this failure is that component 2 is actually a copy of component 1. Unlike component1 which is a separate scdoc file, component 2 is not a separate file. If you have component2 as a separate file, then the saving will work fine. I have created a similar test case to demonstrate this behavior. In the attached model, if you follow the same steps as you shown in the video, you can see that component2 gets saved with a new name and is also reflected in both the assemblies of the main file.

         

        🛈This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions

    • mc
      Subscriber

      Naresh Patre Brian Bueno Marco Ugolotti Subashni 

      Roberto

      Hello Naresh,

      thank you for your answer but ... I'm sorry I can't be agree with you.

      - First of all in the previously version the behavior was correct and not like now.

      - Second, even if a component is a copy of another one is not possible that the software "destroys" the assembly references and leave a message saying that there was an assembly....or the software makes the replacing in right way or at least does nothing ... but cannot make damages!!

      • Naresh Patre
        Ansys Employee

        Marco Checcoli Thanks for your reply. Let me discuss this with the development team and let you know.

    • rg
      Subscriber

      Thank you Naresh Patre

      • Naresh Patre
        Ansys Employee

        Roberto In the example you shared, it can be noticed that Component2 is instanced as external as well as internal. See below image.

        Somehow, I was unable to create such instances at my end and would like to know how you were able to create internal and external instance of Component2. This will help to investigate this issue further.

    • mu
      Subscriber

      Naresh Patre

      Hi Naresh,

      in the attached video you can see that in this case the icon that represents Internal or External component are ‚Äúnot true‚ÄĚ (bom continues shows them as the same component). The separation between the two components icon happens when we¬†make external sub-assembly ‚Äúasm_01‚ÄĚ.¬†¬†

       

      🛈This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions

      • Naresh Patre
        Ansys Employee

        Marco Ugolotti Thanks for sharing the steps. I will pass it on to development team and will let you know their response.

    • rg
      Subscriber

      Naresh Patre Hi 

      You have some news?

      Regards

    • Naresh Patre
      Ansys Employee

      Hello  Roberto

      I have submitted a defect for this issue. Below are the defect details for your reference. I will keep you updated on this defect as I hear about its progress.

      Defect Title: Problem while saving component in a sub-assembly

      Defect ID: DE189755

      Release: 2019 R1

    • rg
      Subscriber

      Thanks for letting me know

Viewing 9 reply threads
  • You must be logged in to reply to this topic.