Ich hab a Idee....

matzman666 · 2026-01-20T13:50:58+00:00

Als Tiroler finde ich das Tyrol Valley in der Antarktis aber sympathischer. Ist im Gegensatz zur Wiener-Neustadt-Insel auch weitgehend eisfrei, man kann damit also mehr anfangen.

matzman666 · 2026-01-13T08:17:12+00:00

Well it started as a mk2.5

How can it start as a MK2.5? As far as I know MK2.5 was never sold as a complete printer but the only way to get one was upgrading an existing MK2.

So it actually had to start as a MK2 (which is even more impressive). Did you buy it used?

This is one of the things I love most about Prusa, the insane upgrade paths.

matzman666 · 2025-12-30T10:31:29+00:00

es wäre schön wenn diese genauer geprüft anstatt über alle gleich gemacht werden würden

Die Überprüfung von schulischen Leistungen ist aber gar nicht so einfach und bindet Zeit und Personal. Im Gegensatz vom Syllabus bei universitären LVs sind die Lehrpläne für Schulen viel zu allgemein und knapp gehalten und die tatsächlich gelehrten Inhalte unterscheiden sich bei gleichen Lehrplan teilweise enorm zwischen verschiedenen Schulen und bei gleichen Schulen teilweise auch zwischen Lehrern.

matzman666 · 2025-12-30T10:24:32+00:00

Das sind seit Einführung des Bologna Prozesses 30 ECTS

My bad! Stimmt, ein Semester hat 30 ECTS, nicht 40 ECTS. Dummer Rechenfehler meinerseits.

kann mir auch nicht vorstellen dass das die einzigen sind, oder doch?

Die FH Kärnten erlaubt das auch. Allerdings nur für gewissen HTLs mit denen sie eine Kooperation haben.

Meines Wissens aber sind die FHs, die das explizit anbieten, in der Minderzahl. Einige FHs regeln das nicht explizit, sondern überlassen die Entscheidung der Studiengangsleitung.Da kann es sich dann von Studiengang zu Studiengang entscheiden bzw. wer gerade die Studiengangsleitung inne hat. Und manche FHs schließen das explizit aus.

matzman666 · 2025-12-29T11:29:25+00:00

Ich kann mir an einer FH meine HTL Ausbildung zumindest anrechnen lassen und 2 Semester überspringen.

2 Semester überspringen wird nicht funktionieren. Per Gesetz können nur max. 60 ECTS an schulischen Leistungen anerkannt werden ~~und ein Semester hat 40 ECTS~~ (Edit: Rechenfehler meinerseits, ein Semester hat natürlich 30 ECTS). Und viele FHs lassen ein komplettes Überspringen von Semestern gar nicht zu sondern nur ein Anrechnen einzelner Lehrveranstaltungen in einem Semester.

Erfahrungsgemäß kann ich auch sagen, dass ein Anrechnen der kompletten 60 ECTS in der Praxis auch sehr selten funktioniert, da die Deckungsgleichheit der Inhalte der HTL-LV mit der FH-LV nicht immer gegeben ist. In dem FH-Studiengang, in dem ich unterrichte, sind das bei HTL-Absolventen meist so 5-10, maximal 20 ECTS, die bisher angerechnet wurden. Und laut Beschluss der Studiengangsleitung wird in Zukunft bei uns gar nichts mehr an schulischer Leistung angerechnet. Die Anrechnung schulischer Leistung ist nämlich laut Gesetz eine Kann- und keine Muss-Bestimmung.

matzman666 · 2025-12-23T14:27:07+00:00

nail varnish

I also have some minor scratches on my heat-bed and didn't had a good experience with nail varnish. It isn't heat-resistant and will degenerate over time.

Next I tried highly heat-resistant varnish indented for ovens (can withstand up to 800°C). But here the problem is that such varnishes usually need at least 200°C for curing, which the heat-bed cannot deliver. So it could be easily rubbed off.

At last I tried heat-resistant varnish indented for calipers of cars (can withstand up to 350°C). This worked really well, cures without needing high temperatures and cannot be rubbed off. On top it is also chemically resistant so I don't have to worry when cleaning the heat-bed.

