I think it is the big squarish IC (that's the CPU right?) anyway, I do think I have accidentally short circuit the board probably that explains why. maybe a nice insulated case will be a good add on
thanks for replying me though! always appreciate it!
If the wires come directly out of the stepper motor (no connector on the motor itself) then you can rely on red and blue being one phase, and green and black the other. So put red and blue at one end of the 4-pin connector on the Duet, and green and black on the other. I use the order red-blue-green-black.
If there is a 6-pin connector on the motor and the wires plug into that, then you can't rely on the colours because different motor manufacturers use different pinouts on the connector. So you need to establish which pairs are phases. Here are 2 easy ways:
Use a multimeter. A pair of wires with continuity between them (a few ohms resistance) is a phase. There should also be continuity between the other pair of wires (the other phase).
Spin the shaft with your fingers. Then short 2 of the wires together and spin it again. If the shaft is much harder to spin with those 2 wires shorted, then those 2 wires belong to the same phase.
Please check that baud rate is configured correctly on both, duet and PanelDue.
You can add this line to config.g file : M575 P1 B57600 S1 to configure duet and check baud rate on Paneldue in settings screen.
@dc42 said in I think my Duet and/or Duex5 is/are dying:
................ The I2C driver has been completely rewritten since the 2.02RC version that you are using.
Oh really? Since RC4? I must have missed that.
Thanks - I'll give it a try.
@phaedrux said in Wiring a NF-A4x20 FLX Noctua:
Even the FLX should work with the Duet PWM.
It does. I'm using a NF-A4x20 FLX.
When I first installed it I had to up the M106 PWM frequency to F5000 to work at lower percentages.
Just connect the red and black and set M106 frequency to 5000.
My guess is that you are running 2.02 beta firmware. We introduced the motor disconnected warning in the 2.02 beta series, but we didn't get it quite right until late in the beta cycle. So if the M115 command confirms that you are running beta or RC firmware, upgrade to the 2.02 release.
@jamesadoty said in Duet 2 Wifi Tronxy X5SA Z probe setup:
Should I disable z end stop in config.h? I have it set to standard NO switching.
You mean in config.g? Yes, assuming you use a G30 command in your homez.g and homeall.g files to home Z. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z.
Yes, the Duet/RepRap is easily configured for open or closed.
I am a very strong believer in Nclosed (and wired in series if there is more than one). This detects failed switches, broken wires, loose connections in so many ways that Nopen does not.
(It is late, I'm tired, and I hope I typed that correctly, not backwards... you get the drift).
@dc42 said in Duet Wifi + Ender 3: cooling with stock electronics box:
@3dmntbighker said in Duet Wifi + Ender 3: cooling with stock electronics box:
I have a Pro with a Maestro. I just stuck a blower fan on top pulling air out around the driver area under the Duet. I drilled a hole in the top since the Pro has the vent on the bottom, and the board mounts upside down. My board NEVEr reports over 40C so far. So as DC says, you probably don't need a fan at all. The Ender doesn't tax the board.
The advice I gave was specifically for the Duet WiFi (or Duet Ethernet). The drivers on the Maestro get hotter than those on the WiFi/Ethernet, so I can't say that you don't need a fan for a Maestro driving an Ender 3. My guess is that if the currents are set to no more than 800mA then it may be OK without a fan.
Please note, the CPU temperature reported by the Duet needs to be calibrated before you rely on it. There is a wiki page about this.
Yeah, I have nothing over 800. And my board mount channels air past the driver area where my blower fan pulls the air out. Mine is probably over kill. As for calibration, I just watch the increase from ambient If it's 22 at power on and never exceeds 40 I'm pretty sure I'm good.
Well, I deleted my config.g override, and changed to p8. It stopped travel.
Changed back to p5, seems to be working now.
Odd, nothing in the config override should have been doing anything, but it seems to be working now.
Thanks for all your help @dc42
Looks like your connection to Duet3D was lost, please wait while we try to reconnect.