RRF3 Homing Issues
-
OK so my homexy macro fails 100% of the time if either X or Y is marked as unhomed.
So It's back to homing individually.And now I'm thoroughly confused. I just tried this from CodeConsole
G1 X150 Y410 Z10 G28 and got this...
Oct 29 11:09:07 duet3j.f5.int DuetControlServer[24860]: [info] Sent G1 H2 Z-2 F200, remaining space 544 (3872 total), needed 44 Oct 29 11:09:07 duet3j.f5.int DuetControlServer[24860]: [info] Completed G91 Oct 29 11:09:08 duet3j.f5.int DuetControlServer[24860]: [info] Completed G1 H2 Z2 F200 Oct 29 11:09:28 duet3j.f5.int DuetControlServer[24860]: [info] Received file abort request on channel SPI for all files Oct 29 11:09:28 duet3j.f5.int DuetControlServer[24860]: [info] Aborted macro file '/opt/dsf/sd/sys/homey.g' -
@dc42 said in RRF3 Homing Issues:
@Danal, is your machine a Cartesian, CoreXY, or something else? What is the purpose of the final G1 command in homex.g? The X axis should be at X=0 already.
This one is a Core XY on Duet 3 6HC and software releases shown above.
The final G1 command is because the axis is defined as -5:305. Therefore, the switch is at -5.
Iif not for that final command, X would be sitting at X-5 when the G1 X-10 F600 H1 finishes. Example (already sorted to be readable top down):
10/29/2019, 12:17:19 PM G1 X15 10/29/2019, 12:17:36 PM G1 X-100 F600 H1 10/29/2019, 12:18:13 PM M114 X:-5.000 10/29/2019, 12:18:22 PM G1 X0 10/29/2019, 12:18:28 PM M114 X:0.000 -
A temporary workaround for the G1 issue is to add H2 to the back off commands...
-
I have reproduced the following problem: If I try to home X with the X endstop initially not triggered, it mostly works. If I try to home X with the X endstop triggered at the start, it mostly fails with "Error: insufficient axes homed".
If I reconfigure the machine as a Cartesian, it works every time whether or not the endstop is triggered initially.
-
I think I've now found the cause - and a workaround. When preparing for the G1 H1 move, the code isn't waiting for the previous move to complete before priming the endstops. It works if I change homex.g to this:
; homex.g G91 G1 H2 Z2 F200 M400 ; <========= added G1 H1 X-500 F6000 G1 X4 F600 G1 H1 X-10 G1 H2 Z-2 F200 A similar change will be needed to homey.g.
I'll fix this in the next build.
-
I've put new RRF3 binaries at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0. The problem was wider than I originally thought, so the workaround I suggested earlier can't be guaranteed to work always. Please try the new firmware.
-
Board: Duet 3 MB6HC (MB6HC)
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta11+1 (2019-10-30b3)This does seem to have fixed it. My previous test case, "G1 X-5" followed by "G28 X" now works. Also, "home all" was failing on x quite a bit of the time, and it now runs over and over, cleanly.
-
@dc42 said in RRF3 Homing Issues:
I've put new RRF3 binaries at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0. The problem was wider than I originally thought, so the workaround I suggested earlier can't be guaranteed to work always. Please try the new firmware.
@dc42 Are those changes all pushed to github?
-
@gtj0 said in RRF3 Homing Issues:
@dc42 said in RRF3 Homing Issues:
I've put new RRF3 binaries at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0. The problem was wider than I originally thought, so the workaround I suggested earlier can't be guaranteed to work always. Please try the new firmware.
@dc42 Are those changes all pushed to github?
yes.
-
@Danal said in RRF3 Homing Issues:
Board: Duet 3 MB6HC (MB6HC)
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta11+1 (2019-10-30b3)This does seem to have fixed it. My previous test case, "G1 X-5" followed by "G28 X" now works. Also, "home all" was failing on x quite a bit of the time, and it now runs over and over, cleanly.
Thanks for the confirmation.
-
@dc42 said in RRF3 Homing Issues:
@gtj0 said in RRF3 Homing Issues:
@dc42 said in RRF3 Homing Issues:
I've put new RRF3 binaries at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0. The problem was wider than I originally thought, so the workaround I suggested earlier can't be guaranteed to work always. Please try the new firmware.
@dc42 Are those changes all pushed to github?
yes.
PS- if you haven't built RRF for a while, be sure to pick up the changes in CoreNG, FreeRTOS and RRFlibraries projects too.
-
@dc42 said in RRF3 Homing Issues:
@dc42 said in RRF3 Homing Issues:
@gtj0 said in RRF3 Homing Issues:
@dc42 said in RRF3 Homing Issues:
I've put new RRF3 binaries at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0. The problem was wider than I originally thought, so the workaround I suggested earlier can't be guaranteed to work always. Please try the new firmware.
@dc42 Are those changes all pushed to github?
yes.
PS- if you haven't built RRF for a while, be sure to pick up the changes in CoreNG, FreeRTOS and RRFlibraries projects too.
Yeah I've been keeping up and I can confirm that the fixes fixed the homing issues!
-
Thanks, I'll mark this as solved.
-
This post is deleted!