Hi Everyone,

I'm part of the team at Modix3D, where we make big printers (up to 1x1x1m, or 60x60x180cm)

We've been using Duet 2 and Duex5 control boards in our printers for the past 2 years, and we're a big fan of the ease of development that RepRapFirmware brings.

I've been working with the team over the past few months to bring some large updates to the configuration and macro files, trying to start to use some of the features that RepRapFirmware 3 bring, in particular G-code meta commands are a game-changer.

One area that we use G-code meta commands heavily is in the homing files. The (move.axes[0].max or min) is something that has made it possible to use the same homing commands across all printers, as it references things from the config.g files.

Things like that have made development a lot easier.

We also use it in the Duex5 enabled printers to do do fully automated tilt calibration, until the tilt of the corners is within a certain range ( less than 0.02mm of adjustment)

While our files aren't the most advanced or fancy ones, hopefully some of our uses can inspire or help you in your own development. We've definitely learned a lot by reading these forums and are hoping to at least give back a little

you can see our latest configuration and macro files on our GitHub: https://github.com/Modix3D/Modix-V3-configuration-and-Macro-files

If for whatever reason you want to store the Z-offset outside of the config.g file (in this example in a file named config_probe.g), here is the method I've found out to work quite well.

This method works for RepRapFirmware 3.4 and up, as we need to use the ability to write to a file using the echo command. It has been tested on 3.4.1

For more info, see https://docs.duet3d.com/User_manual/Reference/Gcode_meta_commands#echo-command

The macro also allows you to automatically compensate for using of a known thickness shim, using the var probing_tool setting at the start of the macro.

Z-offset macro:

var probing_tool = 0.000
; This allows you to compensate for whatever tool you use to measure the nozzle distance.
; It is set to 0.000 by default, you can set this to the thickness of the tool or paper you use for the Z-offset calibration
; A sheet of paper is on average 0.05 to 0.10mm thick.

M291 S3 R"Heating up nozzle" P"Wait for the nozzle to reach printing temperatures"
M568 P0 S215		; set tool 0 (primary hotend) temperature to 215c
T0			; select tool 0 (primary hotend)
M116 P0 H5		; wait for temperature to reach within 5c of set temperature

M300 S666 P666               ; beep
M291 S3 R"Setting the Z-offset Height" P"Press OK to continue, or CANCEL to abort"
G28                          ; home all
G29 S2                       ; cancel mesh bed compensation
M290 R0 S0                   ; cancel baby stepping
G90                          ; absolute movements

G1 Z10
G1 X100 Y100 F1800
G4 P0

M300 S1111 P666              ; beep
M564 H1 S0                   ; ignore axis limits
M291 S2 R"Test Z Probe Trigger Height - Step 1" P"Place a paper sheet under the nozzle and raise the bed until slight friction can be noticed" Z1 ;

G92 Z0                       ; the nozzle should now be just touching the bed so set the logical Z position to match the physical Z position
M300 S666 P666               ; beep
G1 Z8 F300                   ; insure Z position will allow for probing
G4 P0						 ; wait for the movement to stop

M291 S2 R"Test Z Probe Trigger Height - Step 2" P"Please remove the paper sheet and wait for the bed-probing to begin" ;
G30 S-1                      ; probe the bed and report the Z probe trigger height
M564 S1 H1                   ; respect axis limits

;M291 S2 R"Test Z Probe Trigger Height - Step 3" P"Copy the reported height value on the G-Code console and paste it into the config_probe.g file"

var Z_auto_offset = {sensors.probes[0].lastStopHeight+var.probing_tool} ; math to calculate the BLTouch offset
echo >"0:/sys/config_probe.g" "G31 Z"^{var.Z_auto_offset}				; write the Z-offset to the config_probe.g file

echo "the Z-offset has been stored in the config_probe.g file. The Z-offset is", var.Z_auto_offset, "mm"

G4 P0						 ; wait for the movement to stop
G1 Z10 F300                  ; Lift up the nozzle again so it's not pressed against the bed surface

config_probe.g :

G31 Z1.5 

It's a fairly simple macro, but if there are any questions let me know

@mikeabuilder
I've gone through this list and added all the gcode meta commands, including var and param: https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands

In notepadd++, to change the stylers you can go to language -> user defined languages -> define your language -> pick the language from the dropdown and then you can change the stylers

For the var and param for example. they are in the 3rd group. You can change the styler, or put it in a different styler.

I've used a VERY basic grouping, so absolutely do use and adapt it to your own liking! If you send me a message or a Github pull request I'll very gladly add it to the UDL!

