Setting up DUET wifi + Duex5 - help needed

dc42

If you upgraded from pre-1.19 firmware, delete any default deployprobe.g and retractprobe.g files that came on the SD card.

CTRDevelopments

Super, it now no longer wanders around somewhat randomly! Many thanks.
To call the leadscrew adjustments i call G32, which seems to work and the console tells me the adjustments it has made, even better!

The printer is quite large, X and Y approx 500mm, so can I still use mesh bed levelling also? I realise it will add wear to the ballscrews but given the size I am sure the bed will have slight curvature etc.

Then presumably I can add the G32 command, and whatever call the mesh bed at the start of each print gcode file?

dc42

Yes you can still use G29 mesh bed compensation after G32 bed levelling. However, some users find they need to run G32 more than once to get the bed level, if it is a long way off level to start with. Firmware 1.21 includes a "fudge factor" parameter in the M671 command to help achieve faster convergence.

CTRDevelopments

OK, thanks. Is there an auto way of calling it multiple times, or do I just call G32 5 times at the start of the file? I have had a look at M671 but which is the fudge factor? Or do you mean this is inbuilt in the firmware?

I have another quick question on G31 - probe setup. I am using your IR probe and it is behind the nozzle (+ve y direction) and to the left of the nozzle (-ve x direction). Would this mean I need to write in the config.g file
G31 X-2.0 Y30

thanks

dc42

Just call G32 as many times as needed (2 may be enough in normal use). Or duplicate the sequence of G30 commands in bed.g.

I'm sorry, I forgot to document the M671 F parameter in the GCodes wiki page in the Duet3D wiki. I've corrected that.

Your G30 offsets are correct because they are measured from the print head reference point to the probe, just like tool offsets are.

CTRDevelopments

OK, many thanks for the update, I will give this a try this evening

CTRDevelopments

@ctrdevelopments said in Setting up DUET wifi + Duex5 - help needed:

M208 X0 Y-25 Z0 S1 ; Set axis minim

Hi, I am still struggling with mesh bed leveling. If I call G32 that all seems to work, if I call it 2-3 times the changes very rapidly go to zero. However, I then call G29 and I dont seem to be able to probe the whole bed.

in config file I have

M557 X15:450 Y15:410 S50 ; Define mesh grid

However, it only probes in 100mm steps and only goes to x 352 and y 285

I have also got this in config

M208 X-8 Y-18 Z0 S1 ; Set axis minima
M208 X451 Y410 Z400 S0 ; Set axis maxima
G31 P500 X-12 Y55 Z2.5 ; Set Z probe trigger value, offset and trigger height

Cheers

dc42

Please run M557 without parameters to check that your M557 command in config.g was accepted.

Which firmware version are you using?

CTRDevelopments

Dc, all seems fixed now. Not sure what I changed this morning that I hadn't done previously, but it's working.

I have used all the motor outputs on the duet and the duex5. Is there a way to get anymore? I am thinking of implementing more extruder but cannot currently.

Cheers

dc42

You can connect 2 more stepper drivers to the CONN_LCD connector. See the wiki page on connecting external drivers.