Thanks you Sir, Appreciated your lot of efforts for making this informative videos
@COF-MM-MAINT
Жыл бұрын
Mechantronics tech here, just saved the boss $1000s of dollars watching this video so we didn't have to call anyone out. Appreicate the videos buddy!
@FutureRoboticsChannel
Жыл бұрын
That's great! I'm glad to hear that! If you are interested in training or more information how to optimize your robots, feel free to contact me at: info@f-robotics.com or visit the website at www.f-robotics.com
@wienswladimir6734
3 жыл бұрын
Thank you, very good explanation, keep it up!
@para2konrad
2 жыл бұрын
Thanks for the videos. They taught me a lot :)
@MohanLal-cx1he
3 жыл бұрын
Excellent 👌
@ATOMACH
Жыл бұрын
Awaiting your next videos
@FutureRoboticsChannel
Жыл бұрын
Thank you for supporting! and yes the new videos will be coming this year!
@krlexideegan5989
2 жыл бұрын
Can you do a video explaining when you would simulate I/O’s (in real world situation) and what needs to be checked first before the robot is simulated, if the robot stops in the middle of a cycle with a part in the grippers? I simulated the I/O the program was calling for and it crashed into another robot.
@FutureRoboticsChannel
2 жыл бұрын
It's never ok to simulate 🙂, unless you are debugging a new running cell and making modifications as you go. Of course in real live there will be situations where you need to simulate DI, but you need to be aware of why are you simulating this I/O and what are the consequences of this action. It's always better to check why you need to simulate (maybe a Part Present sensor is broken or maybe it's not on because the part is not properly held by gripper), there is always a reason for simulating and I/O and it's your responsibility to find why you need to simulate it and if you need to simulate it, if you don't know a reason why, than don't do it, that's the rule that will prevent robot from doing unexpected actions🙂
@statuswalaking5797
2 жыл бұрын
Hello sir , please make a video on how many types of fault comes in robot.
@FutureRoboticsChannel
2 жыл бұрын
I don't fully understand the question, I do have a video about robot faults already, maybe that's what you are looking for
@paulvanhulle5002
2 жыл бұрын
Quiz questions for this video 1) Using the statement mode for step mode the robot will go line by line in the current program *a) TRUE b) FALSE 2) Using the motion mode the robot will execute each motion but will not stop on logical command, it will ignore things like close gripper *a) TRUE b) FALSE 3) Using the routine the robot will step through line by line but with in the sub program the robot will execute motions only it will not stop on the logic. *a) TRUE b) FALSE 4) What type of test should be performed prior to running the program in continuous? -- a) Constant Test b) Auto Test c) Running in continuous is fine *d) Step Test 4) In STEP mode testing, to change the execution direction of the program, which hard key should you press while holding the shift key? -- a) Cursor (Arrow) Keys b) Step Key *c) FWD or BWD Keys d) +% or -% keys
@Blacksquadron
3 жыл бұрын
Great videos. What is the difference between FLAG, TEST1123 programs and UF_TO_PR, UF190? Why does Statement go inside the FLAG, TEST1123 CALLS but not UF_TO_PR, UF190 CALLS?
@FutureRoboticsChannel
3 жыл бұрын
Those two are KAREL programs. UF_TO_PR.PC and UF190.PC. You are not able to see what's inside of the KAREL program when it's loaded onto robot controller.
Пікірлер: 17