- #SIMPLE MOTION ANALYSIS SOLIDWORKS WITH BLOCKS VERIFICATION#
- #SIMPLE MOTION ANALYSIS SOLIDWORKS WITH BLOCKS SOFTWARE#
Simplexity typically engages with production component suppliers and contract manufacturing groups early in this phase to provide additional manufacturing input on the design. Phases 2B and 2C are typically the largest efforts in the product development process, where the specific implementation for all disciplines occurs (mechanical, industrial design, electrical, firmware, systems, software, manufacturing, and quality).
The detailed design phase usually has multiple, iterative sub-phases as the design progresses and representative prototypes are built.
#SIMPLE MOTION ANALYSIS SOLIDWORKS WITH BLOCKS SOFTWARE#
#SIMPLE MOTION ANALYSIS SOLIDWORKS WITH BLOCKS VERIFICATION#
All requirements are intended to be tested, and at the end of Phase 2 there will be confidence that the units will pass verification in Phase 3. Some projects also benefit from additional iterations of the product based on prior learnings through additional phases (2D, 2E, etc), which are not represented in this graphic. Phase 2C iterates on the learnings of Phase 2B and involves a refined prototype build of a fully integrated system. Please subscribe to Simplexity’s blog for future installments of this series, where I will dive further into those cases.Ĭategories: Engineering & Analysis, Mechatronics If we want to deal with more complex 3D motion analysis, though, we’ll have to reconsider using these readily available and simple equations.
See below in the “Extra Credit” section for a more detailed explanation. Applying the simple relationship to design our system yields that. Each of the gears is rotating about its center of mass.īy essentially treating this system as 2D, we’re safe to use in our analysis (this expression is ubiquitous in references like the Machinery’s Handbook, Wikipedia, and the Engineering ToolBox).For the larger gear, for example, we can say that its angular velocity is described by The angular velocity of each gear is equal to the time rate of change of just one angle.We can easily define angular information in this example:
It turns out the equations we need are quite simple. If the bottom rack is moving at mm/s, how fast is the top rack moving (assuming no loss in the gears)? Let’s assume the centers of the two gears are fixed, so that the gears are only rotating, and the top rack is moving in the x-direction. In the diagram to the above, the bottom rack is driving the two gears and another rack. I’ll demonstrate this idea with a simple gear example. It’s important for engineers of embedded motion systems to know when the simple equations are useful - and when they don’t hold water. The simple equations can be appealing, though, because they’re quick and easy. The universally applicable equations can handle multidirectional 3D rotating and translating bodies, while the simple equations can only handle translation and simple, unidirectional rotation. No doubt, the tenet also applies to 3D motion: Some kinematic and dynamic models can be appropriate in one scenario, but they can be insufficient in other scenarios.įor motion, the choice is usually one between universality and simplicity. We must be cautious about the models we choose to use. If we want to define these parameters and use them to answer our broader questions about the motion, we often enlist the help of trusted kinematic and dynamic models. – Forces and moments applied to the system.– The orientation of an object at a certain time.To help answer these broader questions, we’re interested in very specific parameters, such as: – What’s the best way to achieve the desired motion?.– How can we make the motion smoother and more elegant?.When we design motion systems, we ask things like: I’ll also walk through an example where it’s appropriate to use simplified motion equations. In the first of the three posts, I will discuss what we care about with regards to motion. In this three-part series, I delve into how we describe and model the latter term, motion, which we often take for granted as being quite simple. As embedded motion engineers, we have to know how the smart electronics get placed within the physical structure (“embedded”) and how each component moves relative to each other (“motion”). At Simplexity, part of our work is designing embedded motion systems.