Gcode meta commands

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Gcode meta commands

Syntax Highlighter for RepRap Gcode
• garethky

1

4
Votes

1
Posts

34
Views

No one has replied
Conditional G Code introduction "tutorial" (PDF)
• OwenD

3

7
Votes

3
Posts

195
Views

@droftarts Feel free I can send the text and images tomorrow if it helps.
Conditional GCode and object model variables
• dc42

64

5
Votes

64
Posts

1242
Views

I think this thread might be the right location for this I guess because it's something I would need Since I upgraded my Prusa MK3s to a Duet 2 WiFi board I try to enable all the features the Prusa original FW had. This means: automatic loading of filament when there is no filament in the extruder PINDA temperature compensation table because the probe Z offset differs depending on the temperature. In my experience this is not linear and the higher the temperature the lower Z = 0 becomes meaning if you calibrate your printer with PLA, ABS will need recalibration as the nozzle will be too low. My target is to create a config package for others so they can 1:1 swap their board and don't need to tweak much as my config uses all the convenient features, like the filament sensor, with explanation of what needs to change in the config depending of the used extruder or stepper motors (e.g. 0.9/1.8 degree). 1. Feature to load the filament automatically. Status: no filament in the extruder, extruder has PLA temperature (210°C) Behaviour: Putting filament in the extruder triggers the filament sensor which then automatically loads filament. Problem I had: The firmware only allows me to operate the filament sensor in one direction because the pin is blocked/reserved. Meaning I could only enable auto load or run out detection at once. So I had to split it in two over macros and start gcode. So here is my (over complicated?) solution right now: config.g ; Filament Sensor Port and Loading Feature ON M950 J1 C"e0stop" ; Input 1 e0 Filament Sensor M581 P1 T2 S0 R0 ; Filament Sensor P1 triggers Trigger2.g always (R0) Runout is not working right now. So when the printer is starting up and there is no filament and filament is put into the extruder trigger2.g is called: trigger2.g: ; Loading Filament Script M300 S800 P200 M581 P1 T2 S-1 R0 ; Filament Sensor does not listen anymore (S-1). Autoload is disabled. M291 P"Please wait while the nozzle is being heated up" R"Loading PLA" T5 ; Display message T0 ; Activate Hotend M291 P"Feeding filament Trigger2" R"Loading PLA" T5 ; Display new message G1 E70 F800 ; Feed 70mm of filament at 800mm/min G1 E55 F300 ; Feed 50mm of filament at 300mm/min G4 P1000 ; Wait one second G1 E-5 F800 ; Retract 3mm of filament at 800mm/min M400 ; Wait for moves to complete M292 ; Hide the message G10 S150 ; Set current tool temperature to 150C ;G10 S0 ; Turn off the heater again ; Filament Sensor Port and Runout Feature ON M581 P1 T2 S-1 R0 ; Filaent Sensor does not listen anymore (S-1). Autoload is disabled. M950 J1 C"nil" ; Input 1 e0 Filament Sensor M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor After the loading script the sensor is put into mode "runout detection ON" But what if you turn your printer on and filament is already loaded and you directly start your print? This would mean that there is no runout detection enabled. My solution right now is putting this into the Start GCODE in the slicer software: ; Prime Filament Sensor for Runout M581 P1 T2 S-1 R0 ; Filament Sensor P1 triggers Trigger2.g always (R0) TRIGGER OFF M950 J1 C"nil" ; Input 1 e0 Filament Sensor M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor And there is a third scenario. What if you want to manually change your your color (filament) mid print? After unloading the filament the sensor needs to be in mode "autoload" and after the autoloading is complete it has to go back to the mode "runout detection". So i added this to my filament-change.g macro: M25 G91 ; Relative Positioning G1 Z20 F360; Raise Z G90 ; Absolute Values G1 X200 Y0 F6000 ; Parking Position M300 S800 P8000 ; play beep sound M98 Pejectfilament.g M400 Called Pejectfilament.g: M591 D0 P0 C"e0stop" S1 ; Filament Runout Sensor M950 J1 C"nil" M291 P"Please wait while the nozzle is being heated up" R"Unloading PLA" T5 ; Display message T0 ; Activate Hotend M109 S210 M291 P"Retracting filament..." R"Unloading PLA" T5 ; Display another message G1 E+8 F300 ; Extrude 8mm of filament at 300mm/min G1 E-45 F800 ; Retract 480mm of filament at 800mm/min G1 E-15 F900 ; Retract 480mm of filament at 900mm/min G1 E-25 F900 ; Retract 480mm of filament at 900mm/min M400 ; Wait for the moves to finish M292 ; Hide the message again M300 S800 P200 ; Filament Sensor gets ready for next load M950 J1 C"e0stop" ; Input 1 e0 Filament Sensor M581 P1 T3 S0 R0 ; Filament Sensor P1 triggers Trigger3.g At the end trigger3.g: M300 S800 P200 M581 P1 T2 S-1 R0 ; Filaent Sensor does not listen anymore (S-1). Autoload is disabled. M291 P"Please wait while the nozzle is being heated up" R"Loading PLA" T5 ; Display message T0 ; Activate Hotend M291 P"Feeding filament Trigger3" R"Loading PLA" T5 ; Display new message G1 E70 F800 ; Feed 70mm of filament at 800mm/min G1 E55 F300 ; Feed 50mm of filament at 300mm/min G4 P1000 ; Wait one second G1 E-1 F800 ; Retract 1mm of filament at 800mm/min M400 ; Wait for moves to complete M292 ; Hide the message ; Filament Sensor Port and Runout Feature ON M581 P1 T2 S-1 R0 ; Filaent Sensor does not listen anymore (S-1). Autoload is disabled. M950 J1 C"nil" ; Input 1 e0 Filament Sensor M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor I know it first seems quite complex but when runout is enabled the port is blocked and can't be used for autoload. Now I've read about the implementation of if / else statement which could make things quite simpler and also lowers the change of error as there would be no need to put code into the start gcode. Like so (be aware, I'm no coder! ) Filament Sensor Status = 1 means no filament func autoload { M581 P1 T2 S-1 R0 ; Filament Sensor does not listen anymore (S-1). Autoload is disabled. M950 J1 C"nil" ; Input 1 e0 Filament Sensor M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor } func runout_detection { M581 P1 T2 S-1 R0 ; Filament Sensor P1 triggers Trigger2.g always (R0) TRIGGER OFF M950 J1 C"nil" ; Input 1 e0 Filament Sensor M591 D0 P2 C"e0stop" S1 ; Filament Runout Sensor } if Filament_Sensor state changed to "1" { autoload } else { runout_detection } Something like that 2. PINDA Temperature calibration The PINDA (v2) has an built in thermistor to use the Prusa FWs temperature compensation table. RRP FW has has similar feature built in into the G31 command: G31 P1000 X23 Y5 Z0.995 C0.0010 S20 H2 I've measured the Z trigger height with several temperatures from 20°C, 25°C up to 50°C and saw that the variance was not linear. At first the offset got bigger meaning the nozzle would be too close to the bed and after 40°C the difference were much smaller up to 50°C. I'm not quite sure how the Prusa FW stores and uses the recorded values when the FW does it's auto temperature PINDA calibration but what would work is if you could use different G31 code lines depending of the temperature of the PINDA thermistor. My "I'm no coder" mind thinks of the following: if PINDA_Thermistor <25°C { G31 P1000 X23 Y5 Z0.995 } else if PINDA_Thermistor >=25° AND PINDA_Thermistor <30° { G31 P1000 X23 Y5 Z1.005 } else if PINDA_Thermistor >=30°C AND PINDA_Thermistor <35° { G31 P1000 X23 Y5 Z1.020 } . . and so on... else { G31 P1000 X23 Y5 Z2.0 ; safety height } Hope it is clear what I mean
Automatic Bed Leveling with Conditional Gcode Iterations
• Kolbi

79

0
Votes

79
Posts

371
Views

@fcwilt Thanks Frederick!
SOLVED Single Macro for filament handling?
• Kolbi

20

1
Votes

20
Posts

252
Views

This is the latest version - most likely won't change until variables are enabled in the firmware. Use the included Macros for filament handling. To make filament loading, unloading, and changing the most straightforward and simplistic possible evolution, I have made a macro set that is readily accessible from the PanelDue. To take full advantage of the duet filament system you will need to make the system filaments PLA, PETG, ABS, and PC. This will allow you to have custom instructions for each different filament, by adding such to the filament's config.g file. !Note: Based on my current macro version, it is required that each filament's load.g and unload.g remain empty. Placing code into these files will make these macro fail. "Set Filament Type" asks what type filament you are going to use; PLA, PETg, ABS, or PC. Based on the selection, this macro rewrites the "Heat Nozzle" macro to heat the nozzle for the selected filament type. !Note: This macro only has to be executed once for the given filament type change as it's settings are nonvolatile, regardless of reset or power off. !Note: The script will not let you change the filament type while filament is loaded. "Filament Handling" is for any filament unloading, loading, and changing regardless of the printer's state, printing or not. This macro will load, unload, and change filament based on two conditions; whether it detects filament is currently loaded or not, and if a print is in progress or not. !Note: The logic function in the macro retrieves the current status of the filament sensor to base the perceived desired action to enact. If your printer's filament is currently empty and you intend to load filament, please do not place it into the extruder until requested to do so by the macro. Else the macro will determine that filament is loaded and that you desire to unload filament, instead of load. "Heat Nozzle" is created by the "Set Filament Type" macro and can be selected to heat the hotend to the set temperature for the last chosen filament type. You do not need to run this to change filament, the "Filament Handling" macro automatically runs this macro to perform the heating of the hotend to carry out the filament handling, whether it be loading, unloading, or changing. /macros /macros/Filament Handling ; 0:/macros/Filament Handling ; Macro used for all filament handling evolutions if state.status != "processing" ; Printer is not currently printing! if sensors.filamentMonitors[0].filamentPresent = true ; Filament is detected, currently loaded M291 P"Press OK to begin filament UNLOADING, else press CANCEL to exit." R"Filament Handling" S3 M98 P"0:/macros/Heat Nozzle" ; Heat nozzle to predetermined temp M291 P"Ready for filament unloading. Gently pull filament and press OK." R"Filament Handling" S2 M291 P"Retracting filament..." T5 ; Display another message G1 E-150 F5000 ; Retract filament M400 ; Wait for the moves to finish T0 M702 ; Select tool 0, set filament is unloaded M104 S-273 ; Turn off hotend M140 S-273 ; Turn off heatbed M98 P"0:/macros/Filament Handling"; run again ; Now that filament is unloaded, lets ask to load filament else M291 P"Press OK to begin filament LOADING, else press CANCEL to exit." R"Filament Handling" S3 M98 P"0:/macros/Heat Nozzle" ; Heat nozzle to predetermined temp M291 P"Ready for filament loading. Insert filament and press OK." R"Filament Handling" S2 M291 P"Feeding filament..." T5 ; Display new message G1 E150 F450 ; Feed 150mm of filament at 600mm/min G1 E20 F100 ; Feed 20mm of filament at 100mm/min G4 P1000 ; Wait one second G1 E-1 F1800 ; Retract 10mm of filament at 1800mm/min M400 ; Wait for moves to complete M98 P"0:/sys/filaset" ; Set system filament type M400 ; Wait for moves to complete M104 S-273 ; Turn off hotend M140 S-273 ; Turn off heatbed else M291 P"Press OK to begin filament CHANGE, else press CANCEL to exit." R"Filament Handling" S3 M98 P"0:/sys/filament-change.g" ; Call filament-change.g M24 ; Start/resume SD print /macros/Heat Nozzle ; 0:/macros/Heat Nozzle ; Heat nozzle to set temp M291 R"Filament Handling" P"Heating nozzle for PETg, please wait." S0 T10 T0 ; Select Tool 0 M109 S230 ; set temp to 230c and wait /macros/Set Filament Type ; 0:/macros/Set Filament Type ; Macro used to set system's loaded filament type if sensors.filamentMonitors[0].filamentPresent = false ; if filament is loaded then reject action to change filament type M291 P{"System filament is currently set to " ^ move.extruders[0].filament ^ ". Press OK to change filament type, else press CANCEL to exit."} R"Filament Handling" S3 ; Set PLA temp M28 "0:/macros/Heat Nozzle" ; Begin writing to SD card file M291 R"Filament Handling" P"Heating nozzle for PLA, please wait." S0 T10 T0 ; Activate Hotend M109 S200 ; set temp to 200c and wait M29 ; Stop writing to SD card M28 "0:/sys/filaset" ; Begin writing to SD card file T0 M702 ; Set system filament as UNLOADED T0 M701 S"PLA" ; Set system filament as PLA M29 ; Stop writing to SD card M291 S3 R"Filament Handling" P"Filament type currently set to PLA. Press cancel to save this selection or OK to proceed to next filament type." ; Set PETg temp M28 "0:/macros/Heat Nozzle" ; Begin writing to SD card file M291 R"Filament Handling" P"Heating nozzle for PETg, please wait." S0 T10 T0 ; Activate Hotend M109 S230 ; set temp to 230c and wait M29 ; Stop writing to SD card M28 "0:/sys/filaset" ; Begin writing to SD card file T0 M702 ; Set system filament as UNLOADED T0 M701 S"PETG" ; Set system filament as PETG M29 ; Stop writing to SD card M291 S3 R"Filament Handling" P"Filament type currently set to PETg. Press cancel to save this selection or OK to proceed to next filament type." ; Set ABS temp M28 "0:/macros/Heat Nozzle" ; Begin writing to SD card file M291 R"Filament Handling" P"Heating nozzle for ABS, please wait." S0 T10 T0 ; Activate Hotend M109 S250 ; set temp to 250c and wait M29 ; Stop writing to SD card M28 "0:/sys/filaset" ; Begin writing to SD card file T0 M702 ; Set system filament as UNLOADED T0 M701 S"ABS" ; Set system filament as ABS M29 ; Stop writing to SD card M291 S3 R"Filament Handling" P"Filament type currently set to ABS. Press cancel to save this selection or OK to proceed to next filament type." ; Set PC temp M28 "0:/macros/Heat Nozzle" ; Begin writing to SD card file M291 R"Filament Handling" P"Heating nozzle for PC, please wait." S0 T10 T0 ; Activate Hotend M109 S270 ; set temp to 270c and wait M29 ; Stop writing to SD card M28 "0:/sys/filaset" ; Begin writing to SD card file T0 M702 ; Set system filament as UNLOADED T0 M701 S"PC" ; Set system filament as PC M29 ; Stop writing to SD card M291 S3 R"Filament Handling" P"Filament type currently set to PC. Press cancel to save this selection or OK to proceed to next filament type." else M291 S3 R"Filament Handling" P"Filament is currently loaded. Please unload filament before changing filament type." filament.pdf
Invitation to share your conditional GCode scripts
• dc42

23

5
Votes

23
Posts

1102
Views

@OwenD said in Invitation to share your conditional GCode scripts: Perhaps a forum section dedicated to this might be in order? This now exists here: https://forum.duet3d.com/category/34/gcode-meta-commands
Guide for posting requests for help.
• Phaedrux

1

1
Votes

1
Posts

43
Views

No one has replied
Avoiding accidental homing via screen input while mid-print
• Trideo

8

0
Votes

8
Posts

47
Views

state.status=processing maybe? That's different than the busy for homing.
load unload macro with endless loop and cancel condition
• LB

44

0
Votes

44
Posts

401
Views

Also, if you put this in your load.g echo "In PETG.load, calling M703" M703 echo "In PETG.load, M703 returned" echo {move.extruders[state.currentTool].filament} and this in your config.g echo "PETG Config Loaded" Then click the load filament button in the UI, You will get this in the console: M701 S"PETG" M703 In PETG.load, calling M703 In PETG.load, M703 returned PETG Config Loaded If you drop the same code into the unload macro you get different output: M702 In PETG.unload, calling M703 PETG Config Loaded In PETG.unload, M703 returned PETG So calls to M703 inside load.g don't appear to work. This is similar to how homing calls inside a homing file are illegal, so I'm not surprised. M703 inside of unload work just fine. So I love all of the optimizations above but I cant get any of them to work. I'm just going to ignore the blank string in load.g until variables show up.
Measure lost steps on dual Y?
• markz

1

0
Votes

1
Posts

28
Views

No one has replied
M572's D parameter doesn't process expressions
• garethky

8

0
Votes

8
Posts

71
Views

@garethky said in M572's D parameter doesn't process expressions: @dc42 said in M572's D parameter doesn't process expressions: M572 AHH! That makes sense, I was going to separately ask how that worked because I couldn't figure out the syntax for extruders: ; this doesn't work: M92 E{13.6 * 60}:{13.6 * 60}:{13.6 * 60}:{13.6 * 60} I'm guessing it would be something more like this, which is more complicated to evaluate as currently no expression can do array assignment: M92 E{[13.6 * 60, 13.6 * 60, 13.6 * 60, 13.6 * 60]} I really hope that when variables happen we will be able to declare arrays. I think this is a good case for including that. Your first example should work in standalone mode, but won't work in SBC mode. Your second example (or something like it) is what we plan for release 3.4.
UNSOLVED Pause.g Resume.g problems
• Deluxe 600

54

0
Votes

54
Posts

284
Views

I have just tested that on my delta running 3.2 and it works properly for me. Pause.g: ; Pause macro file if state.currentTool != -1 M83 ; relative extruder moves G1 E-4 F2500 ; retract 4mm G91 ; relative moves G1 Z5 F5000 ; raise nozzle 2mm G90 ; absolute moves G1 X0 Y85 F10000 M106 S0 Resume.g: ; Resume macro file M106 R1 G1 R1 X0 Y0 Z2 F5000 ; move to 2mm above resume point G1 R1 X0 Y0 Z0 ; lower nozzle to resume point if state.currentTool != -1 M83 ; relative extruder moves G1 E4 F2500 ; undo the retraction The GCode file I am printing uses M106 S0 at the start, M106 S255 at the start of the second layer, and M106 S0 at the end. My M563 command in config.g does not have a F parameter.
Meta Commands, Variable table
• NeueKlasse

6

0
Votes

6
Posts

57
Views

@PCR Thanks! it's exactly what i want
Crazy ?, can you configure a pop up on Duet Web Control
• Jaw8850

4

0
Votes

4
Posts

31
Views

https://duet3d.dozuki.com/Wiki/Gcode#Section_M291_Display_message_and_optionally_wait_for_response Might work?
Macro to update PanelDue Firmware
• OwenD

10

2
Votes

10
Posts

107
Views

@zombiRon said in Macro to update PanelDue Firmware: @LB it will just error if there's no update file, so you could check the return of that alone, but I think @OwenD was meaning elegant in that there's no ERROR output in the console. M997 S4 Error: M997: File 0:/sys/PanelDueFirmware.bin not found Thanks! Hash might be good for the company-admin to check if they want to -> will add that!
Heater fault checking routine to be run in daemon.g
• OwenD

2

4
Votes

2
Posts

34
Views

Nice work! I ran into this mid print yesterday. I got about 1 hour and 30 minutes into the print. Herd a loud clicking coming from the extruder. Took a few minutes to figure out why! The heater had faulted and shut off, but the print hadn't stopped! I really wish we didn't have to write a routine for this. A fault mid job should stop or pause the job and log an error to the console. Maybe there are some janky printers out there that have intermittent faults that this would break, but come on! What part of the model does the GUI read to get the "fault" that shows up on the heater?
"Virtual Axis" break stall detection?
• garethky

6

0
Votes

6
Posts

50
Views

This is really turning out to be the right answer. One of the benefits of using the work offsets is that they are one of the few things that can be stored with M500! (I thought I could store things from the object model by exploiting M28/M29. But no expressions between those commands gets evaluated, so you can't store the result of an expression.) So I explained above how to store things by writing gcode to a file you run on startup. But what if you want to store something in the work offsets during operation of the printer? You have a tool number, say 2, and you need to write a gcode expression with an axis letter, G10 L2 P5 Z.... How do you get that Z? Well, you can write an if block to do that but that code is pretty long and you wouldn't want that cluttering up your all your macros. So I wrapped that up into macro itself so I can re-use it everywhere I need to store something. The trick is we don't have a way to pass variables into macros yet. So I just write the tool #, value to store and desired coordinate system index into coordinate system #9. Basically coordinate system #9 is now the stack for my program: ; copy_var.g ; ; this macro copies a variable from the temporary variable slot and stores it in the requested slot for the specified tool: ; ; How To use: ; ; G10 L2 P9 X{state.currentTool} Y{value_to_store} Z{target_coordinate_system_index} ; M98 P"/macros/scripts/copy_var.g" ; ; Inputs: ; ; move.axes[0].workplaceOffsets[8] - tool number to store the value for ; move.axes[1].workplaceOffsets[8] - the value to store ; move.axes[2].workplaceOffsets[8] - the coordinate system number to store it in if move.axes[0].workplaceOffsets[8] == 0 G10 L2 P{floor(move.axes[2].workplaceOffsets[8])} X{move.axes[1].workplaceOffsets[8]} elif move.axes[0].workplaceOffsets[8] == 1 G10 L2 P{floor(move.axes[2].workplaceOffsets[8])} Y{move.axes[1].workplaceOffsets[8]} elif move.axes[0].workplaceOffsets[8] == 2 G10 L2 P{floor(move.axes[2].workplaceOffsets[8])} Z{move.axes[1].workplaceOffsets[8]} elif move.axes[0].workplaceOffsets[8] == 3 G10 L2 P{floor(move.axes[2].workplaceOffsets[8])} C{move.axes[1].workplaceOffsets[8]} else abort ; if you pass -1 you call at the wrong time! Now that is solved I can combine it with M500 and I give you per-tool baby stepping adjustment that persists between reboots: call this in tfreeN.g ; save_babystep.g ; writes the baby stepping value into the work offset 7 and then stores it with M500 G10 L2 P9 X{state.currentTool} Y{move.axes[2].babystep} Z6 M98 P"/macros/scripts/copy_var.g" M500 and call this in tpostN.g ; restore_babystep.g ; restore the absolute babystepping value from its storage slot M290 R0 S{move.axes[state.currentTool].workplaceOffsets[5]} Then call M501 at startup before you write any config values as described in the post above.
UNSOLVED How to: G1 F<expression>
• schpongo

12

0
Votes

12
Posts

156
Views

Thanks for reporting this problem, I'll fix it in the next version.
Calling M25 from within nested macro doesn't pause till return
• OwenD

7

0
Votes

7
Posts

20
Views

@gloomyandy Thanks for confirmation
UNSOLVED filamentPresent no longer recognized after FW update
• mitch

1

0
Votes

1
Posts

11
Views

No one has replied
Sample code for variable workaround
• DaveA

4

0
Votes

4
Posts

89
Views

@DaveA I already do something similar. You can use the workplace coordinates to same information and then calculate from. I mainly use this when probing on my CNC. Examples can be found here https://forum.duet3d.com/topic/19698/rrf3-2-request-to-enable-g43-g44-tool-height-offset?_=1609278343985
Bed.g repeated execution based on deviation results
• MikeS

7

0
Votes

7
Posts

73
Views

@dc42 Thanks David this isn't a huge problem, only an aesthetic one. Also thanks on the development roadmap for RRF! I can't wait to try a future input shaper implementation!
G10 Z offset ignored for second tool ?
• brampie

9

0
Votes

9
Posts

47
Views

I think I got it working , I made a couple of wrong assumptions, most importantly offset Z needs to be -0.2 is the second head is 0.2mm higher. thx for your help
UNSOLVED Event Trigger for Status Messages
• NeueKlasse

3

0
Votes

3
Posts

43
Views

@dc42 What do you Think about 2.? After the Board is repowered, It has forgotten the previous loaded filament in Tool 0.
How to disable mesh probing grid?
• Dep

4

0
Votes

4
Posts

57
Views

An alternative is to use G32 and in bed.g put: M561 ; clear any bed transform G29 S1 ; load current heightmap.csv if result > 1 ; if no heightmap.csv, make one. G29 S0