thank you for your answer,

What I meant was that I tried on a corporate network and it didn't work, so I tried on my home network and it didn't work either. So I changed my DUET IP address to 192.168.1.202 and now DWT works fine.
Thank you for your reactivity and your precise answers.

Timothyz is spot on. Step/Dir is the interface to external drivers. The section in the WiKi is short because the interface is simple, and "just works".

He is also correct that the built in drivers are likely better, AND the firmware has SPI access to them, so it can set current, detect faults, etc.

Can you link to the motors, and particularly the drivers, so we can look at them in more detial?

Commanding movement to the drivers won't work unless you can specify both speed and acceleration, because the movement of the axes and the extruder all need to be synchronised. This generally means that one of the drivers will be moving at full acceleration but the other won't be.

I guess you could use the built-in homing function by changing the homing file to temporarily map the axis being homed to a non-existent driver, using M42 to send the homing signal, then commanding the homing move. If you connect the "homed" signal from the driver to the endstop input, then the Duet will know when the axis is homed.

figured it out, it was also a strange setting that was in simplify3d. printing well so far, the true test will start tonight.

It sounds to me that the processor has been damaged. The symptoms you describe (overheating processor and L7 failed) suggest there was a short between the VSSA side of a thermistor connection, and a heater or fan wire. I've heard of this happening a number of times on Duet 06 and 085 boards. That's why we added protection to the VSSA line on the Duet WiFi/Ethernet.

If you just want to use the E1 motor output to drive the Z motor in place of of the Z motor output, all you need is M584 X0 Y1 Z4 E3 in config.g. Put it before any M350 or M906 commands. Also, if you have a M569 P3 line in config.g, change P3 to P5 in that line.

As I said "in the order you create them". Wouldn't it be less error prone if the endstops inputs are assigned based on the actually used drivers? Because that was my mistake... I already had axis X, Y, Z and dummy U for slave Y and tried "inserting" W before U in M584 and gantry squaring stopped working!

I fixed it by swapping completely the mapping for axis U and W while I should have just moved the endstop for axis U! Doesn't come "naturally", really!

Please post your bed.g file, and the GCode commands that do the purging if they are in a different file.

Does the problem still occur if you don't do the purge?

I updated to 1.21, and saw a message that the G3 was outside limits.
After updating the printable radius all is good. Sorry for the noise.

Your E acceleration in the M201 command is 10000 which is much too high. Try reducing it to 1000 or less.

What is the specification of the Z stepper motors on the CR10? If they are low current high inductance motors, they may need to be connected in parallel instead of in series (the Za and Zb motor connectors are wired in series).

Last time I used much in the RC world it was racing model cars when it was still 27mhz and brushed DC motors! 😄

Thinking on it that was about 22 years ago! Did have a car project with 4 mini bldc motors but it got shelved when a full sized car project came along. I'll remember your comments though as that would have caught me out!

The photo is a bit out of focus so it's hard to tell, however it looks to me that TR5 has an indentation towards its right hand side which is typical of a blown mosfet. I can't tell whether the others have or not. If you are using a phone camera, try holding the phone a little further away to get the mosfets in focus, then use zoom.

Are they ordinary brushless DC fans, or some other type? Have they ever been connected to the fan outputs with the wrong polarity?

Spot on guys, all fixed and up and running.

Thanks for the speedy help!

@brisma

......or another option (but this might be a bit extreme for you) is to do what I do and use a mains powered bed heater. Then you can use a much smaller, fan less power supply (which of course is totally silent).

I found here on google, but the info is there:
https://forum.duet3d.com/topic/860/dual-z-axis-endstops/14

If you mean that you have connected the latser module power input directly to the E1 heater output, I don't recommend that. The laser module may not like having PWM applied to its power input.

k thanks guys!

@nraynaud said in 12V on duetwifi + duex5:

Thanks you all.

dc42> may I suggest you break out the 12V with an actual 2A capable connector for the next revision? This is a really compelling power rail.

Already done!