Incomplete slicer config. used the default profile for v-core 4 500 hybrid in orca
I tried also pasting the provided info from GitHub but I get the same message.
Another problem I have is that I keep getting prompted for invalid mesh coordinates
Any help would be greatly appreciated
31 Replies
And it also seems like I’m unable to save my z-offset
I’m probably just stupid but I’m lost here…
What slicer and version are you using. For orca and prusa on the latest version I have not had any issues. Go back and double check that you have all of the fields copied over. As for the mesh when do you get that. Also how are you trying to save your z offset.
I’m using orca’s 2.2.0
It sounds like you didn’t copy the gcode start over correctly. Double check that
Make sure to click the copy button on the GitHub page as it might have more scrolled to the side you don’t see
To save the z-offset I did as in the guide, changed it during a print, when happy about it I sent in the console a save_z_offset
Then cancelled the print and hit save config
START_PRINT EXTRUDER_TEMP={first_layer_temperature[0]}
EXTRUDER_OTHER_LAYER_TEMP={nozzle_temperature[0]} BED_TEMP=[bed_temperature_initial_layer_single] CHAMBER_TEMP={overall_chamber_temperature} TOTAL_LAYER_COUNT={total_layer_count}
TOTAL_LAYER_COUNT={total_layer_count} X0={adaptive_bed_mesh_min[0]} Y0={adaptive_bed_mesh_min[1]} X1={adaptive_bed_mesh_max[0]} Y1={adaptive_bed_mesh_max[1]}
This is what I have
I am on my mobile so cannot compare things right now
I can check later though
I’ve tried with the default one, with the one on GitHub and also tried prusa slicer’s one
Thank you, that would be perfect
You have fully updated ratos under the machine tab?
Yep
Missing just the klippy screen
I also checked if the mesh is actually saved and it is, at the end of the printer.cfg
Your start code is different than the github recommendations. Not sure if its a cut and paste error or not. It should be Double check the fields as well. https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/slicers.md#orca-slicer
GitHub
RatOS/site/docs/slicers.md at documentation_v2.1 · HelgeKeck/RatOS
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - HelgeKeck/RatOS
you have like two total_layer_counts in there
Like chicken is saying, these are not supposed to be multiple lines. That's why it's failing.
I had the same result also when using the default profile, I will still try to change them again, probably the problem with the z offset occoured due to this
the orca profile might be outdated for all i know, i'll take a look
The orca profile has the exact same bug that you made manually https://github.com/SoftFever/OrcaSlicer/blob/main/resources/profiles/Ratrig/machine/RatRig%20V-Core%204%20300%200.4%20nozzle.json#L41
GitHub
OrcaSlicer/resources/profiles/Ratrig/machine/RatRig V-Core 4 300 0....
G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.) - SoftFever/OrcaSlicer
Notice the
\n that is not supposed to be there that breaks it into two commands, ie, everything after that \n is ignored because it's invalid.
@Cruz :this:Thanks! Will look into it
if you want i can submit a quick PR
I will do it. Eventually, but if it is a quick job for you I'd appreciate it
I'll only be able to do it next week
Tomorrow morning i’ll check out if this corrects the issue and update you, thanks to everyone
Just noticed yours have never been merged, the current ones are unofficial. Yours don't have the error.
Dam PR 🥲 never got officially submitted
You just posted a big ass zip file in the issue section 😂
GitHub
Fix invalid START_PRINT in unofficial Rat Rig profiles. by miklschm...
Description
This PR fixes a pretty major bug in the current Rat Rig V-Core 4 profiles shipped in OrcaSlicer, where the START_PRINT arguments where broken up by a linebreak, resulting in non functio...
As I did with prusaslicer and they published it 🤣
"Here you go, you fix it" 😂
Kinda😅 i spent more time testing than submitting it, will make in proper next time for sure
Good time for it. Hopefully it'll make the next release.
Now everything seems to work fine, thank you very much