New Duet WiFI, now hotend not heating

mhackney

Yesterday, I commissioned a new delta with a Duet Wifi. Made a couple of nice prints. Firmware was outdated and I wanted to install the 1.17RC2 for grid leveling. I was not able to install over DWC - keep getting could not rename file errors and after I manually renamed them, file would upload and when I said Ok to install, nothing happened. Even after several reboots. So I transferred the files to SD and used Pronterface to install. That worked, I see the new set of firmware files. But now I can not heat up the hot end. The bed works fine. I do not get a fault or any type of error. I did try M562 P1 but that had no effect. Double checked my config.g and it is identical to what I had working. The Heater display in DWC says "off (T0)" and the current temp display looks normal and working (i.e. it's reading the thermistor fine). The temp display on PanelDue also looks normal (no colored background). Any suggestions on what is going on and what to do?

mhackney

Just crazy! I reset with M999. The hot end finally became responsive. So I heated up the bed and hot end and attempted to auto calibrate. I am getting "Error: Z probe already triggered at start of probing move"

Running FSRs with DaveSL board. I've probed successfully several dozen times. FSRs are triggering properly - I just tested them, they are not triggered to start.

z probe definition
M558 P4 X0 Y0 Z0 H3

I'm not 100% sure what version of dc42 was installed originally, I recall something like 1.15 (file dated 6/13/2016)

mhackney

Ok, more info…

FSRs not triggered:
M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: at min stop

Then I tapped the bed and ran:
M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped

so something has changed it appears

mhackney

and this is still the same in config.g as it was yesterday;

M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high)
M574 E0 S0 ; set FSR controller active low

mhackney

I reverted back to stable 1.16 WiFi release and still have the probe error. It goes through the motions - positions to each point - but them shows the "Error: Z probe already triggered at start of probing move" message and moves on to the next point.

mhackney

Got it - M574 E0 S0 deprecated in 1.16, now use M558 I1 in 1.17

So the probing works but it is incredibly slow. I read the docs on M558 and set travel and probe speed like:

M558 P4 X0 Y0 Z0 F25 H3 I1 T100

But it is still going incredibly slow to the bed after homing. Like 5 minutes or more to reach the bed.

Sniffle

Have you tried adding the FXXXX command to change the feedrate?

I know one of the probing commands is effected by the feedrate but not sure which.

dc42

@mhackney:

Got it - M574 E0 S0 deprecated in 1.16, now use M558 I1 in 1.17

So the probing works but it is incredibly slow. I read the docs on M558 and set travel and probe speed like:

M558 P4 X0 Y0 Z0 F25 H3 I1 T100

But it is still going incredibly slow to the bed after homing. Like 5 minutes or more to reach the bed.

That's fixed in 1.17RC3 which I hope to release later today. The default feed rate was being set to 1/60 of the intended value. Workaround: in your bed.g file you probably have a G1 command near the start to move the head to the vicinity of the first probe point. Add an F parameter to it.

mhackney

Great, thanks David. I now realize my "issues" above (except the odd heater one) was related to migrating from a 1.15 firmware to the new stuff. My board shipped with the 1.15. All of my other Duets I migrated firmware as it is released and actually read the release notes to implement any changes. Forgot to do that on this one in my excitement to update this new printer.

I actually don't have a G1 to position the head in any of my bed.g files. Perhaps its time to go through all of my config files and update to best practices. I did note that all of the example configs on Git are a year or more old. Is there a good recent set of example delta and Cartesian printer config files to use as examples somewhere?

ianlee74

I thought you were going to say you had the same issue I observed last night after loading 1.17RC2. Everything is working fine but it seems like it takes my hotend forever to get up to temperature now. It seems like its using a very linear ramp. I'll try re-running the auto PID tuning later and see if that gives it a better curve. Didn't feel like messing with it last night.

dc42

I haven't made any intentional changes to the heating control in RC2.