When uploading a filament configs zip with the wrong files, the error message states "fiels" instead of "files"

Version: Duet Web Control 3.4.5

I have updated the UDL I made with better colors based on the latest RRF version, with both a dark mode and light mode skin

I was however not able to figure out how to match the styling of certain parts. RepRapFirmware for example does X200 with the X being either white/black, and then the 200 part having color.

For the life of me, I could not figure out how to implement that behavior, so I just grouped them as one

https://github.com/ComedianTF2/RepRapFirmware-UDL-For-Notepad

@grahamsoukup

Make sure to update the configuration and macro files to those compatible with RepRapFirmware 3.4.1

The instructions can be found on the modix support site, and you can download them here

https://github.com/Modix3D/Modix-V3-configuration-and-Macro-files/releases/tag/v3.4.1.a

@ritz One mistake I see is people keeping the negative modifier in the G31 value, as the default value we provide with the printers is G31 Z-3, just so that in the initial setup it

So if you'd for example get a value of 1.25, from the Z-offset maco, and you don't erase the -, but just replace the 3 with 1.25, you'd get a G31 value of Z-1.25 instead of Z1.25. And with that, the nozzle would be 1.25+1.25 away from the print surface.

You can always reach our support directly at support@modix3d.com, preferably with a copy of your config.g files so we can check that as well.

@phaedrux User confirmed that the pause behavior has been fixed

@Trojan3D If you change it to be >> instead of > on the echo, it adds data to the file instead of overwriting it

So in your case it would be:
echo >>"0:/sys/config-override.g" "G31 Z"^{var.Z_auto_offset} ; write the Z-offset to the config-override.g file

This adds the value to the last line of the config-override.g, however you will see it become quite a mess over time, as the echo >> only adds another line

So after doing it ten times, you it would have the G31 Z value added ten times in a row, with the bottom one being the value you're trying to have.

That's why it's generating a separate file called config_probe.g in this example, and then you can load the Z-offset using a M98 P"config_probe.g" in your config.g and homing files

@dc42 Sadly this did not trigger the calibration prompt

Downgrading to 1.24 and then back to 3.4.1 did the trick, it erased the calibration data going back to 1.24 and triggered the prompt going both to 1.24 and then again when going to 3.4.1.

@T3P3Tony

I will be able to check that in January, once I'm back from holidays

@droftarts

Same, will test it out in January once I'm back. The wiring I've done per the guide you've shown. I had missed the driver enable polarity jumper, so that's quite likely the issue there.

With re-sending the commands we were able to get the printer up and running, and the printer has completed a successful print, though hopefully we won't need to use the driver_enable.g file I used before with the fixes recommended.

Thanks both for the help, I'll enjoy the Christmas break for now and get back to it in Jan

@T3P3Tony it's on 3.5.4

After further testing, it seems that sending a small move command, after which sending the M569 command seems to enable them reliably.

At the bottom of the config.g I've added a M98 command calling for motor_enable.g, with the contents below

M98 P"motor_enable.g" ; enable motor at boot

M564 H0 S0					; allow unhomed moves + moves out of min/max area. Only for testing. Remove later on
G91 						; relative moves
G1 X0.1 					; move 0.1mmm
G1 Y0.1 					; move 0.1mmm
G1 Z0.1						; move 0.1mmm
M569 P0 S0 R1 T2:2:5:2.5	; X axis, Drive 0, active high enable, 2us minimum step pulse, 2 us minimum step interval, 5us DIR setup time and 5us hold time
M569 P1 S0 R1 T2:2:5:2.5	; Y axis
M569 P2 S0 R1 T2:2:5:2.5	; Z axis
M564 H1 S1 				; re-enable safety stuff

@T3P3Tony it doesn't seem to do the trick.

It's also weird that it doesn't seem like the M569 command enables it 100% if the time, I seem to work around 70% of the time, and then sometimes I gotta send it multiple times in a row until it "takes"

I'm currently testing settling the idle timeout to a very large number as well to make sure that once it takes it stays

So I'm helping out a friend install a 6XD in his printer. Ideally we should have installed a 6HC, but we needed to get it up and running asap and it was out of stock locally so we went with a 6XD option.

We have managed to get movement out of the steppers, but it seems I need to re-send the M569 commands before the motors get "energized". Once they have had the commands sent, they can be moved with no issue.

The weird thing is that the commands are being sent in the config.g, but somehow aren't activating the drives there. It's only when I send them later on a second time that things work properly.

