Gcode meta commands

• 

  Conditional G Code introduction "tutorial" (PDF)
  • OwenD  

  3
  6
  Votes
  3
  Posts
  104
  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
  1138
  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
  298
  Views

  

  @fcwilt Thanks Frederick!
• 

  SOLVED Single Macro for filament handling?
  • Kolbi  

  20
  1
  Votes
  20
  Posts
  182
  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
  944
  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
  0
  Votes
  1
  Posts
  34
  Views

  No one has replied

• 

  Independent control of 2 drivers assigned to the same axis
  • RincewindBoi  

  4
  0
  Votes
  4
  Posts
  21
  Views

  

  Thanks all! Ill try it out.
• 

  Duet 3 / RPi Power Toggle Script
  • oozeBot  

  1
  1
  Votes
  1
  Posts
  20
  Views

  No one has replied

• 

  UNSOLVED Parallel tasking
  • Anthoval  

  11
  0
  Votes
  11
  Posts
  144
  Views

  

  After running multiples tests at a reasonnable speed (Feedrate : 15000 mm/min), I can tell that the motion is continuous between multiple G0/G1 commands! By the way, I don't understand how the "T" parameter from the M670 works (when using the "P" parameter in a G1 command). I thought at first that is was the delay between the beginning of the movement and the beginning of the output being set to '1'. But when testing with multiple values for "T", the output was always set to '1' immediatly after the beginning of the G1 command. Edit : The "T" parameter appears to be important when using the P1 parameter with a G1 command on a very short distance. Reduce the "T" value if you're looking to trigger an output to '1' on a short distance and high speed (30 mm and 15000 mm/min).
• 

  How to ping Z-probe state
  • code7  

  17
  0
  Votes
  17
  Posts
  87
  Views

  

  @dc42 OK. I'll give it a try. In regards to running real-time loops in daemon.g, would it be possible to use a loop in daemon.g to call for a variable that can reduce the feedrate mid-print to 1% while a long single line segment is being printed? Ideally I would be able to pause mid deposition, but I know the current command needs to complete before a pause can be invoked.
• 

  UNSOLVED How to: G1 F<expression>
  • schpongo  

  6
  0
  Votes
  6
  Posts
  67
  Views

  

  @schpongo said in How to: G1 F<expression>: Hey, I have a quick question. I'm trying to write a loop were in each loop iteration the set feedrate increases. My current approach is the following, but this isn't working. Does anyone have any pointers? while iterations < 10 G28 U G1 U180 F6000 G1 F{6000+iterations*2000} while iterations <5 G1 U56 G1 U304 I've tried replacing the {} with () or [] but did not have any success. I've just tried that on my delta, with a few changes to suit the geometry: while iterations < 10 G28 G1 X0 Y0 Z50 F6000 G1 F{6000+iterations*2000} while iterations <5 G1 X-150 G1 X150 It works for me as expected. For each iteration of the outer loop, the speed of the moves in the inner loop increases. I'm using RRF 3.2beta1.
• 

  Problem with m291
  • schpongo  

  9
  0
  Votes
  9
  Posts
  52
  Views

  

  @chrishamm Hmm.. I'm actually on 3.1.1. I did not yet do the update to the beta Version. Might there be something else that I'm doing wrong?
• 

  Z-probe / Light - meta command help
  • code7  

  1
  0
  Votes
  1
  Posts
  17
  Views

  No one has replied

• 

  % - Modulo Operator Support in GCODE Meta Commands
  • lee7670  

  2
  0
  Votes
  2
  Posts
  20
  Views

  

  RRF provides the mod(a,b) function instead.
• 

  Mesh bed leveling travel speed
  • Deluxe 600  

  3
  0
  Votes
  3
  Posts
  31
  Views

  

  @droftarts Oh yeah found it! I cant believe i havent noticed . Anyway thank you for your help in understanding the problem. It works much better now . Have a great day
• 

  Axis skew compensation
  • foster1111  

  5
  0
  Votes
  5
  Posts
  22
  Views

  

  i printed a calibration cube when i first biuilt the printer noticed the skew and kept it for comparison. so i compared the new prints with the values entered and the is no change between the models. the firmware version iam running is Board: Duet 2 WiFi (2WiFi) Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2) Duet WiFi Server Version: 1.23
