Orca Slicer not uploading to VC4. Error 7. Network unreachable.
I deleted my main 0.4 nozzle preset profile in orca slicer and now orca wont upload to the printer. I have confirmed the ip address rat.os local and it says its connected and working. The device tab also allows me to operate the printer still as well but still cant upload. Any help would be appreciated!
13 Replies
Might be a better question for #slicers , in the meantime are you able to upload files manually using the mainsail interface?
Im slowly learning there is something wrong my klipper and that is why orca cannot upload to it. The update manager now will not update most of the files below and they are invalid without success with hard recoveries.
Currently ssh into my pi and running ratos doctor. It has identified a problem and is now installing dependencies.
good, hard recovery will break things but the doctor is intended to fix those very things
so im at the point where the doctor failed again i think and dont worry they will fix it. installing dependencies. then nothing has happened for a while. not sure whats going on.
they said dont worry they will fix it. installing dependencies.
it might take a few minutes, let it ride and lets see what the output is
im using mobaxterm to do this. how do i refresh the page. I see the refresh the folder icon is that the same thing ?
no, i corrected myself. Got confused with a different procedure.
thank you for responding and your help by the way! It is greatly appreciated !
No promises on results, but happy to do what I can 😛
If you're able to ssh in, are you also able to get to the web interface?
Error:
at /home/pi/ratos-configurator/app/node_modules/.pnpm/zx@8.1.4/node_modules/zx/build/core.cjs:105:43
exit code: 7
RatOS package issues detected! Don't worry, we'll try to fix them for you...
Installing dependencies...
~/ratos-configurator/app ~
this was the last error for reference
i was able to get on the interface before going down this road. What i was not able to do was upload from orca slicer directly. I was able to do so last night but i abruptly unplugged it after realizing i forgot to move a print off the bed before homing. i heard the toolhead crushing the print as it was touching the bed. it was only a max flow rate test not a lot.
thats good, you can at least upload gcode that way while you wrestle with this
well now i cant connect to anything during this process
still at the same spot
open a second xterm and verify you can still ssh in?
then maybe something like
top to see if the doctor is still running? Dunno if that will work but worth a shot