Hello, Thank you for the video ! I will like to add a little remark on this subject: When you create TP program. You must specify which group mask the instruction will affect. Even if it is only logic I did MACRO with only COL GUARD ADJUST and did not specify group mask and result in error. Keep this small detail in mind ;) Thank you
Can you please make a video about brief introduction about Fanuc robot controller and components of controller like 24 V relay 0 V Relay And How to set up DI and DO Also thanking to you for making great videos it help me too much to understand
Check out videos that I already have for FANUC components: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-oy3bkwMXEZQ.html ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-vFcrZu5L65U.html DI/DO video is coming, don't forget to subscribe and click on the bell icon, so you will get latest updates about new videos :-)
I have a robot 2000ia/210f and i have mastering to 0 and when i move with its teach pendant i have the collision detected even when i disable the collision guard and with a low speed (10%) could you tell me what do you think that is?
Hello. the robot takes parts from the table. there is R100 - 180 on the table. the robot has not arrived yet and has started reading points from the table. did not reach the table and collision occurs
@@Zdravko86100 that statement is correct for every point that does not use FINE, only FINE movement will execute the logic AFTER the point is reached, all CNT will execute the logic before robot will reach the programmed point
I've had an issue where we used LR-MAte to snap 2small plastic part into another bigger part. Collision guard setting above 50% gave a lot of collision guard faults during normal snapping, so I've had to lower it between 30 and 40%. I could never figure out if that's a "normal" collision guard setting to use for this kind of application (interference snap part assembly), we have issues with plastic geometry variance (parts interering slightly more sometimes), pos variance of fixtures part, too fast a speed of tool during assembly, or something else going on.
Interesting case @Stanislav Sheyn, I did work with plastic snapping but on ABB robots, however I did not experienced issues. How was your payload setup ? That might have been a root cause, going down to 30% is A LOT, however it's a LR-Mate robot, so not too much of a payload. If the payload was set correctly than I would assume that you had wrong robot for the application (not enough payload), keep in mind that robot application is part of the robot process and the payload might be critical for it, as a good example you can take a look at roller hemming, the tool weights "few" kg so you could use LR-Mate, but the force required to make the process is much greater, that's why you want to use at least 165kg payload robot, so you can achieve the force required to form the metal. For your case if the payload was set correctly and you are running at 30% at collision guard your gears / motors will wear out extremely fast. You could've taken a look at disabling collision guard for those few points. Message for all of you guys: Robot programming is much more than just touching up the points, the moment when you start understanding robotic applications is when the fun starts :-)
@@FutureRoboticsChannel Duly noted with Payload (I'll check schedule). Wrt to disabling collision detect for that point of snap assembly - that's exactly when you want to have it on. The purpose is to basically ensure you are not ramming one plastic part into another damaging product if something doesn't line up or there is the part underneath the base part offsetting height. Can probably retrofit additional sensor to not have to rely on Collision Guard to do that function but a lot more work and engineering.
Check if you have the option installed: MENU -> NEXT -> STATUS -> VERSION ID -> F3 (CONFIG) and see if you can find those options: R534 - Collision Guard J684 - Collision Guard Pack
Do you know of a way to see what the current feedback on a servo motor is? Basically I want to monitor what the current collision detection value actually is while trying to set it up.
Sometimes robot working as per program that time collision detect alarm will come ..if payload is set correctly also alarm coming then what is the reason sir?
If there is no physical collision usually one of 2 things might happen: - wrong payload definition - too aggressive movement 1. Check your payload 2. Check your program and it's movements, maybe you should slow the robot down in the point that collision occurs. I would suggest to run the robot slower in the point where the robot is triggering collision and see if the collision will happen on a slower speeds. Than speed up the robot by 5/10% and see when you will see collision. Temporary you can modify the speed in this point to whatever percentage was working without the collision (eg. 50%) As a long time solution you would need to modify the movement so it will be smoother for the robot than you can bring your speed back to a 100%
I work with a LR200id robot that does not have a collision guard, how would the procedure be to add it ?; I also work with other identical ones that if they have it, is it possible to obtain the data package of one of them?
ok, I understand, the two robots were bought from the same seller and the only difference is that one did not come with collision guard; both have the same program and perform the same function; Could it be possible to load the image of the robot with collision guard in the other one that does not have it? Would it have any protection that does not allow it to be carried out? otherwise I must make the claim to the seller; Thanks for the help and for spreading the knowledge.
