Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- 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.
Options
Hows the STL functionality working for folks?
OpenR2
OS Professional Posts: 188 ✭✭✭
Took a break from OnShape for a while ,,, the STL functionality lured me back.
So hows the STL functionality working for folks?
I tried importing two files.
Both are uploaded but only one converts to part studio,
Says part failed validation.
But I can read this STL in to every other CAD program and mesh program that I have loaded on my computer.
Grrrrrrrrrrrrr.
So hows the STL functionality working for folks?
I tried importing two files.
Both are uploaded but only one converts to part studio,
Says part failed validation.
But I can read this STL in to every other CAD program and mesh program that I have loaded on my computer.
Grrrrrrrrrrrrr.
0
Comments
I took a look at this a few months ago and it really didn't do anything for me because I was looking to integrate STL models as background into my assemblies. I was also not very excited that the interface did not seem to really follow the OnShape interface look and feel. It felt like a completely different app that was being opened in side a window inside OnShape.
I do have an STL file that Lou says is failing the body check when importing into OnShape. It would be an interesting exercise to see if you application has the capability to determine where the issue is and correct it in a manner that allows it to be imported. Is this something that STLWorkbench can do? Do you have a user guide or how to that shows how to do it?
Robert
That is exactly the problem STLWorkbench is designed to address. Fixing problem STL data.
Start by using the the automatically fixed STL file.
If this still proves to be a problem, try the simplify option.
One of these two options seems to work for just about every problem STL I have encountered.
Onshape will continue to make reading STL data more tolerant as time goes on. However it's a bit of game of Whack a Mole, gaps, bad data etc.. The technology behind STLWorkbench represents a LOT of research, lots of man hours and resources. So with the combination of Onshape and STLWorkbench you have a pretty robust solution.
Joe
I am a little confused.
STL is simply an array of triangles with per triangle normal information.
It does not get any simpler than this.
There is no geometry in the file other than floating triangles.
The request for STL was to be able to import STL files into the assembly to be used for reference.
It looks like OnShape is trying to enforce the requirement of a continuous closed mesh? Why? We don't need that for reference.
I can open these STL files in every other application I have tried....I am guessing because they are not trying to force the requirement that the STL be anything more than STL to import as STL.
Its really frustrating to wait this long for functionality and then find out that we don't really get STL support.
We have STL support for a subset of STL files that are of a certain criteria that meets the requirements for some downstream applications.
Can we just start with reading in an STL file?
If the file has no parsing errors....then it should be loaded.
Yes?
Robert
But it shows no Open Edges and no Self Intersections.
So obviously STLWorkbench can load the original STL ... so why not just load the same raw STL in the OnShape document?
So I figured why not save out the "unchanged" STL file from STL workbench and try to import into OnShape.
This imports.
The STL import gave no information about why the import failed.
I opened a ticket and was given a little info about not being able to recognize the STL as a body.
I am told that STL is very complicated (LOL) but restrictions may be relaxed in the future.
I am told a partner tool may help "correct" my "bad quality" STL.
The partner tool shows there is no error with my STL.
But ... saving it out of the partner tool and back into OnShape works.
So this just leaves me feeling a bit like Ive been to the used car lot.
I opened an problem ticket on this issue and have no real information about if its being looked at. Or if there is a problem with my STL. Or if there is a problem with the OnShape STL importer. Or if maybe the partner tool did a correction but didnt report it. What ever it is. The conversion with OnShape so far feels more like deflection than problem resolution.
For $100 a month this is not the kind of problem resolution I would expect.
So how do I find out what caused the problem with the original import. The actual technical reason why the import failed?
How do I find out if any data changed between the original STL and "repaired" STL in STL workbench?
How can I determine if the problem with the imported was specific to an ascii STL vs a binary STL?
How to we document what "fixed" the problem?
STL is not a format that is complicated. It's more that it is prone to many "problems"
self intersections
Flipped normals
zero area faces
Orphaned triangles
Lack of closed volume
Gaps, holes, etc...
Just to name a few
Onshape's current requirements STL are very similar to what most 3D printers typically have.. You cannot print an STL model with these types of errors either.
Just to be clear, you were able to get the STL file to import into Onshape correct?
Onshape takes an approach of Agile software development. One of the tenets of this approach is we do smaller more "agile" projects. This means you get access to new functionality much faster. It also means sometimes there things missing we wish were there. It's a trade off. But I think this is better way to go. This also allows us to hear from you what needs to be added next, vs "thinking" we know everything ourselves.
STL import functionality has just been released. Rest assured it's not done, there will be more capabilities as time goes on. Feedback and diagnostic tools are high on the list.
Also I am working with the STLWorkbench team to streamline the workflow for fixing and importing the STL data. Remember it was designed as a tool to fix STL files in preparation for 3D Printing. Now that Onshape added import, they are looking at making that workflow a bit more obvious as well. So I anticipate the repair process in STLWorkbench to have improvements too.
Joe
Yes. I was able to read the STL file into OnShape after loading into Geometric's STL Workbench....which reported no errors and no corrective activity. Luckily I was able to do this for free and no have to purchase the STL Workbench. I would have been furious if I had spend more money to read in an array of 3 point + a vector sets.
Agile has nothing to do with what the customer sees. Any programming team that was worth anything in the past 20 years has used an agile philosophy. Todays latest buzzword for something that we've all been doing for the last 20 years doesn't have anything to do with the discussion we are having.
What difference does it make that the STL file has any of those issues? The STL functionality as advertised by OnShape in the latest release is that STL can be imported in to be used as reference in your designs. Putting a restriction on the quality of the STL makes no sense at all. I am not going to print the mesh down stream. I just need the points as reference for mating parts or for reconstructing the part as a solid.
So what I am not getting from my ticket or the forum is what was wrong with the file. Which gives me 0 confidence that you have looked at the issue, the you have determined what the issue is, or that it will be fixed next release.
Just thinking of reasons why you would need a "clean" STL file could be something like you need a closed body for your STL section cut code to work correctly. Is this the case? But thats the opposite of Agile. Instead of getting the ASCII and binary importers working rock solid in the first release you would have gone a very non-agile direction and compromised the stability of the importer itself for the Gee-Wiz of the section cut.
The question that I would like answered is what was wrong with my ASCII STL file that simply reading it into STL Workbench and writing it back out as binary STL fixes the OnShape import. No redirection. No "in the next version". No "how would you feel if we incorporated your STL into our test process" .....
Just tell me what was wrong with the ASCII import that the Binary import fixed.
Meanwhile I will find something that converts the ASCII to Binary without any other changes and determine if STL Workbench did a fix it didn't report or if its the difference between your ASCII or Binary parser.
Looks like doing a straight convert to a binary file resulted in the binary file still failing the import.
This points to the STL Workbench making changes to the file that are not being reported.
OnShape has the capability to open a bug report .... but how do you open a bug report with an OnShape app partner?
How do I report this as an issue and work with Geometric to identify the modification that was made to the STL file?
Robert
joe
Great. I will send them feedback with the feedback tool.
How does the OnShape partner gain access to my data or to the logs generated from my data? Isn't my data completely secure on the Amazon (or is it Goggle) servers?
Robert
As part of the Integrated Cloud App qualification process, support mechanisms are enabled and tested between Onshape and the Integrated Application. So that when the feedback tools is used it automatically feeds into the appropriate partner mechanism.
Permissions are handled by the user. The user grants an app permission to access the user's data. Each app also spells out their privacy policies and can be found in their respective App Store entry.
Joe
So wait....now I'm becoming really uncomfortable. So the App Store applications aren't guaranteed to abide by the infrastructure guarantees that Onshape laid out in its sell on their implementation of the cloud? And I'm expected to read each partners terms? Understand them? And keep up with them as they change?
I've been using them a lot.
stl mainly for export
obj mainly for importing scanned data
-John
@ivan_volpe I don't usually jump to the defense of SW companies but in this case feel compelled to do so. OS is new, revolutionary and is opening up CAD to a whole new market.
2 weeks ago we couldn't do anything with STL files. Today we can import them (when they work) and use as reference geometry. Every 3 weeks (roughly) there's an update to OS. The last two have had some really good stuff in them. I'm sure there's more to come in STL-wise in he not to distant future.
Previous updates plugged the holes that prevented me from using OS for work. The devs brought the package up to a level that made sense to go pro, and OS continues to grow.
As mentioned earlier perhaps reverse engineering an stl is often better than using it as a part. On the other hand using a mesh for the topography of a construction site in architecture, or as a scan of a healthy limb to make a matching prosthetic one are a couple of examples where what we have now is useful.
[soapbox mode /off]
Cheers, Owen S.
HWM-Water Ltd