Simulations of clock motion works, Possible limit of pivots in mech files?
Posted: Fri Jan 25, 2019 3:33 pm
Art
I'm continuing my experiments with the Auggie Vector Processor. I decided to take an example of a clock's motion works model that I developed a couple of years ago and recreate it using the Vector Processor.
For non-clock folks motion works are a set of gears that provide a 12:1 reduction between co-axial input/output shafts. Tower clocks use such a mechanism to take the shaft that drives the minute hand and reduce the rotation to power an hour hand.
Attached are two VCP files:
The first file MotionWorks-Stationary.vcp shows gear set and hands with the pivots attached to the background. I created a mech file to serve as the starting point for the moving version.
The second file MotionWorks-Moving.vcp imports the above mech file and attaches it to a movable platform that crawls along a long rack. All the gears and clock hands from the above mech file had to be detached from the background and then reattached to a movable platform using the pivot feature of the vector processor (this is a total of six pivots). A pinion/rack set attaches via two more pivots to the movable platform the left pinion has a motor attached to drive the entire assembly to the right along the rack.
The third file is a zip file of the mech files that supported the development of the above two simulation models.
My goal is to develop sets of mech files of components that have been tested and working. Multiple mech can be then imported to serve as the basis of more complex simulated mechanisms.
Possible bug?::
I'm not sure if this is a bug or feature of mech files.
The mech file MotionWorks-Moving-error.mech did not save any of the pivots that make the model work.
I did try importing your "foot-walker" mech file and placed it above a static floor. The pivots in your foot-walker model were preserved and the foot-walker model worked as expected. Perhaps the complexity of my moving model exceeded the capabilities of the program that creates the mech files.
I am quite impressed with the physics behind the vector processor and do plan to continue exploring its features. I will continue to stretch the limits of the program.
Bill Michael
I'm continuing my experiments with the Auggie Vector Processor. I decided to take an example of a clock's motion works model that I developed a couple of years ago and recreate it using the Vector Processor.
For non-clock folks motion works are a set of gears that provide a 12:1 reduction between co-axial input/output shafts. Tower clocks use such a mechanism to take the shaft that drives the minute hand and reduce the rotation to power an hour hand.
Attached are two VCP files:
The first file MotionWorks-Stationary.vcp shows gear set and hands with the pivots attached to the background. I created a mech file to serve as the starting point for the moving version.
The second file MotionWorks-Moving.vcp imports the above mech file and attaches it to a movable platform that crawls along a long rack. All the gears and clock hands from the above mech file had to be detached from the background and then reattached to a movable platform using the pivot feature of the vector processor (this is a total of six pivots). A pinion/rack set attaches via two more pivots to the movable platform the left pinion has a motor attached to drive the entire assembly to the right along the rack.
The third file is a zip file of the mech files that supported the development of the above two simulation models.
My goal is to develop sets of mech files of components that have been tested and working. Multiple mech can be then imported to serve as the basis of more complex simulated mechanisms.
Possible bug?::
I'm not sure if this is a bug or feature of mech files.
The mech file MotionWorks-Moving-error.mech did not save any of the pivots that make the model work.
I did try importing your "foot-walker" mech file and placed it above a static floor. The pivots in your foot-walker model were preserved and the foot-walker model worked as expected. Perhaps the complexity of my moving model exceeded the capabilities of the program that creates the mech files.
I am quite impressed with the physics behind the vector processor and do plan to continue exploring its features. I will continue to stretch the limits of the program.
Bill Michael