Adding these commands to the bottom tot he config.g doesn't seem to work either. Writing this out, i wonder if there is maybe there a time/power delay that would cause things?

If anyone has some clues on what to check/test for, let me know

The drivers used are SL2690A drivers, here is the manual: https://www.123-3d.nl/pdf/SL2690A--English.pdf

Per the manual, it seems that the config is 2us minimum step pulse, 2 us minimum step interval, 5us DIR setup time and 5us for the hold time. I am not 100% sure on the hold time. but testing 0, 2, 5 and 10 made no noticable difference so I kept it at 5us

The config.g is below. Note some parts of the config.g haven't been written out fully, as we're enabling things one by one to check the systems.

G90												; send absolute coordinates...
M83												; ...but relative extruder moves
M550 P"Everything3D"							; set printer name

; Network
M552 S1 P0.0.0.0								; enable network for 

; Drives
M569 P0 S0 R1 T2:2:5:5							; X axis, Drive 0, active high enable, 2us minimum step pulse, 2 us minimum step interval, 5us DIR setup time and no 5us time
M569 P1 S0 R1 T2:2:5:0							; Y axis
M569 P2 S0 R1 T2:2:5:0							; Z axis
;M569 P124.0 S0									; physical drive toolboard goes forwards using default driver timings. Update with the correct CAN address (the P value)
M584 X0 Y1 Z2 ;E124.0							; set drive mapping
;M350 E16
'M906 E1000 									; 1amp

;M350 E16 I1									; configure microstepping with interpolation
;M906 E1000 I50									; set motor currents (mA) and motor idle factor in per cent
; steps/mm and current set by external stepper motor 
M92 X200 Y200.00 Z2000.00 E400					; set steps per mm
M566 X600 Y600 Z50 E3600						; set maximum instantaneous speed changes (mm/min)
M203 X4800 Y4800 Z500 E5100						; set maximum speeds (mm/min)
M201 X600 Y600 Z15 E5100						; set accelerations (mm/s^2)
M204 P500										; travel move accelerations
M84 S100										; Motor idle timeout

; Axis Limits
M208 X0 Y0 Z-4 S1								; set axis minima. Updated from -2 to -4 on the Z
M208 X1200 Y580 Z600 S0							; set axis maxima

; Endstops
;M574 X1 S1 P"!io1.in"							; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0
;M574 Y2 S1 P"!io2.in"							; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io1
;M574 Z1 S2										; configure Z-probe endstop for low end on Z

; Z-Probe
;M950 S0 C"124.io0.out"							; create servo pin 0 for BLTouch
;M558 P9 C"^124.io0.in" H5 F120 T6000			; set Z probe type to bltouch and the dive height + speeds
;G31 P500 X-15 Y30 Z1.7							; set Z probe trigger value, offset and trigger height
;M557 X30:1150 Y30:570 S50						; define mesh grid

; Heaters
M140 H-1										; disable heated bed (overrides default heater mapping)
;M308 S0 P"temp0" Y"thermistor" T4700000 B4725	;C7.06e-8 ; configure sensor 0 as thermistor on pin temp0
;M950 H0 C"heat0" T0								; create nozzle heater output on heat0 and map it to sensor 0
;M307 H0 R1.929 K0.248:0.000 D6.80 E1.35 S0.90 B0 V25
;M143 H0 S285									; set temperature limit for heater 0 to 285c

; Fans
;M950 F0 C"124.out0" Q500						; HEATSINK FAN create fan 0 on pin fan0 and set its frequency
;M106 P0 S1 H0 T45								; set fan 0 value. Thermostatic control is turned on
;M950 F1 C"124.out1" Q41						; PART COOLING FAN create fan 1 on pin fan1 and set its frequency
;M106 P1 S0 H-1									; set fan 1 value. Thermostatic control is turned off

; Tools
;M563 P0 D0 H0 F1                            ; define tool 0
;G10 P0 X0 Y0 Z0                             ; set tool 0 axis offsets
;G10 P0 R0 S0                                ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined
; Toolboard

;M308 S2 P"124.temp1" Y"thermistor" A"toolboard temp" T100000 B4092


;LCD
;M950 P1 C"LCD_D4"
;M42 P1 S0
;G4 P500
;M42 P1 S1
;M918 P2 C30 F50000 E4

;********
;TESTING ONLY REMOVE ME IN FINAL BUILD
M564 H0 S0								; allow unhomed moves + moves out of min/max area. Only for testing. Remove later on
;TESTING ONLY REMOVE ME IN FINAL BUILD
;*********

