search

Klipper3d / klipper

Klipper is a 3d-printer firmware
GNU General Public License v3.0
9.39k stars 5.29k forks source link

No next step, I did not found any connection with other simalar issues #3286

Closed mistrjirka closed 4 years ago

mistrjirka commented 4 years ago

Hello, I am running klipper on debian Core 2 duo with mechanical HDD. When I am printing very slowly I am getting error mentioned bellow. I read these issues https://github.com/KevinOConnor/klipper/issues/2112 this did not help I was printing slowly changing klipper priority did not help and I do not have slow computer for klipper, https://github.com/KevinOConnor/klipper/issues/1390 there is solution some bug fix, but I have newly installed klipper. https://github.com/KevinOConnor/klipper/issues/1012 I have no idea what even is Force_move and it is nowhere to be found in my gcode. How I said I am printing very slowly 5mm/s. I attached log, previously I found in the file the error and copied it here. The whole log has 51MB. printer.txt

2klippy.log.zip

Read 195509.617502: 'N63527 G1 X111.605 Y110.039 E0.00746106\n' Read 195509.619468: 'N63528 G1 E-0.10000 F4800.00049\n' Read 195509.621273: 'N63529 M400*44\n' gcode state: absolute_coord=True absolute_extrude=False base_position=[0.0, 0.0$ MCU 'mcu' shutdown: No next step This is generally indicative of an intermittent communication failure between micro-controller and host. Once the underlying issue is corrected, use the "FIRMWARE_RESTART" command to reset the firmware, reload the config, and restart the host software. Printer is shutdown

KevinOConnor commented 4 years ago

Can you provide the gcode file that was printing at the time of the error?

-Kevin

mistrjirka commented 4 years ago

https://pastebin.pl/view/984d4359 Sorry for delay. I was not sure which one it was. Btw it does not matter if it is Prusaslicer or Cura both create same error. This one failed in like 70% printing

mistrjirka commented 4 years ago

New update. Printed again on slow settings and about 20% into the print it stopped with same error. Here are logs from octoprint klippy and config bugrepport.zip

mistrjirka commented 4 years ago

Snímek obrazovky pořízený 2020-09-22 20-51-18 Snímek obrazovky pořízený 2020-09-22 20-51-08 Snímek obrazovky pořízený 2020-09-22 20-50-44 Snímek obrazovky pořízený 2020-09-22 20-49-05 Snímek obrazovky pořízený 2020-09-22 20-48-56

KevinOConnor commented 4 years ago

Are you running a 32bit Linux OS? There was a problem with old "387" 80bit floating point math that was fixed just a couple of days ago - issue #3313 . I recommend you upgrade to the very latest code (see the FAQ for upgrade instructions).

-Kevin

mistrjirka commented 4 years ago

I did. Thank you. I upgraded OS and also downloaded new klipper. If anything comes up. I will reopen the issue.