Discovery Import

Discovery Import

CAD Dimensions Change When Imported to Discovery

    • seffa
      Subscriber
      🛈 This post originally contained file attachments which have been removed in compliance with the updated Ansys Learning Forum Terms & Conditions
        I create my geometry using AutoDesk AutoCAD. I always use English units (feet, inches). I then load this into AutoDesk Mechanical so I can use its export-to-step feature to get my geometry as a STEP files.   When I load this into discovery I noticed that the entire drawing gets scalled down by a factor of 2.54. I attached a picture of this. Notice the dimension of 55 feet.   Now ill create a STEP file and import that into ANSYS Discovery. I measure the same line and it says its 21.6535 ft. This is a 2.54 factor.   This is the first time I caught this issue and now I believe every simulation I have ever run with this program was useless as the geometry was probably wrong. This is very unfortunate as hundreds of hours have probably been wasted.   Sam
    • seffa
      Subscriber

      I now realize that 2.54 is the centimeter to inch conversion. So Discovery interprets all inch units as centimeters? How do I correct this without just scaling my geometry up in AutoCAD.

    • Charudatta Bandgar
      Subscriber

      Hello seffa

      That is rather unfortunate. Will it be possible for you to send me the files so that I can test them and file a bug if it is an issue in Discovery/SpaceClaim. 

      Regards.

      • seffa
        Subscriber

        Charudatta Bandgar This is the drawing as it was exported from CAD. The room is 55 ft long and 25 ft long. I will find that ANSYS imports this interpreting the inches as milimeters. 

         

        Sam

    • Charudatta Bandgar
      Subscriber

      seffa

      Can you convert it into some other format and then try to import that file? We can rule out the possibility that it is not an AutoCAD export issue.

      Regards.

    • Charudatta Bandgar
      Subscriber

      seffa  I have filed a bug ticket, 401559. So that the developers can comment on it.

      Regards.

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