I have the following code in a macro called "Start" which runs perfectly fine when I run it on its own. Basically, I just want the printer to pause at a certain location and wait for an external signal to resume.

G1 Y96 X68 F3000
G1 Z5 F500
M581 E5 S1 T2 ;Start the trigger (trigger2 file)
M25 ;Pause and wait for a switch to be pressed to resume
M581 E5 S-1 T2 ;Turn off the trigger

I want to run this macro from a GCode file using this command: "M98 P/Macros/Start". The issue is that all other commands in the Start macro run just fine except for the trigger portion. The trigger doesn't work this way. I have to put the trigger commands inside the GCode file to run them.

This is important for me because I have different machines and the setting is slightly different for each one. I want to have the same line (M98 P/Macros/Start) in all the gcodes and don't deal with creating a new GCode file for each machine.

Is there a way around this?

David, I sent the file to your email.

I uploaded the gcode to the board through the web interface and just clicked on it and started it.

I found an interesting/annoying bug here! I slice my STL models and save each layer into a different gcode file. When I reach the file that has "layer122.gode" in the name this error happens. It seems for some reason the software confuses those layers with M122 command. When I change the file name it solves the issue!

Duet Ethernet: DuetEthernetFirmware-1.19 and DuetWebControl-1.19

No, it doesn't. I reset the board and it didn't help. Also, I upgraded to the newest firmware after I saw that issue, and it's still not solved.

Yes, I'm using the web interface for sending the gcodes. I'm using a separate laptop just for running this machine and I don't remember ever sending the M122 command before.

Hi, I'm using duet ethernet with the latest stable firmware and web interface versions. The problem is whenever I send a GCode to the machine, no matter what the commands are, it just returns a diagnostics message starting with "====Diagnostics===" as if I have sent M122. All the commands in macros work, however. If I copy the same gcode to a macro it works. Does anyone know what is going on?

Works perfectly, Thanks.

I don't have an M563 tool definition command. I put M140 H-1 on top of my config.g, still didn't work.