So I have a raspi2 and can run Qlight on it. I'm using enttec open dmx. I have full control with OSC and iPads over wifi. The issue is after the system has been running a few hours (usually happens after 4 hours or so) I lose control over the dmx and the enttec box stops sending. If I go into the pi desktop and refresh the opendmx, it will come back on. It's not deselected at all - still is highlighted in profile. After a double click and refresh it's back on live.... Any ideas or suggestions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I wonder if this is a power saving settings issue?
I'm not a pi player, but maybe if you are running the pi on through osc then there are no physical inputs (mouse clicks and key strokes)
Is the pi is thinking "I'm not being used so I'll shut down a few things."
Just a thought...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That could be, but it still happens when a keyboard and trackpad are connected - also, how would I change a pi setting for "power Save" if I can't boot into the pi OS as Qlight boots immediately with the build. I know it's running on a weezy build, if there was a way anyone knows to change a power save mode let me know... That's how it acts, cause a refresh will get dmx working again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So I have a raspi2 and can run Qlight on it. I'm using enttec open dmx. I have full control with OSC and iPads over wifi. The issue is after the system has been running a few hours (usually happens after 4 hours or so) I lose control over the dmx and the enttec box stops sending. If I go into the pi desktop and refresh the opendmx, it will come back on. It's not deselected at all - still is highlighted in profile. After a double click and refresh it's back on live.... Any ideas or suggestions?
Hi,
I wonder if this is a power saving settings issue?
I'm not a pi player, but maybe if you are running the pi on through osc then there are no physical inputs (mouse clicks and key strokes)
Is the pi is thinking "I'm not being used so I'll shut down a few things."
Just a thought...
That could be, but it still happens when a keyboard and trackpad are connected - also, how would I change a pi setting for "power Save" if I can't boot into the pi OS as Qlight boots immediately with the build. I know it's running on a weezy build, if there was a way anyone knows to change a power save mode let me know... That's how it acts, cause a refresh will get dmx working again.
My RPi runs 24/7 and nothing happens in this way. It's used as an ambient lighting controller. It runs and runs and runs...
I'm using a cheap kind of open dmx interface...
I for myself can't imagine that any power saving mode disturbs the operation of QLC+ (the image file from Massimo...)
Moved to the RPi forum.
As far as I know there is no "real" power saving on the Rpi except for the HDMI output going black after a while.
Anyway, the first result Google gives me is this: http://www.raspberrypi.org/forums/viewtopic.php?f=29&t=35054
Please try that and also do the same test on a PC with the same project and the same USB adapter.
In this way you can cut the problem in a half.