Regular random "Internal error in stepcompress" last 2 months

General Discussion
1

Basic Information:

Printer Model: FBG6 (deeply modified)
MCU / Printerboard: MKS Nano6 3.2
Host / SBC OPi 3LTS
klippy.log

klippy (1).zip (1.1 MB)

Describe your issue:

…

I haven’t updated the klipper since February 2024, and the devil pulled me to update it in September…

With a probability of 5-10%, any print containing G2/G3 commands can be interrupted with the error “stepper.error: Internal error in stepcompress” no matter at what height (but more often up to the height of the mesh alignment).
The same g-code can be printed again without error.

I update as soon as a new update comes out, I really hoped that this was a temporary phenomenon that was known and it would soon be working properly, but 2 months have passed, the problem still remains, it has become impossible to print for 6+ hours.

Also, the printer on the new version is not able (timer too close
in the same place in the code) to print the same g-code with microsteps (128/128/128-64/64/64 have to be reduced to 64/64/64-32/32-32) at a speed of 230 and acceleration of 10,000. The same model prints beautifully on another printer (on an old version of klipper) on the same OPi3LTS and the same MCU (MKS3.2) with microsteps (128 for 7 engines), with speed 240 and accel 15000-20000.
but this is a secondary problem - I’ve already accepted it

2

2klippy.log.zip (62.6 KB)
3klippy.log.zip (3.1 MB)
klippy (2).log.zip (4.6 MB)
klippy.log.zip (3.9 MB)
More 4 logs

3

Hello @Murdo !

Have you tried without arcs?

They are not necessary for Klipper anyway.

4

Yes, without arches there is no problem. But without arches it is impossible to get the same quality, even approximately… I can’t slice the models so that the quality would be comparable to a print with arches.

I repeat, the printer is already 1.5 years old, of which I have been using the arches for more than a year, i.e. the problem is new.

5

Have you raised the resolution in the slicer?

6 
Untracked files: klippy/extras/autotune_tmc.py, klippy/extras/fan_extra.py, klippy/extras/gcode_shell_command.py, klippy/extras/heater_fan_extra.py, klippy/extras/heaters_extra.py, klippy/extras/led_effect.py, klippy/extras/motor_constants.py, klippy/extras/pid_calibrate_extra.py, klippy/extras/rotation_distance.py, klippy/extras/cartographer.py, (+2 files)
Modified files: klippy/extras/ads1220.py, klippy/extras/bme280.py, klippy/extras/bus.py, klippy/extras/fan.py, klippy/extras/gcode_arcs.py, klippy/extras/hx71x.py, klippy/extras/led.py, klippy/extras/output_pin.py, klippy/extras/probe_eddy_current.py, klippy/extras/servo.py, (+3 files)
Branch: master

Revert to original Klipper. Reproduce the issue, issue a M112 right after and post a new log. Modified Klipper version are not supported here.

7

Yes, I use SuperSlicer and import files into .step, but with no settings I can’t achieve better quality than in this photo. The photo doesn’t do the whole thing justice, but it’s literally HORRIBLE compared to the print with arches

image
image590×1280 55.6 KB

8

some logs are already old, I have been struggling with this problem for 2 months, including at some point I tried to manually replace some of the files with old ones for testing - it did not help. The current log is in the first post, the rest are examples

I tried about 50+ solutions before writing here, at some points there were changes in the klipper, but this did not affect this error, now there is a clean, fresh version - the problem remains

9

Also, during all this time, I removed everything “unnecessary” from the printer (neopixel, built-in dryer controlled by macros, SHT31, etc. little things), but there may be “tails” of these things in the old logs. Again, nothing I tried helped. There were many other bugs after the update (homing problems, problems with neopixel and SHT31 - everything was solved except the current problem with stepcompress)
I literally spent about 200+ hours adjusting to the new realities (bugs) after the update.

10

So what next? Do you recognize this as a bug or ignore it because of the dirty version in the additional logs?
I repeat the LOG IN THE FIRST POST WITH THE ORIGINAL KLPPER, the rest of the logs are for example, they are older and there may be many other errors because there were several problems after the update.

Git version: 'v0.12.0-322-g0855994e-dirty'
Untracked files: klippy/extras/heaters_extra.py, klippy/extras/led_effect.py, klippy/extras/pid_calibrate_extra.py, klippy/extras/cartographer.py, klippy/extras/idm.py, klippy/extras/scanner.py
Branch: master
Remote: origin
11

Please tell me - are you not satisfied with the degree of originality of the klipper in the log of the first post? In this?
klippy (1).zip (1.1 MB)

If you don’t like it, ok, I can reproduce it, but tell me how “clean” the klipper should be? In general, remove all modules, incl. cartographer, led effect, PID_V,?

12

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