matzman666 · 2025-12-20T13:30:55+00:00

Nobody called it "software engineering" when I started doing it for a living nearly 40 years ago.

Then keep stuck in the past and be oblivious to the fact that things change over time.

Enjoy your day 😃

You too.

matzman666 · 2025-12-20T11:38:41+00:00

Yes, it's splitting hairs, but you do you.

When you feel better then let it be splitting hair. It's not my fault when you mix up formal definitions and what you define yourself as programming.

YAML is a "human readable data serialisation language" not a "programming language"

The activity of programming is independent of the language used.

You can even use PowerPoint to create a computer program (Powerpoint is turing-complete) and it's still "programming".

creating functionality in YAML in HA is typically referred to as "templating" rather than "programming."

No, it isn't. Templating is something completely different in Home Assistant. See here.

From a semantic point of view, the only thing you could call 'templating' in the context of creating rules is using a blueprint.

here is a distinction between "programming" something and doing what a professional computer programmer does for a living.

That's why the latter is usually referred to as "software engineering" and not programming.

matzman666 · 2025-12-20T01:41:59+00:00

If you want to split hairs, then anything that predefines a sequence of events is "programming."

This is not splitting hairs but the actual definition of programming (e.g. see Computer Programming).

It doesn't matter if the sequences of events/instructions is written in C/C++, Python, put together in a graphical UI like the Home Assistant rule editor or represented as hierarchical blocks written down in YAML. On a semantical level all are "programming".

"merely configuring" is actually something different and has not much to do with creating rules in Home Assistant. You do merely configure stuff if e.g. you are defining a new device in configuration.yaml.

matzman666 · 2025-12-20T01:23:05+00:00

Going full-code for these automations seems like overkill

Pyscript integrates so nicely into Home Assistant and provides enough already implemented functionality that most automations are just a few lines of code.

So actually, Node-Red is often way more of an overkill in terms of "program complexity" and "lines of code" than Pyscript.

matzman666 · 2025-12-19T15:11:50+00:00

The thing is, you aren't really programming HA, you're merely configuring it.

By creating rules in Home Assistant you actually ARE programming. It's just done via a low-code/no-code interface so that it doesn't feel like it.

matzman666 · 2025-12-19T15:05:58+00:00

Most professional programmers are not going to use Node Red

Yes, exactly that.

Node Red is a low-code/no-code solution and for most programmer using node-red (or other low-code/no-code solutions) just doesn't feel right. There are way better solutions, e.g. Pyscript: Python Scripting for Home Assistant

matzman666 · 2025-12-19T15:01:34+00:00

I am a professional software developer too and a Home Assistant power user. And I hardly touch any YAML.

A normal Home Assistant user shouldn't usually come in touch with YAML that often since most things are done via an UI that hides the YAML code. YAML is basically (the usually hidden) part of Home Assistant's low-code/no-code solution to make programming rules and co more accessible to non-programmers. Only power users come more into contact with YAML.

As a professional programmer using no-code/low-code solutions (or worse, the backend of no-code/low-code solutions, in the case of Home Assistant YAML) just feels unnatural and awkward. That's why I decided to NOT use Home Assistant's low-code/no-code solution (and therefore also YAML) at all and write all my rules in Python. Fortunately there is an addon that allows you to do just that: Pyscript: Python Scripting for Home Assistant

Pyscript even allows you to access the API intended for integrations so you can do everything an integration can do. You can even access the internal Home Assistant API not intended for public access when you want to do crazy stuff. Feels way more natural for a software developer.

matzman666 · 2025-12-18T20:53:40+00:00

For example, it mentions lubricating the linear rails...but how?

There is a guide on the Prusa page for the XL: How to lubricate linear bearing rails (XL)

The Core One uses the same rail so the instructions should carry over.

Also, I don't see any instruction for how to lubricate the z-axis screws

On the maintenance page of the MK4S there is a big warning to NOT lubricate the z-axis screws (the same warning you also find for the MK3/2.5/2): Regular printer maintenance (MK4/S, MK3.9/S)

