Very good video about about call program with arguments, clear and easy to understand. Thank you Adam! couldn’t wait for more advanced topics like PNS.
Great Videos Adamn. I am in the Advanced TPP programming class this week. Can you show how to use timers? I understand them in the PLC world. But I am struggling to understand them in Fanuc Programming. Thanks
Hey Sam! I just uploaded a video on Timers last week. Thanks for the recommendation, I hope it helps! ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-GnsAEnFkYz8.html
@@AdamWillea it did. Brought up another question though. Lol. If I start a timer in a program and then get called into another program. Will my original timer keep timing? Maybe make it a macro and just run it from the beginning?
@@samjanes7088 That is an AWESOME question and I should've covered it in the video! Answer: YES the original timer will keep timing even if you call other programs. It will continue timing until the TIMER[1] = STOP command is issued. Thanks for asking!
Great video Adam! Can you show us a way to always now the value of an argument in the secondary program? For exemple, if the primary program call an handshake program (secondary program) multiple times but with differents arguments each time.... How can we know the value of that argument if the program is stop in the secondary program and we can't go back to the primary program to see what was the passing argument? Thank you in advance
Great question! Off the top of my head, I'd say you should set a numerical register up; call it R[10:ArgVal] or something. Then in your subroutines, the first line of code would be: R[10:ArgVal] = AR[1] This way, whatever you passed to that program in the argument would be stored into R[10] for the remainder of that program. Now R[10] can be viewed on the TP, passed to a PLC, shown on an HMI... etc etc.
Thank you very much about your video share. I'm beginner in Fanuc robot. Can you make some basic video using roboguide. For example: teaching, programming basic, how to insert cad file into roboguide. Thank so much again, If you have any contact information, I'm so happy to be a student
In a typical application, you will not need to pass arguments to open/close a gripper in a Macro. It'd be simplest to create a new program, (set group mask to "*" and set as a macro) and inside the macro is just your I/O call. Normally looks like: 1: DO[1:GripperAdvance] = OFF 2: DO[2: GripperRetract] = ON that would "Open" your gripper. Flip the on/off in a separate macro to close. It's possible you could pass an argument and have DO[R[x]] = ON and indirectly address your code so that you can control multiple grippers using one command and an argument. It'd work, but seems a bit excessive for basic I/O.
