-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal error on command:"SDCARD_PRINT_FILE" #4794
Comments
Ok. I found a workaround. The problem is the "µ" in the filename. If you replace or remove the character it works fine. |
Happens to me as well with non ascii filenames (german "Umlaut" for example) Körper1.gcode does not work |
Glad I found this... Renaming file worked |
Jepp, same for me. Typical german Fusion 360 export of Bodies is Körper :D |
The error checking is not complete in this change - the code should handle the case where an input string is not valid utf8. The code will continue to run on Python2 after this change, however the execution time on Python2 is measurably slower after making this change. Signed-off-by: Kevin O'Connor <[email protected]>
Hello, It looks like there hasn't been any recent updates on this Best regards, ~ Your friendly GitIssueBot PS: I'm just an automated script, not a human being. |
Still existing... |
There are two options to work with non-ASCII characters:
|
Is Klipper fully supported on Python 3 yet? According to the author of KIAUH it does not really sound like it: |
Can confirm this error still persists. |
As long as the issue is not tagged as "resolved" it will continue to exist 😉 |
This issue got marked as a duplicate of #4959, but I think that's incorrect. I have #4959 exactly. The same stack trace, etc. Which is not the stack trace of this issue. Klipper seemingly won't print any files from the LCD with a space in it. For example |
Today, for me this happend also again with an german "ü". Everything up to date. |
Same thing. All software is up to date. |
got the issue today with a French word containing accentued characters (é) |
I'll said it: this issue is waiting for python2 support to be removed. If you want to keep a legacy python2 installation you need to stay on a stable release that support it. (v0.10) While trying to have a look I realized that I can no longer easily install python2 on my dev machine and pi. This is probably the reason that no one will tackle this, even if the fix might be easy to implement. I've been running klipper on python3 since April 2021 with minimal modifications. Since then, support has been added to klipper master in the wake of the v0.10 release. As of October 4, 2021, klipper runs without modification on python3. I believe it will be made official with the v0.11 release. |
I got an error when using uppercase letters, got this on the log:
the original name of the file is |
Same occurrence - sliced an STL from a file which had Chinese characters in the name, and this happens:
in fact, this is not the only place where things break - even after changing the gcode file name on the rPi host, it still refused to print, bailing out like this:
which from Fluidd looks like file is accepted and starts printing, but nothing is actually happening on the printer side this is with klipper v0.11.0-66-g4671cf2d
the system has fully functional python3, but the default one (and the one in klippy-env) is still python 2.7.16 |
It seems that generated gcode contains Chinese characters in comments and it produces this error. |
I think if the file name that contains the characters that not in |
How do I change from Klipper Python 2 to Klipper Python 3? |
@Murat65536 The manual way is to recreate Klipper's python virtual environment. Something in the lines of: cd
mv klippy-env klippy-env-py2
python3 -m venv klippy-env
./klippy-env/bin/pip install -r ./klipper/scripts/klippy-requirements.txt
sudo systemctl restart klipper This relies on |
@Piezoid |
Cant print file with russian Exclude object names. |
Same here with german and named objects from Prusaslicer 2.7.1
error from klippy
|
I think it's solved after reinstalling Klipper using KIAUH and select Python 3. |
It doesn't matter which file is selected to print. Even files that worked flawlessly before the update won't work either.
The text was updated successfully, but these errors were encountered: