Macrojob, What are?

Any job could be a macro job. It is a form of edit protection. Lower security levels cannot create or modify a macro job. They are typically used with some type of calculations. Instructions the programmer does not want anyone to mess with.

That macro job looks like a canned job from Yaskawa. Yaskawa has created a macro job that will fit many scenarios. That is a reason the CNVRT is in Base Frame. They (Yaskawa) don't know if the robot is mounted on a base track or is stationary on the floor or riser. Using BF fits those two scenarios. If your robot is not on a base track those instructions could be changed to robot frame (RF).

Quote from Roger Alexander Moresco

Thanks man!

I was reading, for the works of touchsense, already have some macro jobs, how can I get them?

Call your local Yaskawa office.

Quote from Roger Alexander Moresco

And in the touchsense programming part, do you know where to start?

You could download the manual from Motoman.com

The way I think about a MACRO job is, It is a job used as an instruction. One that I have used frequently is a job called Handshake. In a cell that has multiple robots, I set the arguments for which robots are working in close proximity while allowing the others to continue.
I also use one called CLAMPS to fire outputs for clamps, the argument sets which clamps should be opened or closed....

Quote from tony gast

The way I think about a MACRO job is, It is a job used as an instruction. One that I have used frequently is a job called Handshake. In a cell that has multiple robots, I set the arguments for which robots are working in close proximity while allowing the others to continue.
I also use one called CLAMPS to fire outputs for clamps, the argument sets which clamps should be opened or closed....

What is the difference with just calling a normal job with arguments? Other than offering the extra code protection noted by 95devils.

No call instruction...You can disguise them... and can be found in the inform list. That's about it