I could use some help
-
@mac
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jun 27 2022 12:50:38 GMT-0700 (Pacific Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Frankenstein's Cinderella" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z4000.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z600.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z200.00 E250.00 ; set accelerations (mm/s^2) M906 X600 Y600 Z600 E600 ; set motor currents (mA) M84 S0 ; Disable motor idle current reduction ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X220 Y220 Z240 S0 ; set axis maxima ; Endstops M574 X2 S1 P"!^io5.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !^io5.in M574 Y2 S1 P"!^io6.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io6.in ; Z-Probe M950 S0 C"io3.out" ; create servo pin 0 for BLTouch M558 P9 C"io3.in" H5 F120 T3600 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X15.875 Y0.625 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X5:190 Y5:215 S10 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S33 ; set temperature limit for heater 0 to 33C M308 S1 P"temp1" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S100 ; set temperature limit for heater 1 to 100C ; Fans M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 S"optional" D0 H1 F0 ; 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 ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
@mac said in I could use some help:
@fcwilt Y homes like it should. None of the + moves work. When I -10 it moves FORWARDS.
I understand about the jogging move.
And since it is wrong you need to change normal to reverse or vice-versa in the M569 for the Y stepper.
That should get jogging going in the right direction.
IF it does try homing Y
Frederick
-
@mac
; homex.g ; called to home the X axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jun 27 2022 12:50:38 GMT-0700 (Pacific Daylight Time) G91 G1 H1 X-230 F3600 G1 X15 G1 H1 X-10 F360 G90 G1 X110 F3600 ; this just moves X to the centerline of the bed - doesn't matter where - it can be any place at all that suits you. -
@mac
; homey.g ; called to home the Y axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jun 27 2022 12:50:38 GMT-0700 (Pacific Daylight Time) G91 G1 H1 Y-230 F3600 G1 Y15 G1 H1 Y-10 F360 G90 G1 Y110 F3600 ; this just moves Y to the centerline of the bed - doesn't matter where - it can be any place at all that suits you. -
This post is deleted! -
@mac
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jun 27 2022 12:50:38 GMT-0700 (Pacific Daylight Time) M98 P"homeZ.g" M98 P"homeX.g" M98 P"homeY.g" ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F60 ; lift Z relative to current position ;G90 ; absolute positioning -
@mac That's where the code for my Duet3D Mini 5+ is today. Thank you to @droftarts , @fcwilt , and @alankilian for all their valuable contributions to this effort.
-
@mac
6/27/2022, 2:06:04 PM G28 Z Error: Failed to enable endstops 6/27/2022, 2:05:32 PM Warning: Driver 0.0 warning: phase B may be disconnected 6/27/2022, 2:05:32 PM G28 X Warning: Driver 0.0 warning: phase B may be disconnected -
@mac said in I could use some help:
@mac
6/27/2022, 2:06:04 PM G28 Z Error: Failed to enable endstops 6/27/2022, 2:05:32 PM Warning: Driver 0.0 warning: phase B may be disconnected 6/27/2022, 2:05:32 PM G28 X Warning: Driver 0.0 warning: phase B may be disconnectedWell the warning about driver 0.0 would explain the noise and lack of proper movement.
Frederick
-
@mac said in I could use some help:
@mac
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jun 27 2022 12:50:38 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z5 F3600 ; lift Z relative to current position G1 H1 Z-245 F1800 ; move Z down until the endstop is triggered G92 Z0 ; set Z position to axis minimum (you may want to adjust this) ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F60 ; lift Z relative to current position ;G90 ; absolute positioningI don't get it, mac.
I give you code to try and you end up with something rather different.
I really do know what I am doing.
Frederick
-
@fcwilt I don't know how that happened, honestly. I absolutely don't remember seeing that in your code, or copying anything that looks like into my code.
Frankenstein's Cinderella, that's all I can suggest.
This extraordinarily long thread has the code you suggested in it. It was the first code you provided to me. I know where it is. So I will go and get it, and put it in the homez.g again.
Now we will see what happens.
-
@fcwilt @droftarts @alankilian
G91 ; relative movements G1 H1 Z-250 F3600 ; fast move toward Z endstop G1 Z10 ; backup off a bit G1 H1 Z-15 F360 ; slow move toward Z endstop G90 ; absolute movements G1 Z10 F3600 ; move to 10mm off the bed to allow X and Y movementsThis is the correct homez.g @fcwilt provided. I have no idea where that other code came from.
-
@mac said in I could use some help:
@fcwilt @droftarts @alankilian
G91 ; relative movements G1 H1 Z-250 F3600 ; fast move toward Z endstop G1 Z10 ; backup off a bit G1 H1 Z-15 F360 ; slow move toward Z endstop G90 ; absolute movements G1 Z10 F3600 ; move to 10mm off the bed to allow X and Y movementsThis is the correct homez.g @fcwilt provided. I have no idea where that other code came from.
You been drinking?
Anyway, have you changed the rotation of the Y stepper so the jogging operations move it in the right direction?
I'm still anxious to verify that the S setting is the problem there.
Frederick
-
@fcwilt I'm going to work on that now.
Mac
-
@droftarts @fcwilt @alankilian
In the config.g now:
M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwardsOur change:
M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S0 ; physical drive 0.1 goes backwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards -
@alankilian @droftarts @fcwilt
On the X-axis, the printhead's chattering up a storm. When I 119 it, this is what I get:
6/27/2022, 4:18:07 PM M119 Endstops - X: not stopped, Y: not stopped, Z: no endstop, Z probe: not stopped -
@Mac
; Endstops M574 X2 S1 P"!^io5.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !^io5.in M574 Y2 S1 P"!^io6.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io6.in ; Z-Probe M950 S0 C"io3.out" ; create servo pin 0 for BLTouch M558 P9 C"io3.in" H5 F120 T3600 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X15.875 Y0.625 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X5:190 Y5:215 S10 ; define mesh gridI guess the X-motors toast.
6/27/2022, 4:13:45 PM G28 X Warning: Driver 0.0 warning: phase B may be disconnected -
@mac
It's more likely just a bad connection.
Did you get a chance to change the rotation of the Y axis and then test jogging?
Frederick
-
; Endstops M574 X2 S1 P"!^io5.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !^io5.in M574 Y2 S1 P"!^io6.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io6.in M574 Z2 S1 P"!^io2.in" ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin !^io2.inI pulled the connector off of Driver_0, and put a short length of wire in the first two holes, then the second two holes. When I turned the X-motor, both phases resisted my efforts. So the phases are both there, but I guess that doesn't mean much?
Above is a change I made. The listing for the Z-endstop disappeared, I guess (I don't know). So I re-entered it, saved the config, and there it is now.
6/27/2022, 4:50:03 PM M119 Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped 6/27/2022, 4:50:01 PM M119 Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped 6/27/2022, 4:49:54 PM M119 Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped 6/27/2022, 4:44:54 PM Connection established 6/27/2022, 4:44:48 PM Connection interrupted, attempting to reconnect... HTTP request timed out 6/27/2022, 4:44:36 PM Upload of config.g successful after 0s 6/27/2022, 4:40:53 PM M119 Endstops - X: not stopped, Y: not stopped, Z: no endstop, Z probe: not stoppedYou can see by the entries in the Console that the Z-endstop is now present (again). On the lowest line you can see that there was "no endstop" previously.
Mac
-
@mac
Good, glad to hear the Z endstop is back.
As I recall (or maybe I'm wrong) that you had some problems getting good crimps?
Can you verify that the connector that plugs onto the Duet has good crimps for each wire?
Does the stepper have a connector mounted on it for plugging in a cable OR are the wires part of the stepper?
Also, can you please change the rotation of the Y stepper in config.g and see if the Y jogging now works as it should?
Thanks.
Frederick
