Update :

Working on Duet 0.8.5 with release 1.19alpha2

The F parameter only takes into account XYZ movements, the U axis now adapts it's speed to be completed on time.

(But if U max acceleration is too low, it will still slow down the overall movement, adjust it with M201 command)

THANKS DC42 !

Update: So just for the heck of it I decided to remove the I1 from the M558 command and now it is working.

What I am using.
; Z Probe
M558 P1 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
G31 P500 X0 Y-19.5 Z1.497 ; Set Z probe trigger value, offset and trigger height

Thanks for the explanation, David.

I will make the suggested changes.

John

Thanks for sharing!

PM'd you on reprap but Ill send another in light of this thanks.

Thanks Dougal1957 - will do.

I think things are looking better. I took everything apart once again in all 3 towers. Stripped the belts, idlers, steppers, all of it.

Found two possible things… one, my pulleys on my steppers weren't as well aligned as they could have been. Adjusted that, which cleaned up the belt path. (They weren't bad, just a tick off)

The other is the Z stepper wiring was directly laying on top of my 12v PSU's output ports. Not sure it was definitely getting any interference, but it's probably something to avoid. The first layer looks better now, so it's promising that was it. Need to run through a few prints to see.

The links to all the source files are on the wiki:

https://duet3d.com/wiki/Source_Files

The Ethernet files on github are for the Ethernet module, I have updated the wiki page to make that clearer.

If you have a look here:
https://duet3d.com/wiki/Hardware_overview

You will see that the Wifi/Ethernet modules are mounted on the Duet main board.

The Duet 0.8.5 is an older design.

Got it, thanks.

Then I will use 2 on the Y/U axis, 1 on the X axis, and I'll use the IR probe on the Z axis.

For the Z axis, I'll home in the center, use the M584 trick to split the Z axis into 4 channels.

Then move the Z probe over 4 corners, and re-home each corner.

M584 to join the 4 steppers into Z axis again, and home in center to set Z height.

Yes to all! Thanks. And after tuning it is not an issue. Thanks

I found the problem 🙂
I've used "M570 S999" command in config.sys, but this command is only valid for ver 1.14 or earlier.
The first attempts the printer was stopped because the heater temperature drops more than 10 C.
Later attempts failed, with increased M570 P and T parameters, because the printer time out after 999 seconds (with unspecified heater…:-O ).
The strange thing now is the heater temperature are stable close to 250 C when I'm printer ABS.... but I don't care to found the main reason or faults behind the earlier temperate drops, because the printer works perfect now 🙂
Thanks DC42 !

It looks like it could be an overextrusion issue. I would calibrate the extruder and maybe up your motor currents if you hear or see the xy motors skipping. Zwobble is also another likely problem. I would look up your printer and z wobble fixes and check them out.

Hope this helps

Looks like there is an issue with the bed temp channel. Please contact your supplier.

@NoSkillzEngineer:

Hmm sooo would I destroy something if it was….hypothetically....on 5V for a couple seconds....or minutes?

Possibly, the touch driver chip on the panel is rated at 3.6V absolute maximum. Although I've heard of a user getting away with running a 3.3V display with the jumper set to 5V before. In any event, it sounds to me that the touch panel or touch driver chip on the TFT panel is faulty.

I've no idea if that would work. We did make a few Duet WiFi prototypes using ESP-07 WiFi modules which have an antenna socket.

Must be gremlins…..seems to suddenly be working!

Ok, thank you for all the assistance, both in my case here, and for all the great assistance you all have provided for others. It is greatly appreciated

@DjDemonD:

I am still getting what appear to be uncommanded tool changes happening despite removing any T commands from my gcode, which is making printing with one material (using my second extruder) difficult to say the least.

For compatibility with slicers that don't handle tool switching properly, an M109 command with a T parameter will cause a switch to that tool in recent versions of RRF. So check your gcode for M109 commands.