Ratos update 1.2.4.4 to 2.0.2 - no Klipper connection

I tried a 4th attemp to do an upgrade to the latest RatOS version. With the same result as ever. No klipper connection. Current setup RPi4 - Octopus 1.1 with all heaters, drivers & sensors etc connected. (I didn't disconnect anything before, during, after upgrade) When I succesfully automatically or manual (same result) the Octopus board during the setup and want to proceed to the mainsail screen after step 3 I don't get Klipper responding. Thus not able to access the mainsail interface. When I tried to reflash the MCU or simlink (3dots) I even don't get this working. Did I overlook anything? Should I remove alle cables, stepper drivers, ... during the installation of RatOS 2.x? I don't get it, thank you
17 Replies
Vannue
Vannue10mo ago
This is the result after the mcu flash
No description
blacksmithforlife
you cannot upgrade from 1.x to 2.x. it requires a reinstall by flashing 2.x image to a SD card and using that in your pi
Vannue
Vannue10mo ago
Sorry forget to mention this. I’m aware of this requirement. I’ve installed it everytime from a new flashed sd cards (tried multiple cards and windows/mac os)
blacksmithforlife
ok, then next thing to do is remove all connections to the octopus except for power and USB to pi
Vannue
Vannue10mo ago
Okay, thanks. I’ll give it a try over the weekend. I tried to avoid this step 🙈. Just out of engineering perspective, is there a reason why you should disconnect almost everything? Doesn’t make sense in my brains 😅
blacksmithforlife
things connected can cause issues, I have seen it where endstops, drivers, etc have caused flashing to fail. Once it flashed then everything was fine @miklschmidt any ideas what could cause this?
miklschmidt
miklschmidt10mo ago
1) Sd card in the board 2) DFU jumper inserted 3) Broken bootloader Or something electrical like you already mentioned.
Tracy7734
Tracy773410mo ago
I just did the same upgrade with everything connected and it flashed perfectly.
Vannue
Vannue10mo ago
alright, i did try the installation over the weekend with every stepper driver removed all wiring removed expect those to the ssr and power supply. Still with the same result. Even flashed the Octopus 1.1 with a manual firmware. I do notice that int the configure screen klipper is shown ora,ge, mainsail is green. This doesn’t change. I’ve started from a fresh sd card
Vannue
Vannue10mo ago
No description
Vannue
Vannue10mo ago
when I select “Flash all connected MCU’s” you can read the following. Maybe this can help you in finding the reason to my setup issue
No description
No description
miklschmidt
miklschmidt10mo ago
No description
miklschmidt
miklschmidt10mo ago
Seems like the boards bootloader is borked.
Vannue
Vannue10mo ago
Any suggestion? As when I place the sd card with ratos 1.x everythings is still working. Perhaps manualy uploading the firmware.bin via the sd card reader of the octopus board?
blacksmithforlife
It still works because the version of klipper flashed to the MCU matches the version on that SD card When I borked my bootloader I had to contact btt to get the original and reinstall it on my board
miklschmidt
miklschmidt10mo ago
Suggestion to what? You board is detected, it just won't flash automatically because it seems the bootloader is broken (it may throw this error if you leave the SD card in the octopus - don't do that). The workaround is flashing manually (and yes via SD card is fine) if klipper complains about version mismatch.
Vannue
Vannue10mo ago
I believe I’ve managed to get everything working. At least klipper is showing to be green during the full installation. Tomorrow I’ll put the wiring back. I used this my IOT network of which isn’t connected to the lan and that seems to work (maybe same issue as me,tioned at the setup page of os.ratrig.com that you need internet acces after connecting to the wifi) it’s not yet 100% as I get a “?” Mark for the klipper mcu version but as the stepper.drivers etc are working, then I’m happy. Thank you for the guidance gentlemen!
Want results from more Discord servers?
Add your server