Discovery Import

Discovery Import

Discovery Live Add In for Mechanical Export missing geometry selection

    • miyado
      Subscriber

      I tried Discovery Live Add In for Mechanical Export (2020r1 new feature).
      Geometry and Boundary Conditions import was success, but Geometry Scope was missing. 

      Is this feature cannot transfer geometry selections?

    • Naresh Patre
      Ansys Employee

      Hello Miyado

      I can see the geometry imported under boundary conditions. Please see below snapshot. Can you share the .dls file that you exported?

       

      • miyado
        Subscriber

        Naresh Patre 

        I attached 2 files.

        bar_model_e2.dls is loaded successfully in Workbench, but missing geometry scope.

        bar_model_j1.dls cannot load correctly. The below syntax error occurred. 

        Could you investigate these files?
         

        🛈 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 Miyado

      The file bar_modal_j1.dls has some problem. Can you try exporting the model again from Discovery Live and see if it helps?

      I could open the other model successfully.

       

      • miyado
        Subscriber

        Naresh Patre 
        Thank you for your reply.

        bar_modal_j1 was exported in Japanese language mode. On the other hand, bar_modal_e2 was exported in English language mode.

        As I mentioned formally, the bar_modal_e2 cannot open correctly. (missing the geometry scope)
        I think importing named selections were failed.

        I'm wondering if this problem relate to language setting. Could you consult with ANSYS Japan technical staff?

      • miyado
        Subscriber

        Naresh Patre 

        I noticed that the syntax error related to Japanese character code.

        When I lauched bar_modal_j1.dls, the C:UsersusernameAppDataLocalTempPhysicsTransferansys.py file contains kanji character such as system1.DisplayText = "構造1"

        So declaration of encoding will be need at the head of the python script.

        # coding:utf-8

        Therefore OS will recognize that this script is saved as utf-8 encoding. If the declaration missing, OS would run it as S-JIS encoding. This is a problem on Japanese OS, but may also occur on other language OS.

         

        But, geometry scope missing problem is not resolved yet... I don't know why it doesn't work.

    • Naresh Patre
      Ansys Employee

      Hello Miyado

      I set the Discovery Live and Workbench language as Japanese and tested the bracket example and did not find any issue. Can you send the Discovery Live files of both the cases you have?

      • miyado
        Subscriber

        Naresh Patre 

        I attached 2 scdoc files.

        Design1 : the source of bar_modal_e2.dls
        Design3 : the source of bar_modal_j1.dls

        🛈 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 Miyado

      Can you also cross check if you are using the released version of 2020R1?

      • miyado
        Subscriber

        Naresh Patre 

        Yes. I am using the released version of 2020R1.

    • Naresh Patre
      Ansys Employee

      Hello Miyado

      I have submitted bug 231280 for the syntax error. 

      Regarding the scoping issue, I am still not able to reproduce it. Are you seeing it with other models too?

      • miyado
        Subscriber

        Naresh Patre 

        I've tried it on other models a few times, but I've never been successful.

    • Naresh Patre
      Ansys Employee

      Miyado

      I am not sure what could be the reason. I think let's wait for the response from development team regarding the defect submitted.

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