Error: Bad command: gestartet

Anawandur

Hallo,

ich habe mein Duet3 Mini5 mit 3.5.0-beta.2 in betrieb genommen, es funktioniert soweit gut, viele Fehler habe ich beseitigen können, aber ein Fehler bekomme ich nicht weg.

Sobald ich den Druck starte kommt sofort der Fehler (Error: Bad command: gestartet). Habt ihr dazu eine Vermutung was diesen Fehler auslöst, und wie ich diesen finde?

jay_s_uk

@Anawandur check your start gcode. That's probably the culprit

infiniteloop

@Anawandur

Sobald ich den Druck starte kommt sofort der Fehler (Error: Bad command: gestartet).

As the error message says: Your Duet has no idea what to do with the command "gestartet". While you are free to comment your code in any language on earth, even German, all executable code must conform to strict rules.

I can imagine two situations: Either a comment is not marked as such (e.g. not lead-in by a semicolon), or you intend to send a "gestartet" message when the print begins. You would do that with something like

M291 P"Meine Meldung" S0

The potential trap for non-english humans: most 'smart' editors replace the double quotes with dedicated lead-in and closing glyphs like this: „unten/oben“. The RepRapFirmware of the Duet, however, recognises just straight double quotes ("), not those on the base line („) or the fancy curled ones (“). See the difference: " “

Anawandur

Hello, 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.

infiniteloop

@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:

M291 P"Kuckuck" S0

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.