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.
Significant difficulties transitioning from NX
mike_molinari
Member Posts: 5 ✭
in General
Hello,
I have been using Onshape for the past week pretty heavily coming from using other parametric modelers in the past.
I have run in to some difficulties in accomplishing the following tasks and wanted to see if there are any readily accessible solutions.
I have been using Onshape for the past week pretty heavily coming from using other parametric modelers in the past.
I have run in to some difficulties in accomplishing the following tasks and wanted to see if there are any readily accessible solutions.
- My first difficulty stems from the editing in context stuff. Is there a way to enable updating all the time. Right now it seems it is impossible to do an equivalent of wave linking in NX where geometry referenced out side of a part is automatically updated along with related features with out the labors task of updating each context individually. In NX the interface was very clear and the decision to have manual (delayed until user interaction) or automatic inter-part updates was made available and defaulted to automatically updating.
- My second problem is related to sub assemblies. When consuming sub assemblies in to higher level assemblies it seems I can move parts under the sub assembly but when opening just the sub assembly the positions from the upper level assembly is not reflected. I can also find no way of resetting the position of all of the sub components at the higher level assembly level. This is very disconcerting. In NX the position of a part in an assembly is stored in that assembly and the sub assembly as a whole is is treated as a single part for the purposes of positioning and constraining. The only way a part in a sub assembly's location can differ from that of its location in the sub assembly is to manually override its position at the higher level that consumes the sub assembly.
- The third problem I am running in to is related to how the hole command works when used on a sheet metal object. I have tried to make countersink type holes but it seems that the logic used by system for doing a subtract boolean function related to sheet metal is interfering. I understand that when doing a cutout in a sheet metal part it is best not to add any angled faces but because this is a separate operation done post cutting I need to represent the hole in its counter sunk configuration.


