In klippy.log around line 250508 is where it looks like it disconnects, “Got EOF when reading from device”?
I will attach a picture of where it halted. Here is my versions for everything: https://i.imgur.com/kSvvZ6b.png
Open to any ideas on how to fix this, thanks!
Line #152 in moonraker.log, looks to be about where it crashed.
2022-06-22 01:25:25,073 [klippy_connection.py:_get_peer_credentials()] - Failed to get Klippy Credentials
Traceback (most recent call last):
File “/home/chris/moonraker/moonraker/klippy_connection.py”, line 238, in _get_peer_credentials
pid, uid, gid = struct.unpack(“@LLL”, data)
struct.error: unpack requires a buffer of 24 bytes
2022-06-22 01:25:25,490 [klippy_connection.py:_init_klippy_connection()] - Webhooks Subscribed
2022-06-22 01:25:25,510 [klippy_connection.py:_init_klippy_connection()] - GCode Output Subscribed
2022-06-22 01:25:26,273 [klippy_connection.py:_check_ready()] -
Can not update MCU ‘mcu’ config as it is shutdown
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer
Yeah this was it I believe. I reprinted the same slice and reduced characters in the file name and it printed. What’s the guidance here? I checked the documentation and could not find anything regarding character limit.
Going by your log, I do not believe the filename is the problem. Typically such topics will throw you out of the game at the start of a print and not in the middle.
The Moonraker log is strange. Maybe @Arksine could have a look.
With regard to Moonraker’s log, there are two things I notice:
Moonraker can’t extract peer credentials from the Unix Socket. This is probably an issue with Armbian. That said, this isn’t a big problem yet, as the information is just for logging purposes and not used functionally.
There looks to be a lot of websocket ping timeouts. That is likely a local networking issue, however it could be a wifi driver issue as well if the device is connected wirelessly.
With regard to the Klippy log, the got EOF when reading device is probably a commanded restart. The system had been shut down for quite some time before that was logged. On line 6907 Klippy suddenly starts, this occurs without any kind of restart logging. It looks to me that the system killed the Klippy process and then restarted it.
It is very strange… I literally renamed the same gcode file with a shorter name and printed it without fail the next day.
The device is wired, however the ping timeouts might be from 1 or 2 PC which had mainsail open, and went to sleep or just sat there with screen off. Could the websocket timeouts cause the print to drop? If I need to make sure all sessions are closed before I got to bed I can do that, though I typically have 2-3-4 sessions open all day depending.
Hi , i am new here, I have a Alunar FDM M508 3d printer with a Hy Base L V1.0 controller board. it worked fine for 4 years now lately it crash half way in some prints. what could cause this?
