@Sindarius
is it possible to have this also in DWC 3.1.1 for the Duet 3?

@Proschi78
start G-Code:

G90 ; use absolute coordinates
;M83  ; extruder relative mode
;BED_MESH_CALIBRATE AREA_START={first_layer_print_min[0]},{first_layer_print_min[1]} AREA_END={first_layer_print_max[0]},{first_layer_print_max[1]}
;MINX:{first_layer_print_min[0]}
;MINY:{first_layer_print_min[1]}
;MAXX:{first_layer_print_max[0]}
;MAXY:{first_layer_print_max[1]}
M557 X{first_layer_print_min[0]}:{first_layer_print_max[0]} Y{first_layer_print_min[1]}:{first_layer_print_max[1]}
M82 ; absolute extrusion mode
M104 S140 T0
M140 S[first_layer_bed_temperature] ; set bed temp
M190 S[first_layer_bed_temperature] ; wait for bed temp
G32 ; home all
G1 X-14 Y-10 F10000
; Reset speed and extrusion rates
M200 D0 ; disable volumetric e
M220 S100 ; reset speed
M221 S100 D0 ; reset extrusion rate
M109 S{first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} ; wait for extruder temp
G92 E0.0

;G1 X150.0 E20  F1000.0 ; intro line
G1 E20  F1000.0 ; intro line
G1 X0.0 Y0.0 Z0.1 F1000.0 ; go outside print area
;G1 X5 Y0
G92 E0.0
G1 X2 Y2 Z0.2 E0 F18000 ; new
G1 X60 Y2 E9.0 F1800 ;intro Line
;G1 X200.0 E30 F500 ; second Part intro Line
G92 E0.0
G1 Z5 E-{retract_length[0]} F{retract_speed *60}
G1 X{first_layer_print_min[0]} Y{first_layer_print_min[1]} Z{first_layer_height} F30000
G1 E{retract_length[0]} F{retract_speed*60}
G92 E0.0

I do not use a mesh.g this does not exists on my system
my bed.g:

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Feb 09 2020 01:08:02 GMT+0100 (Mitteleuropäische Normalzeit)
M561 ; clear any bed transform
G4 P100
G28 ; home
G0 Z10 F4200

G0 F60000
G30 P0 X5 Y155 Z-99999						;Orbiter
G30 P1 X302 Y155 Z-99999 S2					;Orbiter
G30 P0 X5 Y155 Z-99999						;Orbiter
G30 P1 X302 Y155 Z-99999 S2					;Orbiter
G91 										;Relative positioning
G1 Z5 F1500 								;Raise Z 5mm
G90 										;Absolute positioning

G0 X45 Y-5 F60000
G29 										;Probe the heatbed and generate heightmap

G91 										;Relative positioning
G1 Z5 F1500 								;Raise Z 5mm
G90 										;Absolute positioning

G4 P100
G0 X0 Y0 F60000 						;Go to Parking Position

some settings in config.g that maybe relevant for:

...
M671 X-52:377 Y155:155 S2.5 					   ; leadscrews at left (connected to Z) and right
...
M557 X10:300 Y10:300 P6:6; S40                     ; define mesh grid ( the normal full size mesh config)

@Sindarius
like I said in github it is working with the FixV2 on my SBC for me.
many thx for the great work.

@Proschi78

@Proschi78
no, sorry
but on S3d maybe have a look to this variables:
I do not know what is in, but you can test with a smal object and check then the gcode file

[build_size_x]
[build_size_y]
[build_size_z]
....
[next_position_x]
[next_position_y]
[next_position_z] 

they are mentioned here:
https://community.ultimaker.com/topic/11328-simplify3d-hidden-undocumented-placeholders-for-post-processing-scripts/

@Proschi78
mhm, this makes no sense for me, do you have a M558 on some other positions? like in the the bed.g or config-override.g?

I will test this when I have time for, I normaly use only one probe per point.

@Proschi78 said in Only probe where the part will be printed:

ke A5 in no