0
Comments
Thanks for taking the time to respond. I know I sound like an NX fanboy and that might be true so please don't take the ramblings of a new onshape user to heart. There are major differences in the way onshape and other package work that have proven to make me uneasy about how things actually work. The feeling I get is that onshape is kind of loosey goosey on any kind of structure and lacks being opinionated in any way to foundate a design philosophy weather its top down or bottom up. The document workspace is also a bit jarring coming from a structured environment with individual part files for each item or assembly and heavy use of multi level complex assemblies where portions of the design can be locked or are tightly controlled by there own individual teams. I fear that things might just be too permissive to apply a rigorous approach in design philosophy.
My difficulty with assembly positions is shown in this screen capture.
And to undo unwanted changes, see history and restore to a time in history.
As an alternative to the Wave links, have you tried looking at the "derive" feature? It sounds a lot like what you describe. It allows you to create import a linked part, sketch, or other object from a different part studio. If the original part is ever updated, there will be option to update this link or keep it at the previous version.
For the assembly issues:
- Like Dirk suggested, replacing all of the planar mates with "fasten" and "slider" mates may help clear things up. Unlike some other systems, where mates are added to progressively constrain different degrees of freedom, a single mate in onshape is intended to define the entire relationship between to components. If the two components should not move at all relative to each other - you can use a single fasten mate. If one is supposed to rotate inside of the other, a revolve mate can be used, etc.. Once you get the hang of it, its pretty easy to make sure the assembly is fully constrained.
- Mates from a sub-assembly will propagate up to a top-level assembly. However, new mates at the top-level won't propagate down. When you're in the top-level assembly tab, expand the sub-assembly in the feature tree and you'll be able to see the sub-assembly mates.
- The "position" of parts is not controlled and won't propagate either way.
- I think the best approach for your assembly would be change the mates to "fasten" mates as much as possible. If something like the plate you dragged in the video is supposed to move - you can use a slider mate to define which direction it should slide. Within this, you can also define limits. Then, when you drag the part it'll slide within those limits and you can right-click on the mate and select "reset" to move the part back to its original position when the mate was defined.
Summary: 1) replace the many planar mates with fasten, revolve, and slider mates. 2) define limits for anything that should be able to move. 3) right-click on the mate for a "reset" option.Hope this helps!
Working in the system more and applying the suggested approaches has mitigated some of the issues I was facing. While I am not comfortable with the system as a whole because of the lack of structure I am beginning to understand some of the capabilities and decision made in the onshape approach to CAD.
Fully locking down the locations of parts with in a sub assembly also alleviated the problems and the approach of allowing mates to pieces under a sub assembly that are not completely locked down has some understandable merit. While it is not immediately comfortable at least the rules are becoming more clear for me.
NX, Creo, Catia, SW are all mature and richly featured CAD programs. As designers, we approach Onshape as a CAD package, but actually Onshape is a cloud database which has a CAD interface
If you take time to appreciate this difference you'll begin to understand why the industry is moving to the cloud and why having native cloud database, handling data silently and robustly in the background, frees us to do our best work
@mike_molinari I'm very curious where you are with Onshape 4 years later. I myself have been married to NX for 25 years and have a lot of workflows branded in.
Now I have a lot of reasons to give Onshape a try.
But I'd like to hear stories from NX users that took the dive first…
List what features you use in NX the most and are critical to your workflow. Then you'll need to see if onshape has the capability without workaround or adding to your workflow. I fully priase the cloud based nature of onshape but still catching up in modeling side of mature systems.
Onshape has tons of cool things (cloud based is one of them). I really hope it's the (my) future!
Since both use the same Parasolid kernel, I would think that for example "Delete Face" or "Replace Face" would be equally powerful.
But for example: I imported the .stp model of a (plastic injection molded) part and tried to delete some small blends and Onshape failed…
Deleting the same fillets from the same .stp import is possible in NX.
Aside of specific modeling capabilities which Onshape might add later, can it handle the same underlying math to solve those face replacements?
I suspect it might be some modeling tolerance setting..? In NX you set Distance and Angle Tolerances in your Modeling Preferences… (mine set to 0.001 mm and 0.5 deg for example) but I can't find such setting here. Otherwise I don't know why it's failing…
PS: I am also thinking about specific features (like law extension surface for example), but I'll hold off those questions for now… :-)
(Second time I post this text… clicking "Post Comment" seems to not be working as expected…)
Basically, for the moment I'm comparing when Delete Face and Replace Face would succeed or not…
Now playing around deleting these:
https://cad.onshape.com/documents/d8e7dcd265542207d898ceba/w/e3cf115734a2f294d26b0477/e/d483de1fa76feb87c667729f
NX would delete them in 1 go.
In Onshape, I'm needing to do it in several instances. Not a problem per se..
But these I just can't
Since both are based on the Parasolid kernel, I would think they would be equally powerful in handling the "underlying math"
Could this be tied to some sort of Modeling Tolerance Preference? (NX has Distance and Angle and I have mine set to 0.001mm and 0.5 deg
Could Onshape be using a bigger or smaller tolerance?
With delete face issues like this, I might try the unintuitive order, and see if you can delete/heal the problem ones first. Also be somewhat careful with the "delete fillet faces" option. Usually the default being On is a good things, but occasionally it can behave badly. I don't know if there's a similar option in NX, but it's definitely different than the equivalent Parasolid based tool in Solidworks.
As far as I know the distance tolerance is on the order of 0.001mm, but I don't know about the angle. There's no user way to adjust these tolerances.
Simon Gatrall | Product Development Specialist | Open For Work
If you use the "Modify fillet" feature you can delete all of these in one go (or change the radius…).
I think that tool does things a bit differently from the "delete face" specifically geared towards managing fillets.
@eric_pesty I always forget about this trick. Thanks.
Simon Gatrall | Product Development Specialist | Open For Work
@hoolito
I made the switch from NX to Onshape in 2020 and I don't ever want to go back!
for law extension look into onshapes Ruled surface
Thanks to all, this is exciting (and terrifying) :-)
I see Onshape developed specific resources for migrations from Solidworks: PDFs, video's, guides…. (I guess the similarity of UI and the background of the founder are obvious reasons)
Does anyone know of similar (official) things tailored to NX - expats?