2 alternative solutions:

1. Upgrade your firmware to 1.19 but read the upgrade notes first. Firmware 1.19 deploys and retracts the probe automatically

2. Wrap the G29 command in a macro with M401 and M402 commands around it, then run that macro.

@dc42:

Please provide details instructions for how to reproduce this

I have not found a set pattern yet. As soon as I can easily reproduce the issue I will post.

@dc42:

When you connect DWC, it sets the fan slider to the value reported by the Duet, and you can change it from there. If you want to prevent the fan turning on at all then there are better ways to achieve this than relying on connecting DWC, for example by mapping to an unused fan in the tool definition.

I am not using this as a permanent fan disable, just while I designing/printing my new fan mount. The slider seems like a simple way to achieve what I want, without changing my slicer/config files.

You can configure a maximum amount of individual leadscrew adjustment to apply in the M671 S parameter, to avoid binding. No adjustment will be performed if the adjustment to any leadscrew would exceed that limit.

You can test how well it would work before you buy a DueX by using the manual bed levelling assistant, which uses the same code. See https://duet3d.com/wiki/Using_the_manual_bed_levelling_assistant.

İ just adjusted and its working. İ just wonder can you check my firmware to see if there is a mistake. Mainly i need help in termistor section!

does it recognise anything (Such as a BOSSA port)

The default folder that M98 looks in is /sys. If you put your scripts in /macros or anywhere else, you need to specify the path to the file in the M98 command.

I found the solution in S3D, I was in the correct area but going the wrong direction.

Thanks, Ed

Have you installed the Windows device driver?

@cdl1701@yahoo.com:

It is like the motor is trying to turn but can't and is just clicking really loudly with no movement. I can see the extruder gear and it is not turning at all. I think I am going to make a new cable and see if that makes a difference. Perhaps one of the wires is bad but good enough to show that it has continuity.

That sounds like a blocked hot end to me. Suggest you heat up the hot end, retract all the filament from the extruder, then try running it. i.e extrude with no filament loaded and see if that makes a difference.

I still don't know what was making the noise, but I did find the issue. a terminal had pulled out of the socket for the thermistor on the white plug on the Smart Effector. I bent the tab out a little more and re-seated it, seems to have cured it. Just glad it wasn't a broken wire on the power side coming in, I don't think I have a way to get those out for replacement like the other side.

@Martin_S:

Hi Morten, best of luck with this setup.
Let us know if you made any progress.

Subscribed, I'm also interested.

Wahh, found out what was wrong.. AFTER I spend a day rewiring to move all Extruderst to the Duex5 and so had to solder in extensions to the wires etc…

As I had been using the Z driver to drive both motors at first, I had removed the jumpers back in january.. I thought nothing off it as Ramps doesn't populate the pins when not in use... and I hadn't noticed it either... untill I for the 100th time looked over the diagram to check up on drive numbers and noticed the "jumpers" written on the diagram if you only use 1 Z motor.

After I put in the jumpers everything works perfectly.
I am going to write a blogpost about it, but for now:

My Config.g and homez.g is as follows
Description:
My XY for CoreXY AB. All 5 extruders on Duex5 and the 2 Z-drivers on Z and Ex0
[h]Config.g[/h]

[[language]] ; Define Drives ; Physical Drive conention M569 P0 S1 ; Drive 0 A M569 P1 S0 ; Drive 1 B M569 P2 S0 ; Left z-motor (original Z) M569 P3 S0 ; Right z-motor (Ex0) ; M569 P4 S0 ; EX1 - unused M569 P5 S0 ; Extruder0 - Physical Tool 0 M569 P6 S0 ; Extruder1 - Physical Tool 1 M569 P7 S0 ; Extruder2 - Physical Tool 2 M569 P8 S0 ; Extruder3 - Physical Tool 3 M569 P9 S0 ; Extruder4 - Physical Tool 4 ; Motor remapping for dual Z M584 X0 Y1 Z2:3 U3 E5:6:7:8:9 P3 ; Driver 0 For X, 1 for Y, Z=2:3 U=3, Extruder 5-9 - P3 is number of visible axes XYZ = U is hidden ; Configure Drives M350 X16 Y16 Z16:16 U16 E16:16:16:16:16 I1 ; Configure microstepping with interpolation M92 X160 Y160 Z800:800 U800 ; Steps per mm for XY and Z2:3 +U3 M92 E1025:1025:1025:1025:1025 ; Set steps per mm for 5x physical Extruders M566 X900 Y900 Z12:12 U12 E120:120:120:120:120 ; Maximum instantaneous speed changes (mm/min) M203 X12000 Y12000 Z1000:1000 U1000 E3000:3000:3000:3000:3000 ; Maximum speeds (mm/min) M201 X500 Y500 Z250:250 U250 E250:250:250:250:250 ; Accelerations (mm/s^2) M906 X1000 Y1000 Z800:800 U800 I0 ; Motor currents (mA) and motor idle factor % for XYZ M906 E1000:1000:1000:1000:1000 I50 ; Motor currents (mA) and ide factor % for Extruder motors M84 S30 ; Set idle timeout

[h]Homez.g[/h]

[[language]] G91 ; Relative mode M584 Z2 ; Split Z into 2 (Z+U) G1 Z250 U250 F2000 S1 ; Move up to 250mm in the +Z direction. Stop if endstop is triggered G1 Z-3 U-3 F600 S2 ; Move 2mm in the -Z direction - S2 = If containing axis letters: offset will be added to the pause coordinates G1 Z3 U3 F100 S1 ; Move slowly 5mm in the +Z direction, stopping at the homing switch M584 Z2:3 ; Join U to Z again - Driver 8+9 G1 Z-5 F3000 ; Move back again 5mm in the -Z direction G90 ; Back to absolute mode

Huge thanks to Stian Indal for paving the way with his original post over on the E3D-online forum
https://forum.e3d-online.com/index.php?threads/bigbox-dual-optical-z-max-endstops.2675/#post-29578

Thanks, David, that works perfectly.

Good to know, and makes sense, I see if occasionally on my corexy machine when I'm testing underbed sensors and have z jerk set to 0.

Here is another video by Joe (3D Maker Noob). https://www.youtube.com/watch?v=v3Xnb0XzlAs

Good coverage of the Duet (and my printer) from about 7.52. Duet got about 2 minutes worth of coverage which, for a 15 minute video of the entire TCT show, is pretty good I'd say. Shame I didn't get mentioned by name so fame will have to wait :)….......

I use [c]M28[/c] and [c]M29[/c] for this in my 'Load Filament' scripts:

M28 /sys/current_material.g ; open current_material.g for writing M207 S6.0 F7800 Z0.2 R0.1 G10 P0 R150 S220 M29 ; close current_material.g

And in my [c]config.g[/c] I have this line: [c]M98 P/sys/current_material.g[/c]

Every line between [c]M28[/c] and [c]M29[/c] is written into [c]/sys/current_material.g[/c] which in turn is then loaded when the printer is starting up. You could even write your whole [c]config.g[/c] with a macro. But beware - comments are ignored, ';'s are stripped and the whole line ends up in the file…

I would have the fan at the top of the enclosure with a flap over it. Fan connected to duct running outside. Place the filter on the bottom with a flap on top of it as well. The filter flap needing the best seal to keep any fumes from leaking by it. When done printing, kick on the fan. It will pull open the filter flap and push open the fan flap exhausting all of the fumes outside.