the A5 needs to be in the config.g where you configure the probe type
look for M558
https://docs.duet3d.com/User_manual/Reference/Gcodes#m558-set-z-probe-type

@Proschi78
no, sorry
but on S3d maybe have a look to this variables:
I do not know what is in, but you can test with a smal object and check then the gcode file

[build_size_x]
[build_size_y]
[build_size_z]
....
[next_position_x]
[next_position_y]
[next_position_z] 

they are mentioned here:
https://community.ultimaker.com/topic/11328-simplify3d-hidden-undocumented-placeholders-for-post-processing-scripts/

@Proschi78

@Proschi78
start G-Code:

G90 ; use absolute coordinates
;M83  ; extruder relative mode
;BED_MESH_CALIBRATE AREA_START={first_layer_print_min[0]},{first_layer_print_min[1]} AREA_END={first_layer_print_max[0]},{first_layer_print_max[1]}
;MINX:{first_layer_print_min[0]}
;MINY:{first_layer_print_min[1]}
;MAXX:{first_layer_print_max[0]}
;MAXY:{first_layer_print_max[1]}
M557 X{first_layer_print_min[0]}:{first_layer_print_max[0]} Y{first_layer_print_min[1]}:{first_layer_print_max[1]}
M82 ; absolute extrusion mode
M104 S140 T0
M140 S[first_layer_bed_temperature] ; set bed temp
M190 S[first_layer_bed_temperature] ; wait for bed temp
G32 ; home all
G1 X-14 Y-10 F10000
; Reset speed and extrusion rates
M200 D0 ; disable volumetric e
M220 S100 ; reset speed
M221 S100 D0 ; reset extrusion rate
M109 S{first_layer_temperature[initial_extruder]+extruder_temperature_offset[initial_extruder]} ; wait for extruder temp
G92 E0.0

;G1 X150.0 E20  F1000.0 ; intro line
G1 E20  F1000.0 ; intro line
G1 X0.0 Y0.0 Z0.1 F1000.0 ; go outside print area
;G1 X5 Y0
G92 E0.0
G1 X2 Y2 Z0.2 E0 F18000 ; new
G1 X60 Y2 E9.0 F1800 ;intro Line
;G1 X200.0 E30 F500 ; second Part intro Line
G92 E0.0
G1 Z5 E-{retract_length[0]} F{retract_speed *60}
G1 X{first_layer_print_min[0]} Y{first_layer_print_min[1]} Z{first_layer_height} F30000
G1 E{retract_length[0]} F{retract_speed*60}
G92 E0.0

I do not use a mesh.g this does not exists on my system
my bed.g:

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun Feb 09 2020 01:08:02 GMT+0100 (Mitteleuropäische Normalzeit)
M561 ; clear any bed transform
G4 P100
G28 ; home
G0 Z10 F4200

G0 F60000
G30 P0 X5 Y155 Z-99999						;Orbiter
G30 P1 X302 Y155 Z-99999 S2					;Orbiter
G30 P0 X5 Y155 Z-99999						;Orbiter
G30 P1 X302 Y155 Z-99999 S2					;Orbiter
G91 										;Relative positioning
G1 Z5 F1500 								;Raise Z 5mm
G90 										;Absolute positioning

G0 X45 Y-5 F60000
G29 										;Probe the heatbed and generate heightmap

G91 										;Relative positioning
G1 Z5 F1500 								;Raise Z 5mm
G90 										;Absolute positioning

G4 P100
G0 X0 Y0 F60000 						;Go to Parking Position

some settings in config.g that maybe relevant for:

...
M671 X-52:377 Y155:155 S2.5 					   ; leadscrews at left (connected to Z) and right
...
M557 X10:300 Y10:300 P6:6; S40                     ; define mesh grid ( the normal full size mesh config)

@Proschi78
Hi, I use SuperSlicer, but I think in prusa Slicer it should also work.
in my startcode I added this line:

M557 X{first_layer_print_min[0]}:{first_layer_print_max[0]} Y{first_layer_print_min[1]}:{first_layer_print_max[1]}

