Well done , similar to my DBot, but i've gone for the dual z motors. I like your print carriage \ cooling fan parts, have you published them anywhere ?

I tried a Titan Aero, but just couldn't get it to print nicely, so I've reverted to a normal Titan, combined with a Precision Piezo, which gives great prints.

Personally, I favour the Precision Piezo probes (genuine ones, not clones) and while I have used BLTouchs' (also genuine), I found them more difficult to configure & reliably use, whereas the Precision Piezo probes just work, more reliable, no probe to get stuck\damaged and no probe offset.

Try removing\comment out the

M574 Z1 S2 line, I found I didn't need it for my Precision Piezo z-probe , i.e.

M574 X1 Y2 S0 ; Set active low endstops

M558 P8 I1 R0.4 H5 T24000 F200 ; Set Peizo - P probe type, I Invert, R recovery time, H dive hight, T inter-probe-point speeds, F Probing Speed

DWC - Duet control web pages & sorry I should have taken in what you've written...

So I take it, that at the fourth point the probe hits the bed ??

FYI, as it looks like you are still on RRF2, if so, this was my setting for that version (which worked well)

M558 P8 I1 R0.5 H5 T24000 F250 A3 S0.08 ; Set Peizo - P probe type, I Invert, R recovery time, H dive hight, T inter-probe-point speeds, F Probing Speed, 3 Dives , S calculated difference

Thank You

yes DWC 2.0.7

@Vladimir said in Setting Z probe and mesh compensation in config g:

M574 Z0 S0 "Z-stop

You need to remove the above setting and just leave the M558 command, my RRF2 setting were :

; Endstops - these are for standard standard switched X low, Y high, active low

M574 X1 Y2 S0 ; Set active low endstops

M558 P8 I1 R0.5 H5 T24000 F250 A0 S0.04 ; Set Peizo - P probe type, I Invert, R recovery time, H dive hight, T inter-probe-point speeds, F Probing Speed, 3 Dives , S calculated difference

Thanks Ian, so as I suspected, unless I define additional 'objects' they can't be added to the tool.

Danal, I've included the output from M122 above i.e.
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC2 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6J1F2-3SD6L-9JZHX

Julian

For me, when I try that same command (G28 X G28 Y or G28 Y G28X) the initial G28 is executed, but the second command is not.

Getting closer to a fully working system, thanks to DC, but I've come to a couple of 'funnies'...

M122.csv config.g

Firstly, while trying to define a tool, as per the wiki, I'm unable to add multiple drives, heaters or fans etc to a single default tool definition. The additional 'object' always result in "No Tool defined"
I've not found any additional posts\info on this, so is it me, missing other config settings (M140's ? I have tried to no avail) or does not work as per the wiki anymore ?

The second relates to running multiple G\M commands on a single line, e.g. in the DWC console window, if I enter G28 space G29, the G28 command is executed, but the G29 isn't executed, but the console window, reports successful completion.

DWC - Duet control web pages & sorry I should have taken in what you've written...

So I take it, that at the fourth point the probe hits the bed ??

FYI, as it looks like you are still on RRF2, if so, this was my setting for that version (which worked well)

M558 P8 I1 R0.5 H5 T24000 F250 A3 S0.08 ; Set Peizo - P probe type, I Invert, R recovery time, H dive hight, T inter-probe-point speeds, F Probing Speed, 3 Dives , S calculated difference

If you tap the probe, with your finger, do the led lights flash on the control board and does it also show as triggered in the DWC ???

If leds flash, but no show in the DWC then your configuration is incorrect. If they don't flash, you need to check your board\wiring\probe etc.

David,

@Dr_Ju_Ju said in RRF3.01-RC2 CoreXY Movement differences:

I was on the latest 2.05.1 \ DWC 2.0.7 on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6J1F2-3SD6L-9JZHX

& yes Nuramori, I was playing with the axis limits to try & get things working in the right direction...

Thank you David, I now have movement as I'd expect'ish, even if the Y axis moves 'negatively', which I suspect will be corrected when I update the axis limits....

Julian

@dc42 said in RRF3.01-RC2 CoreXY Movement differences:

M584 Y2 not M584 Y1

Now I'm really confused, Why would I need Y2 in M584, as that setting came from the web configurator, & other examples I've seen ???

Julian