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.
Cuved Part and Flat Part as same Part Name/Part Number?
We have a custom flexible tapelight that is cut to length in 50mm increments and used on numerous products. Currently, I have a part studio which has a configuration variable for the radius of the curved surface to which the tape will be applied to. The tape model is created using a sketch which has a formula for the included angle of the part based on the radius entered (the height and thickness of the tape are constant, no matter what the radius is). Basically, the arc length of the tape needs to be 50mm, so I came up with a formula which ensures the arc length is always 50, no matter what radius is entered.
My question has to do with using this same part on a FLAT surface. I created a configuration list which has "flat" and "curved" as the options. But by doing this, the resulting parts are treated as (2) separate parts. There are instances where we use "x" number of curved pieces, and "y" number of flat pieces in the same assembly. Because of how I have set these up, the BOM for these assemblies show (2) different line items (one for the # of curved pieces, one for the # of flat pieces). Ideally, we want to know the TOTAL number of 50mm pieces used, regardless of whether they are flat or curved. We are struggling to come up with a way to include the flat surface configuration into the curved surface configuration. Essentially, the radius for the flat surface config should be "infinity" in order to get the result we are after.
Has anyone had a scenario similar to this? Or does anyone have any ideas on how to accomplish what we are trying to do?
This may be outside of Onshape's capabilities at this point, but I figured it was worth a shot to see if anyone had any ideas to help.
Have at it...