correct shutdown procedure

All the topics related to QLC+ on the Raspberry Pi
Post Reply
richbass
Posts: 86
Joined: Wed Sep 12, 2018 10:44 am
Real Name: Richard

Is it ok to shutdown my rpi using the ‘shutdown’ command while QLC+ is running, or is it important to press the exit icon in the main toolbar first?

(obviously unsaved changes will be lost)
User avatar
mcallegari
Posts: 4807
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

Debian/Raspbian includes systemd, so when you invoke 'shutdown' or 'halt', systemd will nicely stop all the running services in the proper order. QLC+ is one of them.
You can shutdown/reboot from the web interface too. No need to ssh or access the UI every time.
richbass
Posts: 86
Joined: Wed Sep 12, 2018 10:44 am
Real Name: Richard

Thanks Massimo

I have wired up a button that invokes shutdown, so it’s very simple to shutdown the pi with one button push, but wanted to make sure I wasn’t going to corrupt any files
cannopa
Posts: 4
Joined: Thu Nov 15, 2018 12:53 am
Real Name: Peter Cannon

Hi,

I'm trying to set up an unattended lightig display, running on the Raspberry Pi, which I need to switch on and off at set times. I was planning to just use a time switch for the power for the Pi. Starting the display at power on is fine but if I just kill the power to the Pi then the fixtures remain on, following the last command they received.

I'd thought from this thread that if I schedule a shutdown, before killing power, QLC+ would stop the function and turn off the lights but this isn't the case.

I'd thought one solution could be to run a CRON job to kill the current QLC+ and then start another QLC+ Workspace with all fixtures off, but I can't figure out how to access that second workspace from a command line.

I wondered if anyone could suggest ideas as to how I can schedule a graceful shutdown to QLC+ and the running function?

Hope I'm not highjacking this thread, I think it's close enough to the original question but apologies if it should be a new topic.

(P.S. I'm a Linux novice and QLC+ newbie!)
(P.P.S. - I'v no means to just kill the power to the fixtures)
richbass
Posts: 86
Joined: Wed Sep 12, 2018 10:44 am
Real Name: Richard

What dmx interface do you use?
When I shutdown my pi the lights go out (using an enttec usb dmx pro interface, and a homemade interface using the pi uart port).
Maybe your interface retains last state of it loses power(?)
User avatar
GGGss
Posts: 3145
Joined: Mon Sep 12, 2016 7:15 pm
Location: Belgium
Real Name: Fredje Gallon

This behaviour is an option inside the fixtures itself also... (mostly you can choose between: refrain previous data, go black, go to automated mode, ...)
All electric machines work on smoke... when the smoke escapes... they don't work anymore
cannopa
Posts: 4
Joined: Thu Nov 15, 2018 12:53 am
Real Name: Peter Cannon

richbass wrote: Thu Nov 29, 2018 1:56 pmo you use?
The DMX interface is a Xinfly http://amzn.eu/d/5X5nQY6 . It wasn't very expensive so I guess I might just get what I pay for! But you've got me thinking, if I keep the powered hub up supporting the DMX interface and just power down the Pi - that might make a difference. I'll test that tomorrow when I'm there.
cannopa
Posts: 4
Joined: Thu Nov 15, 2018 12:53 am
Real Name: Peter Cannon

GGGss wrote: Thu Nov 29, 2018 3:03 pm This behaviour is an option inside the fixtures itself also... (mostly you can choose between: refrain previous data, go black, go to automated mode, ...)
I have Chauvet Tour fixtures which do have this option, but I also have MTC PAR64 and PAR144 fixtures which unfortunately don't (according to the data sheet I have).
cannopa
Posts: 4
Joined: Thu Nov 15, 2018 12:53 am
Real Name: Peter Cannon

cannopa wrote: Fri Nov 30, 2018 1:03 am But you've got me thinking, if I keep the powered hub up supporting the DMX interface and just power down the Pi - that might make a difference.
Nope, this doens't work, I tried keeping power on the DMX adapter when the Pi powers off and still the fixtures remain at their last command with the adapter I have.
So, the only solution I can see is to schedule, via CRON, to launch a QLC file, not the default one, but one which will just reset all the fixture to black.
I'm using Massimo's excellently crafted image for the Pi but I'm not sure I can actually access workspaces, that I've downloaded via the web interface, to use on the CRON command. Any assistance here would be appreciated (or other solutions!).
Stringfamily
Posts: 11
Joined: Wed Feb 13, 2019 7:31 am
Real Name: JoelM

cannopa,

I used the script function in QLC+ to create a shutdown function:
systemcommand:/sbin/shutdown

Then I created a Scene that turns off all fixtures.

Then I created a chaser and added 1. The scene to turn off fixtures and 2. The shutdown function.

Works beautifully!
dgallo
Posts: 3
Joined: Tue Aug 27, 2019 4:21 pm
Real Name:

it's not requisite to create a function and a chaser, the script can induce a blackout before the shutdown :

blackout:on
wait:2s
systemcommand:/sbin/shutdown arg:

Daniel
markzvo
Posts: 91
Joined: Sat Jan 28, 2017 1:52 am
Real Name: Mark Z

?

are you asking?

or telling?
Post Reply