@dc42

Again and again I realize how good it was to choose a Duet board. If I miss a function, it's not because it doesn't exist, but because I can't find it in the multitude of functions.

Thanks

@oliof

You made my day!

Updated to 3.4b6 and it works again!
Thank you very much.

@dc42
Thanks, that worked!

Hello!

Today I updated my Duet2Wifi with Extensionboard and Paneldue to the latest Firmware 3.5.1

Everything seems to work fine, but whenever I want to extrude or retract by pressing the button on webcontrol or paneldue, the result is a "busy" and nothing happens. Only reaction: the requested speed ist set on webcontrol. nothing else happens.

My tools are using 2 drivers simultaneusly for extrusion - one in filament changer, one as main extruder. I also tried configuration with only one driver per E-axis, but the result is the same.

Sending an G-Code like "G1 E2 F100" works.

Any hints?
Greetings,
Markus

config.g.txt

Hello!

I have 3 fans, a thermistor and a heater on my print head. All in all 10 cables. Since the thermistor cable is now broken, I would like to interrupt the cables at the print head and continue them with a highly flexible cable. On this occasion: can I connect the 5 ground cables all together and lead them to the board as one cable? Do I have to split them all up again or is it enough to put them all on the heater mass?

I have a Duet 2 Wifi.
Thanks!
Markus Müller

@OwenD
I use a Prusa MMU2s to change filaments.
Pretty reliable now too. But sometimes the new filament cannot be inserted correctly, e.g.

1. previously the cutting process got stuck and the position of the selector no longer fits
2. the cut was unusable because threads formed during the extract or remained in the selector
3. whatever

Then I would like to be able to eliminate the problem, insert the first cm manually and then let the tool change script continue.
Sometimes I have to re-home an axis or move it to a certain position, release the filament for manual movement and switch on the extruder feed again (this involves turning a roller in the MMU2, which presses the corresponding filament onto a gear). It's unpredictable.
And easier if the whole script doesn't just run to the end and I have to do a lot more by hand.

Just hold, do pause.g, let me do it and move on.

Here are my scripts for tool selection, if someone likes to see it.

pre1.g

;  called before tool 1 is selected
M98 P"tool_pre_laden.g" U{global.u1} W{global.w1}

tool_pre_laden.g

; select Filament

G90                ; absolute moves

M98 P"homeu.g"     ; for safety reasons

M400
if sensors.gpIn[0].value = 1
	G1 W{global.w5}                         ; release filament
	M291 P"Filament in selector, please clean" S2 ; blocking, but blocks DWC too
        M25					; Pause (not the way I intend)
        G1 W{param.W}

G1 U{param.U} F2000     			; move selector to Tool position
echo >"uposition.g" "G92 U",param.U     	; save selektor Position (to home at some restart, when filament is in it and moves are not possible)
G1 W{param.W} F10000     			; move idler to Tool position

tpost1.g

; called after tool 1 has been selected
M98 P"tool_post_laden.g" U{global.u1} W{global.w1}

t_post_laden.g

M302 P1								; allow cold extrusion
G90								; absolute moves

while sensors.gpIn[0].value = 0					; feed max 100 mm, till sensor in selector
	G1 E1 F5000
	if iterations > 100 					; error if no sensor signal
		G1 W{global.w5} F10000     			; release filament for manual feed
		M291 P"Filament load error detected. Filament is free for manual feeding" S2  ; blocking, but blocks DWC too
		M25						; Pause (not like I wish to pause)
		G1 W{param.W} F10000				; grab filament for automatic feed
		while sensors.gpIn[0].value=1			; draw back manual feeded filament out of sensor
			G1 E-1 F500
		G1 E1 F500					; ...and forward - so we have are at the point we wanted to be without user interaction - go on
		break

G1 E216  F3000          	; move filament in main extruder 
G1 W{global.w5} F10000     	; free filament in MMU2s - all work now by main extruder
G1 E341 F5000           	; feed to hotend
M116 P4                         ; wait for temperature
M302 P0				; no cold extrusion
G1 E13 F5000			; fast feed into hotend
G1 E10 F300             	; feed into hotend

@OwenD
That would be a possibility but not a solution. And very awkward and without DWC.
The other possibility I see would be to move everything related to tool change scripts to PrusaSlicer's custom gcode. Then the M25 commands are at job file level and should work. But that's also very ugly.
What's wrong with being able to pause a macro in case of a problem?

Hello!

I have a problem within a tool change script. During the filament change, a sensor is queried as to whether the filament has really been inserted. If it isn't, I'd like the script to pause at that point and give me a chance to intervene manually. I also want to be able to enter G-codes manually. A dialog stops at the relevant point, but prevents the G code input. M25 or M226 only pause after the end of the script or only work if the tool change was triggered by a print job.

Suggestions?

Greetings from Germany
Markus

@dc42

Again and again I realize how good it was to choose a Duet board. If I miss a function, it's not because it doesn't exist, but because I can't find it in the multitude of functions.

Thanks

Hello!
Is there a way to have the Z switch approach motion start smoothly?
I drive the print bed up against the print nozzle, the bed rests on four piezo elements. However, these already respond at the start of the upward movement due to the inertial mass of the bed, so that I have to lower the sensitivity unnecessarily, which in turn is bad for my hotend. And I have to move fast at the end for secure triggering.

Greetings from Germany an a Happy New Year,

Markus

@oliof

You made my day!

Updated to 3.4b6 and it works again!
Thank you very much.

Hello!

First the history: i murdered stepper driver 4 on my duet wifi2 some years ago by shooting a hole in the chip (short circuit). I deactivated it by "M569 P4 R-1". All others are OK.

With firmware 3.0 everything else was OK. But all following updates resulted in error messages "motor phase A may be disconnected reported by driver(s) 0" on every phase of every driver 0-9 (except destroyed and deactivated 4). No movements of any motor. They even dont get warm. So i downgraded repeatedly do 3.0 again. All wiring seems ok,

The question: if the error is result of the destroyed driver, can this affect the drivers on the duex5 also? May the solution be to buy a new duet wifi2?

Thanks,
Markus Müller