Posts made by mlbuxbaum

Well, dont I feel like a real idiot.........The red wire on the E0 connector that plugs into the Duet was broken inside the connector. I found when I was moving the connector to E1.....

@dc42 thank you

@dc42 said in Extruder "fighting" itself?:

@mlbuxbaum said in Extruder "fighting" itself?:

I have the wires directly connected together, and it was working prior to yesterday when I uploaded firmware again. I have also tried 3 separate steppers. Can I use extruder 2 to test? How do I activate that driver and set it up in firmware?

Look up M584 in the GCode wiki page.

That didnt help much.... anyway.
How is the duet output color codes? green/black=coil 1 and red/blue=coil 2?

@dc42 said in Extruder "fighting" itself?:

@mlbuxbaum said in Extruder "fighting" itself?:

hooked wires up directly, bypassing terminal block connector and still getting the "fighting" Could this be a firmware issue?

Unlikely unless you have set the acceleration or speed much too high. It sounds like a bad connection, faulty motor or a blown driver. Your reading of .887Mohms definitely means you had a bad connection or a faulty motor at that point. Can you test the driver by connecting a different motor to it, using a different cable?

I have the wires directly connected together, and it was working prior to yesterday when I uploaded firmware again. I have also tried 3 separate steppers. Can I use extruder 2 to test? How do I activate that driver and set it up in firmware?

hooked wires up directly, bypassing terminal block connector and still getting the "fighting" Could this be a firmware issue?

just checked impedance on the stepper while still connected to the DUET. Coil 1 reads .887MΩ and coil 2 reads 1.2Ω. Think my driver is bad? I checked the stepper motor and both measure the same impedance.

My extruder stepper seems to be fighting itself (grinding and not turning) I have the stepper wired directly to the DUET board and double checked that I have each coil wired together, and that i have those coils wired to the black & green (coil1) and the red & blue(coil2) respectively. Any idea what my issue could be, I am thinking it is a firmware issue.

new issue….
when i load an .stl file and try to print, the connection terminates.

Added the S2 command to those files….
homed x - no error
homed y - no error
homed z and....

G28 Z

Error: G0/G1: insufficient axes homed

however when I use Home All
no errors and homes great

I added S2 to the homez file and seems to work fine now

thank you

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Fri Feb 16 2018 11:11:03 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X-13 Y3 F6000 ; go to first probe point
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool on Fri Feb 16 2018 11:11:03 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 S2 Z5 F6000 ; lift Z relative to current position
G1 S1 Y-305 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 S1 Y-305 F360 ; move slowly to Y axis endstop once more (second pass)
G1 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Fri Feb 16 2018 11:11:03 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 S2 Z5 F6000 ; lift Z relative to current position
G1 S1 X-305 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 S1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
G1 Z-5 F6000 ; lower Z again
G90 ; absolute positioning

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Fri Feb 16 2018 11:11:03 GMT-0500 (Eastern Standard Time)
G91 ; relative positioning
G1 S2 Z5 F6000 ; lift Z relative to current position
G1 S1 X-305 Y-305 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-305 ; home X axis
G1 S1 Y-305 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
G1 S1 Y-305 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X-13 Y3 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
;G1 Z5 F100 ; uncomment this line to lift the nozzle after homing

thank you. Updated the web interface and now to test… still getting errors.
7:37:08 AM G28 Z
Error: G0/G1: insufficient axes homed
7:37:06 AM G28 Y
Error: G0/G1: insufficient axes homed
7:36:58 AM G28 X
Error: G0/G1: insufficient axes homed

.

But we also have:

"Added M564 H0 command to allow axis movement before homing on Cartesian/CoreXY printers"

So I'd guess that adding that M564 H0 to your config.g will restore the printer back to it's previous behaviour.

Where do I add this in my config.g file?

cool cuz its at -43 now…....i moved it closer.
Also with regards to this in the 1.21 RC5 update
On Cartesian and CoreXY printers, normal G0 and G1 moves are no longer allowed before the corresponding axes have been homed. In particular, if your homex.g, homey.g and homeall.g files raise Z a little at the start and lower it at the end, you will need to add the S2 parameter to those G1 Z moves. Otherwise the G1 Z move will be refused unless Z has already been homed and the homing macro will be terminated.

would that be like this?
G1 S2 Z5 F6000 ; lift Z relative to current position

It was G1 Z5 F6000
getting errors about homing now, and z axis doesnt stop when endstop is triggered.

M120
G91
G1 Z-1 F6000
M121
Error: G0/G1: insufficient axes homed
Error: Pop(): stack underflow!

com port was shut down for some reason….changed com port and I can connect now.
Is = WiFi signal strength -38dBm, reconnections 0, sleep mode modem okay?

changed and still no response back from Duet

yes it shows up in device manager, YAT says serial port COM15 is open and connected. I dont kow what LINE END SEQUENCE is.