Cartographer in RatOS 2.1
Hi @miklschmidt
stumbling on setting up RatOS 2.1 with m cartographer.
I installed like shown in their HowTo. I used the configurator and choosed there "Generic probe".
I then added a section [probe] to the printer.cfg and added there the z_offset= 0.0
Problem now:
How can I get around there?
27 Replies
Cartographer is not supported for multiple reasons. I know this sucks to hear, but get a Beacon.
You should not have a [probe] section in your config.
Well... not supporting a common used and well working probe is really shitty.
If I remove the [probe] section I get another error:
Well... not supporting a common used and well working probe is really shitty.It's neither of those things imo. But that's not why it's not supported. there's tons of work involved in supporting these things and Cartographer is a bare minimum approximation of the Beacon that involves a hacked klipper repository and non mainline features. It's no where near mature enough for integration.
okay got it... Seems I need to stay on RatOS 2.02
Either that or do a scan of
beacon in the codebase and start overriding
And figure out how to deal with the klipper hacks etc.had a short look into the LOG …
found a BL-touch part enabled
@miklschmidt … is this included if the user is choosing
Gerneric within the configurator?
or it has to be the content of probe.cfg
maybe an idea for the Configurator:
if the user insists to use things like the cartographer an „manual“ entry (resulting in no probe content at all) with a warning to do all manually
i know this will break some basic ideas of RatOS somehow - so, I think it‘s not a preferred wayprobe.cfg === Generic [Inductive] Probe, yes.
the cartographer and IDM are not generic probes
maybe an idea for the Configurator: if the user insists to use things like the cartographer an „manual“ entry (resulting in no probe content at all) with a warning to do all manuallyYeah, i'm a bit afraid this a can of worms, because a large majority of the RatOS macros behave differently based on what kind of probe is installed.
yes … was wondering why there‘s a BLtouch config included
There's no bltouch config included?
at least there's not supposed to be unless you pick it 😄
and thats is the other major point against „manual“ stuff
It's not impossible to add hooks and levers to opt-out of automatic Z handling and implement your own. It's just quite a big feature request, definitely something we can look into after 2.1
doh … sorry for that! … checked the wrong editor tab
will make a yellow sticker on top of the phone:
do not open many logs on a small device - this may lead into confusion
Oh man i can relate lol
yep .. brings me into another basic question
what’s the/your preferred way? as a support case within Discord or as an Issue at GitHub?
Should probably be a combination, it's gonna need a PR for the development branches on RatOS-configuration and RatOS-configurator. So i guess start by creating feature requests there and cross reference them (you can do that with
org/repo#12312.)
We can keep this channel open, once i have time (eeeh.. it's gonna be a while) i can make an overview of what needs to be done.
Btw, this same thing goes for the IDM and the BTT Eddy
Eddy is taking the mainline approach, it's just nowhere near completion yet. The basics are there, but the rest of it requires running their klipper fork.
All of them are lacking the advanced features of the beacon (comprehensive built-in active temperature compensation, beacon contact, data dump streams etc), and rely on all of the work being done on the pi by processing the raw stream from the eddy current sensor, it's quite a different approach that has some quirks.
i believe the cartographer in particular tries to emulate some of it, but i haven't had a chance to diff their modification of the beacon klipper module.
Yeah sure. RatOS is made for those who want an experience closer to a modern "off the shelf" printer. If you're into doing it yourself, you definitely should, it's a lot of fun 🙂
I've seen the work that's gone into making this whole thing work. I don't have a lot of confidence in the clones catching up as it stands right now. But this is not a "my probe is better than your probe" type of thing, it is what it is. I understand some people wants to save money wherever possible, but as usual that means there's stuff you need to do yourself.
You trade your time for money as with everything else.
I know
It doesn't, it requires you to modify the parts that needs modification for your unsupported hardware modification.
Just like a vanilla klipper installation does
Afterall RatOS is just a tool to generate configuration and macros for you.
You can install RatOS 2.1 and just not include RatOS.cfg. Write the whole thing yourself. Pull in the bits and bobs you want etc.
You can literally do anything you want.
It doesn't mean you can save 20 dollars on a copy of a probe and then expect me to use my free time to make it work for you.
If that was the case, i'd rather pay you those extra 20 dollars. The time i've spent in this thread alone has already cost me more.For me it´s not the point of the money... When I installed the cartographer, the beacon was not available... and I don´t throw away this good working probe. I know guys who have both and they don´t see any difference in probing and mesh results.... So why should I switch?
“offering a 3d printer with fitting firmware”I'm not offering 3d printers. I work for Orbit Online, not Rat Rig.
and then making it so hard to users to adaptIt's no harder than any other klipper installation.
But not “trusting the clones” to work is a cheap excuseThat's neither my "excuse" (what would i be making excuses for exactly?) or the case for not supporting them. I focused on the most popular, most feature complete and the easiest to use. That happens to be the original.
And with a difference of like 30-40 Bucks that’s quite a good amount to save for many people.Yes i understand that, but it comes with trafeoffs such as out of the box support.
When I installed the cartographer, the beacon was not available...As in sold out?
I don´t remember the reason why it was not available... on top I had to buy it in the US.
I know guys who have both and they don´t see any difference in probing and mesh results.... So why should I switch?You're at a point where you want one thing to work with the other, and you don't know how to make that happen. That leaves 2 options, wait for someone else to do it, or buy the one that already works.
Nevertheless... I´m back to RatOS 2.02 now. So may be I will switch if I run into issues with the cartographer.
👍 RatOS 2.0.2 will still run until something upstream breaks it (and then you can work around that yourself etc etc).
There's a nice list. Also you can ask 🙂
Also cartographer isn't supported in klipper
You need to modify it with third party code (that cartographer supplies)
Which means it may break at any point and then you're relying on the Cartographer team to make things work again
Yes, but beacon is backed by a company and two of the most capable devs in the klipper community.
Also the vast majority of the beacon functionality happens on-device.
Not in klipper.
Like i said, backed by a company, very capable devs with a proven track record.
Biased how?
Am i biased for making a pros and cons list?
Am i biased for supporting a product before random clones start popping up and then not immediately supporting them?
You are Argumenting over random points that don’t really change if it’s good or bad Probe.Yeah, because that doesn't matter to this thread.
Carto also isn’t just a Garage company. And just as the Carto Dudes might not be the 2 like beacon has, that automatically makes you thinking it’s not as valid of a code as beacons code is?It's not a company at all, is it?
At the end I don’t care, as I would use the firmware that gives me the freedom of doing whatever I want. But kinda feeling bad for people finding out that ratos doesn’t support carto even though it’s based of Klipper.You have a completely warped idea of what this is. RatOS isn't a fork of klipper. RatOS is just tools to help you use klipper. Those tools support a specific set of hardware to generate a configuration and macro setup for you, so you don't need to learn how linux, raspberry pi's, klipper, moonraker etc works. It's free, it's open source, you can modify it however you like. You can override everything after the configuration is generated, you can copy paste or whatever you want, it's literally just klipper. What you're complaining about is that i don't want to spend time supporting (in the sense that i don't want to write klipper configuration for you in my free time) a non-conforming copy of a product. Not even that, you're complaining that i don't want to do it right now. That's not the case. Whatever dude, i'm done with explaining why i haven't invested the hours of work it takes to make that thing work out of the box (which comes with all sorts of caveats because it is very much diy and unstable). If you have a problem with that, that's on you. Now please get out of here so we can get back to options for how we can implement hooks and opt-outs to facilitate running these things with the users own macro implementations. No, i'm not calming down. I've worked my ass off for 6 months on RatOS 2.1 in my own free time, to make your lives easier with a quite broad range of hardware, and then you come in here shitting on me because you have to do some work yourself to use a non-conforming clone. Yeah, that pisses me off. To make it absolutely crystal clear. Not supported in RatOS = you'll have to do it yourself like any other klipper installation.
You're misconstruing my words, you don't listen to what i'm saying, you're just here to tell me i'm biased and i should spend my time differently
Seriously
Okay. Silence now.
Mikle you have the patience of a saint for entertaining these complaints
Jesus Christ this thread. Mikkl went way farther with these clowns than they deserved
let's remember to be kind to all even if we disagree.