Using the Force feedback function.

Originally the Force measurement was available as a Function for programming purpose, but since version 1.6 Force has been build in as a Programming Object to be used for the programmer.

Force as a Function.

This example is the original Force measurement used as a Function. It is possible to set the robot for a task where a certain force (pressure) is desired. This is typical used for a polishing task.

universal-robots-zacobria-force-feedback-1

The Force is selected from the Function drop down menu when building the “If” statement.

universal-robots-zacobria-force-feedback-2
universal-robots-zacobria-force-feedback-3

The robot will move from the “In” position towards the “Out” position as long the force the tool head meet is less than 60 Newton, but if the tool head meets a force greater than 60 Newton then it will retract to the “In” position before reaching the “Out” position.

Force Function as Programming Object.

This example uses the build in Force Object which is available from version 1.6.

There are 4 different methods to use Force which is “Simple”, “Frame”, “Point” and “Motion” as described in the UR manual.

 Force Function – Example – “Simple”.

When using the “Simple” method and the Features are selected as “Tool” or “Base” the robot only considers the “Z” axis for measuring the Force. So in this case an example is constructed which moves the robot head from Up to down position and measuring the force along the way.

In this method the Robot consider the Force sensing as more important that the actual position of the tool head. Therefore the path seems random when applying a force to the tool head -and there is a risk that the Robot “gets lost” if no force is meeting – or the time to the next waypoint is set very high.

universal-robots-zacobria-force-feedback-4

In this example the robot starts at its starting position and go to the “Up” position. The Waypoint_Up and Waypoint_Down is under the Force command and therefore the Force is measured during the downwards movement.

The Force is set to 25 Newton and the Feature is set to “Tool”. The Force type is “Simple” in this example.

When the Robot meets a force of 25 Newton the Robot will maintain this force in the downward direction (“Z” direction).

When the time is up as set under the Waypoint_Down property the robot will go back to its starting position and run the cycle all over again.

universal-robots-zacobria-force-feedback-5

If the Waypoint_Down “Time” property is set very high e.g. 100 seconds – the robot will maintain the force at 25 Newton for 100 Second, but if the Object that resist the Tool head is traveling downwards – the robot can get lost because the tool head position might skip past the Waypoint_Down position and continue its downwards movement, but then eventually will stop with a Safety stop.

universal-robots-zacobria-force-feedback-6

The Robot has stopped with a Security Stop because the Tool head has past the Waypoint_Down position – and the time is still not up – so the robot will keep going downwards until it meet resistance or make a safety stop. In reality this will hardly occur because there would be an object that the robot is meeting e.g. when polishing, and therefore the robot would not be able to travel that far down wards, but it is a matter to consider.

universal-robots-zacobria-force-feedback-7

Notice the Time is set to 100 seconds.

Force feed back and Safety stop.

The UR robot is equipped with a Safety stop when the robot meets a force that is 150 Newton (approximate 15 Kg).

Since there is a safety margin the value is actually lower than 150 Newton in order to ensure that the robot complies with this ISO standard.

On the other hand the robot has a lifting capacity of 5 Kg (approximate 50 Newton) so the safety stops cannot be lower than 50 Newton. So the actual value is between 50 Newton and 150 Newton.

Disclaimer: While the Zacobria Pte. Ltd. believes that information and guidance provided is correct, parties must rely upon their skill and judgement when making use of them. Zacobria Pte. Ltd. assumes no liability for loss or damage caused by error or omission, whether such an error or omission is the result of negligence or any other cause. Where reference is made to legislation it is not to be considered as legal advice. Any and all such liability is disclaimed.

If you need specific advice (for example, medical, legal, financial or risk management), please seek a professional who is licensed or knowledgeable in that area.

Author:
By Zacobria Lars Skovsgaard
Accredited 2015-2018 Universal Robots support Centre and Forum.


Tweet

Follow @zacobria