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: Logic Driven Feature (New Custom Feature!) 🆕 [Extrude, Revolve, Sweep, and more..!]
He looks happier this time.
I did not realize that Onshape will pass emojis through the text fields in custom scripts like that. That was not a good feature to let me have, there's no way I'll be using that responsibly.
NEW Custom Feature: Drape Surface
Drape Surface essentially takes an input surface, and sticks it to another body like a sticker, which is useful for approximating meshes, and for creating a single surface that approximates a bunch of surface patches. Here's a link to the feature, and here's a video explanation of the feature. If your company needs something custom get in touch with me at theonsherpa.com. Enjoy!
EvanReese
Re: Custom Feature: Non-uniform patterns by csv input
Here's a bare bones draft to get you going! https://cad.onshape.com/documents/5e76707630d6a64b888e564c/w/20d7e510ac219d2f35743419/e/17589401124085e6cee56921
FeatureScript 2656;
import(path : "onshape/std/common.fs", version : "2656.0");
annotation { "Feature Type Name" : "CSV to mate connectors", "Feature Type Description" : "" }
export const csvToMateConnectors = defineFeature(function(context is Context, id is Id, definition is map)
precondition
{
annotation { "Name" : "CSV file" }
definition.csv is TableData;
}
{
const lengthUnits = inch;
const angleUnits = degree;
const tableData = definition.csv.csvData -> removeElementAt(0); // removeElementAt(0) to get rid of columns header row
const coordinateSystems = mapArray(tableData, function(row) {
const xAxis = vector(cos(row[3] * angleUnits), sin(row[3] * angleUnits), 0);
// map CSV columns 0, 1, and 2 to a vector of X, Y, Z
const origin = vector(row[0], row[1], row[2]) * lengthUnits;
return coordSystem(origin, xAxis, Z_DIRECTION);
});
for (var i, coordSystem in coordinateSystems)
{
opMateConnector(context, id + "mateConnector" + i, {"coordSystem" : coordSystem,"owner" : qOrigin(EntityType.BODY)});
}
});
Re: Convert lb to kilo in Mass Properties
Re: Using the Spur Gears featurescript
Oh yeah, the reason why specifying the transverse module is nicer is the pitch circle diameter is traverse module * number of teeth. When you specify the gear profile using the normal module, the gear diameter changes when you change the helix angle.
dbaarda
Re: Using the Spur Gears featurescript
The term "normal module" and "transverse module" can be a bit confusing, and I think NeilCooke is actually wrong above.
The problem is with straight spur gears "normal module" and "transverse module" are the same, and are often called just "module" or "normal module".
But in a helical gear, "transverse module" is technically defined as the module as measured in the plane of gear rotation, and "normal module" is measured in the plane perpendicular to the tooth angle.
I think "normal" refers to the gear-cutting hardware size/shape, and you would use a "normal" 1.0mm module cutter to make a helix gear as you would use to make a straight gear, because you always cut in the direction of the tooth angle. But this does mean the "transverse module" depends on the helix angle for helical gears. You can (and you can get) helical gears with a transverse module of 1.0mm, but these have to be cut with a custom tool that depends on the helix angle, because the "normal module" is not actually that "normal" for those gears.
The Spur Gear featurescript works by first creating the transverse (in the plane of rotation) profile for the gear, and then extruding (for straight gears) or sweeping (for helical gears) that profile. It does not adjust the module of the transverse profile to account for the helix angle, so technically the module setting you enter in the inputs is the transverse module.
Note that the general use of "normal module" for specifying helical gears instead of "transverse module" is an artefact of how they are machined. IMHO you normally want to specify the transverse module. CAD and 3DPrinting don't have the normal machine manufacturing limitations so being able to specify the transverse module is nicer. However, if you intend to get these gears machined somewhere, you probably want to specify the normal module or you'll end up paying more.
dbaarda
Re: Is there a way to see who made a copy of someones work?
The other method is of course to sit the little darlings down. Give them a simple drawing and ask them to CAD it up infront of you, just to check…
Re: Willing but a bit clueless
Thanks again ste_wilson & MDesign for your input I'll try and take a look at the learning centre over the weekend when I've a little time and give it a go then I'll report back if that's ok. 👍
Re: Looking for Beta Testers – Try Out OnDisplay!
Dear all,
OnDisplay v0.1.5 is now live in the Onshape App store!
With your help we improved and strengthened the application a lot. We reduced its memory footprint, improved UI/UX, fixed several bugs, and cracked some tough nuts, like a misunderstanding in a particular usage of the Onshape API that caused difficulty in loading documents that included references to other documents, in some cases.
I attach an image of a wonderful locomotive created by our tester Jack based on original historical build records! Thank you Jack, this was the model we used to test and verify that we finally fixed this.
I hope you will all enjoy using OnDisplay!
Looking forward to your feeback, and please please spread the word a little bit if you can!
Thank you!
The OnDisplay team.
Re: Bending a wire mesh sheet
@MDesign is right.
Here is an example of how you can configure it with bend functionality in mind:
I also updated your pattern to convert the pitch to the closest allowed pitch, keeping the start and end wires at the ends.
Also, this is a bit of a hack, but it still exists. It's a custom feature for bending or flexing things:
https://forum.onshape.com/discussion/18615/featurescript-flex-taper-twist-deform…
