Author Topic: Collision Detect response time  (Read 627 times)

0 Members and 1 Guest are viewing this topic.

Offline ticktack

  • Jr. Member
  • **
  • Thank You
  • -Given: 10
  • -Receive: 1
  • Posts: 71
Collision Detect response time
« on: January 10, 2017, 07:21:01 PM »
Does anyone know the response time in ms of a standard E series controller with collision detect turned on and used properly?

Offline Alexandru

  • Full Member
  • ***
  • Thank You
  • -Given: 1
  • -Receive: 7
  • Posts: 103
Re: Collision Detect response time
« Reply #1 on: January 11, 2017, 06:32:44 AM »
In collision detection, the current motor current is monitored, and when the peak current exceeds the set threshold, the robot considers it has collided.


In shock detection, changes in the motor current per unit time are monitored, and when the amount of change exceeds the set threshold, the robot considers it has collided.    This function detects collision faster than the collision detection described above, and is efficient in lessening the damage given to the robot or tool.   

Offline kwakisaki

  • Global Moderator
  • Sr. Member
  • *****
  • Thank You
  • -Given: 19
  • -Receive: 69
  • Posts: 446
Re: Collision Detect response time
« Reply #2 on: January 15, 2017, 07:02:10 PM »
You would have to contact a distributor for that kind of information in terms of response time from the CPU as collision and shock detection uses different characteristics.
- Collision detection is based on peak current detection in relation to threshold settings - upto 500%.
- Shock detection is based on current/time and is much quicker than collision detection - upto 200%/ms.

Correct Tool Load (WEIGHT) and speeds will create various results due to change in inertia/momentum.