DX100 - Collision Detect (Code 4315)

Summary

The video demonstrates the setup and implementation of the collision detection feature for the DX 100 controller, designed to safeguard the manipulator from unexpected collisions. Initially, the robot's collision detection is shown ineffective, with the robot not stopping during a crash. The tutorial then guides viewers through adjusting the maximum disturbance levels to activate the feature, ensuring the robot stops upon collision. After repairing damage and resetting the system, the video concludes with a successful demonstration of the collision detection in action.

Takeaways

• 🛠️ The script discusses the setup and implementation of collision detection for the DX 100 controller, which is crucial for protecting the manipulator from unexpected collisions.
• 🔍 Collision detection does not include tool or tool tip sensors; additional sensors are required for comprehensive protection.
• 📊 The script demonstrates the operation of the robot with factory-delivered collision detection settings, where valid values range from one to five hundred.
• 🚫 A mock-up scenario shows that the robot did not stop upon a collision, indicating the need to adjust the settings.
• 🔎 The 'maximum disturbers detected' can be found under the 'robot shock twister level', and it's necessary to be in 'management security' to access this feature.
• 🔑 The script highlights the importance of selecting a number smaller than the detected maximum (e.g., choosing 30 instead of 52) to ensure the collision detection engages.
• 🔧 After repairing any damage and adjusting the settings, the script shows a demonstration with the collision detection feature expected to be fully active.
• 💡 The script instructs on how to reset the alarm and move the machine out of a collision condition by using the 'teach reset' and 'job' functions.
• 🛑 The robot's shock sensor level can be adjusted by selecting any field and changing the feature to 'invalid', which stops the machine's operation.
• ✅ Once the machine is moved out of the collision area, the script emphasizes resetting the condition back to 'valid' to conclude the demonstration.

Q & A

What is the primary purpose of the collision detect feature in the DX 100 controller?

The primary purpose of the collision detect feature is to protect the manipulator in the event of an unexpected collision.

Does the collision detect feature include protection for the tool or tool attachment?

No, the collision detect feature does not include protection for the tool or tool attachment; a separate sensor would be required for that.

What is the range of valid values for the collision detect settings on the DX 100 controller?

The valid values for the collision detect settings on the DX 100 controller range between one and five hundred.

What is the significance of the 'maximum disturbers detected' value in the collision detect feature?

The 'maximum disturbers detected' value indicates the level of disturbance or shock that the robot can tolerate before the collision detect feature engages to protect the manipulator.

How can one access the 'robot shock twister level' setting on the DX 100 controller?

To access the 'robot shock twister level' setting, one must be in management security mode for the button to appear, and then it can be adjusted accordingly.

What action was taken in the demo when the robot did not stop during the first attempt?

When the robot did not stop during the first attempt, the maximum disturbers detected value was checked and adjusted to a number smaller than the largest number in the field to ensure the collision detect would engage on the next try.

What is the procedure to reset the robot after a collision has been detected?

To reset the robot after a collision has been detected, one should perform a teach reset to clear the alarm, job the machine off, and then change the feature to invalid for any field, allowing the machine to move out of the collision condition.

Why is it important to reset the condition back to valid after moving the machine out of the collision condition?

It is important to reset the condition back to valid after moving the machine out of the collision condition to ensure that the collision detect feature remains active and functional for future operations.

What is the role of the 'teach mode' in the collision detect feature demonstration?

In the collision detect feature demonstration, 'teach mode' is used to safely operate and adjust the robot's settings without performing actual tasks, allowing for adjustments such as the maximum disturbers detected value.

How does the collision detect feature protect the robot during operation?

The collision detect feature protects the robot by detecting unexpected collisions and stopping the robot's operation when the disturbance exceeds the set threshold, thus preventing damage to the manipulator.

Outlines

00:00

🤖 Collision Detection Setup for DX 100 Controller

This paragraph introduces the setup and implementation of the collision detection feature for the DX 100 controller. The feature is designed to protect the manipulator from unexpected collisions. It's noted that the feature does not include tool or tool offset sensors. The script outlines a demonstration of the machine's operation with the collision detection settings set at the factory default, with valid values ranging from one to five hundred. The demo shows that the robot did not stop during a mock collision, indicating the need to adjust the settings. The maximum disturbers detected are examined, and it's found that the largest value is 52. The decision is made to set the level to 30 to ensure the collision detection will engage. The paragraph concludes with a demonstration of the robot's motion with the adjusted collision detection settings, showing that the robot now stops as expected during a collision.

Keywords

💡Tech Support

Tech Support refers to the assistance provided by technical experts to users of technology products or services. In the context of the video, Tech Support is likely the team or department responsible for helping users set up and implement features like collision detection for the DX 100 controller. The video's theme revolves around demonstrating how to use these features effectively.

💡Collision Detect

Collision Detect is a safety feature designed to protect machinery, such as manipulators or robots, from damage due to unexpected collisions. It is a crucial component in industrial automation, ensuring that operations can be halted in response to physical impacts that could otherwise cause significant damage. In the video, the setup and implementation of this feature on the DX 100 controller are discussed, highlighting its importance in maintaining the integrity of the equipment.

💡DX 100 Controller

