prime line not done properly

I'm having a bit of an issue with the prime line. Since I'm a right handed person, its a pain for me to have it in the front right corner. In RatOS1 the prime line was on the left side which was ideal for me. So I copied the content of macro.cfg into a new file, changed the reference in printer.cfg and got to work. Changed the variables to ~prime_start_x: "5", ~prime_start_y: "50" and ~prime_direction: "forwards" (which actually means that the printhead moves to the back!). But I'm not happy with the extruded amount, and the wipe is also "in the wrong direction" for me. But changing the prime-line macro doesn't change anything. If I paste my prime line from my RatOS1 config and comment the real prime line out, it gets ignored. Like there is a second prime-line macro that gets executed instead. But I can't find it anywhere. Also.... if I home the printer, get it up to heat and just manually type "prime_blob" in the console.... the printer does a primeline instead! How is this possible if I start the macro directly?
18 Replies
MightyMini
MightyMiniā€¢14mo ago
this is the only part of the config where i could find the definition of the primeline
miklschmidt
miklschmidtā€¢14mo ago
If you want to change PRIME_LINE, just override [gcode_macro PRIME_LINE]. If you're using PAM, it comes with it's own implementation which is just called PRIME i think.
Also.... if I home the printer, get it up to heat and just manually type "prime_blob" in the console.... the printer does a primeline instead! How is this possible if I start the macro directly?
That's probably your own overrides šŸ™‚ Wait, why are you overriding the entire macro's file?
MightyMini
MightyMiniā€¢14mo ago
well... i did change it, but it didn't have any effect. Didn't think, that PAM also has an effect on this. will check the config because maybe I want to change some more things, and that way I have more overview
miklschmidt
miklschmidtā€¢14mo ago
This is not a great idea You will break compatibility with future updates this way Please don't do this If you want to change a macro, copy that macro to your printer.cfg Do atomic changes, what you're doing here will bite you in the ass Basically change as little as possible to achieve what you want It sounds to me like your entire problem is solved by just doing
variable_prime_start_x: 5
variable_prime_start_x: 5
and nothing else. And then use prime blob primeline is shit šŸ™‚
MightyMini
MightyMiniā€¢14mo ago
whats the difference to when i copy the whole file... because if I only cope a certain macro and will get updated in the "master file" than it will have no effect either
miklschmidt
miklschmidtā€¢14mo ago
No, any changes made to RatOS macros.cfg would have to be made in your custom file too, or you'd get unexpected behavior and errors. So each time there's a change in RatOS you need to manually maintain your macros-adapted.cfg Don't do this I cannot support you if you go this way, it's impossible
MightyMini
MightyMiniā€¢14mo ago
i can#t change the primeline in the pam macro. as soon as helge updates it, its all back to the start šŸ˜¦
miklschmidt
miklschmidtā€¢14mo ago
Yes obviously you don't change the source files
miklschmidt
miklschmidtā€¢14mo ago
Includes & Overrides | RatOS
RatOS uses a modular configuration that heavily takes advantage of the config file include and merge logic in Klipper. For this reason, the order of includes and overrides are very important, do not change the order of the configuration unless you know what you're doing.
miklschmidt
miklschmidtā€¢14mo ago
Carefully.
MightyMini
MightyMiniā€¢14mo ago
ok but .... stuffing everything in the printer.cfg doesn't help to keep an overview in my opinion. So I put certain parts in seperate files that get included in the override section. Just like my file above. Why can helge alter the macros, and I'm not allowed (i mean, yes, he does a very good job), but I'm just not happy with the priming options given because I think the primeline from my old ratOS1 config worked perfect for me. I'll try the blob now, but I don't think I'm a fan of that. whats bad with the line? thank you for trying to make me a better user šŸ™‚
miklschmidt
miklschmidtā€¢14mo ago
but .... stuffing everything in the printer.cfg doesn't help to keep an overview in my opinion. So I put certain parts in seperate files that get included in the override section. Just like my file above.
Agree, and this is totally fine, just don't copy everything imaginable šŸ˜„ As long as you include those files in USER OVERRIDES, you're gucci.
Why can helge alter the macros, and I'm not allowed (i mean, yes, he does a very good job), but I'm just not happy with the priming options given because I think the primeline from my old ratOS1 config worked perfect for me.
It is not optimal, it is however a rather small change (he calls a new prime macro instead of overriding the old ones) compared to overriding every single macro to make a small change to the priming. It has however caused problems, and the fact that helge has to override RatOS macro's is one of the reasons why PAM is getting discontinued and a native solution will be implemented. KAMP is also an option, although it won't work with it's adaptive priming.
but I'm just not happy with the priming options given because I think the primeline from my old ratOS1 config worked perfect for me.
The current PRIME_LINE implementation is identical to RatOS v1, it just moved position, which can be customized via RatOS variables (https://os.ratrig.com/docs/configuration/macros#nozzle-priming) as you already did.
I'll try the blob now, but I don't think I'm a fan of that. whats bad with the line?
The line fails to properly capture ooze in all cases, the prime blob has a much higher success rate in my experience, that's why it's the default now. It's also much easier to clean up and doesn't permanently embed plastic in your build plate, like PRIME_LINE will, especially if you Z_OFFSET isn't perfect.
Configuring RatOS Macros | RatOS
RatOS comes with a bunch of flexible predefined macro's that can be customized via variables and macro hooks.
MightyMini
MightyMiniā€¢14mo ago
I don't get, why he had to change the priming for the print area mesh. Since the primeline was one of the first things i changed in ratOS1, I didn't recognise it. Made a relatively simple prime line where the nozzle moved a bit back over the line as a wipe and I never had issues. Lift 5 mm G1 Z5 F3000 # Move to prime area G1 X5 Y70 F{speed} # Get ready to prime G1 Z0.3 F3000 # Reset extrusion distance G92 E0 # Prime nozzle G1 Y160 E20 F1500 # Wipe G1 Y140 F{speed} # Reset extrusion G92 E0 was simple and quick
miklschmidt
miklschmidtā€¢14mo ago
I don't get, why he had to change the priming for the print area mesh.
For RatOS v2 he doesn't. For RatOS v1 he does.
MightyMini
MightyMiniā€¢14mo ago
i changed the preference in the variables now to "primeblob". I called "prime_line" in the console, but the printer did a primeplob instead. well... it tried, because the hotend was still cold šŸ«£ how is it possible that the printer executes something else than i told it to do? ah yes... pam just overrides them at the end. thats why.
miklschmidt
miklschmidtā€¢14mo ago
As long as you have PAM enabled, that isn't a RatOS issue oh you figured it out šŸ™‚
MightyMini
MightyMiniā€¢14mo ago
Thanks for the help and the info to look into PAM. I was working the last 3 days on this problem and nearly went insane. Never in my dream I had imagined that PAM would do that. Guess I know where to set the lever now. Any idea when the built in feature might be "ready"? (I know, Software development, spare time, ect.) may I DM you on another topic of an idea I have started working on just something nformative... no troubleshooting or anything