xblax / flashforge_ad5m_klipper_mod

Unoffical mod for Flashforge Adventurer 5M (Pro) 3D printers to run Moonraker, custom Klipper, Mainsail & Fluidd
GNU General Public License v3.0
82 stars 4 forks source link

Message: Print is not paused, resume aborted #164

Open Tiwatz opened 3 weeks ago

Tiwatz commented 3 weeks ago

My print paused at 97% today and it was impossible to start again. As soon as I hit the "Resume print" button in Mainsail the Console message was "Print is not paused, resume aborted". I could not find that message in any of the config files. Skärmbild 2024-04-26 235855

klipper.log moonraker.log can-holder-70mm_PLA_2h11m.gcode.txt

xblax commented 2 weeks ago

I think I've seen this issue mentioned somewhere else before, that the printer went into Pause for unknown reason.

For the first time I did now also encounter this issue with an overnight print.

And I think it's caused by this (from my klipper log)

virtual_sdcard read
Traceback (most recent call last):
  File "/root/printer_software/klipper/klippy/extras/virtual_sdcard.py", line 237, in work_handler
    data = self.current_file.read(8192)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x9c in position 4315: invalid start byte
Exiting SD card print (position 5865465)

Your log shows a similar error. Thanks for attaching it:

virtual_sdcard read
Traceback (most recent call last):
  File "/root/printer_software/klipper/klippy/extras/virtual_sdcard.py", line 237, in work_handler
    data = self.current_file.read(8192)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x9f in position 136: invalid start byte
Exiting SD card print (position 10854385)

We have to check if it's a known issue on Klipper side or think what else could cause this.

xblax commented 2 weeks ago

I attempted to print the same file again and it fails at exactly the same position.

virtual_sdcard read
Traceback (most recent call last):
  File "/root/printer_software/klipper/klippy/extras/virtual_sdcard.py", line 237, in work_handler
    data = self.current_file.read(8192)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x9c in position 4315: invalid start byte
Exiting SD card print (position 5865465)

I had it uploaded directly from Prusa slicer. I have to investigate if it's actually corrupted.

consp commented 1 week ago

0x9c is œ. but I doubt it's ascii/latin1 encoded.

Rand it though xxd and then looked at the results containing 9c:

Line 678351: 00a59ce0: 4c49 4d49 5420 4143 4345 4c3d 3230 3030  LIMIT ACCEL=2000
Line 678352: 00a59cf0: 0a47 3120 4639 3130 392e 3832 370a 4731  .G1 F9109.827.G1
Line 678414: 00a5a0d0: 2129 7845 583d 2f55 e89c 25a5 4865 5026  !)xEX=/U..%.HeP&
Line 678424: 00a5a170: e89c 25a5 4865 7026 0000 19a4 0020 1901  ..%.Hep&..... ..
Line 678433: 00a5a200: 2129 7845 583d 2f55 e89c 25a5 4865 8026  !)xEX=/U..%.He.&
Line 678438: 00a5a250: 4c1d 19cc c482 e0be 6000 c480 0190 0021  L.......`......!
Line 678443: 00a5a2a0: e89c 25a5 4865 b026 0000 1da4 0020 1901  ..%.He.&..... ..
Line 678452: 00a5a330: 2129 7845 583d 2f55 e89c 25a5 4865 c026  !)xEX=/U..%.He.&
Line 678557: 00a5a9c0: 332e 3239 3920 4a37 2e36 3038 2045 2e30  3.299 J7.608 E.0
Line 678813: 00a5b9c0: 312e 3732 3120 5934 2e37 3720 452e 3230  1.721 Y4.77 E.20
Line 678957: 00a5c2c0: 3782 df81 9c40 6a16 6000 c480 0190 0021  7....@j.`......!
Line 678958: 00a5c2d0: 6e02 89c0 1310 0000 0004 fe3f 887f 0e00  n..........?....
Line 678962: 00a5c310: e89c 25a5 4865 e026 0000 20a4 0020 1901  ..%.He.&.. .. ..
Line 678967: 00a5c360: 6000 c480 0190 0021 6f02 89c0 1310 0000  `......!o.......
Line 678971: 00a5c3a0: 2129 7845 583d 2f55 e89c 25a5 4865 f026  !)xEX=/U..%.He.&
Line 678977: 00a5c400: 7002 89c0 1310 0000 0004 fe3f 887f 0e00  p..........?....
Line 678981: 00a5c440: e89c 25a5 4865 0027 0000 22a4 0020 1901  ..%.He.'..".. ..
Line 679069: 00a5c9c0: 3832 2059 3635 2e37 3039 2045 2e31 3937  82 Y65.709 E.197

It's borked.

Line 457015 and on:

G1 X15.966       ŸNஉ[Ѡ Ā !e‰    ‚þ?ˆ  Y68.996 Z68.667 E.02421
G1 X-49ˆB0 HLء)xEX=/U蜥¥HeP&  ¤    ªª    E  (£Á@ €|Ԁ¨¬倨¬ém9Àk~VvPn        ǟ¨H!. Ā !g‰    ‚þ?ˆ Z68.757 E.0565
G1 X-55.391 Y67.2ˆB0 HLء)xEX=/U蜥¥Hep&  ¤    ªª    E  (£À €|Ҁ¨¬倨¬ém9Àk~mFPꝠ       ƒMOI¤›T` Ā !h‰    ‚þ?ˆ 08879
G1 X-61.155 Y64.413 Z68.86ˆB0 HLء)xEX=/U蜥¥He€&  ¤    ªª    E  (£Ā €|р¨¬倨¬ém9Àk~x®Pߵ        L̄‚ྠ Ā !k‰    ‚þ?ˆ E.20135
G1 X-70.52 Y55.759 E.201ˆB0 HLء)xEX=/U蜥¥He°&  ¤    ªª    E  (£ǀ €|΀¨¬倨¬ém9Àk~š搐¼ý        ¬ˆ!5TW¶Ǡ Ā !l‰    ‚þ?ˆ 6.456 Y41.029 E.20135
G1 X-76.74ˆB0 HLء)xEX=/U蜥¥HeÀ&  ¤    ªª    E  (£Ȁ €|̀¨¬倨¬ém9Àk~¦NP±•        ख I"y.434 Y2.772 E.01075
;WIDTH:0.174968
G1 X4.94 Y3.299 E.00898
G1 E-.8 F2100
;WIPE_START
G1 F12000
G1 X5.434 Y2.772
xblax commented 1 week ago

Yes my GCode file is corrupted as well. I don't have the original to compare since I directly uploaded from Prusa Slicer. The one attached here is from Orca Slicer, so at least it does not seem to be a specific issue.

@Tiwatz did you also directly upload the file from the slicer?

Tiwatz commented 1 week ago

@Tiwatz did you also directly upload the file from the slicer?

Yes I did. No more issues since this one time though.

consp commented 1 week ago

Looks to me like a string offset error (oob) and the extra data is random memory data. Surprised it didn't crash orca if that is the case.

thhdragon commented 2 days ago

could this be related to what appears as a max queue overflow error on stock fw and pauses the print? in the 3dp discord we were able to the issue to the gcode having too many/too fine arcs from the arc fitting setting thats enabled default in orcaslicer. i see that print has a lot of circles and the gcode is full of g3 moves. try reslicing with arc fitting disabled. klipper doesnt use arcs like marlin does. i think the 0.12 default resolution in orcaslicer is fine for our boards. if not related i still wanted to make you aware of the gcode arcs causing max queue overflow on stock in case that helped troubleshoot any failed prints on this build that might not have to do with the firmware