• 

  Very Slow Retraction/Extrusion Movement
  • FoxLab  

  6
  0
  Votes
  6
  Posts
  44
  Views

  

  You could edit the PanelDue firmware itself maybe. If the extrusion speeds in the PanelDue interface are too high it won't really matter, because if the speed limit is set low in the config.g it won't be able to move it faster.
• 

  SOLVED state.status and filament runout?
  gcode filament runout status • • mitch  

  10
  0
  Votes
  10
  Posts
  58
  Views

  

  @dc42 thank you. This is very helpful. I will give it a try. It seems the assistant you have asks the user to adjust per a given thread pitch. I do like the craftbot method of just continuously probing and letting the use make micro adjustments to see how close they are getting to the desired positions. Perhaps once we have SBC capability on the Duet2 we can make more elaborate wizards and guided assistants.
• 

  This topic is deleted!
  • mitch  

  1
  0
  Votes
  1
  Posts
  6
  Views

  No one has replied

• 

  Need help with homing XYUV and conditional gcode
  • deckingman  

  13
  0
  Votes
  13
  Posts
  83
  Views

  

  @deckingman said in Need help with homing XYUV and conditional gcode: EDIT. Thinking about it a bit more, I guess an elegant solution would be to have a macro which checked the status of all end steps, which could be called at the start of any homing macro, but I'm open to suggestions. You can iterate over all endstops (or other arrays) by using # to give you the number available while iterations < #sensors.endstops if sensors.endstops[iterations].triggered echo "Endstop " ^ iterations " is triggered" abort I had thought maybe this could be expanded to try to move away from any active endstop which would effectively test if it was broken (i.e. if it's still active after a 6mm move it's broken), but I can't see an easy way in the object model to determine if the endstop is at min/max or whether it's N/O or N/C. Nor does it seem possible to determine the axis it is associated with other than to assume the endstop number would align with the axes number. But if you had two endstops on an axes that'd fail.
• 

  'elif' did not follow 'if'
  • peter247  

  3
  0
  Votes
  3
  Posts
  21
  Views

  

  @fcwilt Like this ? if state.status = "paused" M24 elif state.status = "processing" M25 still getting the same 'elif' did not follow 'if o.k I've got you if state.status = "paused" M24 elif state.status = "processing" M25
• 

  RRF 3.1.1 move.axes[0].userPosition=move.axes[0].userPosition/2
  • rzi  

  3
  0
  Votes
  3
  Posts
  66
  Views

  

  Thanx! woprks very well now. This is what I ended up with. M558 K0 P5 C"!io2.in" F100; create probe #1 for use with M585, active low G38.2 X596 P0 G10 P2 L20 X0 G0 X{move.axes[0].userPosition-1} G38.2 X0 P0 G0 X{move.axes[0].userPosition/2} G10 P2 L20 X0 G38.2 y810 P0 G10 P2 L20 Y0 G0 Y{move.axes[0].userPosition-1} G38.2 Y0 P0 G0 Y{move.axes[1].userPosition/2} G10 P2 L20 Y0
• 

  SOLVED G-Code Loop
  • R3D  

  8
  0
  Votes
  8
  Posts
  61
  Views

  

  Well this is definitely going to be a game changer for me, I will have to do some testing on one of my other test rigs to play around with this. Thanks a million @OwenD, I am constantly amazed on how helpful the Duet Community is and i hope one day I know enough to be able to help others out as you have helped me.
• 

  Bed compensation condition
  • Marco Bona  

  9
  0
  Votes
  9
  Posts
  68
  Views

  

  @fcwilt, what your macro does is very similar to what I do at start printing, obviously I do not load the map but start the probing. Nowever I would like to add an additional condition, but I understand that it is not possible
• 

  Random number generation with Meta Commands?
  • Kolbi  

  11
  0
  Votes
  11
  Posts
  99
  Views

  

  @Kolbi said in Random number generation with Meta Commands?: @dc42 said in Random number generation with Meta Commands?: It will be in the 3.02beta releases. Nice! Is there a list of new expected features? You can see what is already implemented or partly implemented at https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md.