You are not logged in.
Hi,
thanks for this awesome software. I am new to SLA Printing and in the process of building my first printer.
I already grabbed my old RPI2 and installed and updated the generic image. I have a few questions, though.
In between projection of the layer images, the console messages of the system are shown. Is that normal behavior or is there something wrong? How do I get rid of that?
The other question I have is – don't lough – what are stop layers and what do they do?
Thanks
Sebastian
Offline
You means activity log on dashboard? It is safe to ignore.
It is useful when you are changing settings and debugging. Maybe with next dashboard revision we hide it.
Stop layers, make printer stop on specific layers.
Offline
Thanks for the swift reply, Shanin!
Sorry, I did not make myself clear.
during the booting process of the RPI, is see the usual bunch of messages on the screen (projector) connected to the HDMI output. After the bootup, this screen gets partially cleared with some messages remaining (usually something about NTP or so. I think it is stuff that also goes into /var/log/messages). When I run a print job, the layer images get displayed, but whenever they change, these system messages are displayed on the projector output (which would cause letters being printed in 3d in the upper left corner :-)
Any ideas?
Thanks
Sebastian
Offline
Oh
Have you installed SD card image or used command line installation?
On full version of raspbian jessie we had this issue as systemd does not run program in blocking way. But issue was solved at-least for that version.
Offline
I have installed the SD-card image, expanded it and updated to 1165.
The message says "[OK] LSB: Started NTP Deamon" sometimes there is other stuff, too
Can i change it manually?
btw, I have added an entry to rc.local in order to disable screen blanking after keyboard/mouse inactivity
(setterm -blank 0 ) but I guess that should not cause it.
Thanks
Sebastian
Offline
Sebastian,
Screen would not get blank, remove setterm.. see if it fixes the issue.
rc.local file should looks like this.
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
/bin/bash /home/pi/printer/config/run.sh
exit 0Offline
Thanks again for your help!
Well, I put it there because the screen went blank.
I tried removing it from rc.local, rebooted RPI and tried printing. same behaviour.
After the boot, the LSB message remains on the screen, during printing the layers get shown, between the layers, the screen with the message is shown again.
In case it helps, here is the debug stuff: http://sebastianstetter.de/transfer/nan … 426719.zip
Thanks!
Offline
Could you share content of this file?
/home/pi/printer/config/run.sh
Also run these commands and reboot
sudo systemctl enable rc-local.service
sudo systemctl set-default multi-user.targetIf it does not fix the issue, somehow rc.local runs before NTP. Put delay in run.sh file before clear command.
sleep 5Offline
Thanks, man! It finally works!
Just putting the delay in solved it.
run.sh now looks like this:
#!/bin/bash
touch /var/log/printer.log
chmod 644 /var/log/printer.log
answer=""
read -n 1 -p "Press any char key in 3 seconds to abort nanoDLP and go to Terminal" -t 3 answer
if [ "$answer" = "" ]
then
/usr/local/bin/pigpiod -s 10
sleep 5
clear
setterm -cursor off
(cd /home/pi/printer;ionice -c 2 -n 0 nice -n -20 ./printer >> /var/log/printer.log 2>&1)
fi
exit 0I was not able to enable rc-local.service, though:
pi@raspberrypi:~ $ sudo systemctl enable rc-local.service
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).But I guess that should not be an issue since it works, now.
Is there any chance that later messages might be appearing after the clear?
Thanks, again, for your quick and awesome help!
Sebastian
Offline
I do not think they could appear again.
Offline
Thanks dude!
Awesome work!
Offline
Here we go again...
Sometimes in the middle of a print there is a console message on the projector that does not get cleared:
"starting cleanup on temporary directories...
[OK] started cleanup on temporary directories."
Only after rebooting, the message is gone.
This is in both, the current release and the beta (1255)
Any ideas?
Thanks, best, Sebastian
Offline
Please, use official image. I have not got report about jessie lite for last couple of months So I think it must be pretty stable in this regard.
Offline
Hi Shanin,
Thanks for your reply!
Uhm... I use the Image from http://www.nanodlp.com/download/ where it says "Download nanoDLP SD card image file". Is there a more official one?
Just upgraded after install.
Sometimes it seems to take a little longer until a layer image is displayed on the screen and the message seems to appear right after that and stays until reboot.
Any idea what action / function writes this message to console? I don't really understand how this image display / console thing works together, or when / how the screen is cleared by what functions, so it is hard to track down.
Thanks,
Sebastian
Offline
Use this command and see if it helps.
sudo systemctl mask systemd-tmpfiles-clean.timer
Offline
Thanks, Shanin,
looks like this solved it. However image display and shutter seem to be out of snyc, now (image is shown before shutter opens), but as far as I can tell, the exposure times are still maintained.
Offline
add delay before layer display. to give shutter some time to open.
Offline
Oh - of course... should have thought of that...
Thanks again!
Offline