Topics created by Anawandur

@Anawandur

I have now searched through all the files (start.g, start script, filament script, intro line script) and I did not find the word "started" anywhere.

Lost in translation? I hope you didn’t search for "started" but instead looked for the German word "gestartet" … 😁

This aside, can you provide us with a screenshot of the error message?

Then, try to narrow down on the spot where the error occurs. To begin with, insert this line at the end of your start.g macro:

And start your print (sufficient to simulate it with M37). If the error pops up before you see the message, it must be in start.g or any other macro which has been called before that. So, remove the M291 gCode and paste it into another macro of the call chain.

If, however, the error occurs after the message, look at the start section from your slicer.

Admittedly, this is a tedious task, but it's a good way to locate the origin of the error message you get. When you've spotted that macro, post it here.

@Proschi78 as @droftarts says, we don't recommend load cell amplifiers based on the HX711 chip for use as Z probes because of the slow response time. Also these devices are normally used with the offset voltage zeroes immediately before use, to compensate for any temperature-induced drift.

As a Z probe needs fast response time but only needs to detect a sharp change in load, it's better to use a low noise op amp to read the output from the sensor instead of a load cell. You could take a look at the schematic of our Smart Effector to see how we do it. The Smart Effector uses an on-board microcontroller for signal conditioning and to perform self-test functions, but for a basic Z probe you could probably use just the voltage regulator and op amp.