You are not logged in.
Pages: 1
Hi All,
First of all, I love NanoDLP. The web interface is awesome and I appreciate the hard work that has gone into developing this software.
Recently, I've ran into issues with NanoDLP crashing after around 300 layers. I am developing a LCD Daylight resin printer and just got to the point where it is reliably printing, so I am printing larger objects. I don't know if this problem existed before and I just hadn't printed anything large enough to see it.
When it crashes, the web server becomes unreachable and I have to restart the Raspberry Pi. This has happened with two different stl files. For one of the stl files, NanoDLP crashes at different layer heights so I am thinking that it isn't an issue with the stl file.
I had this issue on build number 1392 and recently upgraded to build 1437 and am getting the same issues.
I've looked through the debug file and from what I can see it looks like the raspberry pi lost connection to my wifi and was trying to reconnect. Would this cause NanoDLP to crash?
I also found the message "Warning","msg":"Limit touched position reset". I'm not sure what to make of this other than maybe there's something funky with my Z axis limit switch? I haven't had any issues with the limit switch before and it functions as it should.
I read another post suggesting that it could be power supply issues. My Raspbery Pi is on its own power supply. My Arduino and ramps board have their own power supply and my LCD screen has its own power supply. This leads me to believe that power isn't an issue.
The debug file is attached below.
I will probably try a fresh install to see if it fixes the problem if I don't hear anything back in the next week.
Thank you for taking the time to read my post and I appreciate any insight into my problem. Please let me know if you need any more information about my setup and the issues I'm having.
Offline
Debug file does not contain necessary information for troubleshooting.
Please, dry run until crash and after restart get another debug file. I do not think fresh install will help.
Offline
Thanks for your reply. I will do this tomorrow. I have two other debug files on hand at the moment.
This is the first debug file I captured after I noticed this happen once or twice. I was on build 1392 for this.
Here is another 1437 build debug.
Thank you for taking the time to look into the problem I'm having.
Offline
ssh into rpi and type command below, paste result here.
cat /home/pi/printer/config/run.sh
Offline
#!/bin/bash
touch /var/log/printer.log
chmod 644 /var/log/printer.log
/usr/local/bin/pigpiod -s 10
sleep 5
clear
setterm -cursor off
(cd /home/pi/printer;./printer >> /var/log/printer.log 2>&1)
Here was the result. I'm not sure what to look for or if this is even the correct output.
Offline
Yes it is the correct output, thanks. Will wait for another crash report.
Offline
Great! Thank you for your help. I will try to capture one tomorrow night.
Offline
#!/bin/bash
touch /var/log/printer.log
chmod 644 /var/log/printer.log
/usr/local/bin/pigpiod -s 10
sleep 5
clear
setterm -cursor off
(cd /home/pi/printer;./printer >> /var/log/printer.log 2>&1)
Offline
Here is the debug file from the dry run I ran tonight. Thank you in advance for looking through it.
Offline
1125lbs,
Do you experience the same issue?
Offline
yes,
my nano was suffering from near-death experiences,
so rebuild everything and then update to 1448. now its working ok thanks
Offline
Shahin,
Were you able to determine anything from the debug file?
Should I try reinstalling?
Thanks
Offline
Unfortunately I could not find the cause of the issue. But I see you have enabled both direct control and RAMPS together which is wrong. Disable one to see if it effects this issue or not.
Offline
Thank you for looking at it. I disabled direct control and started another dry run. I'll report the results.
Thank you again for your help.
Offline
Dry run was successful! I'm thinking this was the problem. My lift sequence also now runs as it should!
Thank you so much for the help!
Offline
Pages: 1