Weird fault on homey.g
-
Creality CR10-S5 printer, Duet2 wifi, RRF3.0
I did a stupid and as a result the Y motor lost a bunch of steps but it was working fine with the revised position so I aborted the print.
Next thing I know, the printer is not homing right.
It has been a little while since I last homed (the printer stays on) so it could be something I did a couple of weeks ago but no clue what it could be. It gets more interesting though .....If I move the build plate away from the y stop and then home, the build plate travels to the Y stop, stops as it is supposed to but then y is no longer reacting to any commands.
If I move the build plate away from the y stop, home, manually trigger Y it stops. When I move my finger away from the Y stop, the Y motor responds to input.
If I run all of the homey.g commands manually (copy and paste into command line), everything works.
If I now run the homey.g script with all the commands that I just ran manually, the script hangs again.
I copy and pasted the entire homey. g script to a text editor thinking that maybe there were some weird characters/corruption someplace ....none found.
I rename the homey.g file and create a new one with the content from the text editor and it runs just fine.
I export the original file, avoiding copy & paste and look at it in a text editor - no weird characters.
What the heck is going on ?????
This is the content of the file with the last line added as a diagnostic flag:
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v2 on Sat May 25 2019 18:49:41 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 Z5 F6000 H2 ; lift Z relative to current position
G1 H1 Y-505 F6000 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 H1 Y-505 F360 ; move slowly to Y axis endstop once more (second pass)
G1 Z-5 F6000 H2 ; lower Z again
G90 ; absolute positioningM117 "Hello World 55"
The issue is likely solved now (haven't run full tests yet) but I need to know how a simple gcode script can hang the printer somehow.
-
If you still have a "file" of the original (that should/does cause the hang), please upload it here.
With this button above:
-
I still have the old file but I doubt it will be of much use to you. I now have conclusive proof that the Gods are screwing with me and are having a grand old time laughing it up.
To clarify ...
I have two files, homey.g and homeyback.g with the second being the old file.
I press the homey button and everything works as expected (this is the re-created homey.g file).
I delete homey.g and rename homeyback.g to homey.g (so the original homey.g was restored).
I press the homey button and the y axis fault happens as before.
I run the homey.g file by entering M98 P"homey.g" in the console and it works just fine.
I press the homey button again and everything works fine !?!?!?!I did find a long flexible section of a brim somehow entangled in the works of the Y axis but there was never any chattering that would happen if the axis was prevented from moving due to an obstruction. It was removed just before the last pressing of the homey button.
-
Please attach both your homey.g and homeyback.g files to a post. We may be able to find what's going wrong.
Also, please update your firmware to 3.01-RC2 and see whether the problem still occurs.
-
as a side note regarding duet 3 (6hc): when an end switch - let's say y (active low) is disconnected for some reason and i try to home y the printer hangs - no motion related commands are accepted afterwords until it is reset by power cycling duet + raspberry (emergency stop, reset, and (at least sometimes) a reset of the hc6 does not unhang the printer).
-
@spllg said in Weird fault on homey.g:
as a side note regarding duet 3 (6hc): when an end switch - let's say y (active low) is disconnected for some reason and i try to home y the printer hangs - no motion related commands are accepted afterwords until it is reset by power cycling duet + raspberry (emergency stop, reset, and (at least sometimes) a reset of the hc6 does not unhang the printer).
Unplugging a Normally Closed switch (the switch pulls the pin to ground when NOT triggered) is equivalent of a broken wire. This should, and does, cause the switch to "look triggered all the time" and the machine will not move on a homing sequence.
It shouldn't hang like you describe... although, I've noticed similar hangs when homing moves don't complete on D3+Pi. Reset the firmware does not fix it, which makes me assume the Pi is still 'out-of-sync' waiting for that move.
I have not taken the time to see if stop/start of either of the Duet services fixes it.
Summary: I've seen the same hangs. I will start a new thread to report this as a bug.
