RatOS 2.1RC1 SKR pro 1.2 automatic flashing fail
Hello, having automatic flash failing during setup on a V-Minion.
Board has an older RatOS version detect, I try do flash a more recent version and it fails after a while.
What's your guess?
95 Replies
Looks like the script is bad, which is very odd. Hasn't changed. Which flashing method did you use?
I tryed automatic, the first one on the left.
Ah, do you have an sd card in the board?
yes
aight let me check, i think this might just be because SKR Pro 1.2 only flashes automatically via a separate script. It's using an old borked bootloader.
Can't figure out where that 'e' argument is coming from
Just to give as input, It didnt show any erro flashing with old configurator on 2.0.2
it's not in the script
yeah there was some syntax fixes but i fail to see how that results in the error you're getting. I will find out.
well, I can try to go ahead on config with mismatch versions ?
yeah it's prolly fine. I'll see if i can find the bug in the mean time and let you know when there's something to test
Oh well.. I found it 😂
Thanks for fast reply btw
sure thing 👍
@spoown fix pushed, update "RatOS" and try the configurator again, should flash now 🙂
Ok. I’ll try. It’s slower because I use a zero2 😅
Ah yeah. I should bust out mine and see how big the difference is, it's been a while since i tested on a zero 2.
btw RatOS repo says corrupt. is it the configurator repo ?
No it's a bug in moonraker that was fixed after RC1
Hard recoverytime maybe?
It should fix itself if you update moonraker and reboot. If that doesn't fix it do:
And it should stop being a dramaqueen 😂
never use hard recovery it deletes the entire repository so you lose all the setup
if there's no way around using hard recovery (this should be very very rare), you need to manually run the update.sh script on the repository before doing anything else.
@miklschmidt I'm sorry, but new error..
oh boy lol
another fix incoming
It means I managed to update repo 😄
indeed! 😄
Should be actually fixed now, if you update yet again 😅
pushed, trying to flash already.... I have faith 🤞
This error I don't fully inderstand the problem
@miklschmidt ping 🙈
I ran again the version check and I don't get any version warinin, so it may be fine
Oh that's interesting, it actually flashed it just didn't exit properly
God my bash sucks
If you need that I flash again to test something later tell me
I think I found another mapping bug for the board... damn
I went back to the 2.0 style, it's pushed. If you could run it again at some point and let me know if that works, that would be nice!
tell me
I told Z motor on Z, and extruder in E0
stepper pin is same and got error duplicate pin
It may be a error pinmapping that board?
Not sure where the PE13 is coming from
That would be Z
not by hand 😄
ie, the one that is used for E by default in the RatOS wiring diagrams
did you actually save this?
yeah, i tryed to reconfigurate but it tells no change
because the screenshot you posted matches the default config
Is this in RatOS.cfg?
yeah
it doesn't have a slot assigned
... what the heck
Can you send me the debug zip?
need to look at the config it's using to generate this
this part is good
the extruder isn't mapped to that slot when it generates the config, it's still mapped to Z (or nothing and it defaults to the original assignment)
I had to change the default assigment I have on the wizzard
oh jesus christ i'm not including the files i actually need in the god damn debug zip :facepalm:
it was using Z on the extruder as I remember
Helping to help for some debugging 😄
Unfortunately i have to go and won't be back for like 5 or so hours
can you grab the contents of
will try
np, i should receive VC4, will be busy with other things
thank you!
ping me when you're back with something to try. Thanks for your help
This might explain it:
It's very strange since you literally just sent it to me
@spoown can you try deleting RatOS.cfg and Printer.cfg, then go to the last page of the configurator and save the configuration again?
still
I tryed to put E1 to provoke changes and then I saw
it's reading as it was already PE14
That's good. Can you send me the debug zip again?
@miklschmidt Didn’t apply the changes, I can try that and apply and send you debug
If you apply the changes and then change it back it'll work
Something went wrong somewhere in the process, and i'm not sure where
I'll try and reproduce it
.... i can't
Does exactly what it should do in my case
changed to E1, saved, same duplicate pinout
Ah it keeps fuckin it up in the extruder section
Reproduced!
Aight i'll get it fixed
I think I made it
I put Z ->E2
no, same problemwith PE13 duplicate
so it's a real bug? 🙂
Yes, and the generator. It looks for a toolboard pin specifically when the rail is assigned to an extruder axis, it then decides there is no toolboard in your case and then it falls back to default pin from the board pin map and never checks the slot assignment.
Yeah I don’t have tool board, yet.
fix implemented, live in 10 minutes
Worked 😉
it's FIXED !
Good work 👍🏼 if I find another thing I’ll open new topic
Excellent, thanks for reporting!
Ran into the repo corrupt on all repos issue. Updated Moonraker, which resolved the issue on all but one repo - RatOS
I ran the update script, that allowed me to update ratos. Post ratos repo update, the repo corrupt message also disappeared
Do you have the moonraker.log from this?
certainly, will send over in private chat
Seems like hard recovery failed and further broke it
Hard recovery kills all the setup so you have to run the update scripts manually
@Steef try that ☝️
I haven't used hard recovery though
and it's currently working as expected
ah sorry i misread
024-06-14 21:26:55,195 [git_deploy.py:_repair_loose_objects()] - Attempt to repair loose objects failed, hard recovery is requiredyeah i think the files are fine, just the repo is borked
let me go through my SSH log, a moment
The above should fix it
I used $ sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
after that, only RatOS reported as corrupt
however, it did provide me with an update botton for RatOS
that's safe to run, it'll restore setup stuff
after using the update for RatOS, everything worked
lol i think i missed this part 😂
so to summarize:
1. all repos report corrupted
2. $ sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh
3. RatOS reports corrupted
4. Update RatOS through interface
5. all working
6. profit?
It should be enough to just wait for moonraker to unfuck itself
It's a bug in moonraker that was fixed a week or so after the image was released
unfuck itself
😂
I'll tell it to do so 😛
If moonraker is up to date, all should be good 🙂
anyway, all fine, thanks for the hard work on 2.1
🙂
Thank you for giving it a shot! 🙂
presets scared the everlasting crap out of me though
800 mm/s on cooled v3.1 was about tripple what I ran manually before, lol
Welcome to real performance mode 😂
I'm at this exact step right now, first had everything corrupted, then updated moonraker
I'll try to run the update script as well
ssh pi@ratos.local
cd ~/printer_data/config/RatOS
git pull
sudo systemctl restart moonraker
I did this but still have the repo is corrupt showing up under ratos
will I have to do the setup and pid calibration again if I run this script?
~/printer_data/config/RatOS/scripts/ratos-update.sh
please start your own post
@AsicResistor I did
sudo ~/printer_data/config/RatOS/scripts/ratos-update.sh and rebooted, that gave me an update button for RatOS (though it was still reported as corrupted). After that update, all was well