internal error when homing Z
recently updated klipper and now get internal error on command g28 when homing the z axis.
"Internal error on command:"G28"
Internal error on command:"G28"
Traceback (most recent call last):
File "/home/pi/klipper/klippy/gcode.py", line 211, in _process_commands
handler(gcmd)
File "/home/pi/klipper/klippy/extras/homing_override.py", line 23, in cmd_G28
self.prev_G28(gcmd)
File "/home/pi/klipper/klippy/extras/ratos_homing.py", line 77, in cmd_G28
self.template.run_gcode_from_command(context)
File "/home/pi/klipper/klippy/extras/gcode_macro.py", line 68, in run_gcode_from_command
self.gcode.run_script_from_command(self.render(context))
File "/home/pi/klipper/klippy/gcode.py", line 226, in run_script_from_command
self._process_commands(script.split('\n'), need_ack=False)
File "/home/pi/klipper/klippy/gcode.py", line 211, in _process_commands
handler(gcmd)
File "/home/pi/klipper/klippy/extras/homing_override.py", line 23, in cmd_G28
self.prev_G28(gcmd)
File "/home/pi/klipper/klippy/extras/ratos_homing.py", line 28, in cmd_G28
self.prev_G28(gcmd)
File "/home/pi/klipper/klippy/extras/homing.py", line 268, in cmd_G28
kin.home(homing_state)
File "/home/pi/klipper/klippy/kinematics/corexy.py", line 64, in home
homing_state.home_rails([rail], forcepos, homepos)
File "/home/pi/klipper/klippy/extras/homing.py", line 185, in home_rails
hmove.homing_move(homepos, hi.speed)
File "/home/pi/klipper/klippy/extras/homing.py", line 85, in homing_move
wait = mcu_endstop.home_start(print_time, ENDSTOP_SAMPLE_TIME,
File "/home/pi/klipper/klippy/extras/beacon.py", line 1512, in home_start
trsync.start(print_time, self._trigger_completion, expire_timeout)
TypeError: start() missing 1 required positional argument: 'expire_timeout'
MCU 'mcu' shutdown: Command request"
37 Replies
Don't put this in your config and you won't break it 🙂
Added the z axis g28 z0 after failing. This has worked up until now. I need to home my y axis first then x axis at y360.
This is not the way to do that. It may have worked (except you've skipped every single RatOS related homing feature), but it sure doesn't anymore (and hasn't ever since
ratos_homing was introduced ages ago)
changing the homing order will be a supported feature in RatOS 2.1
The only way to achieve that in 2.0 is by copying the [ratos_homing] section from homing.cfg to your user overrides section and swapping the X and Y part of the homing routine.@miklschmidt Okay so
I modified the homing config file and the x and y work. but z still fails
removed the override section
Please upload your printer.cfg and i'll take a look
thanks
Delete that
if you want to change the safe home position use the
safe_home_x and safe_home_y RatOS variables: https://os.ratrig.com/docs/configuration/macros#homingConfiguring RatOS Macros | RatOS
RatOS comes with a bunch of flexible predefined macro's that can be customized via variables and macro hooks.
The reason it's broken for you is that you've defined multiple mutually exclusive homing mechanisms
You can only use one of
homing_override, safe_z_home or ratos_homing. ratos_homing is a combination of the homing_override and safe_z_home. RatOS only works with ratos_homing.interesting! I'll test it out
@miklschmidt I'm still getting the error
post your updated printer.cfg
@blacksmithforlife 🇺🇸
And you restarted klipper after changing printer.cfg?
@miklschmidt yesss
is your beacon extension up to date?
It looks like this fixes your exact issue https://github.com/beacon3d/beacon_klipper/commit/afcd4e98f257413aea2c14a48ffee0a0c7dc402b
@miklschmidt
yes I think it is
seems like it is a beacon issue
that is not the latest version
Do a moonraker refresh and update
should fix your problem
Oh i'm blind
you're right it is
the prefixed
g in the commit hash confused me
So @ElevatorMusic you prolly just need to restart the klipper service
Klipper won't reload the python file unless it's actually restarted
I've even rebooted the pi
@miklschmidt same thing
woot
Odd.. There's a pretty huge try / catch block on the exact line it's complaining about
@ElevatorMusic i'd try asking on the annex discord or post an issue on the beacon github (https://github.com/beacon3d/beacon_klipper/issues), remember to show them this https://discord.com/channels/582187371529764864/1199533915912798268/1199873889367503039 and mention the rpi booting :).
ouch ouch its getting serious
wait @ElevatorMusic when you setup your beacon did you go through the beacon install procedure? There's a chance you overrode RatOS's preinstalled beacon setup, and you're updating the wrong one.
Because i noticed you hardcoded a by-id serial in your printer.cfg when RatOS already handles all this for you
@miklschmidt I had my old beacon setup before ratos supported it. When I upgraded to the revH the serial wouldn’t work and so the solution I found was to hardcode it.
Yeah that's definitely it then, RatOS won't symlink the beacon.py file if it already exists in the destination. Go and update your old beacon installation and i'm sure the problem is solved 🙂
I would also advise that you either override the beacon entry in your moonraker.conf to point to your old installation or you delete the beacon.py file in klippy/extras and run
~/printer_data/config/RatOS/ratos-update.sh
Also RevH is supported in RatOS now so you can remove the serial.
btw the way you do that is by ssh, navigate to your old beacon installation cd ~/whereveryouputit and do git pull
I wonder if beacon and beacon klipper are both supposed to be there
@miklschmidt
beacon_klipper is your old installation
That's the one that's currently symlinked into klipper/klippy/extras
so delete it
That's why updating through Mainsail does nothing (that updates ~/beacon)
I wrote what you should do https://discord.com/channels/582187371529764864/1199533915912798268/1199894035867897957
if you just delete beacon_klipper you're gonna leave a dead symlink in ~/klipper
should get rid of your old installation, symlink the one managed by RatOS and restart klipper.
and it works!
moonraker was updating the other install
Thank you for all the help.
np 🙂