Rat Rig Community [Unofficial]•2d ago

Internal error on command:"G28"

Hi all : PRUSA MK3S. Been running Ratos for a serious while; SD went corrupt so reinstalled. I've first tried 2.1 RC3 but wizard would fail systematically (same symptoms as : https://discord.com/channels/582187371529764864/1328642949373755482/1328642949373755482 ), so went-back to Ratos 2 Any help would be great, I have 4 of these bad boys nervously waiting for a fresh SD..... Many thanks in advance

40 Replies

TheTik•2d ago

Did you update ratos first, making sure it had a good internet connection?

3DBoomerOP•2d ago

Yes, in the right order

TheTik•2d ago

Got a screenshot of the actual error? What actions are you taking that trigger it? Include your config files as requested in the pinned post

3DBoomerOP•2d ago

printer.cfg

3DBoomerOP•2d ago

TheTik•this hour

hm. How about the klippy.log? Hopefully it'll show what the "internal error" actually is

3DBoomerOP•22h ago

sorry

klippy_18.log

3DBoomerOP•22h ago

I've gone as far as I could in the investigation but the klippy log is beyond my skills

TheTik•22h ago

Internal error on command:"G28"
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/gcode.py", line 212, in _process_commands
    handler(gcmd)
  File "/home/pi/klipper/klippy/extras/ratos_homing.py", line 42, in cmd_G28
    toolhead.set_position(pos, homing_axes=[2])
  File "/home/pi/klipper/klippy/toolhead.py", line 466, in set_position
    self.kin.set_position(newpos, homing_axes)
  File "/home/pi/klipper/klippy/kinematics/cartesian.py", line 69, in set_position
    axis = "xyz".index(axis_name)
TypeError: must be str, not int
Transition to shutdown state: Internal error on command:"G28"

Internal error on command:"G28"
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/gcode.py", line 212, in _process_commands
    handler(gcmd)
  File "/home/pi/klipper/klippy/extras/ratos_homing.py", line 42, in cmd_G28
    toolhead.set_position(pos, homing_axes=[2])
  File "/home/pi/klipper/klippy/toolhead.py", line 466, in set_position
    self.kin.set_position(newpos, homing_axes)
  File "/home/pi/klipper/klippy/kinematics/cartesian.py", line 69, in set_position
    axis = "xyz".index(axis_name)
TypeError: must be str, not int
Transition to shutdown state: Internal error on command:"G28"

something is not right about how you installed or updated ratos. If you're on 2.0.2 then you don't have the convenience of ratos doctor. I'd recommend starting over again with flashing.

3DBoomerOP•10h ago

Ok. But flashing fails. Via ssh ? Make flash etc ? Installing 2.1? I had not heard /read anything about ratos doctor, I'll give it a try Hummm... I have raspberries 3a+ in my mk3s.... I'm afraid they're too weak to run 2.1. I must stay on 2.0.2

TheTik•4h ago

Docs say that 3A+ should be enough

3DBoomerOP•4h ago

Yep 3A+ should be fine.... I don't get it : I've gone through klipper and RatOS install so many times over the last 2/3 years.... It's usually straightforward. Should I roll back to RC1 ? I've succeeded 3 full installs with it recently. Could that help ? Just the initial updates after connecting to the net takes ages

TheTik•3h ago

"flashing fails" how?

3DBoomerOP•3h ago

OK : just spend hours on RC2. Looks better (updates more easily) but still same bug

3DBoomerOP•3h ago

klippy_21.log

3DBoomerOP•3h ago

printer_10.cfg

3DBoomerOP•3h ago

Just tried adding the following (early in the printer.cfg file), nos success : [MCU] serial: /dev/serial/by-id/usb-Prusa_Researchprusa3d.comOriginal_Prusa_i3_MK3__-if00

3DBoomerOP•3h ago

I might be completely beside the point, but I see this :

3DBoomerOP•3h ago

And this is weird as well, I can't soft or hard recover anything from the Ratos github (that's on a V-core 3.1 / Rasp 3b+ I'm trying to update as well)

3DBoomerOP•2h ago

blacksmithforlife•2h ago

don't hard or soft recover a repo, it messes everything up

3DBoomerOP•2h ago

OK. What should you do then when it appears as broken ?

blacksmithforlife•2h ago

mainsail for some reason shows it as invalid, but really that is just that it hasn't been able to get the updates yet. Try refreshing the updates and wait but now that you are in a bad state, it is easier to start over with a fresh Pi image

3DBoomerOP•2h ago

I have tried to refresh / Wait / reboot many times.

blacksmithforlife•2h ago

I would start investigating your network setup

3DBoomerOP•2h ago

No... Network is is fine, I have several other printers running fine (Ratos 2.0.2 mostly, 2 x 2.10 printers.... WIFI 2.4, same SSID for everyone. Been running it for years

blacksmithforlife•2h ago

I can only point to what mainsail is doing. Drop your debug.zip into the chat

3DBoomerOP•2h ago

Where can I find this guy ? (Many thanks for being here by the way 😉

blacksmithforlife•2h ago

the pinned comment in #ratos-support details how to get it

3DBoomerOP•2h ago

OK ! That's from the V-Core 3.1 / Rasp 3b+ / RC1 I'm currently trying

ratos-debug.zip

3DBoomerOP•2h ago

Interresting : we've just wired it to the network rather than wifi : looks much faster. Previous releases or RatOS were notthat slow on wifi

TheTik•1h ago

might have something wrong with the wifi on that particular raspi if the others on your networks are fine

3DBoomerOP•1h ago

Both rasps I'm currently trying have been running Ratos 2.0.2 for a while on wifi, same network (Same Unify relays, using just the 2.4 ghz SSID)

3DBoomerOP•1h ago

This one is on proper RJ45 now, directly to the router. I've let them run quietly for a while, all items look ready for upgrade now, except these 2 guys :