Hello Peter

Thanks for spending time running a test on the current problem that I am having.

Thanks
Renato

Renato, I apreciate it. The test was easy and just a few minutes. It sounds still unlogical that RFH turns your device off, because the first M71 in RFH is executed isolated.

(Please be aware that RFH seems only preparatory, and after that two RUN are required. The prompts are written  in the message windows. The line for RFH is selected with the arrow keys, not by clicking with the mouse on the line. Did you take all  this into account?)

renato wrote:
Macro M71 turns on a Solinoid Pneumatic Valve and its turning on and OFF during the run of RFH.

Peter writes:
this seems correct behaviour, as there are in fact several M71 and M70 above the RFH line.
RFH seems preparatory. After RFH, one has to start the program using RUN twice. First RUN is again preparatory, second RUN actually starts from the line.

Actually should maybe clarify what I said above,  Custom User macros should be over m100. It is quite OK to have custom versions of standard m-codes such as tool change (M6), Coolant(m7,m8,m9) etc.
Hood

From the Mach3 customization Wiki, chapter 2:
Mach3 macros. As already mentioned, a macro is a piece of VB Script. Each macro has a name like M134. The M is used at the start of every macro name and the number can be any integral value up to 99999 that is not used to define a built-in M-code. These built-in numbers are listed in chapter 11. Thus for example, M12, M50, M16543 are all valid macro names; while M3, M-56, M0234, M567.4 are not valid names. Standard macros will use the number range up to M999, Original Equipment Manufacturers (OEMs) are advised to use M1000 to M89999 and end-users can avoid naming conflicts by using M90000 to M99999.

edited for readability.

Every day is a school day

Hood

Renato:
The other similar command, Set Next Line, lets abbreviate it as SNL, doesn't preparatory scans. But it wouldn't do either other preparatory state changes (G20/G21 and more, see any documentation on G Code for the modal states)

Hood has been right in one of his earlier posts on page 2 of this thread:
The checkbox, Ignore M Calls While Loading in the third column of Config->General Config, inhibits Macros only when Loading G Code. It does not inhibit macros during RFH.  Hood also mentioned SNL in that earlier post.
(http://www.machsupport.com/forum/index.php/topic,14579.msg101852.html#msg101852)

Hi Peter, Hood.

Sorry for the late reply. We were busy the whole week moving to a new Factory. Anyway I have tried SNL which Hood and you suggested. I have notice that the feedrate is not taken into account when running SNL.

Thanks
Renato

I dont use the Set Next Line but I would have thought the feedrate should be taken into account as long as it is on or after the line you are starting from. Possibly your code is written with the feedrate only at the beginning of code? If that is the case then have you tried entering the feedrate into the DRO before you do the SNL?
Hood

Hello Hood,

That might be the case.  Anyway thank you very much for your support

Thanks
Renato