@Tinchus

From the docs..,
The H parameter defines the Z probe dive height, which is the height above the trigger height from which probing starts. The default is 3mm or 5mm depending on firmware version. You may wish to increase it during initial calibration. When using mesh bed compensation or running G30 commands with specified XY coordinates (for example from the bed.g file), the firmware moves the Z probe to this height above where it expects the bed to be before commencing probing. The maximum depth of probing from this position is twice the dive height.

I think you'll find on straight G30 Z home, the dive height is ignored as the height is unknown.
Otherwise you would never be able to home from any height.
About the best you can do is check for typical errors before you start using the object model.

I use this macro which is called before any Z homing or bed leveling

check BL Touch var probeOK = true if sensors.probes[0].value[0]=1000 ; if probe is in error state set var.probeOK = false echo "Probe in error state- resetting" M280 P0 S160 ; reset BL Touch G4 S0.5 if state.gpOut[0].pwm < 0.05 set var.probeOK = false echo "Probe is already deployed - retracting" M98 P"0:/sys/retractprobe.g" G4 S0.5 if sensors.endstops[2].triggered set var.probeOK = false echo "Probe is already triggered - resetting" M280 P0 S160 ; reset BL Touch G4 S0.5

I also use this check in my homeall.g to cancel the print if any errors occur during homing
Any successful command should return a value of 0

G30 ; home Z by probing the bed if result !=0 abort "Print cancelled due to probe error"

Outside that, you'd have to have a secondary switch, pressure sensor or similar attached I'd think.

@StevenL You can buy the Ethernet module separately; it is available to replace a defective Ethernet module on an existing card, but can also be used to convert a WiFi card to Ethernet.

You will need to desolder the WiFi module, and replace it with the Ethernet module; the underlying Duet 2 board is common to both, unlike Duet 3 Mini 5+. You'll need some two 6x1 low profile header pins to solder into the board for the Ethernet module to plug into, and two plastic 5mm high standoffs. I think these are supplied with the replacement module.

There are a couple of threads on doing it, this is the best I think (from 2017):
https://forum.duet3d.com/topic/2890/converting-a-duet-wifi-to-a-duet-ethernet

Ian

@gloomyandy
Ok, now (after calibrating it at Z3) it doesn't give the error.

But now it does all 5 loops because it doesn't manage to be consistent. 😬
EDIT: going slower doesn't have problems.
I'll also try to move the coil further away from the extruder.

Then I'll have to understand how to make the scanning without lifting and lowering the bed on every point (just removing the Z-999999 from G30 makes it ignore said command).

@rubens what hot end do you have? If it's an E3D Revo Roto then there is a special Duet3D filament monitor to fit it.

I am not familiar with Klipper or which Duet boards it supports. If you ask around here, you'll likely be encouraged to just use RepRapFirmware, but what's easiest for you may be what you're already familiar with.

@DIY-O-Sphere OK, I knew I would make a fool of myself with this question, now I feel a bit embarrassed but well informed. Thanks!

@gloomyandy It happens after I print a tall print. I have a lot of crash avoidance logic in my gcode that uses the G60 coords to make sure the bed is at a safe height during less determinant situations.

@DTinNC you can try running the board in AP mode creating it's own WiFi.

@santy none that I can think of for four extruders.

Ian

@droftarts
By commenting out M84 command and using the above modication , seems to work but has issues. i think i spoke too soon. it will shut off the motors after a while and i am not sure why

M906 Z1360 U1360 V1360 W560 A560 B560 C560 D560 'G560 I100

then just use openPnP commands

ENABLE_COMMAND to send M17 to Duet3 6XD Controller DISABLE_COMMAND to send M18 to Duet3 6XD Controller

This way if the PNP machine is started and operational it will have the axes and motors enabled and as soon as all jobs are done and PnP machine is disabled in openPnP it will send a command to Duet3 6XD to disable all axes and motors

@dc42
managed to side step the issue and use just a single parallel homing file in Duet3

Merci à tous, mon problème est résolu.

@chrismbp Whenever you get an unexpected crash, please make sure to run M122 as soon as possible, and post the response. This usually can give valuable troubleshooting info. As you're using SBC, the system log may also be useful. Without these, it's difficult to know what might have happened.

Ian

@infiniteloop Adding T0 in did the trick.

Many thanks for the swift support and guidance!

@chrishamm excellent, thanks

@reisusjesus @elmoret Apologies for taking so long to get back to you. Yes, the motor should be replaced under warranty. Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

Ian

@tecno Maybe BtnCmd? https://github.com/MintyTrebor/BtnCmd

Ian

@P0HakaAustin It looks like you're using the G30 command incorrectly; you have substituted all the 'G1 Z' command for 'G30' but kept the parameters for G1.

I think you want to use the probe you have defined in config.g as follows:

... ; Z-Probe (sin sensor) M558 P5 H5 F500 T4000 X0 Y0 Z1 ; Set Z probe type/mode 5. Not using on XY, but using it on Z. M307 H3 A-1 C-1 D-1 ; Disable the 7th Heater to free up PWM channel 5 on the Duex board M280 P3 S10 I1 G31 P500 X-35 Y-5.5 Z6.68 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ...

Does the BLTouch deploy during startup? It should do a 'self test' of deploy/retract twice. But you have a command in config.g to deploy it again. It would be best to remove the 'M280 P3 S10 I1' command from config.g.

RRF 2.04 supports the BLTouch probe type 9. You should change the M558 command from P5 to P9. Then add two files to your /sys folder, deployprobe.g and retractprobe.g. They should have the following in them:

Create a 'deployprobe.g' file (in the /sys folder of the SD card) it should contain the following single command:

M280 P3 S10 I1

Create a 'retractprobe.g' file (in the /sys folder of the SD card) it should contain the following single command:

M280 P3 S90 I1

Restart, and test deployprobe.g and retractprobe.g are working correctly by sending M401 to deploy the probe, and M402 to retract the probe.

Then follow the guide here to test and calibrate the probe: https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_testing

Finally, fix your homeall.g and homez.g. Change homeall.g to:

; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v2 on Thu Jan 17 2019 20:56:52 GMT+0100 (hora estándar de Europa central) G91 ; relative positioning G1 Z5 F1000 S2 ; lift Z relative to current position G1 S1 X-330 Y-330 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 X5 Y5 F6000 ; go back a few mm G1 S1 X-330 Y-330 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X190 Y120.5 F1800 ; Move Probe to middle of bed G30 ; Probe bed

Change homez.g to:

G91 ; relative positioning G1 Z5 F1000 S2 ; lift Z relative to current position G90 ; absolute positioning G1 X190 Y120.5 F1800 ; Move Probe to middle of bed G30

If you want to lift Z after probing, add the following on the end of homeall.g and homez.g:

; Uncomment the following lines to lift Z after probing G91 ; relative positioning G1 S2 Z5 F1000 ; lift Z relative to current position G90 ; absolute positioning

Ian

@JRCL the medium-current (i.e. fan) outputs on Duet 2 are rated 1A but can handle 1.5A for short periods e.g. when a fan is starting up. However, the entire fan power circuit (2 always-on output and two switched outputs) shares the fuse, which is normally 1A. You can increase it to 2A or even 3A if you are sure that the individual outputs are not overloaded.

Duet 2 boards include flyback diodes on the fan outputs but not on the heater outputs.