Latest update rendered Vcore 4 nonfunctional
I had updated everything last night as I was working through some print quality issues with T1. The fan on T0 stayed at full 100% despite my test printing with T1. It would not respond to Mainsail at all. So this morning I updated all components again and I get this error. I can't find the RatOS section containing this variable. Any thoughts on fixing this situation?
Solution:Jump to solution
Mine is working again. Try shut down your printer, get him off and restart after a few seconds. Then reload the updater and then should be a klipper update there. After this all seems to be fine.
45 Replies
please share your debug.zip file
Same failure here.
Where/How do I find the debug.zip that is needed?
Solution
Mine is working again. Try shut down your printer, get him off and restart after a few seconds. Then reload the updater and then should be a klipper update there. After this all seems to be fine.
its in the ratos configurator in the navigation drawer
please first make sure there are no other updates available
One just popped up for Klipper on my machine page
running it now
Did it but the klipper update was first shown after full restart.
if the error persists pleae ssh into the pi and run
Can confirm that the error only appears to occur if that Klipper update hasn't been run yet. And, it only appeared for me after the full reboot like @Dor_Amboss .
My is booting again. Thanks very much!
Apologies - I had to mark this one as not yet solved. I still can't run a print. Getting a new set of errors when I try. I'll post a new debug.zip and I try the sudo update.
the same error?
whats the issue exactly?
It can't resolve the path to the files.
From the console.
@miklschmidt any idea what can cause this issue. afaik we didnt touched any of that
is it maybe bc of the symlink we added to the config folder?
can you try to print something directly from the slicer
I can try to get to this. I haven't set it up to print directly, and it may take me a bit.
then just upload a file via drag nd drop and try to print it
checking logs
without moving it to other folders
"The file format is from an old version of RatOS which is no longer supported. The original file must be re-uploaded or re-sliced."You can't print files processed by the legacy post-processor so you have to reslice those.
isnt that the issue i once told you about, raise error within a try catch doesnt print the message to the console
this is super misleading
It should have given you a prettier error though
Can you send me the bad file (ie. download it from mainsail and post it here)
No 🙂
Raise error in a try catch, catches that error in the
catch block and then you deal with it there. That's how try catch works everywhereyeah, im aware of that. but if you dont handle the actual message in the catch block then it leads to this useless error messages in the console
im pretty sure you have a much better error message in the code
Yes, of course, or rather, you'd have to raise it again (which i do on purpose)
Thanks - it does again start a print. Re-uploading the file was the issue. It does throw up a post-processing message as well.
I'd still like the old file so i can show a proper error to people (i need the file to reproduce the problem)
Only if you don't mind of course, if it's proprietary or secret etc then i'll find another way 🙂
I'll mark it solved again. I will mention one other weird thing. My T0 fan goes to full 100% during the whole print, even though I'm printing with T1.
Other than that - thanks very much!
This sounds like wiring to me. When exactly does T1 go to 100% and does it stop at any point?
T0 and T1 go to 100% when Klipper boots, then both go to 0%. The file I'm printing uses only T1. So I start the file and both heads move to the middle and T0 goes to 100% but T1 stays at 0%. Then when the print startes, T1 is printing, which normal fan control, but T0 moves over to its park position (after beacon, etc) and goes to 100% constantly.
@Helge Keck any idea here?
I have the same issue and I have just posted a new request.
please try to turn on both fans indivdually t test if they work
if you print with T1 only its normal both toolheads move to the middle before the print starts, to heat soak both of them equally before doing the automated z-offset calibratrion
also, before a print, when heating the chamber its also normal that only one fan turns on, its made to circualt the air during heat up
i would need a gcode file to check why T0 blows when printing with T1
I'm at work. I'll test these things when I'm home tonite.
I found that there is an issue now when printing gcode from PrusaSlicer 2.9.0-rc1. No issue I have found so far with PS 2.8.1 using same STL.
2.9 is not supported, we'll look at it once it's released. Like it should tell you, you can allow unsupported slicer versionens if you want to try and process it anyway, but in you should stick to the supported slicer versions.
I found a wiring issue and pretty sure it explains the fan behavior. Thanks for your help.
Sorry, my bad. I didn't see and havent seen any error or note informing me I am using an unsupported slicer. Prior to upgrading I was using 2.9.0-beta1 (not as my primary slicer I have to add) and didn't see or experience any issues with printing.