I have random Internal error on command:"G1"

General Discussion
1

Basic Information:

Printer Model: voron 2.4
MCU / Printerboard: BTT octopus 1.1 / ebb36 1.2
klippy.log
klippy42.log (1.7 MB)

Describe your issue:

…
i have random Internal error on command:“G1” problem
i suspect gcode but it happens randomly
and i can not fine actual problems in log file

what is couse of this problem?

2

Your log seems modified and you are also using a modified Klipper version. Try reproducing the error without any modification and provide a log.

3

ok here is new log file
klippynocut.log (2.1 MB)

i do flash install klipper and reset kliipy.log and test run until internal error g1 apear

4

This still does not look like a full log from a pristine Klipper version.

5

um… previous time i removed klipper folder and git clone agian
this time reinstall klipper by kiauh…
and reset log and reboot and try to print
klippy (46).log (1.6 MB)

is this log ok??

6

Always the complete log as you get it from Klipper, no changes or cut-offs.

If it is too large, make a ZIP-file from it.

7

This is quite strange. Every klippy.log typically contains

Starting Klippy...
Args: ['/home/klipper-2/klipper/klippy/klippy.py', '/home/klipper-2/printer_data/config/printer.cfg', '-I', '/home/klipper-2/printer_data/comms/klippy.serial', '-l', '/home/klipper-2/printer_data/logs/klippy.log', '-a', '/home/klipper-2/printer_data/comms/klippy.sock']
Git version: 'v0.12.0-111-g4f00f219'
Branch: master
Remote: origin
Tracked URL: https://github.com/Klipper3d/klipper
CPU: 8 core Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Python: '3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]'

these information. Even if the log gets rolled over. In all your logs it is missing, which is a bit suspicious.

8

ok reboot host now i get that line in my log file
klippy (47).log (4.7 MB)

9

Interesting.
If you are able to provoke the error then please:

  • Issue a M112 immediately after the error and provide the log file
  • If it comes from a gcode file provide this as well
10

klippy (50).log (1.6 MB)
FFFx.gcode (2.4 MB)

here is log file execute M112 after error
and gcode i tryed

11

Thanks, but if you check the log, you will see that this is a different error. The last case was

mcu 'et0': Timeout on connect
Created a socket
mcu 'et0': Wait for identify_response
12

oh thanks…
i miss it due ignore related paragraph…

have a good day thanks again

13

i check it now… sadly it does not couse of G1 error…

that log after m112 and M112 send et0 reset command
and mcu reset take time more then klipper expect then
“mcu ‘et0’: Timeout on connect” printed.

i serching old log and i found same line a lot even loged when no g1 problem occurred…

now no clue again…

14

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.