Error: G0/G1: insufficient axes homed
-
hello I have a question I use the duet maestero corexy and I get the ender 6 just not to run endstops I use photocells these work but I always get this error when I want to move axes Error: G0/G1: insufficient axes homed can someone help me I despair of the ender 6 slowly what am I doing wrong
firmware is the newest on it if I start pronterface endstops are not recognized and also there comes this error Error: G0/G1: insufficient axes homed
here once a copy of the firmware
Configuration file for Duet Maestro (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Fri Mar 10 2023 22:19:10 GMT+0100 (Central European Standard Time)General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P "ender6" ; set printer name
M669 K1 ; select CoreXY modeNetwork
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable TelnetDrives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.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 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 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 X255 Y255 Z400 S0 ; set axis maxima; Endstops
M574 X1 S1 P "xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P "ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S1 P "zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop; Z sample
M558 P1 C "zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid; Heaters
M308 S0 P "bedtemp" Y "thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C "bedheat" T0 ; create bed heater output on bedheat 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 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P "e0temp" Y "thermistor" T100000 B4138 ; 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 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280CFans
M950 F0 C "fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S1 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 onTools
M563 P0 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 0CCustom settings are not defined
Translated with www.DeepL.com/Translator (free version)
-
-
-
-
@almundili post your homing files as well please
-
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Sat Mar 11 2023 18:08:57 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X260 Y260 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X260 ; home X axis
G1 H1 Y260 ; home Y axis
G1 X-5 Y-5 F6000 ; go back a few mm
G1 H1 X260 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y260 ; then move slowly to Y axis endstop
G1 H1 Z405 F360 ; move Z up stopping at the endstop
G90 ; absolute positioning
G92 Z400 ; set Z position to axis maximum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Sat Mar 11 2023 18:09:29 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X260 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X-5 F6000 ; go back a few mm
G1 H1 X260 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Sat Mar 11 2023 18:09:55 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y260 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y-5 F6000 ; go back a few mm
G1 H1 Y260 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.15 on Sat Mar 11 2023 18:10:22 GMT+0100 (Mitteleuropäische Normalzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Z405 F1800 ; move Z up until the endstop is triggered
G92 Z400 ; set Z position to axis maximum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@almundili what's strange is you have your endstops set as being on the low side but you home to a positive position for them. I think you need to revisit either your endstop location or your homing files
-
-
When looking at your printer from the front, where are your endstops physically located?
Keep in mind that your movement directions should be like this
-X to the left, +X to the right
-Y to the front, +Y to the backCan you also send M122 and M98 P"config.g" and copy and paste the results here?
-
This post is deleted! -
This post is deleted! -
This post is deleted! -
@Phaedrux m122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 Maestro version 3.4.5 (2022-11-30 19:42:44) running on Duet Maestro 1.0<LF>Board ID: 08DJM-9X66L-LG3SN-6JTD0-3SJ6M-TAZQR<LF>Used output buffers: 1 of 26 (23 max)<LF>=== RTOS ===<LF>Static ram: 23620<LF>Dynamic ram: 66788 of which 0 recycled<LF>Never used RAM 24080, free system stack 204 words<LF>Tasks: NETWORK(ready,30.3%,262) HEAT(notifyWait,0.1%,350) Move(notifyWait,0.0%,402) TMC(notifyWait,1.3%,117) MAIN(running,68.3%,492) IDLE(ready,0.0%,31), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:08:19 ago, cause: software<LF>Last software reset at 2023-03-11 23:04, reason: User, GCodes spinning, available RAM 24080, slot 1<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>Aux0 errors 0,0,0<LF>Step timer max interval 937<LF>MCU temperature: min 26.5, current 27.3, max 27.6<LF>Supply voltage: min 23.6, current 23.7, max 23.7, under voltage events: 0, over volt[Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.] -
@Phaedrux m122
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.4.5 (2022-11-30 19:42:44) running on Duet Maestro 1.0
Board ID: 08DJM-9X66L-LG3SN-6JTD0-3SJ6M-TAZQR
Used output buffers: 1 of 26 (23 max)
=== RTOS ===
Static ram: 23620
Dynamic ram: 66788 of which 0 recycled
Never used RAM 24080, free system stack 204 words
Tasks: NETWORK(ready,31.0%,262) HEAT(notifyWait,0.1%,352) Move(notifyWait,0.0%,402) TMC(notifyWait,1.3%,117) MAIN(running,67.6%,492) IDLE(ready,0.0%,31), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:02:34 ago, cause: software
Last software reset at 2023-03-11 23:04, reason: User, GCodes spinning, available RAM 24080, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 937
MCU temperature: min 26.5, current 27.0, max 27.3
Supply voltage: min 23.6, current 23.7, max 23.7, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, read errors 0, write errors 0, ifcnt 13, reads 7591, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, read errors 0, write errors 0, ifcnt 13, reads 7591, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, read errors 0, write errors 0, ifcnt 13, reads 7591, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, read errors 0, write errors 0, ifcnt 13, reads 7591, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, read errors 0, write errors 0, ifcnt 13, reads 7591, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-03-11 23:06:53
Slowest loop: 1.69ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest read time 0.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1, chamber heaters -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 5.18ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
11.3.2023, 23:06:38 m98
Error: M98: No P or R parameter -
@Phaedrux said in Error: G0/G1: insufficient axes homed:
Keep in mind that your movement directions should be like this
-X to the left, +X to the right
-Y to the front, +Y to the backThe endstop position is arbitrary, so rear right is fine. But are your motor directions correct?
To have the endstops at the rear right and the low end of travel means that your axis movement would need to have
-X moving to the right, +X to the left
-Y to the back, +Y to the leftYour homing files would need to flip their directions from what you have now so that they move towards the endstop.
You may need to change the direction of rotation of the motor to achieve this.
And keep in mind this would have the effect of your prints being rotated 180 degrees from the slicer preview.