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.
Best Of
Re: FS cPlane angled plane
You are probably better off using opPlane. Ultimately, cPlane is calling opPlane, it just has some extras for the user.
All you would need to do is calculate the normal direction of your plane (and the origin), which will be a lot less work.
qCreatedBy is failing because the Id is that of a sketch entity, but that query type takes in the feature id ("angledPlaneSketch"). To use that sketch line, you need to do something like qCreatedBy(id + "angledPlaneSketch", EntityType.EDGE); As its the only line in the sketch, quering for all edges made by the sketch should produce only that edge.
Or you can do sketchEntityQuery(id + "angledPlaneSketch", EntityType.EDGE, "angledPlaneLine"); if you were to have multiple sketch lines.
All you would need to do is calculate the normal direction of your plane (and the origin), which will be a lot less work.
qCreatedBy is failing because the Id is that of a sketch entity, but that query type takes in the feature id ("angledPlaneSketch"). To use that sketch line, you need to do something like qCreatedBy(id + "angledPlaneSketch", EntityType.EDGE); As its the only line in the sketch, quering for all edges made by the sketch should produce only that edge.
Or you can do sketchEntityQuery(id + "angledPlaneSketch", EntityType.EDGE, "angledPlaneLine"); if you were to have multiple sketch lines.
Re: Improvements to Onshape - August 12th, 2024
We had a lot of internal debate about the One True Name for this feature. :P I'm curious what you'd name it?john_allen289 said:I hope this message gets across loud and clear as the name 'Exclude from properties' does not tell the whole story of this improvement for Configurations.
_anton
2
Re: Improvements to Onshape - August 12th, 2024
Finally! I have been waiting for "Exclude from properties" for years! Thank you!
Re: Improvements to Onshape - August 12th, 2024
Just did some more testing and found an issue...
I released a test assembly with a part with an "excluded" config variable:
The good news is that this shows it's technically possible to "add" new permutations after the fact already, all we need is the UI to allow it! i.e. allow "change configuration" in the context menu for released parts with excluded properties and show the excluded config inputs in the list when instances are selected through "Configure assembly features".
I released a test assembly with a part with an "excluded" config variable:
- I had two parts with different values of the excluded config variable
- I was able to release them as one part number/item as expected
- However if I want to insert a new instance of the released part I can only pick the default with no option to change the "excluded" value
And I can't change the config of the ones already in the assembly.
Basically the release only "creates" the permutations of configurations that were explicitly in the release but only the default is "accessible" after that.
We need to be able to change any of the "excluded" properties of a released part after the fact (since we've decided they are all the same part number anyway)...
I think this might also resolve the questions about sub-assembly behavior?
EDIT:
I found a workaround of sorts: insert the part with the excluded property from the workspace (or version should work as well presumably) and set the config to what you want. You can then "change to version" and pick the released version and you end it adds one count to the BOM row for that part.
See example: https://cad.onshape.com/documents/d2d3382aa18189471db96624/w/bfdb4819bc7e743e462a92ad/e/6f9f5e6d135f553ea7e3a3df?configuration=default&bomType=flattened&renderMode=0&tangentEdgeStyle=1&rightPanel=BOMPanel&uiState=66bbadc0de9c134b5f7663bd
- I was able to release them as one part number/item as expected
- However if I want to insert a new instance of the released part I can only pick the default with no option to change the "excluded" value
And I can't change the config of the ones already in the assembly.
Basically the release only "creates" the permutations of configurations that were explicitly in the release but only the default is "accessible" after that.
We need to be able to change any of the "excluded" properties of a released part after the fact (since we've decided they are all the same part number anyway)...
I think this might also resolve the questions about sub-assembly behavior?
EDIT:
I found a workaround of sorts: insert the part with the excluded property from the workspace (or version should work as well presumably) and set the config to what you want. You can then "change to version" and pick the released version and you end it adds one count to the BOM row for that part.
See example: https://cad.onshape.com/documents/d2d3382aa18189471db96624/w/bfdb4819bc7e743e462a92ad/e/6f9f5e6d135f553ea7e3a3df?configuration=default&bomType=flattened&renderMode=0&tangentEdgeStyle=1&rightPanel=BOMPanel&uiState=66bbadc0de9c134b5f7663bd
The good news is that this shows it's technically possible to "add" new permutations after the fact already, all we need is the UI to allow it! i.e. allow "change configuration" in the context menu for released parts with excluded properties and show the excluded config inputs in the list when instances are selected through "Configure assembly features".
Re: Please add a thread making feature
Have you tried the Threadlabs FS?
https://cad.onshape.com/documents/5c0528b62c1fbb13a2a0e739/v/f86229e7f586f8517a2068a9/e/7cbb452d4d5e963a034ce616
https://cad.onshape.com/documents/5c0528b62c1fbb13a2a0e739/v/f86229e7f586f8517a2068a9/e/7cbb452d4d5e963a034ce616
Thread pitch (metric) M10x0.75 missing ?
Hello,
i would like to use a thread pitch of 0.75 for an M10 hole, but I can't select this.
Can I manually overwrite this?
i would like to use a thread pitch of 0.75 for an M10 hole, but I can't select this.
Can I manually overwrite this?
There should be, among some other options, the following values (DIN 13):
...
0.75
0.75
1.00
1.25
...
greeting M
...
greeting M
Re: Thread pitch (metric) M10x0.75 missing ?
Yes, it should definitely be there, for it belongs to the metric fine thread series. You could use the Threadlab FS for this case, though:
You need a cylindric face with a 10mm diameter to apply it to, though.
Re: Many problems with operation since yesterday (08/13/2024)
Sheet metal flat patterns are fixed. Thank you Onshape team for your quick response!
Re: Improvements to Onshape - August 12th, 2024
Really good guess, @eric_pesty, although that's not quite what happened. The real story is that we realized that we need more time to understand all of the implications of having an assembly or subassemblies in non-default excluded-from-properties configs, and then you try to make a release and you see something very different than what's in the graphics area. So, help us: could you describe how and for what you would like to use exclude-from-properties in assemblies? Others too, of course @john_mcclary.
Thanks!
Thanks!
