Ender 5 + Duet wifi starts on wrong side g29
-
Hi
i have an Ender 5 my origin 0,0 is on the right back
but G29 starts on left back i dont know why
config.g
; Configuration file for Duet WiFi (firmware version 1.21) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2 on Tue May 07 2019 23:06:50 GMT+0100 (British Summer Time) ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Network M550 P"Ender 5" ; Set machine name M552 S1 ; Enable network M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; Drives M569 P0 S1 ; Physical drive 0 goes forwards M569 P1 S1 ; Physical drive 1 goes forwards M569 P2 S0 ; Physical drive 2 goes backwards 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 X79.92 Y79.84 Z797.61 E277.89 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E4000.00 ; Set maximum instantaneous speed changes (mm/min) M203 X30000.00 Y30000.00 Z600.00 E8000.00 ; Set maximum speeds (mm/min) M201 X500.00 Y500.00 Z200.00 E8000.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E1400 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 X235 Y235 Z300 S0 ; Set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z ;Filament Sensors M591 D0 P2 C"!e0_stop" S1 ;Extruder 1(0) ; Z-Probe M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H3 F120 T6000 A10 S0.003 B1 R0.5 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X41.24 Y6.25 Z2.805 ; set Z probe trigger value, offset and trigger height M557 X0:235 Y0:235 S20 ; define mesh grid ;M557 X41.2:219 Y15:195 S20 M671 X28.8:198.8:198:28.8 Y24:24:194:194 ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; 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 M950 H0 C"bed_heat" Q100 T0 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 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 M143 H1 S280 ; set temperature limit for heater 1 to 300C M307 H1 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 ; Define tool 0 S3D ;M563 P0 D0 H1 F0 ; Für Prusa Slicer G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C ; Automatic saving after power loss is not enabled ; Custom settings are not configured M575 P1 S1 B57600 ; enable support for PanelDue M572 D0 S0.50 ; Pressure Advance M207 P0 S0.45 R0 F2100 T2100 Z0 ; Firmware Retraction M204 P600 T2000 M501
homeall.g
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Jul 28 2020 08:52:12 GMT+0200 (Mitteleuropäische Sommerzeit) G91 ; relative mode G1 H2 Z4 F200 ; raise head 4mm G1 H1 X-240 Y-240 F3000 ; move up to 240mm in the -X and -Y directions until the homing switches are triggered G1 X4 Y4 F600; move slowly 6mm in +X and +Y directions G1 H1 X-10 Y-10 ; move up to 10mm in the -X and -Y directions until the homing switches are triggered G90 ; back to absolute mode G1 X73 Y106 F2000 ; put head over the centre of the bed, or wherever you want to probe G30 ; lower head, stop when probe triggered and set Z to trigger height
homex.g
; homex.g ; called to home the X axis ; ; generated by RepRapFirmware Configuration Tool v2 on Tue May 07 2019 23:06:50 GMT+0100 (British Summer Time) G91 ; relative mode G1 H2 Z4 F200 ; raise head to avoid dragging nozzle over the bed G1 H1 X-240 F3000 ; move up to 240mm in the +X direction, stopping if the homing switch is triggered G1 X-4 F600 ; move slowly 4mm in the -X direction G1 H1 X10 ; move slowly 10mm in the +X direction, stopping at the homing switch G1 H2 Z-4 F200 ; lower the head again G90 ; back to absolute mode
homey.g
; homey.g ; called to home the Y axis ; ; generated by RepRapFirmware Configuration Tool v2 on Tue May 07 2019 23:06:50 GMT+0100 (British Summer Time) G91 ; relative mode G1 H2 Z4 F200 ; raise head to avoid dragging nozzle over the bed G1 H1 Y-240 F3000 ; move up to 240mm in the -X direction, stopping if the homing switch is triggered G1 X4 F600 ; move slowly 4mm in the +X direction G1 H1 X-10 ; move slowly 10mm in the -X direction, stopping at the homing switch G1 H2 Z-4 F200 ; lower the head again G90 ; back to absolute mode
homez.g
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Jul 28 2020 08:52:37 GMT+0200 (Mitteleuropäische Sommerzeit) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G90 ; absolute positioning G1 X73 Y106 F6000 ; go to first probe center point G30 ; home Z by probing the bed
M98 P"config.g"
HTTP is enabled on port 80 FTP is disabled TELNET is disabled
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-02-11
M122
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later Board ID: 08DGM-917NK-F23T0-6JTD2-3S86S-KYBND Used output buffers: 3 of 24 (20 max) === RTOS === Static ram: 23460 Dynamic ram: 73416 of which 40 recycled Never used RAM 15164, free system stack 184 words Tasks: NETWORK(ready,188) HEAT(blocked,308) MAIN(running,449) IDLE(ready,20) Owned mutexes: === Platform === Last reset 00:01:03 ago, cause: software Last software reset at 2021-03-26 08:55, reason: User, GCodes spinning, available RAM 15164, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 37.2, current 37.9, max 38.1 Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-03-26 08:56:12 Cache data hit count 75689644 Slowest loop: 140.37ms; fastest: 0.22ms 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: 20.0MBytes/sec SD card longest read time 1.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === 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: 22.56ms; fastest: 0.00ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.25 WiFi MAC address 84:f3:eb:83:4f:81 WiFi Vcc 3.44, reset reason Power up WiFi flash size 4194304, free heap 24472 WiFi IP address 192.168.2.113 WiFi signal strength -70dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 === Filament sensors === Extruder 0 sensor: ok
-
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Sat Jun 20 2020 16:28:00 GMT+0100 (British Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Ender 5 Plus" ; set printer name M551 P"nnnnnnnn" ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes backwards M569 P1 S0 ; physical drive 1 goes backwards M569 P2 S0 ; physical drive 2 goes backwards M569 P3 S0 ; physical drive 3 goes backwards M569 P4 S0 ; physical drive 4 goes backwards M584 X0 Y1 Z2:3 E4 ; set drive mapping M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation M350 E16 I0 ; configure microstepping without interpolation M92 X80.00 Y80.00 Z800.00 E409 ; set steps per mm , e380 , e135 , bmg 420 cal M566 X1200.00 Y1200.00 Z24.00 E300 ; set maximum instantaneous speed changes (mm/min) M203 X8500.00 Y8500.00 Z180.00 E2700.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2) M906 X600 Y600 Z600 E1000 I50 ; 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 X340 Y350 Z400 S0 ; set axis maxima ; Endstops M574 X2 S1 P"!xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y2 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S2 ; External Triggers M950 J0 C"!^e0stop" M950 J1 C"!^e1stop" M581 P0 T1 S1 R1 ; M581 P1 T3 S1 R0 ; ; Z-Probe M558 P9 C"^zprobe.in" H2 F100 T8000 A5 ; set Z probe type to bltouch and the dive height + speeds M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch G31 P500 X 57.5 Y-10.5 Z 1.70 ; set Z probe trigger value, offset and trigger height M557 X65:275 Y50:290 S30 ; define mesh grid .. 30 , 60 , 80 ; Bed adjustment screw locations M671 X-36:381 Y0:0 S0.5 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S150 ; set temperature limit for heater 0 to 150C ; M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp 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 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S1 H1 T45 ; 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 S0 H-1 ; set fan 1 value. M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H1 T45 ; set fan 2 value. ; Tools M563 P0 D0 H1 F1 ; 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 M572 D0 S0.025 M221 D0 S90 ; 87% extrude M501
; homeall.g ; called to home all axes ; ;G28 XY G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X 355 F3000 ; move quickly to X axis endstop and stop there (first pass) G1 H1 Y 355 F3000 ; move quickly to Y axis endstop and stop there (first pass) ;G1 H2 Z-5 F6000 ; lower Z again G90 ; absolute positioning G1 X125 Y175 F4000 ; Move probe to middle of bed G30
; Drives M569 P0 S1 ; Physical drive 0 goes forwards M569 P1 S1 ; Physical drive 1 goes forwards M569 P0 S1 ; physical drive 0 goes backwards M569 P1 S0 ; physical drive 1 goes backwards
So Y is going the other ways to mine .
; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 X2 S1 P"!xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y2 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop
Your end stops are wrong they are low end not high end . ( and may be the ! , but that could be my wiring )
AND your homing is wrong you should be homing plus not minis !!
-
@peter247 said in Ender 5 + Duet wifi starts on wrong side g29:
M574 X2 S1 P"!xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y2 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin ystop
hi
thanks for hekping me
now after changes my x and y crashes into endstops
-
@lui2004
Don't forget to change all the problems motor direction , end stops and home files plus not minus.Does to crash into the correct end stop , eg right back ?
Use M119 to get the end stop status , and check if the end stop is working before homing .The ! on the end stop , is the switch trigger on normally open or closed , So that may differ , it all depend how you have wired it.
-
@peter247 said in Ender 5 + Duet wifi starts on wrong side g29:
M119
i have changed it all but it crashes in right back.
M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stoppedcan you help me for home files ?
-
@lui2004 o.k , manually home it , eg trigger all the switches and do a M119 ?
How do the opposite , moving the head from all the switches and do a M119 again ... any difference ?One command which may help you is : M84 x y z , switch off all motors.
I don't think you have set up the btlotch yet , so you will have problems with Z homing , but lets get your X , Y end stop switches working first.
-
@lui2004 said in Ender 5 + Duet wifi starts on wrong side g29:
M569 P1 S1 ; Physical drive 1 goes forwards
homeall will try to trigger on left front instead of right back
-
Z axis will crash in the bed also
; homeall.g ; called to home all axes ; ;G28 XY G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X 355 F3000 ; move quickly to X axis endstop and stop there (first pass) G1 H1 Y 355 F3000 ; move quickly to Y axis endstop and stop there (first pass) ;G1 H2 Z-5 F6000 ; lower Z again G90 ; absolute positioning G1 X125 Y175 F4000 ; Move probe to middle of bed G30
This is my home all file , very simple but it works .
G91 set relative , which means move eg move 5mm plus , not to position 5mm.
G1 H2 Z5 F6000 , which means move up 5mmNow this is the part you have wrong !!!
G1 H1 X 355 F3000 , move right ( not left ) until you hit the end stop
G1 H1 Y 355 F3000 , move the head back until you hit the end stop
G90 ; absolute positioning againNext problem
G1 X125 Y175 F4000 ; Move probe to middle of bed
G30 , use the BLTOUCH to home not any end switches .READ THE LAST POST is their any difference between homed and not homed with M119 ?
-
m119
Endstops - X: at max stop, Y: at max stop, Z: not stopped, Z probe: not stoppedi cant home my axis it will crashes every time i change it in config
-
@lui2004 said in Ender 5 + Duet wifi starts on wrong side g29:
Endstops - X: at max stop, Y: at max stop, Z: not stopped, Z probe: not stopped
So that is when homed and you are X and Y not stop if not homed ?
Have you copied my homing all file ? and changed the motor direction . -
not all
only setup for :
Endstop,motor drive
-
@lui2004 X and Y , Z motor should be the same ( MUST ) , But E could be any direction , that is a suck it and see.
O.K , lets make a macro and see if we are on the same page.
Move the head it middle of the bed and try.
G91
G1 H2 Z5 F6000
G1 H1 X 10 F3000
G1 H1 Y 10 F3000
G1 H2 Z-5 F6000
G90Does it move to the right and too the back 10mm in each direction ?
If it doesn't change the motor direction until it does !!!!
-
the macro will only move the bed up and down
-
O.K to safe , it looks like you can see a 10mm change .
G91
G1 H2 Z5 F6000
G1 H1 X 100 F3000
G1 H1 Y 100 F3000
G1 H2 Z-5 F6000
G90This should lift the head up , move right and to the back 100mm now.
-
@peter247 said in Ender 5 + Duet wifi starts on wrong side g29:
G91
G1 H2 Z5 F6000
G1 H1 X 100 F3000
G1 H1 Y 100 F3000
G1 H2 Z-5 F6000
G90only z moves up and down few mm
but x and y dont moves
-
o.k confirm this :- After you run the macro and it goes up and down , does it say homed X an Y ?
-
yes after i run the macro it move only the z but x and y was homed
-
@lui2004 o.k wiser .
; Endstops M574 X2 S1 P"!xstop" M574 Y2 S1 P"!ystop"
So have you changed this and what too ?
-
yes i have changed it
-
@lui2004 With the ! ?