@phaedrux
Thanks phaedrux. BTW it is cartesian I designed for IDEX, I only have one X head setup on it for now though.
Posts made by keith
-
RE: motor phase A may be disconnected reported by driver(s) 1
-
RE: motor phase A may be disconnected reported by driver(s) 1
@dc42
NEMA 17.
1.8° Step Angle.
200 Steps Per Revolution.
1A Phase.
0.48Nm Holding Torque.
40mm Body.
19mm Output Shaft (5mm diameter)
750mm wire lead with Molex connectorMotor current set to .8 amp.
I think I have it sorted out. One of the wires in the cable has a short. I cut the connectors off and checked the wires without any connectors which is surprising considering the Y axis motor and motor wires never move. I might expect a wire to wear down on something like the direct drive motor over time but not the Y axis. Seems to be working now with a new cable. What Molex connectors are these? I want to order some backup connectors.
-
RE: motor phase A may be disconnected reported by driver(s) 1
@phaedrux
I hope its not the board. I really like the Duet2Wifi. I just don't have the tools here so I'll have to look at it again tomorrow. Tried 3 different LDO motors that I know work and it's all the same, so I'm thinking a bad wire somewhere since it did the same thing on the E1 driver. -
RE: motor phase A may be disconnected reported by driver(s) 1
@phaedrux
Yea all the same issues. But it's acting like a bad connection. I'm thinking there has to be bad wire somewhere even though all the connections look good. I'll deal with it tomorrow. -
RE: motor phase A may be disconnected reported by driver(s) 1
@phaedrux
Hmm same issue. The motor gets jerky and the Y fails to home. -
RE: motor phase A may be disconnected reported by driver(s) 1
@phaedrux
Duet2Wifi.
There is no M584 command. Everything above that is for wifi network.
That's what the RepRap configurator gave me. -
RE: motor phase A may be disconnected reported by driver(s) 1
@phaedrux M586 P1 S0 ; Disable FTP
; Drives
M569 P0 S0 ; Physical drive 0 goes backwards
M569 P1 S0 ; Physical drive 1 goes backwards
M569 P2 S1 ; Physical drive 2 goes forwards
M569 P3 S1 ; Physical drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E415.00 ; Set steps per mm
M566 X600.00 Y600.00 Z60.00 E300.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z600.00 E6000.00 ; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z120.00 E5000.00 ; Set accelerations (mm/s^2)
M906 X700.00 Y800.00 Z800.00 E500.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X235 Y235 Z250 S0 ; Set axis maxima; Endstops
M574 X1 Y1 S1 ; Set active high endstops; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P500 X-28 Y5 Z0.80 ; Set Z probe trigger value, offset and trigger height
M557 X10:220 Y25:220 S65 ; Define mesh grid; Heaters
M305 P0 T98801 B4185 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T98801 B4185 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C; Fans
M106 P0 S0 I0 F20 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0 I0 F20 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S0 I0 F20 H1:0 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 S"Hotend" D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C; Automatic power saving
M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss; Custom settings are not configured
; Miscellaneous
M501 ; Load saved parameters from non-volatile memory
T0 ; Select first tool -
RE: motor phase A may be disconnected reported by driver(s) 1
@phaedrux I looked at that. Not sure what stepper motor number to put for Y is it just YE1 ?
-
RE: motor phase A may be disconnected reported by driver(s) 1
@phaedrux already tried a couple of different motors. Not sure how to use the extra extruder stepper for the Y-Axis.
-
motor phase A may be disconnected reported by driver(s) 1
@dc42
My printer has been working fine for a few weeks now. All of a sudden (because stuff always happens suddenly) my Y-axis is making a horrible noise and I'm getting this warning---motor phase A may be disconnected reported by driver(s) 1I checked the wiring and connections. All good. Is this a bad stepper? Hope this is still under warrantee because this is the second board Filistruder has sent me. The first one had a bad EO stepper. I'm starting to have buyers remorse.
-
RE: Cura 4.2.1 to Duet2Wifi plugin problem.
@droftarts Heh, I keep scrolling past the start. Thanks for the help Ian.
-
RE: Cura 4.2.1 to Duet2Wifi plugin problem.
@droftarts Did Cura spit that out with Marlin or RepRap? Which are you using now Marlin or RepRap? I'm building an IDEX not sure which slicer I'll be using.
-
RE: Cura 4.2.1 to Duet2Wifi plugin problem.
@droftarts well that worked. It's odd though. I got the Chamber Heater warning only when using the plugin to send g-code to the Duet board. If I uploaded the g-code manually from Cura 4.2.1 to the Duet I got no Chamber Heater warning. When I activated the Build Volume Temp in Cura it was set to 28, changed it to 0, and now the plugin seems to work without the warning.
-
RE: Cura 4.2.1 to Duet2Wifi plugin problem.
@droftarts I'll give it a try when this print is finished. Wonder why they added it by default, unless all Ultimaker Printers have heated chambers?
-
Cura 4.2.1 to Duet2Wifi plugin problem.
This seems to be a problem with the Duet2Wifi plugin for Cura. I get a Chamber Heater not connected warning only when I use the plugin to send the gcode to the Duet2Wifi. It's like this plugin is adding a chamber heater but I don't have it in my Cura start or stop gcode setting, nor do I have it activated on my Duet2Wifi. Normal slicing and transfer to the Duet by manual upload works fine. It's only when using this plugin to send to the gcode to the Duet that I get this chamber heater warning.
-
RE: New BLTouch not triggering.
@gtaman
Thanks gtaman
That was mostly right. I left the meter long extension in and upon inspection, the Dupont connector on the BLTouch end of the meter long extension had a couple of broken tabs. I like that the BLTouch comes with spare Dupont connectors. Working now. -
New BLTouch not triggering.
Received a new replacement Duet2Wifi board and everything is working, except for the BLTouch. I have tried two different BLTouch's and I am having the same problem with both. When homing Z the probe touches the bed, retracts, then extends again and acts like it is in error mode, while the Z continues moving down to the bed.
M280 P3 S160 I1 resets the error mode.
M280 P3 S120 I1 Self test works.
M401 will extend the probe.
M402 will retract the probe.
It is wired as described in: https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probeconfig.g; Z-Probe
M574 Z1 S2
M307 H3 A-1 C-1 D-1
M558 P9 H5 F120 T6000 R0.2 Note: I've tried setting P9 to P3.
G31 P500 X-28 Y5 Z2.1
M557 X10:220 Y10:220 S40deployprobe.g
M280 P3 S10 I1homeall.g
G91
G1 Z5 F6000 S2
G1 S1 X-240 Y-240 F1800
G1 X5 Y5 F6000
G1 S1 X-240 Y-240 F360
G90
G1 X38 Y20 F6000
G30homez.g
G91
G1 Z5 F6000 S2
G90
G1 X38 Y20 F6000
G30retractprobe.g
M280 P3 S90 I1What am I missing?