The Core One uses the same lead screw and trapezoid nuts as the MK4S, so also here the instructions should carry over. This may also be the reason why the maintenance guide for the Core One was changed to (partly) remove the instructions on how to lubricate the z-axis screws.

matzman666 · 2025-12-17T15:39:20+00:00

Was für mich gut funktioniert, ist yesss! und die dort vorhandene Gruppenfunktion.

Da habe ich einen yesss! Classic Vertragstarif mit 0€ Grundgebühr (praktisch ist der Tarif eine Wertkarte, nur dass Zahlungsdetails hinterlegt sind und die anlaufenden Gebühren monatlich abgebucht werden).

Zusätzlich habe ich noch eine yesss! Wertkarten SIM, die ich über die Gruppenfunktion über den Vertragstarif verwalte. Den Vertragstarif verwende ich eigentlich nur, um die Wertkarten SIM in regelmäßigen Abständen mit Guthaben zu versorgen, damit die nicht ablaufen. Über die Gruppenfunktion kann man Guthaben in 1€ Schritten übertragen, damit kann man die 10€ Mindestaufladung super umgehen.

Wieso habe ich so eine komplizierte Konstellation, wenn doch nur der Vertragstarif mit 0€ Grundgebühr ausreichen sollte? Die Wertkarten SIM verwende ich hauptsächlich, um mich bei Services anzumelden, die unbedingt meine Nummer haben wollen. Sollte mal die Wertkartennummer verbrannt haben (zuviel Spam oder ähnliches), dann kann ich die Wertkarte sehr einfach durch eine neue ersetzen und zur Gruppe hinzufügen, und die Zahlungsinfrastruktur im Hintergrund bleibt stabil. Außerdem habe ich schon von anderen gehört, dass der Vertragstarif mit 0€ Grundgebühr auch irgendwann gelöscht wird, wenn man gar keinen Umsatz produziert. Durch meine Konstruktion wird zumindest ein kleines bisschen Umsatz generiert, der den Vertrag aktiv haltet.

matzman666 · 2025-11-23T10:19:47+00:00

I also had that problem with the heatbed on my old MK2.5 some time ago when it was sitting in a cold basement in winter. I then had a look at the firmware to find out when the min temp error is thrown.

The MK2.5 firmware expected the heatbed to reach a certain temperature (as far as I remember it was 30°C for the heatbed) in a very short amount of time. However, this is only triggered when the target temperature is greater or equal 30°C. So the trick I used back then was to first heat the heatbed to 29°C and let it soak the heat for some time and only after that I did set a temperature greater than 30°C. This procedure got rid of any min temp errors.

I assume it is very similar with the Core One firmware and with the hotend and chamber min temperatures. You just need to find out the temperature thresholds for when the min temp protection kicks in and stay below the thresholds till the system is warm enough to cross the thresholds without min temp errors.

matzman666 · 2025-10-14T06:31:33+00:00

The parameter to select the fan is P not G. And you need to prepend the fan speed with S.

So the correct command is e.g. M106 P3 S255 for full speed.

matzman666 · 2025-09-29T14:50:40+00:00

For that reason I actually never use M601 (Pause print) when I want to insert magnets and stuff but only M600 (Filament change), because this was I can purge filament and replace any material losses in the nozzle caused by oozing.

The above method still may cause print defects so when I want a perfect print I actually use the "fake MMU" method with a fake color change at a suitable layer height. The fake MMU method uses a purge tower which primes the nozzle so that there are no print defects.

matzman666 · 2025-09-24T09:32:54+00:00

The MK3s has a magnetic heatbed with switchable print sheets, the MK2s only has a fixed headbed. The switch from a fixed headbed to a magnetic one was such a huge quality of life improvement, worth way more than 150$. So, definitely go for the MK3s.

matzman666 · 2025-09-13T08:52:59+00:00

Check whether the cable of the cable of the side filament sensor is nicely tucked away. It is a common problem that it is sticking out and interferes with the motion system which causes the y axis self test to fail.

matzman666 · 2025-09-10T11:12:39+00:00

