Sonic pad klippy shut down

Basic Information:

elegoo Neptune 3 plus
sonic pad/ STM 32bit
klippy_20240306093633.log (139.2 KB)

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Soooo I’ve been printing a lot this last month with no issues at all… That is until last night.

I started a pint last night and about 2hrs in I noticed my nozzle was at a dead stand still so I looked at the interface; everything was still hot just not moving. So I canceled the print cleaned off the bed, and homed all axis. I went to hit re print on the interface and it just shut klippy down right out of the gate immediately when I hit print. So I reset everything tried again same way from the interface. I re sliced and tried to send it through orca slicer and got an error 56. So I tried on my other printer same thing. I have no idea what or how to fix this issue I have tried everything to my knowledge and I really don’t want to factory data reset the pad but… Is there any other way

Hello @HoudiniC !

Please read this note on the Sonic Pad:

Traceback (most recent call last):
  File "/usr/share/klipper/klippy/klippy.py", line 243, in run
    self.reactor.run()
  File "/usr/share/klipper/klippy/reactor.py", line 292, in run
    g_next.switch()
  File "/usr/share/klipper/klippy/reactor.py", line 340, in _dispatch_loop
    timeout = self._check_timers(eventtime, busy)
  File "/usr/share/klipper/klippy/reactor.py", line 158, in _check_timers
    t.waketime = waketime = t.callback(eventtime)
  File "/usr/share/klipper/klippy/extras/virtual_sdcard.py", line 813, in work_handler
    gcode_move.recordPrintFileName(print_file_name_save_path, self.current_file.name)
  File "/usr/share/klipper/klippy/extras/gcode_move.py", line 239, in recordPrintFileName
    result = (json.loads(f.read()))
  File "/usr/lib/python3.7/json/__init__.py", line 348, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.7/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.7/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Your error message is coming from a modified Klipper and from files that are not present in regular Klipper.
I recommend reverting to the respective manufacturers for a solution.

Why am I just running into this error now? I’ve been running my Neptune 3 plus and my ender 3 V2 non stop within the last 5 months and then this just happened last night. Ive tried to connect and reconnect Internet no progress… I tried to install the latest update it just fails. So is a factory data reset the only other option… I literally haven’t made any other changes to cfg or anything.

I can’t download the new firmware update it just fails.

Creality is using a modified version of Klipper, and they haven’t released source code which violates the license for Klipper. We’re not going to provide free support for a company that acts in bad faith, and even if we wanted to help, we can’t because we have no idea what modifications they made to the code. You need to contact Creality for support, but from what I’ve heard about them you’re likely on your own.

Thank you yeah I was starting to figure that out from all of the research I’ve been doing today all signs point to a factory data reset… almost just makes me want to switch back to my orange pi lts 3

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