Unexpected U Axis Homing Before Prints
-
I'm working on a custom machine that has a few additional axes outside your standard cartesian printer. However, I can't figure out why my U-axis goes to the end of its axis before every actual print. I played around with the print file, the homing file for that axis (homeu.g), homeall.g, and my config.g to no avail. Hoping for an extra set of eyes on things as to what might be causing it.
;start of actual print file M107 M104 S210 ; set temperature G28 ; home all G1 Z5 F5000 ; lift nozzle ; Filament gcode M109 S210 ; set temperature and wait for it to be reached G21 ; set units to millimeters G90 ; use absolute coordinates M82 ; use absolute distances for extrusion G92 E0 G1 Z0.200 F9000.000; HOME U M400 M913 U50 ; drop motor current to 70% M400 G91; relative positioning G1 H1 U700 F40000 ; move quickly to U axis endstop and stop there (first pass) G1 H2 U-29 F40000 ; move quickly to backwards G90 ; absolute positioning M400 M913 U100 Y100 ; return current to 100% M400; config.g file ; Endstops M574 X1 S3 ; configure sensorless endstop for low end on X M574 Y1 S3 ; configure sensorless endstop for low end on Y M574 U1 S1 P"e0stop" ; configure switch-type (e.g. microswitch) endstop for low end on U via pin estop M574 V1 S3 ; configure sensorless endstop for low end on V M915 X Y R0 F0 S5 ; configure stall detection for X and Y M915 V R0 F0 S40 ; configure stall detection for V M915 V R0 F0 S5 ; configure stall detection for Z -
Sorry but I don't understand.
At the start of a print you are homing all. That would include the U axis.
Frederick
-
@fcwilt yeah it's kind of weird to explain, but maybe part of my confusion too. My G28 command does correctly home all the axes. However, right when the nozzle reaches the set temperature and the print starts the U axis moves again and goes to its end stop (which is not at home) and stays there the remainder of the print until I inevitably abort. Hopefully that helps describe the issue a little better
-
@jrcl What happens if you run homeall stand alone rather than as part of a print? Does the U axis stay in the correct position? If so, then the fault is elsewhere. Can you post your entire homeall.g and your entire configuration file(s) including config-override.g if you use it.
-
@deckingman If I run home all or home U it doesn't do it, so I agree I figured it was likely configuration based too. However, I haven't looked at the config-override yet! I'm new to this all and frankly, I'm not familiar with that file so much but it looks like maybe that is my issue. Here it is though with my home all:
; Home All M98 P"homev.g" M98 P"homeu.g" M98 P"homex.g" M98 P"homey.g" M98 P"homez.g"; Configuration file for Duet WiFi (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sun Jan 09 2022 20:46:24 GMT+0100 (Централноевропейско стандартно време) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"RL1 Proto" ; set printer name ; Network M551 P"SkiBum98" ; set password M552 S1 ; enable Wifi M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards (eventually X) M569 P1 S1 ; physical drive 1 goes forwards (eventually Y) M569 P2 S1 ; physical drive 2 goes forwards (eventually Z) M569 P3 S1 ; physical drive 3 goes forwards (eventually E) M569 P4 S0 ; physical drive 4 goes backwards (eventually U) M569 P5 S1 ; physical drive 5 goes forwards (eventually V1) M569 P6 S0 ; physical drive 6 goes backwards (eventually V2) ; Motor Speeds and Accelerations M584 X0 Y1 Z2 E3 U4 V5:6 ; set drive mapping M350 X16 Y16 Z16 E64 U16 V16 I0 ; configure microstepping without interpolation M92 X80.00 Y80.00 Z400.00 E80.00 U400.00 V80.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 U60.00 V900.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 U180.00 V6000.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 U20.00 E250.00 U20.00 V500.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 U800 V 800 I100 ; set motor currents (mA) and motor idle factor in per cent ; Axis Limits M208 X0 Y0 Z0 U0 V0 S1 ; set axis minima M208 X135 Y135 Z200 U700 V400 S0 ; set axis maxima ; Endstops M574 X1 S3 ; configure sensorless endstop for low end on X M574 Y1 S3 ; configure sensorless endstop for low end on Y M574 U1 S1 P"e0stop" ; configure switch-type (e.g. microswitch) endstop for low end on U via pin estop M574 V1 S3 ; configure sensorless endstop for low end on V M915 X Y R0 F0 S5 ; configure stall detection for X and Y M915 V R0 F0 S5 ; configure stall detection for Z ; Z-Probe M950 S0 C"duex.pwm1" ; Duet 2 WiFi/Ethernet + DueX2/5 M558 P9 C"^zprobe.in" H5 F120 T6000 ; Duet 2 WiFi/Ethernet, DueX2/5 G31 P500 X25 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 D5 ; disable bang-bang mode for heater and set PWM limit M308 S2 P"e1temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H2 C"e1heat" T2 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H2 B0 S1.00 ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; tool 0 uses extruder drive 0, heater 1 and fan 0 (part cooling fan) G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 H2 G10 P1 X0 Y0 Z0 G10 P1 R0 S0 ; Epilogue M556 S100 X0 Y0 Z0 ; Put your axis compensation here M912 P0 S0 ; Put your CPU temperature sensor correction here M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool; config-override.g file generated in response to M500 at 2022-04-10 14:40 ; This is a system-generated file - do not edit ; Heater model parameters M307 H1 R3.382 C178.444:87.318 D4.85 S1.00 V24.2 B0 I0 M307 H2 R2.429 C140.000:140.000 D5.50 S1.00 V0.0 B0 I0 ; Workplace coordinates G10 L2 P1 X0.00 Y0.00 Z0.00 U0.00 V0.00 G10 L2 P2 X0.00 Y0.00 Z0.00 U0.00 V0.00 G10 L2 P3 X0.00 Y0.00 Z0.00 U0.00 V0.00 G10 L2 P4 X0.00 Y0.00 Z0.00 U0.00 V0.00 G10 L2 P5 X0.00 Y0.00 Z0.00 U0.00 V0.00 G10 L2 P6 X0.00 Y0.00 Z0.00 U0.00 V0.00 G10 L2 P7 X0.00 Y0.00 Z0.00 U0.00 V0.00 G10 L2 P8 X0.00 Y0.00 Z0.00 U0.00 V0.00 G10 L2 P9 X0.00 Y0.00 Z0.00 U0.00 V0.00 -
@jrcl said in Unexpected U Axis Homing Before Prints:
G1 H2 U-29 F40000 ; move quickly to backwards
Remove the H2. It may be hiding an error message if the homing has actually failed.
Can you post a sliced gcode file so we can see what happens at the start of a print?
Are you using start.g?
Can you send M122 and M98 P"config.g" and post the results?
@jrcl said in Unexpected U Axis Homing Before Prints:
V 800
You have a space between the V and 800 in your M906 command.
-
@jrcl your config.g file indicates that you have a U axis minimum endstop, but your G1 H1 U move in homeu.g homes towards axis maximum. So one of those is wrong.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
This post is deleted! -
@dc42 This did it!!!!
thank you so much, an H2 instead of an H1 solved the issue -
@jrcl said in Unexpected U Axis Homing Before Prints:
@dc42 This did it!!!!
thank you so much, an H2 instead of an H1 solved the issueWhat about the problem mentioned regarding the specified position of the endstop and the homing code moving the wrong way?
And where did you change H1 to H2? That should not have solved the problem.
Thanks.
Frederick
-
@jrcl said in Unexpected U Axis Homing Before Prints:
H2 instead of an H1 solved the issue
Nope. That may hide the issue.
