Qualified as an Electronics Engineer, specializing in Broadcast System (ex BBC), but now a Server Systems Administrator, but just about retired.
Have been building equipment & systems for many years, from specialized broadcast gear & studios etc. to analogue & digital synthesizers, but more recently 3D printers\cnc\scanners etc.
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.
It's by design of of the way IP networks operate.
When a device boots-up, if it has been given a static IP address, it will always use that address.
If it hasn't been given an address it will try and contact a DHCP server, which will give it an address, from a pool of address it has been configured for. Depending on your network configuration, but normally for home use, this will be the router that you use to connect to the internet, which unless you know how to make some advanced configuration changes, will be 'factory set' for the pool, to the local subnet of 253 possible hosts (computers).
So there are 2 ways to always get the same IP address:
Assign a static address in the DWC configuration, which could have knock on effects whereby the DHCP server tries to assign the same address to another device that connects to your network. this risk can be mitigated by assigning an IP address 'high-up' in the subnet range, e.g. if your IP address range is something like 192.168.1.1 through to 192.168.1.254, then assign an address in the 250's
Assign reservations on the DHCP server, such that when the MAC address of your DWC device requests an IP address it is always given the same address.
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
Is there any way to easily customise the DWC pages, without reverting to additional HTTP pages etc ??
I especially want to get rid of the ridiculous/superfluous three boxes at the top of every screen, two which are effectively displaying the same information !!
I suppose I'll just have to accept that DWC is crap in the usability stakes, and use it for configuration only, its a pity that there also isn't a simple control interface...
Other than that, I would probably have to dump the board & go for something else.
As I said, I'm using Edge, that is already set for dark theme, there are no configurations settings for these pages ....
So it's not possible to undo this rubbish??
BTW, for me, even this page is virtually unreadable, unless I can't find the settings to be able to set a 'dark' theme...
Sorry yes, I got my left & right swapped 
and in my browser (M$ Edge) the individual windows are fixed & not flexible !!
Is there any way to undo/customise the site pages as they relate to the GCode Dictionary page ?? especially for those of us that wear glasses, and are light sensitive, as the pointless blue section on the right, offers nothing but taking up screen space....
@dc42 Thank you for the suggestion of running G30 (Z home) before running G29, as it now looks like I may be close to a workable solution...
But that is only if I have M671 set, to the bed coordinates, if it is set to the motor/belt coordinates, then errors keep increasing i.e.
Note that the bed is fixed, and only the XY gantry moves in the Z axis using four motors/belts.
my bad for not stating things correctly, within a few mm, i had configured the positions of the belts that raise/lower the Z axis as defined at https://docs.duet3d.com/User_manual/Reference/Gcodes, which are outside of the bed coordinates. for a Voron2.4 printer.
Maybe getting somewhere....
To ensure that the Z motor mapping were/are correct, I plugged in each motor it turn, leaving the others unplugged, and ensured that only the appropriate motor moved.
I then re looked at the mappings in the config files etc. and all appeared to be ok. Re-ran the levelling loop with no change.
On a whim, I decided to change the defined positions of the Z motors using M671, from their true positions to the bed co-ordinates i.e.:
M671 X-80:-80:380:380 Y-70:390:390:-70 S10
to
M671 X0:0:300:300 Y0:300:300:0 S10
Re-running the bed levelling loop, after the update, produced a significant improvement in repeatability etc. console.txt
This then me thinks that either I didn't have the settings correct in the first place ?? or that the system doesn't like negative numbers ??
@phaedrux Thanks for all your help...
After removing the M574, and additional Z move settings, the system now uses the probe as the end-stop correctly.
Yes, I have checked that the probe trigger heights are the same at various points on the bed..
But after all that, the system still does not give consistent results, and worsens through multiple iterations:
Yea, that's what I was thinking about re-flashing the firmware, but I didn't want to go down that route until I've exhausted everything else in trying to get the current 3.4 setup working.
Now I'm getting totally confused as per (https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_endstops) Firmware configuration paragraph, that is exactly how it should be configured (M574 Z1 S2)
I've re-enabled the G30 setting, but unless I've enabled the M574 setting I only get "Error: Failed to enable endstops" when trying to home the Z axis.
And still, after setting the above, the system still does not give a reliable/repeatable solution, and worsens through iterations.
@phaedrux Thanks for your suggestions, to answer:
I've set M566 command to a single value, not multiple for each motor, my bad.
M98 just runs with no errors/output etc.
Yes, I tried that method, and I also created another SD card (using Raspberry Pi Imager) with 3.3 from the original stable version, I downloaded last year. In both instances, the hardware was not recognised, so DWC service would not start...
My homing files are attached, X & Y are ok but Z is still a "work in progress" till I can get repeatable
HomeFiles.zip.txt
I believe I've defined the Z endstop to be the Precision Piezo Probe (M558 command) and then selecting it using the M574 Z1 S2 command ?? Note: once again the G31 command will be "fine tuned" when things are stable.
@phaedrux said in V3.4 SBC - G32 not working correctly ??:
Have you tested the probe trigger height at the different points on the bed? Is it basically the same
Yes, I'm using under bed piezo sensor and I get the same results no matter where I probe..
And after making the changes to config.g (above), and re-running the "start up" macro, I still get the same results with worsening height maps on each iteration HeightMaps-new.zip.txt