Fresh install of RatOS - internal errors.

It's been a while since I've had the minion up an running. Edited the wifi in the supplicant.. wouldn't connect. So fresh install.. it's an older minion. Has the SKR 407. after updating everything.. I can't home the axis's .. machine crashes. Starting a print crashes throws "error on maybe_home and start_print Will provide pictures of everything
62 Replies
TheTik
TheTik3mo ago
what version of ratos are you using? What errors? Why didn't you supply logs and config files? What have you tried to fix it and what changed?
SgtKiLLx
SgtKiLLxOP3mo ago
RatOS 2023-06-09 2.0.2 Initially, I edited the supplicant for the new wifi. It wouldn't connect. So I did a fresh install on the sd card The last time I had to do this for the same reason, in the config I selected the skr 2 429. Wouldn't connect. Selected the 407 and everything was fine
TheTik
TheTik3mo ago
the fresh install is stil 2.0.2, correct?
SgtKiLLx
SgtKiLLxOP3mo ago
Same image yep
blacksmithforlife
That's because you are supposed to use the configurator to change WiFi. The supplicant edit will mess it up
SgtKiLLx
SgtKiLLxOP3mo ago
I can't home. Can't start print
No description
SgtKiLLx
SgtKiLLxOP3mo ago
Oh well. Fresh install . But now I can't do nothing
blacksmithforlife
Ok. You should also attach your printer.cfg
SgtKiLLx
SgtKiLLxOP3mo ago
Can do 1 sec
TheTik
TheTik3mo ago
jumped the gun there well, I can actually open it up, but the name of the file sure is concerning
SgtKiLLx
SgtKiLLxOP3mo ago
take a gander cause maybe im missing something g28 crashes and "internal error on command "g28"
TheTik
TheTik3mo ago
attach klippy.log please
TheTik
TheTik3mo 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"
And did you make any edits to the printer.cfg? ooh, did you try updating ratos using the updater?
SgtKiLLx
SgtKiLLxOP3mo ago
Updated everything that way.. ☠️
TheTik
TheTik3mo ago
Does the printer move at all when you attempt to home, or just immediately error?
SgtKiLLx
SgtKiLLxOP3mo ago
No description
SgtKiLLx
SgtKiLLxOP3mo ago
Soon as I hit the home all it crashes
TheTik
TheTik3mo ago
How about if you try to home just X or just Y
SgtKiLLx
SgtKiLLxOP3mo ago
Shutdown
SgtKiLLx
SgtKiLLxOP3mo ago
No description
SgtKiLLx
SgtKiLLxOP3mo ago
Both x an y Should I go pull the sd and do another fresh install?
TheTik
TheTik3mo ago
I don't have any better idea yet, go for it and triple check you're using the correct board Fresh install, use the configure page to setup the wifi, update ratos using the update manager, reboot, update the rest, see if anything improves. I gotta run some errands for now, good luck
SgtKiLLx
SgtKiLLxOP3mo ago
well no change. im sure the board is the skr 2 407 when i select the 407, it connects. the skrat 1.0, nothing, the 429, nothing i can still heat the machine up.
blacksmithforlife
what do you mean by "nothing"?
SgtKiLLx
SgtKiLLxOP3mo ago
Attempting to home crashes the service But it can heat up the heaters . Detect the endstop status.. On the skr 2 407 But the skrat 1.0 and skr 2 429 is not the right boards @TheTik
TheTik
TheTik3mo ago
So strange that we're getting python errors. In my mind this means something went wrong with the install/updating, but if you're getting it after several install attempts I'm not sure what is going wrong. Nor do I know enough to debug the exact error :/
3DBoomer
3DBoomer3mo ago
Hey guys, I've been on the same issue for a week now. On an Mk3 setup : https://discord.com/channels/582187371529764864/1334134184738029629/1334134184738029629
SgtKiLLx
SgtKiLLxOP3mo ago
🤔
SgtKiLLx
SgtKiLLxOP3mo ago
we need someone that can actually help the board is an skr 2 407. selecting the 429 just causes issues so why when we try to home it crashes the entire service soo it turns out, upon actual inspection of the main chip on the board.. it is the skr 2 429 @blacksmithforlife 🇺🇸 😑
SgtKiLLx
SgtKiLLxOP3mo ago
No description
SgtKiLLx
SgtKiLLxOP3mo ago
i am getting this on Y tho i think it thinks the endstop is at the front oh nothings been updated and i am on rc2
blacksmithforlife
is it, or is the stepper moving backwards?
SgtKiLLx
SgtKiLLxOP3mo ago
stepper might be moving backwards but why lol @blacksmithforlife i put ratos 2.0.2 on.. same issue had no issue with rc2
Théodore
Théodore3mo ago
Hey ! i'm no expert but i think that i found the solution... Do a fresh install but do NOT update Beacon and KlipperScreen. (On RatOS 2.0.2) Quick summup of what i've done : - update ratos : reboot - update ratos-configurator : reboot - update everything EXCEPT beacon and klipperscreen (maybe even timelapse just in case) - Click Install macro on dashboard (Prusa MK3 in my case) - Done (Tell me if my msg is in the wrong section)
SgtKiLLx
SgtKiLLxOP3mo ago
🤔 ratos 2.0.2 is bad im back on rc2
blacksmithforlife
Because it depends on the way the coils are setup via the pins. Just change the config to move in the opposite direction after checking that it is actually moving backwards
blacksmithforlife
Configuring RatOS | RatOS
This is preliminary documentation for the upcoming v2.1.0 release. The work is still ongoing and the documentation is not yet complete.
SgtKiLLx
SgtKiLLxOP3mo ago
done
blacksmithforlife
And does it home correctly now?
SgtKiLLx
SgtKiLLxOP3mo ago
yep on the new ratos rc2 on 2.0.2 it crashes on home still so.,.
blacksmithforlife
2.0.2 is super old, use 2.1
SgtKiLLx
SgtKiLLxOP3mo ago
where is 2.1... that may be the prolem problem**
blacksmithforlife
Installing RatOS | RatOS
This is preliminary documentation for the upcoming v2.1.0 release. The work is still ongoing and the documentation is not yet complete.
SgtKiLLx
SgtKiLLxOP3mo ago
i am on 2.1 rc2 2.0.2 was my issue
Théodore
Théodore3mo ago
Yeah i can understand, but 2.1 on my mk3's doesn't seems to work for me, like at all. I hope that it can help someone at least, been working on this the whole week with @3DBoomer Nvm... It looks like its the systems OS-packages (200 of them) is the one thing that is messing everything up
SgtKiLLx
SgtKiLLxOP3mo ago
and i got my issue figured out
Théodore
Théodore3mo ago
Nice ! What did you do ?
SgtKiLLx
SgtKiLLxOP3mo ago
2.0.2 is bad 2.1 rc2 is what im running and all is well
TheTik
TheTik3mo ago
I'm wondering if it is the same issue where klipper updated something that broke a little backwards compatibility I was reading about in another thread Oh, no. Seems klipper and moonraker are pinned. The issue was with beacon library https://discord.com/channels/582187371529764864/1333487139756834816/1335291452015509576
SgtKiLLx
SgtKiLLxOP3mo ago
i narrowed it down to being ratos 2.0.2 being bad (as with any outdated code)
SgtKiLLx
SgtKiLLxOP3mo ago
No description
TheTik
TheTik3mo ago
Lookin good! And has certainly convinced me not to update my 2.0.2 and go straight to 2.1 once something prompts a change. Still have my beacon in the package, just haven't pulled the trigger as it is printing great for now
SgtKiLLx
SgtKiLLxOP3mo ago
for some reason the part cooling fan isnt coming on during the print nvm figured it out ya skip 2.0.2. iz bad code
TheTik
TheTik3mo ago
It is working for me. But I won't update.
SgtKiLLx
SgtKiLLxOP3mo ago
fair. but food for thought.. 2.1 rc2 reverses the Y and extruder motor on the minion, and sets the part cooling fan to digital , disabling it during printing
MDFPereira
MDFPereira3mo ago
The fan thing is set on configurator by the user. The direction issue is why there is that section on printer.cfg To not be stuck to a precise wiring.
SgtKiLLx
SgtKiLLxOP3mo ago
Ya. But in the configurator, the PCF is set to digital, which with the code from superslicer, when instructed for the entirety of the print, doesn't turn on. And the slider on the UI , maxed out disables, and set to 0 (or off) turns it on. So when the print is done, it cranks it.
MDFPereira
MDFPereira3mo ago
That is the thing. Configurator has nothing to do with the slicer. Is a hardware config thing. Digital PWM is for 4 pin fans. And for that, usually, you need a toolboard. You need to choose Input Voltage on the configurator.
SgtKiLLx
SgtKiLLxOP3mo ago
Learned that. But for some people that may not know.

Did you find this page helpful?