Directional Conflict in Motor
Hi everyone,
I'm using Inspire Motion to simulate the motion of a robot arm. Part 1 (yellow) connects to the ground part, and controlled by the motor 1. Part 2 (red) connects to the part 1 and controlled by the motor 2. Each motor has its own function. When I run the analysis, Inspire give me a warning (shown below). I've tried to activative Restrain Centerline (motor 2) but the result is unrealistic. I also increase the Deformation Allowed.
What should i do in this case?
Thanks all for spending your valuable time!
Best Answer
-
Hello,
There is a good chance you defined the motor between one arm and ground instead of between the two arms. When defining the motor, the first click defines the shaft part, the second defines the base part. For example, if you just click twice on the arm, it will attach the motor to that part and ground. Make sure your second selection is on the second part. Then make sure Restrain Centerline option (via the Property Editor) is turned on (Revolute).
Tip: A good debug technique in these situations can be to turn off the sensor and let the simulation proceed with the error, so that the problem may become (visibly) obvious. Go to Motion Run Settings --> Advanced --> Model Checking, and change Runtime Sensors to None. Then solve the analysis. Many times, you can physically see what's happening, like the parts separating, and it can become apparent where you might have to start looking to debug.
Hope this helps.
Scott Z
1
Answers
-
Hi Lam,
Please redefine the motor.
Please select base and a base. It has to be different.
Best regards.
1 -
Hello,
There is a good chance you defined the motor between one arm and ground instead of between the two arms. When defining the motor, the first click defines the shaft part, the second defines the base part. For example, if you just click twice on the arm, it will attach the motor to that part and ground. Make sure your second selection is on the second part. Then make sure Restrain Centerline option (via the Property Editor) is turned on (Revolute).
Tip: A good debug technique in these situations can be to turn off the sensor and let the simulation proceed with the error, so that the problem may become (visibly) obvious. Go to Motion Run Settings --> Advanced --> Model Checking, and change Runtime Sensors to None. Then solve the analysis. Many times, you can physically see what's happening, like the parts separating, and it can become apparent where you might have to start looking to debug.
Hope this helps.
Scott Z
1