Hi Pascal
Please email info@duet3d.com referencing this forum thread and we will arrange a warranty replacement.
Done, thx 4 your support.
Regards
Pascal
Hi Pascal
Please email info@duet3d.com referencing this forum thread and we will arrange a warranty replacement.
Done, thx 4 your support.
Regards
Pascal
Hi DC42,
M906: the current is set to 1000
M913: Says 100%
Stepper Motor is Wantai 0.9° with 1.7 amps
The Z motor works on Y and X axis, and the X and Y axis motors will not work on Z axis. The driver of Z Axis is hot as f…. and I burned my finger in Idle mode. The Duet wifi has been purchased directly by duet3d.com under order number 672.
Hi folks,
I´m using my wifi since a few month now, 1 or 2 hours per day, not much and no 24H prints. Today my Z driver stoped working. My last print yesterday was a small 45mins BLTouch attachment. I did no changes on the wifi board, just deaktivated the printer und tried to print this morning. Without success. The Z axis is complety dead. I tried to plug in the Z motor in the y axis: The motor works. The Y motor wont turn on the z axis.
Is the board unusable or is there any workaround or warranty?
The printer is a Delta printer with heated bed and prometheus hotend.
Hif Folks,
two weeks ago I received my new Duet Wifi Board and I'm really happy with it, except of one problem: I really kills my fans on pwm sockets.
I bought 3 new fans in a row of one week now (24V), testet them on the always on fan socket. Everything worked fine as long as it is on always on socket. On PWM fan 0 to 2 it only works until restart. (pwm set to 255). As soon as I disconect the device from power and restart, the fan is completely dead and even does not work an the always on socket.
This hapened to three completely new fans, and I guess this would also happen to the fourth fan if I do not find the root cause. I thought this might be a dead mosfet, but in this case, the fan will not be dead, but always on or would work on the always on socket.
Any suggestions?
P.S. 192.168.178.49 does not work on my android device but on windows, is this a known issue?