@dc42 thanks for the reply. I'm using the laser / vfd on out 9. I'm measuring it from the pwm input terminals on the converter.
If there is something you have to suggest that would be great. The further I got into it I discovered it might not be an issue but I have some other weird things going on with the vfd that I need to get figured out before I could even know.
Has it been an issue with the other reports of the converter not reaching 10v?
Im trying to connect a vfd to out 9 using this pwm converter https://www.amazon.com/dp/B091B6LGXB?ref=ppx_yo2ov_dt_b_fed_asin_title
When i measure the pwm signal it is only putting out 3.8 volts when i turn the spindle on at the max rpm of 24,000. The voltage out is only getting to 9V.
; Configuration file for RepRapFirmware on Duet 3 Main Board 6HC
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Sep 09 2024 22:47:07 GMT-0600 (Mountain Daylight Time)
; General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"Duet3CNC" ; set hostname
M453 ; select CNC mode
; Accessories
M575 P1 S0 B57600 ; configure PanelDue support
; Smart Drivers
M569 P0.0 S1 D2 ; driver 0.0 goes backwards (X axis)
M569 P0.1 S0 D2 ; driver 0.1 goes backwards (Y axis)
M569 P0.2 S1 D2 ; driver 0.2 goes forwards (Z axis)
M569 P0.3 S1 D2 ; driver 0.3 goes forwards (U or Y2 axis)
M569 P0.4 S1 D2 ; driver 0.4 goes forwards (V or Z2 axis)
; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S1000 ; set motor current idle timeout
; Axis
M669 K0 ; set Cartesian kinematics
M584 X0.0 Y0.1:0.3 Z0.2:0.4 U0.3 V0.4 P3 ; U=Y2 V=Z2 set axis mapping
M350 X16 Y16 Z16 U16 V16 I1 ; configure microstepping with interpolation
M906 X1205.2 Y1100.4 Z1100.4 U1100.4 V1100.4 ; set axis driver currents
M92 X100.067 Y100.067 Z400 U100.067 V400 ; configure steps per mm
M566 X60 Y60 Z60 U60 V60 ; set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z3000 U12000 V3000 ; set maximum speeds (mm/min)
M201 X600 Y600 Z60 U600 V60 ; set accelerations (mm/s^2)
; Axis Limits
M208 X0 Y0 Z-100 U0 V-100 S1 ; set axis minimum
M208 X1252 Y2467.8 Z140 U2467.8 V140 S0 ; set axis maximum
; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io2.in
M574 Y1 S1 P"io2.in+io3.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z2 S1 P"io4.in+io5.in" ; configure active-high endstop for high end on Z via pin io4.in
;M574 U1 S1 P"io3.in" ; configure active-high endstop for low end on U (Y2) via pin io3.in
;M574 V2 S1 P"io5.in" ; configure active-high endstop for high end on V (Z2) via pin io5.in
; Probes
M558 P5 C"!io6.in" H5 F120 T6000 ; configure analog probe via slot #0
G31 P850 X-10 Y-10 Z5.89 ; set Z probe trigger value, offset and trigger height
;M574 V2 S1 P"io5.in"
;M666 Y+2 ; move Y1 motor -1.5 from block to adjust for square
; Heaters
M140 H-1 ; disable heated bed (overrides default heater mapping)
M141 H-1
; Tools
M453 ; Set to CNC mode
M950 R0 C"out9" Q1000 L0:24000 K1 ; configure spindle #0
M563 P1 S"Makita R0701C" R0 F0 ; create tool #0
; Lasers
M950 P2 C"out4" ; air Assist solenoid
; Laser offset from spindle is X - 57.5 Y - -49.10
M452 C"io7.out" R255 F500 S1 ; configure Laser port
;M563 P2 S"Laser"
;M452
; LED Lighting
;M950 P3 c"out1" Q500
M950 F0 c"out1" Q500
;M42 P3 S1
M106 P0 S0 H-1 C"LEDs"
;M563 P0 D-0 R0 ; tool 0 uses extruder 0, heater 1 and fan 0
; Emergency Stop
M950 J1 C"io8.in"
M581 T1 P0:1 S1 R0
;M582 T1
;M42 P2 S1
; Tools
M563 P2 S"Laser" F0
;M568 P0 F0 ; set initial tool #0 active and standby temperatures to 0C
; Miscellaneous
;M452 ; select Laser mode
T0 ; select first tool
M308 S10 Y"mcu-temp" A"MCU"
M308 S11 P"DRIVER_0" Y"drivers" A"X Driver"
M308 S12 P"DRIVER_1" Y"drivers" A"Y Driver"
M308 S13 P"DRIVER_3" Y"drivers" A"Y1 Driver"
M308 S14 P"DRIVER_2" Y"drivers" A"Z Driver"
M308 S15 P"DRIVER_4" Y"drivers" A"Z1 Driver"
What am i missing?
Thanks
@jay_s_uk i had tried that previous but just added it again with no luck.
I have a duet 3 6HC with running in 3.5.3 i have a spindle and a laser. Both function as they should but only the spindle showing in DWC. I'm also using "out1" for a 6000K light strip. I have configured it as a fan but it is not showing in DWC either. I would like to have access to adjust the laser power and brightness of the led strip.
Here is what I have in my config.g
M950 R0 C"out9" Q1000 L10000:30000 ; configure spindle #0
M563 P1 S"Makita R0701C" R0 F0 ; create tool #0
M453 ; set to CNC mode
; Lasers
M950 P2 C"out4" ; air Assist solenoid
M452 C"io7.out" R255 F500 S1 ; configure Laser port
code_text
and
;M950 P3 c"out1" Q500
M950 F0 c"out1" Q500
;M42 P3 S1
M106 P0 S0 C"LEDs"
code_text
Are laser controls not available in DWC and do fans not show in CNC mode or have I got this configured incorrectly?
@Phaedrux Wow, I can't believe I missed that. Everything seems to be working perfectly now.
Thank you for all the help.
@droftarts As of now this is what I have in my config.g
M584 X0.0 Y0.1:0.3 Z0.2:0.4 U0.3 V0.4 P3 ; U=Y2 V=Z2 set axis mapping
; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io2.in
M574 Y1 S1 P"io2.in+io3.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z2 S1 P"io4.in+io5.in" ; configure active-high endstop for high end on Z via pin io4.in
and in my homez.g
; home Z
M574 Z2 S1 P"io4.in+io5.in" ; configure active-high endstop for high end on Z via pin io4.in
G91 ; relative positioning
;var maxTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
;G1 H1 Z{var.maxTravel} F1000 ; coarse home in the +Z direction
;G1 Z-5 F6000 ; move back 5mm
;G1 H1 Z{var.maxTravel} F300 ; fine home in the +Z direction
;G90 ; absolute positioning
;G1 H0 Z130 ; move z down 10mm
; level Z
M584 Z0.2 V0.4 P5 ; split Z motor control to Z and V and show V (param P5) in the UI
M547 Z2 S1 P"io4.in"
M547 V2 S1 P"io5.in"
G1 H1 Z140 V140 F500 ; Move Z and V down until the switches triggers
G92 V0 ; set V to 140
G1 H0 V-1.7 F1 ; Add move to square axis, can be Z or V
G92 Z140 V140 ; set V to 140
M584 Z0.2:0.4 P3 ; back to combined axes and hidden V
M574 Z2 S1 P"io4.in+io5.in"
G90 ; absolute positioning
G1 H0 Z130 F1000 ; move z down 10mm
After reading a little closer i realized i miss the point of adding M574 Z2 S1 P"io4.in+io5.in" in the begining of homez.g. I still get the error "Failed to enable endstops" error.
@droftarts So I changed my config.g to this
; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io2.in
M574 Y1 S1 P"io2.in+io3.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z2 S1 P"io4.in+io5.in" ; configure active-high endstop for high end on Z via pin io4.in
and my homez to this
; home Z
G91 ; relative positioning
;var maxTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
;G1 H1 Z{var.maxTravel} F1000 ; coarse home in the +Z direction
;G1 Z-5 F6000 ; move back 5mm
;G1 H1 Z{var.maxTravel} F300 ; fine home in the +Z direction
;G90 ; absolute positioning
;G1 H0 Z130 ; move z down 10mm
; level Z
M584 Z0.2 V0.4 P5 ; split Z motor control to Z and V and show V (param P5) in the UI
M547 Z2 S1 P"io4.in"
M547 V2 S1 P"io5.in"
G1 H1 Z140 V140 F500 ; Move Z and V down until the switches triggers
G92 V0 ; set V to 140
G1 H0 V-1.7 F1 ; Add move to square axis, can be Z or V
G92 Z140 V140 ; set V to 140
M584 Z0.2:0.4 P3 ; back to combined axes and hidden V
M574 Z2 S1 P"io4.in+io5.in"
G90 ; absolute positioning
G1 H0 Z130 F1000 ; move z down 10mm
This leads to "Warning: M547: Command is not supported" and "Error: in file macro line 15: G1: Failed to enable endstops"
in the link https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_auto_levelling#axis-levelling-using-endstops It has the endstops configured one per axis and doesn't reference them at all in the home z example. My U and V endstops were not triggering the corresponding drivers to stop so changing the config g solved that.
Let me know if you can see what I'm missing with the endstops in my home z file.
Thanks
@droftarts Thanks. I actually just got it working in a similar way. I probably have a few extra steps but here is what I have as of now.
home Z
G91 ; relative positioning
var maxTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
G1 H1 Z{var.maxTravel} F1000 ; coarse home in the +Z direction
G1 Z-5 F6000 ; move back 5mm
G1 H1 Z{var.maxTravel} F300 ; fine home in the +Z direction
;G90 ; absolute positioning
;G1 H0 Z130 ; move z down 10mm
M584 Z0.2 V0.4 P5 ; split Z motor control to Z and V and show V (param P5) in the UI
G1 H1 Z140 V140 F500 ; Move Z and V down until the switches triggers
G92 V0
G1 H0 V-2.184 F1 ; Add move to square axis, can be Z or V
G92 V140
M584 Z0.2:0.4 P3 ; back to combined axes and hidden V
G90 ; absolute positioning
G1 H0 Z130 F1000 ; move z down 10mm
and
homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Sep 09 2024 22:47:08 GMT-0600 (Mountain Daylight Time)
; increase Z
G91 ; relative positioning
G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning
; home Y
G91 ; relative positioning
var maxTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G1 H1 Y{-var.maxTravel} F6000 ; coarse home in the -Y direction
G1 Y5 F7200 ; move back 5mm
G1 H1 Y{-var.maxTravel} F300 ; fine home in the -Y direction
G90 ; absolute positioning
; decrease Z again
G91 ; relative positioning
G1 H2 Z-5 F7200 ; move Z relative to current position
G90 ; absolute positioning
M584 Y0.1 U0.3 P5 ; split Y motor control to Y and V and show U (param P5) in the UI
G1 H1 Y-205 U-205 F1000 ; Move Y and U down until the switches triggers
;G92 Y0
G1 H0 Y5.175 F100 ; Add move to square axis, can be Y or U
G92 Y0
M584 Y0.1:0.3 P3 ; back to combined axes and hidden U
G90
I think I will leave it as is for now unless you see anything that will cause me problems.
Can I just add the additions to the end of my home all file?
Thank you for the help.
@droftarts Thanks for the reply. I treid this but I'm having endtop issues.
If I have the drivers set like this:
; Smart Drivers
M569 P0.0 S0 D2 ; driver 0.0 goes backwards (X axis)
M569 P0.1 S0 D2 ; driver 0.1 goes backwards (Y axis)
M569 P0.2 S1 D2 ; driver 0.2 goes forwards (Z axis)
M569 P0.3 S1 D2 ; driver 0.3 goes forwards (U or Y2 axis)
M569 P0.4 S1 D2 ; driver 0.4 goes forwards (V axis)
and Axis like this:
M584 X0.0 Y0.1:0.3 Z0.2:0.4 U0.3 V0.4 P3 ; U=Y2 V=Z2 set axis mapping
If I have my enstops configured like this:
; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io2.in
M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z2 S1 P"io4.in" ; configure active-high endstop for high end on Z via pin io4.in
M574 U1 S1 P"io3.in" ; configure active-high endstop for low end on U (Y2) via pin io3.in
M574 V2 S1 P"io5.in" ; configure active-high endstop for high end on V (Z2)via pin io5.in
Then the U and V don't work. I can see them triggering correctly in the endsop monitor for U and V axis but when they are triggered during homeing they don't stop the motor when triggered.
So I tried this:
; Endstops
M574 X1 S1 P"io1.in" ; configure X axis endstop via pin io1.in
M574 Y1 S1 P"io2.in+io3.in" ; configure active-high endstop for low end on Y via pin io2.in + io3.in
M574 Z2 S1 P"io4.in+io5.in" ; configure active-high endstop for high end on Z via pin io4.in + io5.in"
But then they work they are combined on the same axis but I get "Error: Failed to enable endstops"
code; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Sep 09 2024 22:47:08 GMT-0600 (Mountain Daylight Time)
; increase Z
G91 ; relative positioning
G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning
; home Y
G91 ; relative positioning
var maxTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G1 H1 Y{-var.maxTravel} F6000 ; coarse home in the -Y direction
G1 Y5 F7200 ; move back 5mm
G1 H1 Y{-var.maxTravel} F300 ; fine home in the -Y direction
G90 ; absolute positioning
; decrease Z again
G91 ; relative positioning
G1 H2 Z-5 F7200 ; move Z relative to current position
G90 ; absolute positioning
M584 Z0.1 U0.3 P5 ; split Z motor control to Z and V and show U (param P5) in the UI
G1 H1 Z-205 U-205 F1000 ; Move Z and V down until the switches triggers
G1 H2 U3.175 ; Add move to square axis, can be Z or U
M584 Z0.2:0.4 P3 ; back to combined axes and hidden U_text
; home Z
G91 ; relative positioning
var maxTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
G1 H1 Z{var.maxTravel} F1000 ; coarse home in the +Z direction
G1 Z-5 F6000 ; move back 5mm
G1 H1 Z{var.maxTravel} F300 ; fine home in the +Z direction
G90 ; absolute positioning
G1 H0 Z130 ; move z down 10mm
M584 Z0.2 V0.4 P5 ; split Z motor control to Z and V and show V (param P5) in the UI
G1 H1 Z205 V205 F1000 ; Move Z and V down until the switches triggers
G1 H2 V-1.014 ; Add move to square axis, can be Z or V
M584 Z0.2:0.4 P3 ; back to combined axes and hidden V
How should the end stops be configured and are the homez.g and homey.g seup correctly?
Thanks
Hi have a DND With 2 Y motors and 2 Z motors on a Duet3 6hc board. I want to be able to make adjustments when homeing to level the Z and Square the Y within the homey.g, homez.g, and home all files.
My under rstanding is that to do this you need to create an axis for each motor.
"M584 X0.0 Y0.1:0.3 Z0.2:0.4 U0.3 V0.4 P3 ; U=Y2 V=Z2 set axis mapping"
I'm not positive that this is needed or if it is that I did it correctly. I have read that you can add M584 Y0.1 P5 to the homeing and this would split the Y axis to make the neccesary adjustments.
Looking for a little guidance on this one and what would need to change in my homez.g, homey.g and hamoeall.g files.
; Smart Drivers
M569 P0.0 S0 D2 ; driver 0.0 goes backwards (X axis)
M569 P0.1 S0 D2 ; driver 0.1 goes backwards (Y axis)
M569 P0.2 S1 D2 ; driver 0.2 goes forwards (Z axis)
M569 P0.3 S1 D2 ; driver 0.3 goes forwards (U axis)
M569 P0.4 S1 D2 ; driver 0.4 goes forwards (V axis)
; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout
; Axis
M669 K0 ; set Cartesian kinematics
M584 X0.0 Y0.1:0.3 Z0.2:0.4 U0.3 V0.4 P3 ; U=Y2 V=Z2 set axis mapping
M350 X16 Y16 Z16 U16 V16 I1 ; configure microstepping with interpolation
M906 X1000 Y1000 Z1000 U1000 V1000 ; set axis driver currents
M92 X100 Y100 Z400 U100 V400 ; configure steps per mm
M566 X60 Y60 Z60 U60 V60 ; set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z3000 U12000 V3000 ; set maximum speeds (mm/min)
M201 X600 Y600 Z60 U600 V60 ; set accelerations (mm/s^2)
; Axis Limits
M208 X0 Y0 Z-100 U0 V-100 S1 ; set axis minimum
M208 X1248 Y2470 Z140 U2470 V140 S0 ; set axis maximum
; Kinematics
;M669 K0 ; configure Cartesian kinematics
; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io2.in
M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z2 S1 P"io4.in" ; configure active-high endstop for high end on Z via pin io4.in
M574 U1 S1 P"io3.in" ; configure active-high endstop for low end on U (Y2) via pin io3.in
M574 V2 S1 P"io5.in" ; configure active-high endstop for high end on V (Z2)via pin io5.in
homeall.g
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Sep 09 2024 22:47:08 GMT-0600 (Mountain Daylight Time)
; increase Z
G91 ; relative positioning
G1 H2 Z5 F7200 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning
; home XY
var xTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
var yTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G91 ; relative positioning
G1 H1 X{-var.xTravel} Y{-var.yTravel} F6000 ; coarse home in the -X and -Y directions
G1 H2 X5 Y5 F7200 ; move back 5mm
G1 H1 X{-var.xTravel} Y{-var.yTravel} F300 ; fine home in the -X and -Y directions
G90 ; absolute positioning
; home Z
var zTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
G91 ; relative positioning
G1 H1 Z{var.zTravel} F600 ; coarse home in the -Z direction
G1 H2 Z5 F6000 ; move back 5mm
G1 H1 Z-10 F300 ; fine home in the -Z direction
G90 ; absolute positioning
G1 H0 Z130 ;move z down 10mm
homey.g
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Sep 09 2024 22:47:08 GMT-0600 (Mountain Daylight Time)
; increase Z
G91 ; relative positioning
G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning
; home Y
G91 ; relative positioning
var maxTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G1 H1 Y{-var.maxTravel} F6000 ; coarse home in the -Y direction
G1 Y5 F7200 ; move back 5mm
G1 H1 Y{-var.maxTravel} F300 ; fine home in the -Y direction
G90 ; absolute positioning
; decrease Z again
G91 ; relative positioning
G1 H2 Z-5 F7200 ; move Z relative to current position
G90 ; absolute positioning
homez,g
; home Z
G91 ; relative positioning
var maxTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
G1 H1 Z{var.maxTravel} F1000 ; coarse home in the +Z direction
G1 Z-5 F6000 ; move back 5mm
G1 H1 Z{var.maxTravel} F300 ; fine home in the +Z direction
G90 ; absolute positioning
G1 H0 Z130 ; move z down 10mm
Thanks
@Phaedrux That was it. Thank you for your help.
@dc42 I don't want it to use the center of the bed. I want the z to home at x0 y0.
I inverted the zprobe and it now reads 0 in DWC and I changed this line
G1 H1 Z{-var.zTravel} F600 ; coarse home in the -Z direction
to
G1 H1 Z{var.zTravel} F600 ; coarse home in the -Z direction
I also reversed the direction on the Z steppers and now the homeall seems works correctly.
If I try to just home Z i get "G28 Z
Error: Failed to home axes Z"
Here is the homeall.g that is working
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Sep 09 2024 22:47:08 GMT-0600 (Mountain Daylight Time)
; increase Z
G91 ; relative positioning
G1 H2 Z5 F7200 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning
; home XY
var xTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
var yTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G91 ; relative positioning
G1 H1 X{-var.xTravel} Y{-var.yTravel} F6000 ; coarse home in the -X and -Y directions
G1 H2 X5 Y5 F7200 ; move back 5mm
G1 H1 X{-var.xTravel} Y{-var.yTravel} F300 ; fine home in the -X and -Y directions
G90 ; absolute positioning
; home Z
var zTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
G91 ; relative positioning
G1 H1 Z{var.zTravel} F600 ; coarse home in the -Z direction
G1 H2 Z5 F6000 ; move back 5mm
G1 H1 Z-10 F300 ; fine home in the -Z direction
G90 ; absolute positioning
Here is the homez.g that is giving the error
; home Z
G91 ; relative positioning
var maxTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
G1 H1 Z{var.maxTravel} F600 ; coarse home in the +Z direction
G1 Z-5 F6000 ; move back 5mm
G1 H1 Z{var.maxTravel} F300 ; fine home in the +Z direction
G90 ; absolute positioning
@droftarts after power up if I use home z I get " Error: in file macro line 14: G1: insufficient axes homed"
If I then home x and y, then use home z i get "Error: in file macro line 14: G1: target position outside machine limits"
After power up if I hit homeall (this is new) it will home correctly but then if I try to lower Z by -25 it tries to raise z even though the endstops are triggered.
This just keeps getting more weird.
@droftarts on my duet 2 board this all worked fine and I used the probe to determine 0 for the work peice while the microswitches were used for homing z.
I have changed the homez and homeall but still getting the 2 errors
Error: in file macro line 14: G1: target position outside machine limits
Error: in file macro line 14: G1: insufficient axes homed
This is how they read now.
Home z.g
; home Z
var zTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
G91 ; relative positioning
G1 H1 Z{-var.zTravel} F600 ; coarse home in the -Z direction
G1 H2 Z5 F6000 ; move back 5mm
G1 H1 Z-10 F300 ; fine home in the -Z direction
G90 ; absolute positioning
homeall.g
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Sep 09 2024 22:47:08 GMT-0600 (Mountain Daylight Time)
; increase Z
G91 ; relative positioning
G1 H2 Z5 F7200 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning
; home XY
var xTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
var yTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G91 ; relative positioning
G1 H1 X{-var.xTravel} Y{-var.yTravel} F6000 ; coarse home in the -X and -Y directions
G1 H2 X5 Y5 F7200 ; move back 5mm
G1 H1 X{-var.xTravel} Y{-var.yTravel} F300 ; fine home in the -X and -Y directions
G90 ; absolute positioning
; home Z
var zTravel = move.axes[2].max - move.axes[2].min + 5 ; calculate how far Z can travel plus 5mm
G91 ; relative positioning
G1 H1 Z{-var.zTravel} F600 ; coarse home in the -Z direction
G1 H2 Z5 F6000 ; move back 5mm
G1 H1 Z-10 F300 ; fine home in the -Z direction
G90 ; absolute positioning
@droftarts I'm using a touch plate like this.
@droftarts I have 5 endstops that are all switches. 1 on x 2 on y and 2 on z.
When I use the end stop monitor plug in they all seem to be working correctly. The screenshot shows that x and y are homed which was correct. I can manually trigger the 2 end stops Z and see that thay appear to be working too.
I have a probe to find 0 on the material. The 2 endstops used to home z are set to find the high end.
I'm thinking there is something in the config of the touchplate probe that is incorrect. I commented out the probe but the behavior remained the same.
Can you see where I have made a mistake with between the endstops and touch plate probe?
@Phaedrux how do I find the macros file the errors is referring to?
@Alijambo73 Could this have anything to do with the Z-probe? I havent connected it to the board yet.
@Phaedrux I'm still getting the both error messages.
Im using Home Z on the DWC dashboard.
Here is the M122 results
9/19/2024, 2:54:10 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.2 (2024-06-11 17:13:58) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 0JD2M-9P9DA-F0PS8-6JKD6-3S06P-1NUR2
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 155360
Dynamic ram: 90872 of which 216 recycled
Never used RAM 96616, free system stack 146 words
Tasks: LASER(5,nWait 7,0.0%,235) SBC(2,ready,0.7%,837) HEAT(3,nWait 1,0.0%,341) Move(4,nWait 6,0.0%,238) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,336) TMC(4,nWait 6,9.5%,55) MAIN(2,running,89.7%,101) IDLE(0,ready,0.1%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:38:32 ago, cause: software
Last software reset at 2024-09-19 14:15, reason: User, Gcodes spinning, available RAM 96688, slot 2
Software reset code 0x6003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 45.1, current 45.6, max 45.8
Supply voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.2, current 11.2, max 11.3, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/180/180, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 472, reads 28165, writes 9 timeouts 0
Driver 1: standstill, SG min 0, mspos 424, reads 28165, writes 9 timeouts 0
Driver 2: standstill, SG min 0, mspos 520, reads 28161, writes 13 timeouts 0
Driver 3: standstill, SG min 0, mspos 984, reads 28164, writes 9 timeouts 0
Driver 4: standstill, SG min 0, mspos 776, reads 28160, writes 13 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 28173, writes 0 timeouts 0
Date/time: 2024-09-19 14:54:13
Slowest loop: 83.76ms; fastest: 0.05ms
=== Storage ===
Free file entries: 20
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 2048692ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 20, completed 20, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000007
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 2837, received 0, lost 0, errs 1493127, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 1576/0/0
Tx timeouts 0,0,1576,0,0,1261 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 7250/7250
SPI underruns 0, overruns 0
State: 5, disconnects: 1, timeouts: 1 total, 1 by SBC, IAP RAM available 0x24cfc
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.2 (2024-06-12 07:12:47, 64-bit)
HTTP+Executed:
Executing M122
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 39.42, max time between full transfers: 62.3ms, max pin wait times: 64.4ms/2.0ms
Codes per second: 0.40
Maximum length of RX/TX data transfers: 4392/316
@Phaedrux I made the 2 changes. When I enter M98 P"config.g" into the console it just shows M98 P"config.g" with a green background and does not report any errors.