Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.

First time visiting? Here are some places to start:
  1. Looking for a certain topic? Check out the categories filter or use Search (upper right).
  2. Need support? Ask a question to our Community Support category.
  3. Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
  4. Be respectful, on topic and if you see a problem, Flag it.

If you would like to contact our Community Manager personally, feel free to send a private message or an email.

STEP file translation errors.

me_againme_again Member Posts: 18
I've uploaded a .STEP file, but the result I see contains translation errors.

The file is originally produce by SpaceClaim in ACIS (.sab) format where it looks like this:


If I upload and view this is CadExchange it looks like this:


If I use CAD exchange to translate it to STEP format and then view it, it looks like this:


But when I import the .STEP file here and view it, it looks like this:

Note: Then convex edge of the flange has been mis-converted as a concave edge.

I suspect that explains a lot of the problems I have had down stream when using this site to import .step files.

Comments

  • Jake_RosenfeldJake_Rosenfeld Moderator, Onshape Employees, Developers Posts: 1,646
    Hi @me_again

    Sorry you're having this trouble.  It would be helpful if you reported this to our support team using the "Report a bug" or "Feedback" button under the "?" menu in your Part Studio.

    In the meantime, we accept ACIS .sat format, so maybe you could try saving your file out as that and then importing directly into Onshape?  Otherwise, if you only have access to the .sab file, you could use your exchanger to change it to Parasolid (.xt) rather than STEP, as we use Parasolid as our modeling kernel.
    Jake Rosenfeld - Modeling Team
  • me_againme_again Member Posts: 18
    Hi @me_again

    Sorry you're having this trouble.  It would be helpful if you reported this to our support team using the "Report a bug" or "Feedback" button under the "?" menu in your Part Studio.

    In the meantime, we accept ACIS .sat format, so maybe you could try saving your file out as that and then importing directly into Onshape?  Otherwise, if you only have access to the .sab file, you could use your exchanger to change it to Parasolid (.xt) rather than STEP, as we use Parasolid as our modeling kernel.

    Thanks for the response Jake.

    I just converted the original .sab file to .sat using SpaceClaim's sabSatConverter.exe, and then uploaded here directly:

        https://cad.onshape.com/documents/c4d14e10da3f21c434d02bfe/w/37b93269860b2d4095bde767/e/ca84acb67d12088b756b588d

    The result is a file labelled "translatable", but not translated? (I initiated an investigation as requested.)

    Then I use CadExchanger to convert directly from .sab format to parasolid .x_t format, and then attempted to upload that.

    The results was:
     
           Translation not supported b17xf144xe359.x_t failed to translate.
           The following 1 part(s) failed validation and have been removed:
    • 1 unnamed - number of faults:1
            Created at 8:45 PM Today

    Let me know if I can provide further information, or files, or if you have further suggestions?

    Thanks.
  • Jake_RosenfeldJake_Rosenfeld Moderator, Onshape Employees, Developers Posts: 1,646
    Hi @me_again

    Thanks for all the info.  Our internal team will investigate.
    Jake Rosenfeld - Modeling Team
  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 5,683
    @me_again if you try importing again with “allow faults” switched on, you will see the same result as shown in CadExchanger. Looks like there is a surface missing - Onshape will reject an import unless it is a fully enclosed solid.


    Senior Director, Technical Services, EMEAI
  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 5,683
    However, I exported it as STEP from CadExchanger and it came in just fine. Very strange.


    Senior Director, Technical Services, EMEAI
  • me_againme_again Member Posts: 18
    Sorry, I've looked at so many different versions of this that I'm a little confused about which ones you are referring to in each of your replies?
    @me_again if you try importing again with “allow faults” switched on, you will see the same result as shown in CadExchanger. Looks like there is a surface missing - Onshape will reject an import unless it is a fully enclosed solid.

    To which version are you referring here? The .STEP version uploaded/translated okay (except for the concave edge).

    It was the .sat and .x_t versions that didn't translate. Which of those had the missing surface when you allowed errors?

    However, I exported it as STEP from CadExchanger and it came in just fine. Very strange.

    By which you mean: the .STEP version didn't have the missing surface, (although it still had the concave edge where it should have a convex one)?

    (Also, which version of CadExchanger is that you are using? The screen display is different to the cloud version I'm using.)



  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 5,683
    edited June 2018
    I imported b17xf144xe359.sab.sat (the original) into the latest version of CadExchanger for Mac (never knew this program existed before) and the surface was missing. Export as STEP and it comes in as in the image above - I was so focused on the missing surface I missed the inverted arc, sorry. Importing the .x_t had the missing surface.

    Do you have any other examples that exhibit strange behaviour?
    Senior Director, Technical Services, EMEAI
  • NeilCookeNeilCooke Moderator, Onshape Employees Posts: 5,683
    @me_again I just tried it again.
    • CadExchanger for Mac, imported b17xf144xe359.sab.sat from your original Onshape doc (shows missing surface)
    • Exported as sat
    • Imported into Onshape - this time it's perfect
    • Must be something to do with the original conversion, perhaps try it again from the sab file?
    I also just tried the above with their web version with the same results


    Senior Director, Technical Services, EMEAI
  • me_againme_again Member Posts: 18
    NeilCooke said:
    I imported b17xf144xe359.sab.sat (the original) into the latest version of CadExchanger for Mac (never knew this program existed before) and the surface was missing. Export as STEP and it comes in as in the image above - I was so focused on the missing surface I missed the inverted arc, sorry. Importing the .x_t had the missing surface.

    Do you have any other examples that exhibit strange behaviour?
    Not to hand.

    I have repeatedly had trouble with converting any .sab file produced by  SpaceClaim that contains thread forms; the problems manifest themselves down stream at SimScale when I try to mesh them for simulation purposes; the meshing fails with small triangle errors.

    For the most part, I've re-drawn the parts from scratch and the new version work. (I don't have a satisfactory explanation for this!)

    This flange nut is the first time where a visibly obvious defect has shown up in a conversion that OnShape accepted without errors.

    I'm a bit stumped as to what to try next.

    (I'd try re-creating the part here in OnShape, but I and your sketcher do not get along :) )

  • me_againme_again Member Posts: 18
    NeilCooke said:
    @me_again I just tried it again.
    • CadExchanger for Mac, imported b17xf144xe359.sab.sat from your original Onshape doc (shows missing surface)
    • Exported as sat
    • Imported into Onshape - this time it's perfect
    • Must be something to do with the original conversion, perhaps try it again from the sab file?
    I also just tried the above with their web version with the same results

    Do I read this right. You import the .sat file, then export it again as .sat; and then upload the exported .sat to OnShape and it comes in correctly?

    (If so, I'll try that :)

  • me_againme_again Member Posts: 18
    edited June 2018
    Update: Now I see why. They aren't listed because those components have imported as surfaces not solids!

    You asked if I had any other parts with weirdness :smiley:
    NeilCooke said:

    Do you mind if I ask you a follow-on question here? It relates to this https://cad.onshape.com/documents/9bfda64bffb9e12362dd3787/w/3028677bfab9eb655f4b7f70/e/f63c60ecf95ce303ca901eb8 where I have finally succeeded in uploading all 18 components of my assembly.

    Having got them uploaded as individual parts and deleted all the extraneous tabs, I want to assemble them all together into one assembly.

    However, when I select the 'Insert' tool, the 'insert parts and assemblies' dialog only offers me 16 of the 18 parts?

    Specifically, parts 'b2xf26xe62.sab' & 'b18xf26xe56.sab' are missing from the dialog list?

    (I'd raise a new ticket, but I don't see any mechanism for that? )

    ( I'd ask on the forums, but I have asked many questions there in the past, I whilst Jousef diligently responds with "I've referred this to @powers" etc; I've never yet received an answer there that solved my problem.)


    Thanks for your time, M.

  • MBartlett21MBartlett21 Member, OS Professional, Developers Posts: 2,050 ✭✭✭✭✭
    me_again said:
    NeilCooke said:

    Do you mind if I ask you a follow-on question here? It relates to this https://cad.onshape.com/documents/9bfda64bffb9e12362dd3787/w/3028677bfab9eb655f4b7f70/e/f63c60ecf95ce303ca901eb8 where I have finally succeeded in uploading all 18 components of my assembly.

    Having got them uploaded as individual parts and deleted all the extraneous tabs, I want to assemble them all together into one assembly.

    However, when I select the 'Insert' tool, the 'insert parts and assemblies' dialog only offers me 16 of the 18 parts?

    Specifically, parts 'b2xf26xe62.sab' & 'b18xf26xe56.sab' are missing from the dialog list?

    (I'd raise a new ticket, but I don't see any mechanism for that? )

    ( I'd ask on the forums, but I have asked many questions there in the past, I whilst Jousef diligently responds with "I've referred this to @powers" etc; I've never yet received an answer there that solved my problem.)


    Thanks for your time, M.

    @me_again
    For some reason, they have imported as surfaces. In the insert dialog, make sure surfaces is selected as well as parts
    mb - draftsman - also FS author: View FeatureScripts
    IR for AS/NZS 1100
  • Jake_RosenfeldJake_Rosenfeld Moderator, Onshape Employees, Developers Posts: 1,646
    @me_again

    In those two Part Studios you'll notice that some of the surfaces that are required to enclose the part are missing from the import.  Because of this, the imports come in as a set of surfaces rather than a solid part.  You can tell visually, but you can also tell because the bodies come into the Parts list under the "Surfaces" header rather than under the "Parts" header.  Here are some screenshots, I've tried to capture an angle which shows which surfaces are missing visually:



    You actually can insert these surface bodies into your assembly as long as you have the "surfaces" filter selected in the insert dialog:



    But most likely you'll want to actually fix the missing surfaces by following @NeilCooke 's steps.
    Jake Rosenfeld - Modeling Team
  • owen_sparksowen_sparks Member, Developers Posts: 2,660 PRO
    edited June 2018

    It looks like there is an error in those two missing files.  They have missing faces, so they're not watertight.  As such they're shown as surfaces not solid parts, and can't be put into an assembly as a solid.



    You can however click the "surface filter" in the assembly dialogue if you wish, and it will then be available.



    Hope that helps,

    Owen S.
    Business Systems and Configuration Controller
    HWM-Water Ltd
Sign In or Register to comment.