Help with setting up firmware for coreXY machine - unable to home.

[cap]

fantastic changed this bit of code and now that x and y work correctly
M569 P0 S1 ; Drive 0 goes forwards
to
M569 P0 S0 ; Drive 0 goes forwards

thankyou for the help any ideas about homing is it a case of changing the homeall flie

[dc42]

Are you using the homeall.g file from the sys-CoreXY folder in my repo? See also https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_CoreXY_printer#homeall.g_file.

[cap]

hi my filing sys folders are a mess here all the folders i have

Size
bed.g 343 B
config.g 2.4 KiB
config.json 2.3 KiB
deployprobe.g 283 B
DuetWebControl.bin 3.0 MiB
DuetWiFiServer.bin 288.3 KiB
homeall.g 335 B
homedelta.g 644 B
homex.g 437 B
homey.g 436 B
homez.g 352 B
iap.bin 52.3 KiB
iap4e.bin 54.1 KiB
pause.g 239 B
resume.g 234 B
retractprobe.g 292 B
sleep.g 54 B
stop.g 86 B
tfree0.g 150 B
tpost0.g 210 B
tpre0.g 153 B
just removed homedelta.g
which to me dose not look right
my homeall.g look like this
G91 ; relative mode
G1 S1 X-200 Y-240 F3000 ; course home X or Y
G1 S1 X-200 ; course home X
G1 S1 Y-200 ; course home Y
G1 X4 Y4 F600 ; move away from the endstops
G1 S1 X-10 ; fine home X
G1 S1 Y-10 ; fine home Y
; Z homing section follows
i changed to the print bed to 200 in xy and z to start with keep to things i know while working this stuff out

thanks for any help the info for all this stuff is all over the places

[dc42]

The homing switches are only active during homing, so there are no limits on movement until you have homed. For testing homing, you may wish to reduce the homing speed and motor current.

[cap]

ok ive now removed all the 3 of these files homex.g homey.g homez.g
and just left the homeall.g
i can get x and y to home but not z in fact on the web interface it is now in yellow telling me it not available

[dc42]

Read https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Homing_files. The files for a CoreXY printer are similar except for homeall.g.

[cap]

