Newbie with a bit of a dumb question. I have an M900iA that is tending 4 machines and two conveyors. I am creating a main program that infinite loops until program stop pb is pressed. Inside this program I have IF statements that tell the robot (for example) IF the infeed conveyor has a part on it AND IF one of the machines DI goes true (ready signal), move the object from the infeed conveyor to this machine. Currently I am writing a program for each possible scenario of movement and then CALL'ing the individual program. My question is, when would I create a program and when should I just write a macro? I guess I don't really have a clear understanding of the difference between the two in RoboGuide-HandlingPro, and when it's appropriate to use which one and the benefit of using one over the other. I told you it was a dumb question.
Macro or program
-
ceilingwalker -
June 20, 2023 at 3:07 PM -
Thread is Unresolved
-
-
SkyeFire
June 20, 2023 at 3:09 PM Approved the thread. -
Thread
Macros for the complete amateur
So, having done some TP and KAREL coding, I have a general sort of question about Macros. Basically... why? I mean, what do Macros have that regular TP programs don't? Are they just a leftover from a bygone age, or do they still have real advantages that make them worth using?
To start on answering my own question, I can see that Macros can be called (asynchronously?) from a DI, or triggered to execute as a Manual Function. And a Macro can be CALLed from inside a TP program just like another…SkyeFireJune 16, 2023 at 7:11 PM -
I would use a regular program in your situation.
Also I would add a wait statement inside your infinite loop, waiting on a part to be ready or cycle stop pressed. That way you can see the code stopped on that line when waiting instead of just whizzing though the main program.
-
I would use a regular program in your situation.
Also I would add a wait statement inside your infinite loop, waiting on a part to be ready or cycle stop pressed. That way you can see the code stopped on that line when waiting instead of just whizzing though the main program.
Yes Sir, I did place a wait in it already so the robot doesn't rapid to its next location the moment it completes one.