[landslide1]

I'm trying to pass variables from one macro to a sub macro to remove repetitive code and simplify programing. trouble is the sub-program is wiping the variables when it returns to the main program with M99.

I only have variables #100 to #131 and variables #500 to #531. I'd like to have the 100 series variables stay resident in the sub-macro and when the sub-program ends avoiding the need to save essential variables in the #500-531 range

I tried parameter (0m-a) 40#6 but it didn't seem to have an effect. my previous parameter 40 was 00000000 and changed to 01000000.

found a problem with the macro that caused the issue. now works as I intended.
solved the problem by inserting optional stops M00 to help debug.

[angelw]

I'm trying to pass variables from one macro to a sub macro to remove repetitive code and simplify programing. trouble is the sub-program is wiping the variables when it returns to the main program with M99.

I only have variables #100 to #131 and variables #500 to #531. I'd like to have the 100 series variables stay resident in the sub-macro and when the sub-program ends avoiding the need to save essential variables in the #500-531 range

I tried parameter (0m-a) 40#6 but it didn't seem to have an effect. my previous parameter 40 was 00000000 and changed to 01000000.

found a problem with the macro that caused the issue. now works as I intended.
solved the problem by inserting optional stops M00 to help debug.

Unless you're using the M00 to stop the run of the Macro program in a specific spot, setting parameter 0011.5 to "1" (assuming a Series 0 control) will cause the program to stop after each Macro Statement block when in Single Block Mode. This can also be achieved without setting this parameter bit by including an EOB after each Macro Statement block. Being able to execute the Macro Program in Single Block is a useful debugging tool.


Regards,

Bill

[landslide1]

thanks for the tip. being able to step through will make debugging much easier!