@AndrewG The config.g you have seems to be quite an old one, and that bed.g wouldn't work with it. I have no idea how that would suddenly revert, but I would try and download the correct variant of the config files to use for your printer

https://github.com/Modix3D/Modix-V3-configuration-and-Macro-files/releases/tag/v3.4.5.c

edit: It might also be worth updating your firmware, those files are made for RRF3.4.5

@Surgikill Good catch, I had overlooked the I1 parameter, though that shouldn't give any problems; the parameter is ignored. The rest of the deployprobe.g and retractprobe.g are correct though, and that should not give an error.

@Surgikill That's quite interesting, I've been working hard to re-write the entire code of the printers, and I am pretty sure I caught all of the depreciated code. But if you point me to anything that was missed, I would love to fix it.

@dc42 Thanks for that.

Good to know that the choice selection for the M291 T0 S4 does not need to be indented, that makes a large difference and with that I should be able to get everything in a single file

@dc42 The problem is not in the variable name, I tested it and it did not work with the following script:

M30 "0:/sys/test/config_globals.g"
M28 "0:/sys/test/config_globals.g"
M29
 
M291 T0 S4 R"Welcome" P"Welcome to your Printer. Please select the version of printer you have" K{"V1","V2"} 
	if input = 0
		M291 S3 R"Version V1" P"According to this, you have a V1 printer. Press OK to confirm, or cancel to re-start"
		echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
		echo >>"0:/sys/test/config_globals.g" "   global version = 1"
		global version = 1
	if input = 1
		M291 S3 R"Version V2" P"According to this, you have a V2 printer. Press OK to confirm, or cancel to re-start"
		echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
		echo >>"0:/sys/test/config_globals.g" "   global version = 2"
		global version = 2
 
if global.version = 1
	M291 T0 S4 R"V2 to V3" P"Do you have a A model or a B model" K{"A model","B model"} 
		if input = 0
			echo >>"0:/sys/test/config_globals.g" "   global printer_model = 1"
			global printer_model = 1
		if input = 1
			echo >>"0:/sys/test/config_globals.g" "   global printer_model = 2"
			global printer_model = 2
elif global.version = 2
	M291 T0 S4 R"V2 to V3" P"Do you have a C model or a D model" K{"C model","D model"} 
		if input = 0
			echo >>"0:/sys/test/config_globals.g" "   global printer_model = 1"
			global printer_model = 1
		if input = 1
			echo >>"0:/sys/test/config_globals.g" "   global printer_model = 2"
			global printer_model = 2

That outputs (when choosing V1 and model A)

if !exists(global.config_version)
   global version = 1

However this combination of scripts does work:

M30 "0:/sys/test/config_globals.g"
M28 "0:/sys/test/config_globals.g"
M29
 
M291 T0 S4 R"Welcome" P"Welcome to your Printer. Please select the version of printer you have" K{"V1","V2"} 
	if input = 0
		M291 S3 R"Version V1" P"According to this, you have a V1 printer. Press OK to confirm, or cancel to re-start"
		echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
		echo >>"0:/sys/test/config_globals.g" "   global version = 1"
		;global version = 1
	if input = 1
		M291 S3 R"Version V2" P"According to this, you have a V2 printer. Press OK to confirm, or cancel to re-start"
		echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
		echo >>"0:/sys/test/config_globals.g" "   global version = 2"
		;global version = 2
 
if global.version = 1
	M98 P"0:/sys/test/version1.g"
elif global.generation = 2
	M98 P"0:/sys/test/version2.g"

M291 T0 S4 R"V2 to V3" P"Do you have a A model or a B model" K{"A model","B model"} 
	if input = 0
		echo >>"0:/sys/test/config_globals.g" "   global printer_model = 1"
		global printer_model = 1
	if input = 1
		echo >>"0:/sys/test/config_globals.g" "   global printer_model = 2"
		global printer_model = 2

M291 T0 S4 R"V2 to V3" P"Do you have a C model or a D model" K{"C model","D model"} 
	if input = 0
		echo >>"0:/sys/test/config_globals.g" "   global printer_model = 1"
		global printer_model = 1
	if input = 1
		echo >>"0:/sys/test/config_globals.g" "   global printer_model = 2"
		global printer_model = 2

That outputs (when choosing V1 and model A)

if !exists(global.config_version)
   global version = 1
   global printer_model = 1

I don't see a good reason why the script with everything contained in one file would not work, but that same script just split out over three files does work as it should