The DX 100 Controller is a specific model of a control system for industrial robots or manipulators. It likely includes advanced features like collision detection to enhance the safety and efficiency of the machines it controls. The video focuses on this controller, demonstrating how to configure its collision detection settings, which is a key aspect of its operation and safety protocols.

💡Manipulator

A manipulator, in the context of the video, refers to a mechanical arm or robotic device used in industrial settings for handling materials, assembly, or other tasks. The collision detect feature is designed to protect the manipulator from damage in the event of a collision, which is a significant concern in automated manufacturing environments where precision and safety are paramount.

💡Tool or Tool A Shot Sensor

A tool or tool A shot sensor is a type of sensor used in industrial automation to detect impacts or collisions involving the tooling or end effectors of a robot. While the collision detect feature does not include these sensors, they are mentioned to highlight the broader range of safety measures that can be implemented. The video script suggests that additional sensors might be required for comprehensive collision detection that includes tooling.

💡Maximum Disturbers

Maximum disturbers likely refer to the threshold settings within the collision detection system that define the level of force or impact that will trigger a safety response. In the video, adjusting these settings is part of the setup process to ensure the system is sensitive enough to protect the manipulator. The script mentions looking at the 'maximum disturbers detected' and adjusting them to ensure the system engages correctly.

💡Robot Shock Twister Level

The Robot Shock Twister Level is a setting or parameter within the DX 100 controller that relates to the sensitivity or response level of the collision detection system. It is used to configure how the system reacts to disturbances or impacts. The video script describes checking and adjusting this level to ensure the system is set up correctly and can protect the robot from collisions.

💡Management Security

Management Security likely refers to a mode or setting within the DX 100 controller that allows for the configuration and management of sensitive system parameters, such as collision detection settings. It is a security measure to prevent unauthorized changes to critical system settings. The video mentions being in 'management security' to access certain features, indicating its importance in the setup process.

💡Teach Mode

Teach Mode is a common feature in industrial robot controllers that allows operators to manually guide the robot through its motions, teaching it the desired path or sequence of actions. In the video, the script mentions the robot being in 'teach mode', which is a context where adjustments to the collision detection settings would typically be made.

💡Teach Reset

A Teach Reset is an action performed on a robot controller to clear an alarm or error state, allowing the system to return to a normal operating condition. In the video, after a collision is simulated, a teach reset is mentioned as one of the steps to clear the alarm and reset the system, highlighting the importance of this procedure in troubleshooting and maintaining the robot.

💡Expected Fault

An expected fault in the context of the video likely refers to a predetermined response or outcome when a collision is detected. It is part of the system's design to ensure that the robot responds appropriately to a collision. The video script mentions generating an 'expected fault', which is a way of testing whether the collision detection system is functioning as intended.

Highlights

Introduction to the setup and implementation of collision detection for the DX 100 controller.

Collision detection is designed to protect the manipulator from unexpected collisions.

The feature does not include tool or tool offset sensor requirements.

Demonstration of the robot's operation with factory-delivered collision detection settings.

Valid collision detection values range between one and five hundred.

Observation that the robot did not stop during a mock crash.

Inspection of maximum disturbers detected under the robot shock twister level.

Necessity to be in management security for accessing certain settings.

Identification of the largest number in the field, which is 52.

Selection of a number smaller than 52 (30) to ensure collision detection engagement.

Repair of the robot and adjustment of the max BTEC level.

Demonstration of the same motion with collision detection expected to be fully active.

Procedure for resetting the alarm and moving the machine off the collision.

Instructions on how to change the feature to invalid and move the machine out of the collision condition.

Emphasis on resetting the condition back to valid after moving the machine out of the collision.

Conclusion of the demonstration for the DX 100 controller's collision detection.

Transcripts

hello I'm runnin from tech support and

today we're gonna discuss the setup and

implementation of the collision detect

seizures for the DX 100 controller the

collision detect feature is designed to

protect the manipulator in the event of

an unexpected collision it does not

include your tool or your tool a shot

sensor would be required for that first

part of the demo we will demonstrate the

operation of the machine has delivered

from the factory with the collision

detect settings and 100 with valid

values being between one and five

hundred this example demo is just a

mock-up of typically what could happen

so let's we see the robot did not stop

so half of the crash one thing we can do

is look at the maximum disturbers

detected and that would be found under a

robot shock twister level and we do have

to be in management security for this

particular button to appear and right

now she's showing the teach mode which

detected maximus turbine 452 but I will

look at the other levels and all the

other files shows a similar set for

Pilate in da

deshaun the largest number in the field

is a 52 so I'm going to select a number

smaller than 52 and I like 30 for this

one so that we can ensure on our next

try that the collision detect will

engage and protect my robot if not

mainly the robot all right we have now

repaired the damage and changed our max

BTEC level and we're now going to

demonstrate the same motion with what we

hope collision detect fully active the

generation of the expected fault all

right so at this point the first thing

we would try is called a teach reset the

alarm and we would want to job the

Machine off of here

in this condition we would go to robot

and shock sensor level and we can pick

any field even though we see in this

example when field number 5 by pressing

select he can change feature to invalid

and in this condition she is not running

and we can then move the machine out of

the collision again condition and

remembering that once we've gotten her

out of the arms way

to reset the condition back to valid and

that would conclude today's

demonstration of collision detect for

the DX 100 control

you