ok thanks sorted it
sorry to be a pain could not see it throw looking changed homez to this
G91 ; relative mode
G1 Z4 F200 ; raise head 4mm to ensure it is above the switch trigger height
G90 ; back to absolute mode
G1 X0 Y0 F2000 ; put head wherever you want it to be when you home Z (omit this line if it doesn't matter)
G91 ; relative mode
G1 Z-200 S1 F100 ; move Z down until the switch triggers
G90 ; back to absolute mode
G92 Z0.3

and it worked a treat

[thehands1]

So I had the same type of issues in the previous posts but now it will home the X and Y axis correctly, The drives go in the right direction…Awesome...but...now when I home everything seems to be locked up when I try to make the X or Y axis to move. I can't move by g-code or by pushing the buttons on the PanelDue or Web page. Any ideas?

I tried the sample g-code:
G91 ; relative mode
G1 S2 X10 ; move the X motor forward 10mm
G1 S2 X-10 ; move the X motor back 10mm
G1 S2 Y10 ; move the Y motor forward 10mm
G1 S2 Y-10 ; move the Y motor back 10mm
G90 ; back to absolute mode

Works UNLESS I home the X axis and Y axis then nothing. It just stops and no further movements work.

[dc42]

Please post your config.g file. There may be something wrong with your M574 or M208 commands in particular.

What is the displayed X Y position after homing? Are your homing switches triggered at the front left of the printer, or somewhere else?

[thehands1]

I am homing at the front left of the printer. The XY position displayed is 0,0. The endpoints trigger (and the board LED lights up) when I press the contacts. The X axis increases when I go to the right. The Y axis increases when I go to the back. Here is the config.g

; Configuration file for Duet WiFi (firmware version 1.17)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Mon Jul 10 2017 20:30:20 GMT-0600 (Mountain Daylight Time)

; General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin

M667 S1 ; Select CoreXY mode
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X400 Y400 Z400 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 Z0 S0 ; Define active low and unused microswitches
M558 P1 X0 Y0 Z1 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X15:385 Y15:385 S20 ; Define mesh grid

; Drives
M569 P0 S0 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes backwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation
M92 X87.489 Y87.489 Z4000 E420 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X9000 Y9000 Z180 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y500 Z250 E250 ; 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

; Heaters
M143 S260 ; Set maximum heater temperature to 260C
M140 H-1 ; Disable heated bed

; Tools

; Network
M550 PHypercube ; Set machine name
M551 PXXXXXX ; Set password
M552 S1 ; Enable network
M587 SXXXXXX P"XXXXXXX" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Custom settings are not configured

[dc42]

That looks ok to me. Perhaps it is something in your homing files - please share them too.

What happens if you home just X: are you able to move X and/or Y after that? Similarly if you home just Y.

[thehands1]

If I home either only X or only Y I can move those axis just fine. It I home both then it locks up. Here are the Homing files:

Homeall
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Mon Jul 10 2017 20:30:20 GMT-0600 (Mountain Daylight Time)

; Relative positioning
G91

; Lift Z
;G1 Z5 F6000

; Course home X or Y
G1 S1 X-405 Y-405 F1800
; Course home X
G1 S1 X-405
; Course home Y
G1 S1 Y-405

: Move away from the endstops
G1 X5 Y5 F6000

; Fine home X
G1 S1 X-10
; Fine home Y
G1 S1 Y-10

; Absolute positioning
G90

; Go to first bed probe point and home Z
G1 X15 Y15 F6000
G30

; Uncomment the following line to lift the nozzle after probing
;G1 Z5 F100

---

Home X
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Mon Jul 10 2017 20:30:20 GMT-0600 (Mountain Daylight Time)

; Lift Z relative to current position
G91
G1 Z5 F6000
G90

; Move quickly to X axis endstop and stop there (first pass)
G1 X-405 F1800 S1

; Go back a few mm
G91
G1 X5 F6000
G90

; Move slowly to X axis endstop once more (second pass)
G1 X-405 F360 S1

; Lower Z again
G91
G1 Z-5 F6000
G90

---

Home Y
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool on Mon Jul 10 2017 20:30:20 GMT-0600 (Mountain Daylight Time)

; Lift Z relative to current position
G91
G1 Z5 F6000
G90

; Move quickly to Y axis endstop and stop there (first pass)
G1 Y-405 F1800 S1

; Go back a few mm
G91
G1 Y5 F6000
G90

; Move slowly to X axis endstop once more (second pass)
G1 Y-405 F360 S1

; Lower Z again
G91
G1 Z-5 F6000
G90

[dc42]

This has me puzzled because I can't see the problem. Please try these:

1. Send M208 with no parameters, check that the axis limits it reports are correct and as you have defined them in config.g i.e. minimum zero and maximum 400 on each axis.

2. Send M564 S0 to disable soft endstops and then see if it lets you move after homing.

[thehands1]

I am confused as well. It looked to me like things were correct. Now with you being puzzled now I am VERY confused. I will try those suggestions to see what happens. Thanks for the help!

[thehands1]

OK, well it works now if I do the Homeall manually. If I issue a G28 ; home all axes then the system will home correctly but then just hangs up. No messages in the console nothing. It just sits there and I have to reset and manually do the Homeall then run without the G28. Ideas?

[dc42]

When you say it works if you do the homeall manually, do you mean it works if you send G28 X, then G28 Y, then G28 Z?

[dc42]

Two things:

1. In homex.g and homey.g you do the fine homing at low speed (F360). In homeall.g you don't. You should add that F360 parameter to the commands that fine home X and Y.

2. I remember reading a report recently that another user had to remove comment lines from his homeall file to get it to work. So I am wondering whether there is a problem if the file ends with a comment line. Try removing the two comment lines at the end of homeall.g. Or maybe putting a blank line at the very end would work.

[thehands1]

So when I say Homeall manually it is pressing the home icon on the PanelDue screen. Sending the G28 command from the gcode file not manually from the screen. I will try if sending the code individually if it works and I will then test to see if removing comments makes it work as well. I will do them separately so that I know which one is doing what.

[thehands1]

If I enter the codes G28 X and G28 Y then tell it to print without a G28 code in the gcode file it works. If I have the codes G28 X and G28 Y in the gcode file with no G28 it works. If I just have G28 it stops working. Must be something with the Homeall file. There are no comments at the end anymore. The F360 parameters are there. Wow am I baffled!!!

[Sabagmn]

I just had the same issue with the generated homeall.g file. Despite going through it line by line I could not find an issue.
In the end I just completely cleared the file, saved it empty, and then manually inserted the X, Y, Z homing commands from their respective homing files into homeall.g.
Now it works.

Duet Ethernet with 1.18.1 by the way.