tekkydave

You can dynamically alter the z height using the babystepping controls on the Print Status page.

G31 sets the probe offsets. Does your probe trigger at 3mm above the bed?

I had to push my Titan motor to 1200mA. The X/Y motors are at 1000mA and the Z currently at 1400 (1680 maximum).

In settings -> list items

When you've paused a print the buttons should change to resume or cancel. Cancel will stop the print.

I think thats the issue. 

Try keeping all probes more than 24mm from the edge and see what happens. I'm not sure what the sign of the offset should be as my offsets are effectively x=0, y=0 with the piezo. Where is your probe in relation to the nozzle?

It does. Use Sxxx:yyy.

E.g S100:90 to get 100 x spacing and 90 y spacing.

I think your probe points are too close to the edge (15mm) as your probe has an offset of 24mm.

Some useful info

https://duet3d.com/wiki/Setting_up_automatic_probing_of_the_print_bed

I think for corexy we should be using G29 not the blue button which runs G32 for deltas.

That doesnt look right to me. Do you have a bed.g file. If so what is in it?

See M557 and G32 for some clarity. Maybe

The M557 parameters in config.g get used when you execute G29. Try running G29 from the gcode console (after homing the axes of course).

If you run the Mesh Grid Compensation from the button on the control page it seems to want to run bed.g if present. Otherwise it runs G32 using the M557 parameters. I think. Still a bit confused myself.

When you home the axes it runs the homex.g, homey.g, homez.g or homeall.g depending on what you clicked. Check the contents of those to make sure they are not doing something strange.

Add this to set corexy mode:

M667 S1                                   ; Select CoreXY mode

I think the tiny antenna on the WiFi module lets it down. There was a discussion on the Forum about having a proper connector & antenna but it puts the costs up too much. I think you may need a repeater or a spare router connected via ethernet.

How is the Duet getting its Gnd connection. Via usb?

Signing off for now. I'm not being rude if I don't reply straight away

5v only from the ATX should be ok to see and edit your config files.

From the Duet Wiki:

The Duet operates on two power circuits: a 5V circuit that powers the CPU, WiFi, and web interface, (mostly through a 3.3V LDO) and a 12/24V circuit that powers the motors and heaters.

11 minutes ago, Gina said:

Yes, that's the intention but I'll check the config.g file.  Would it be best to connect the board via USB for power to check or would using the +5v_SB from the ATX PSU be alright?

Do you want to see whats in the config.g or test the probe? USB power wont power the board I think. I'm not using any 5V supplies so I don't know what it will power.

Anyone else know?

Everything else looks good to me

20 minutes ago, Gina said:

I have now carefully checked all the connections and links - twice - and think I'm ready to apply power but I need a cuppa first  

Here's a photo of the Duet board - wiring not tidied up yet.

Check the motor connections for Y and E0 - they seem to be different to X & Z (which match mine). Or is that the non-standard motor wiring you mentioned earlier?

I think the Z probe connector can be used for either analogue or digital probes. I have my piezo probe connected to it. It can behave as analogue or digital depending on config.

From my config.g

; Z Probe / Endstop
M558 P5 I0 R0.4 F225 X0 Y0 Z1             ; P5 = Digital mode, I0 = NO, R0.4 = 400mS delay before probing, F300 = 300mm/min probe speed, X0 Y0 Z1 = used as axis endstop for Z axis
G31 X0 Y0 Z-0.2 P100                      ; X, Y, Z offsets, debounce interval

• P0 indicates that no Z probe is present.
• P1 specifies an unmodulated or smart IR probe, or any other probe type that emulates one (probe output is an analog signal that rises with decreasing nozzle height above the bed). If there is a control signal to the probe, it is driven high when the probe type is P1.
• P2 specifies a simple modulated IR probe, where the modulation is commanded directly by the main board firmware using the control signal to the probe.
• P3 is similar to P1 but drives the control signal to the probe low. This may be used to switch between different Z probes.
• P4 selects a switch for bed probing (on the Duet, this must be connected to the E0 endstop pins).
• P5 (from RepRapFirmware 1.14) selects a switch (normally closed) for bed probing between the In and Gnd pins of the Z-probe connector (Duet 0.8.5 and Duet WiFi).
• P6 is as P4 but the switch is connected to an alternative connector (on the Duet series, the E1 endstop connector).
• P7 is as P4 but the switch is connected to the Z endstop connector (firmware 1.20 and later).
• P8 is as P5 but the signal is unfiltered for lower latency (firmware 1.20 and later).

I guess you are using M558 P4 where the probe (acting as a switch) gets connected to the E0 endstop pins.

Looks good. Are you not using the Z probe socket for your Z probe (at bottom of board)?