Skip to content
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

The printer wont start if the name of the file contains "é" characters #32

Closed
antoineseveau opened this issue Mar 6, 2024 · 5 comments

Comments

@antoineseveau
Copy link

If the name of the body contains a "é" in QIDISLICER, accent character are very commun in french language, the printer wont start, the sending to the printer with wifi seems to works, but then nothing happens, no start print
Capture d’écran 2024-03-06 à 18 41 47
thanks

@CChen616
Copy link
Contributor

CChen616 commented Mar 7, 2024

If possible, please attach a copy of the G-code for us to use for testing.

@antoineseveau
Copy link
Author

Of course,
the g-code name changes itself when i saved it. the "é" change in "e".
Here the g-code for this part :
Capture d’écran 2024-03-07 à 08 52 54

(Non enregistre).gcode.zip

@CChen616
Copy link
Contributor

We have tested the generation of G-code files with French characters in their names on both Windows and iOS platforms and sent them to the printer for printing. Currently, there are no issues observed. Although spaces in the file names are converted to underscores and 'é' is converted to 'e', it seems to not affect the printing process.

If the problem reoccurs, please attach the relevant information displayed in the Fluidd console along with klippy.log and moonraker.log for our analysis.

@antoineseveau
Copy link
Author

antoineseveau commented Mar 14, 2024

MOONRAKER LOG
2022-12-16 22:44:53,854 [shell_command.py:_check_proc_success()] - Command (/home/mks/moonraker-env/bin/python /home/mks/moonraker/moonraker/components/file_manager/metadata.py -p /home/mks/gcode_files -f ".cache/test e.gcode") successfully finished
2022-12-16 22:45:15,618 [websockets.py:on_close()] - Websocket Closed: ID: 281473392980320 Close Code: 1001, Close Reason: None, Pong Time Elapsed: 9.25
2022-12-16 22:45:16,377 [app.py:log_request()] - 101 GET /websocket?token=CGOKPHSTUUHHIAMLNK3OJQ2RCPMF57SC (192.168.1.18) [TRUSTED_USER] 3.82ms
2022-12-16 22:45:16,378 [websockets.py:open()] - Websocket Opened: ID: 281473392443008, Proxied: True, User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36, Host Name: 192.168.1.24
2022-12-16 22:45:16,389 [websockets.py:_handle_identify()] - Websocket 281473392443008 Client Identified - Name: fluidd, Version: 1.19.0-6184c73, Type: web

KLIPPY LOG :
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'\xe9' in position 51: ordinal not in range(128)
Exiting SD card print (position 361)

moonraker.log
klippy.log.zip

@CChen616
Copy link
Contributor

We are still unable to reproduce this issue on our machines. Similar to what was reported in this issue, it seems to be a pre-existing problem with the official Klipper firmware.

Klipper3d/klipper#4794

The current recommendation is to avoid including unusual characters in G-code file names and file contents (for example, content that might be auto-generated by slicing software), and to use UTF-8 encoding.

@CChen616 CChen616 closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants