I could use some help
-
@fcwilt M564 H0 S0
-
@mac sounds more like a wire is loose on the X axis motor. Check your wiring.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@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 Fri Jun 24 2022 15:21:44 GMT-0700 (Pacific Daylight Time) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue 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 S0 ; physical drive 0.1 goes backwards M569 P0.2 S0 ; physical drive 0.2 goes backwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X32 Y32 Z32 E32 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 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 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 M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; 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 X-42 Y-16 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 S1 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"HotEnd" 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 M575 P1 S1 B57600 ; 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 -
@droftarts will do, thanks. Mac
-
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Jun 24 2022 15:21:44 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z5 F3600 ; lift Z relative to current position G1 H1 X225 Y225 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X-5 Y-5 F3600 ; go back a few mm G1 H1 X225 Y225 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X47 Y21 F3600 ; go to first bed probe point and home Z G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F60 ; lift Z relative to current position ;G90 ; absolute positioning -
; homex.g ; called to home the X axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Jun 24 2022 15:21:44 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z5 F3600 ; lift Z relative to current position G1 H1 X225 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X-5 F3600 ; go back a few mm G1 H1 X225 F360 ; move slowly to X axis endstop once more (second pass) G1 H2 Z-5 F3600 ; lower Z again G90 ; absolute positioning -
; homey.g ; called to home the Y axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Jun 24 2022 15:21:44 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z5 F3600 ; lift Z relative to current position G1 H1 Y225 F1800 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y-5 F3600 ; go back a few mm G1 H1 Y225 F360 ; move slowly to Y axis endstop once more (second pass) G1 H2 Z-5 F3600 ; lower Z again G90 ; absolute positioning -
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Jun 24 2022 15:21:44 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z5 F3600 ; lift Z relative to current position G90 ; absolute positioning G1 X47 Y21 F3600 ; 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 F60 ; lift Z relative to current position ;G90 ; absolute positioning -
@droftarts after reading through the code, I think you’re right. I did repair the red wire to X, so I’ll check that.
-
@mac Fixed your Gcode posts. You selected the 'list' format (three dots vertically next to three lines) rather than the 'code' format (like
</>). You can also edit your posts to fix them; click the three blue vertical dots on the right of a post, next to the upvote/downvote buttons, and select edit.Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@mac said in I could use some help:
after reading through the code, I think you’re right. I did repair the red wire to X, so I’ll check that.
The symptoms you describe do suggest a stepper wiring issue.
Frederick
-
@mac said in I could use some help:
@droftarts after reading through the code, I think you’re right. I did repair the red wire to X, so I’ll check that.
... though usually if a phase was disconnected you would get an error. It's possible that the DWC jog buttons are just trying to move the axis too fast. Try sending something like
G1 X10 F100for a short, slow move. This should move the X axis 10mm at 100mm/min, so take 6 seconds.The default for the jog buttons is 6000mm/min, or 100mm/sec. If you want to change this, it's in System > Machine specific > General tab, under 'Machine specific > Feedrate for move buttons'.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts Since my bed on the Y axis was behaving, I decided to change the X-motor's rotation to REVERSED also. When I tested it, that didn't go well the first time. I thought because I reversed the green and white endstop connector at the same time, that may have had something to do with the print head's back-and-forth behavior.
So I left the X-motor reversed, and changed the endstop wiring back. Now, GRN is white, and i05.in is green. Because of that, the x-motor's behaving. It appears that it's limited movement to the left (where the endstop is), has to do with where the board thinks the left of the bed is.
Can you tell me, once again, HOW to tell my board where the LEFT ENDSTOP for the X-AXIS is?
I'll assume that the process is the same for the Y and Z axis, and go from there?
Mac
-
@droftarts Because the X, Y, and Z motors are seem to be happy being reversed, my assumption is A) the wiring to the main connectors is backwards, and B) I need to change the EXTRUDER motor to REVERSED as well?
-
@droftarts So, I just switched to Console, and there's this message: 6/26/2022, 8:23.46 AM / Event / G28 X (new line) Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected
Lovely. That means the Y-axis motor has failed, right?
Mac
-
@droftarts false alarm, the Y motor's working, but it's stopping way short of the front of the printer. So it's doing what the X motor is doing. There's a clue in that, I think.
-
@droftarts okay, final update for today. I homed Y. It went all the way to the right (as far as it thinks it can go, I gather), and started coming down. When I looked at it head-on, I saw that the BLTouch was off the board (to the right). So, I turned the machine off.
Mac
-
@mac said in I could use some help:
Can you tell me, once again, HOW to tell my board where the LEFT ENDSTOP for the X-AXIS is?
The only thing you can do, with the current firmware, is to specify that the endstop is at the low end or the high end of the axis.
When you execute a G1 H1 move and the endstop sensor is activated the logical position of that axis is set to the axis min or max, as defined by the M208 values for that axis.
If the endstop is declared to be at the low end of the axis the min value is used.
If the endstop is declared to be at the high end of the axis the max value is used.
If, because of the actual location of the endstop sensor, the resulting logical position is not correct you have these options:
- adjust the position of the endstop sensor so it matches the M208 min or max value depending on the endstop being at the low or high end of the axis
- adjust the min or max value in M208 so it matches the position of the endstop sensor, again depending on the endstop being at the low or high end of the axis
- adjust the logical position to match the physical position using the needed combination of G1 moves and G92 setting of the logical position.F
Frederick
-
@fcwilt yep, that’s what it gets down too. I’m going to change the setting to what they were in the beginning: Low, instead of high, using RRF, and see how that goes.
-
@mac said in I could use some help:
@fcwilt yep, that’s what it gets down too. I’m going to change the setting to what they were in the beginning: Low, instead of high, using RRF, and see how that goes.
It's not guess work.
You know where the endstop is mounted, either at the min end of the axis, in which case the endstop setting is low, or at the max end of the axis, in which case the endstop settings it high.
And you can make a simple change like what via the DWC Gcode editor.
I believe you are encountering what some folks do when the use the configuration tool. It generates a complete set of files, which may or may not be correct. Folks install the files and hit homeall - and it doesn't work because of a wiring problem, bad part or configuration error.
The procedures I described for determining the max travel of an axis are part of checking the behavior of the printer step by step. And fixing each problem as you find one.
When I build a printer I take a very methodical, and perhaps boring, approach. One thing I will do is wire up one stepper at a time and verify it is working. Once all steppers are verified then I will move on the the endstop sensors. Again wiring up one at a time and verify it is working.
Frederick
