Hi, i need to run as root in order to access the GPIO's of the raspberry with wiringPI_gpio ... at least that is what i understood...
i also found that the process
wish /usr/lib/puredata/tcl//pd-gui.tcl 5400
is sometimes piling up RAM, which causes the RPi to crash. can this be connected?
i thought of reading the GPIO via python and send SensorData via netsend...or use an arduino to handle the SensorCommunication...
Any recommendations?
Michael
ps: it is a special feeling - talking to the creator...
Something's malfunctioning in Pd-watchdog.. but anyhow, is there any way you
can get Pd to run not as root? That way it has no way of kicking systemd (which it somehow seems to be doing).
cheers Miller
On Mon, Dec 03, 2018 at 02:11:07PM +0100, michael strohmann wrote:
Hi, i don???t know if i read this right: to me it looks like PD froze and
the watchdog sent SIGHUP. after which the system rebooted itself.
is there a way do find out why PD froze? thanks! michael
Dec 3 12:15:01 RoomOne CRON[3818]: (pi) CMD (ps aux --sort -rss|head
-15 >> /home/pi/Desktop/ps.log)
Dec 3 12:15:35 RoomOne systemd[1]: Received SIGHUP from PID 634
(pd-watchdog).
Dec 3 12:15:35 RoomOne systemd[1]: Reloading. Dec 3 12:15:36 RoomOne systemd[1]: apt-daily.timer: Adding 8h 8min
33.364295s random time.
Dec 3 12:15:36 RoomOne systemd[1]: apt-daily-upgrade.timer: Adding
56min 30.656756s random time.
Dec 3 12:15:37 RoomOne systemd[1]: Received SIGHUP from PID 634
(pd-watchdog).
Dec 3 12:15:37 RoomOne systemd[1]: Reloading.
On 05.12.18 14:12, Christof Ressi wrote:
is sometimes piling up RAM, which causes the RPi to crash. can this be connected?
do you happen to print stuff to the console continuously? There was an issue that when you print *a lot* of text, the GUI would eventually run out of memory (don't know if this has been fixed in the meantime).
the question is how to actually fix it in a reasonable way. maybe I do want to have zillions of lines of text in my RAMmed up machine?
anyhow, if the printout is indeed the culprit (and it sounds like a plausible analysis to me), then a simpe fix could be to just print to stderr. that is, start pd with:
$ pd -stderr
you will still have a GUI, but the Pd-console will be redirected to the terminal (which just drops the oldest lines).
BTW: your last three e-mails all had different subject lines although the topic is the same. make sure that you keep the subject line, so people can later follow the thread.
+1, although you could have changed the subject as well :-)
fgmr IOhannes
+1, although you could have changed the subject as well :-)
guilty as charged
Gesendet: Mittwoch, 05. Dezember 2018 um 15:14 Uhr Von: "IOhannes m zmoelnig" zmoelnig@iem.at An: Kein Empfänger Cc: pd-list@lists.iem.at Betreff: Re: [PD] RPi Debug
On 05.12.18 14:12, Christof Ressi wrote:
is sometimes piling up RAM, which causes the RPi to crash. can this be connected?
do you happen to print stuff to the console continuously? There was an issue that when you print *a lot* of text, the GUI would eventually run out of memory (don't know if this has been fixed in the meantime).
the question is how to actually fix it in a reasonable way. maybe I do want to have zillions of lines of text in my RAMmed up machine?
anyhow, if the printout is indeed the culprit (and it sounds like a plausible analysis to me), then a simpe fix could be to just print to stderr. that is, start pd with:
$ pd -stderr
you will still have a GUI, but the Pd-console will be redirected to the terminal (which just drops the oldest lines).
BTW: your last three e-mails all had different subject lines although the topic is the same. make sure that you keep the subject line, so people can later follow the thread.
+1, although you could have changed the subject as well :-)
fgmr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Christof Ressi -
IOhannes m zmoelnig -
michael strohmann