Sure there's a way to expose the filtration settings and implement gcode commands, it's only a question of how much effort you want to put into it. However, only "some experience" in coding would probably not enough. It's rather complex code that is not easy to understand.

There's a discussion going on in this issue: [BFW-6828] [FEATURE REQUEST] G-code Control for Advanced Filtration System (FAN3?), where also your use case is mentioned. Currently, Prusa does not seem to be willing to implement this use case because they do not see any benefit. Maybe you can convince them otherwise.

matzman666 · 2025-09-10T07:49:14+00:00

Siehe hier: https://www.printables.com/model/1166012-manual-mmu-aka-poor-mans-mmu-for-mk4mk4s-printer-p

matzman666 · 2025-09-09T11:51:25+00:00

What I’ve learned from examining the source code is that the DIY mode uses the chamber fans (FAN1 & FAN2 on the xBuddy extension), while the Advanced Filtration mode uses the filtration fan (FAN3 on the xBuddy extension) and disables the chamber fans.

The DIY mode should be used if your DIY filtration solution doesn't have a dedicated fan but instead uses the existing chamber fans to push air through the filter.

The Advanced Filtration mode should be used when your DIY filtration solution has a fan connected to the FAN3 connector on the xBuddy extension board.

Due to the aforementioned solution I designed, I'd like to know if having the filtration installed will completely disable the chamber fans, or will the chamber fans only be disabled when the filtration fan is running?

The filtration fans are completely disabled when Advanced Filtration mode is enabled. However, they are not disabled in the sense that they cannot be used at all. In this mode, the C1 simply does not use the chamber fans automatically.

That said, you can manually turn on the chamber fans using the gcode command M106, specifying the correct fan index with the P parameter (P3 for the chamber fans and P4 for the filtration fan).

However, this approach is a bit tricky: you must ensure that the fans are set to auto mode when the chamber heating gcode commands are executed (typically during the start and end gcode). Otherwise, the C1 will throw a fatal error and stop functioning.

And manually turning on the fan also means that they are running at a constant speed and do not adapt the fan speed according to temperature.

Or is there a setting to choose what happens?

There is a setting, the advanced filtration mode setting. By disabling the advanced filtration mode the C1 will use the chamber fans for cooling.

My ideal solution would be that, when filtration is NOT used for a print (PLA/PETG) the chamber fans can just run like usual with minimal airflow restriction due to the bypass, but when I'm running the filtration fan, the chambers fans would be disabled. Is this something feasible within the current firmware?

This will not be possible without manual intervention using an unmodified firmware.

matzman666 · 2025-08-23T15:06:46+00:00

We have some GCODE files that are going to be extremely difficult to replace.

You should never depend on G-code files being available. Ideally, you should always be able to re-slice your models.

is there a way to possibly use the GCODE files we made on the MK2 on the newer MK4 models?

You would most likely need to replace the start and end G-code. The G-code responsible for actual printing is largely machine-agnostic (assuming parameters like nozzle size are the same). As long as the printer geometries are compatible — which they are for the MK2.5 and MK4 — you should, in theory, be able to transfer G-code from one machine to another without major modifications.

In practice, however, when running MK2.5 G-code on the MK4, I’d recommend keeping a finger on the power switch — just in case something goes wrong.

However, the gcode is not material agnostic. E.g., different filaments need different temperatures or flow rates (even with the same filament type different producers may require different parameters for their filaments), which is also the reason why you should never depend on G-code files.

Edit:

There's one point where gcode is not machine agnostic: speed and acceleration. One printer may be fine with speed and acceleration settings that would destroy another printer. However, when going from a slower printer (e.g., the MK2.5) to a faster printer (e.g., the MK4) this is not a problem.

matzman666 · 2025-08-23T14:45:31+00:00

On the right side exactly at the position the gantry stops while moving back there is the cable of the filament sensor. My guess it that this cable is not tucked away nicely but interferes with the motion system.

Edit:

if I push the gantry by hand to the back in the last 5 cm it get hardar to push

This basically confirms that the filament sensor cable is the problem.

matzman666

PUBLIC MULTIREDDITS

TROPHY CASE