Hi, im really sorry in advance for the quality of my information beacause I’m not very experienced. But I would be quite available to provide you with more precise information.
I was making a “big” print (8hrs), when suddently, Klipper crashed (but not the printer) with no possibilities to recover my progression. I tried twice and each time, Klipper crashed at the same moment in the print.
I am attaching the logs concerning the 2 prints (sorry, I was not able to recover the log file)
the pause on the second screenshot can’t be the cause because I didn’t pause on the other one, and the messages regarding the caselights were just me having fun. On the other hand, there is this same message 1 second before the crash:
“SET_VELOCITY_LIMIT velocity=400.000000 accel=4000.000000 accel_to_decel=3500.000000”
and the crash occured with an error message who regarding the SET_VELOCITY_LIMIT
I have never had this type of error except since I recently (2 days) used the web interface to control my printer from the local network
Would it be possible to know where it comes from?
Thank you in advance to those who will respond to me and again sorry for the poor quality of my post
Go to the machine section in your interface and download your klippy log and post that.
Also if you know how to ssh into your Pi, use the dmesg command to view the kernel messages from the pi and look for any messages that could indicate what’s happened. Only the last few messages after the crash should be important. You may as well have look through the syslog in /var/log/syslog.
I didnt managed to ssh into my Pi tidk how to do it and what to search to find (sry ^^) and I also didn’t find any syslog or var/log/syslog folder.
Thanks in advance for your reply and sorry for the quality of my answer.
The Elegoo Neptune 4 Pro is using a modified Klipper version that is not compatible to the original Klipper.
Also, such versions may badly break if you update, outside of what is offered from the manufacturer.
No meaningful help can be provided from our side. Your best options are:
Revert to the original setup of the manufacturer, i.e. do a “factory reset”
Update to latest firmware provided by the manufacture
Directly contact Elegoo for further assistance if the error persists
Thanks, for the advices ! I will try the first option, but dont u think that the problem can came from the fact that im using the fluidd online interface ?
