dark flare
Hello everyone.
I have a bug with the exclude object function, at least that's where I think it comes from.
As soon as I activate object naming in the slicer (regardless of whether it is Prusaslicer or Superslicer), my print no longer starts and it can no longer be canceled.
Only a restart helps then.
Does anyone have an idea of what that could be?
Thanks a lot.
solar bane
Klippy.log
dark flare
solar bane
Klipper.logs shows no problem
There it is Starting SD card print (position 0) virtual_sdcard dispatch Traceback (most recent call last): File "/home/mks/klipper/klippy/extras/virtual_sdcard.py", line 264, in work_handler self.gcode.run_script(line) File "/home/mks/klipper/klippy/gcode.py", line 216, in run_script self._process_commands(script.split('\n'), need_ack=False) File "/home/mks/klipper/klippy/gcode.py", line 200, in _process_commands self._respond_error(str(e)) UnicodeEncodeError: 'ascii' codec can't encode character u'\xf6' in position 47: ordinal not in range(128) Exiting SD card print (position 9755)
Always the same error, at least 5 times the last week. STOP USING SPECIAL CHARAKTERS
send your gcode file and I show you the issue
dark flare
now i'm curious.
dark flare
i think i found what you mean. in German it is Körper and this ist the Problem.
solar bane
Yes Körper is one of the classic cases …
Klipper in a Python2 virtual-env can not handle Special Charakter
dark flare
Fusion 360 generates a separate body for each part of a 3D model. even if the overall file contains your umlauts then the subcomponents are still as bodies in the slicer.
solar bane
You could use Kiauh to setup Klipper in a Python3 virtual-env and then this problem would be gone
dark flare
🙂 amazing fast your answer, thanks a lot, now i know what is the problem