maybe this will help you too.

@Sindarius
like I said in github it is working with the FixV2 on my SBC for me.
many thx for the great work.

@N3XT3D this is exact the same problem that I have from the beginning with the duets boards.
duet wifi 2 (sorry a clone) and a original duet 3. Which Motors you are using?
when I use a SKR GTR board with klipper and TMC5160 it is much quiter, but I had skipped layers when it switch between
steahltshcoop and coolstep.
@dc42 I have still no answare how I can test with a different RSens parameter, all other firmwares use 0.075Ω only the duets use 0.050Ω can be this the difference?

at the moment I don´t have time to test again. But the homing sequence didn´t help yet, only adding stepper dumper to isolate the frame from the motors has helped for me. However, this reduce the print quality.

I read in a post on facebook that useing 1.8° stepper motors instead of 0.9° helped.
I ordered some more motors to test, maybe the moon motors are not the best for the Duet board. I don´t know what the problem is. But I´m not alone with this problem.

@empi00
your storry is particle also my Storry
I have started with a Tevo Tornado Gold, steppers are loud, this machine has a MKS Gen L V1.0 Board so I replaced the drivers with TMC2800, installed Klipper and used Repetier Server as frontend on the raspberry.
I was amazed, the steppers you can not hear anymore when the machine is printing, on quick moves the drivers use SpreadCycle and you can hear the differnces.
So I was really happy with the machine, but I would have more speed.

Then I started to build the BLV with the new BTT SKR Pro 1.1 with TMC5160 sound was ok but regarding the new Type of printer it was louder as the Tevo, this is clear regarding the MGN Hiwin Rails.

But I had sometimes the problem that I lost a stepper after a while of printing (now I know it is a Hardware defect on the board, first driver sockel gets disconnect when the machine gets warm so I think it is a solder problem).
So I decided to try a Duet Wifi clone, but I had not read the full documentation so I missed that stealthchop is not availabe.
I was chocked how loud the machine can be with the 2660 drivers, but the machine was stable.
Then the Duet 3 comes out with TMC5160 and direct connection to a raspberry.
So I was hoping I can get all my wisches now.
But the noise of the printer is nearly the same, only when the steppers are not moving you can hear a difference
I have tested the motors alone, not build in to the printer and you can feel the vibration of the motors when a duet board is
connected.
When I connect a different board like the SKR Pro or now the GTR with TMC5160 and Klipper installed the motors are smoother on the same speed etc.
I have two ideas what can be behind.

As first Klipper/Marlin etc. use for the SenseResistor 0.075 and the duet Firmware use 0.050 this means that you can use motors with higher current on a duetboard but I think this change also the wave so that the sound that the motors creating
are different and maybe louder is normal and it can be changed only when we get a option in the firmware to select as example 0.075 with the correct wave like all other firmware does. But I have not enough knowledge and measuring devices
for checking and testing. So it can be that I´m on the wrong way at all here.

As second what I do not understand is why is there a big noice change between the speed 119mm/min and 121mm/min on 0.9° motors.
When you check my first post you can see that M569 say´s the change should be at 110.3 mm/sec
and @dc42 had confirmed that my settings are correct.
I have tried many different homing scripts but nothing changed.
at the moment I´m a little bit frustrated at all.
what I would wish for the best Board and firmware:

• the gui from Repetierserver on a local touchscreen (sorry but the gui from the duet does not really work for a touchscreen, but is not so bad on the browser. The preview of the print model is missing at all on the duet)
• a mix of the config from Klipper and reprep (the settings for the TMC´s are to complicated like the threshold for stealthchop, the firmware has all information to calculate it from stepper speed like klipper and marlin does)
• the hardware from duet 3 with the direct connection between Raspberry and the board. I like when I stop / pause a print it does directly. On Klipper the printer has a buffer so it pause and cancel when the buffer is empty and not directly.

Sorry for the long text but I have the feeling it goes not forward since month. I understand that Duet3d must look for business and creating new things but it would be helpfull to have all functions that are promised are also correct working
before new things are started.