Page 1 of 1

Changing the file that opens automatically

Posted: Wed Dec 09, 2015 8:39 pm
by jerodkdunn
How do I change the file that loads automatically? I created a workspace on the pi locally, and I would like it to open when the device boots. Is there any way to make this happen?


Thanks for making all of this possible.

Re: Changing the file that opens automatically

Posted: Thu Dec 10, 2015 12:36 am
by mcallegari
It's written in the user guide PDF
Paragraph 5.1.4: Project autostart

Re: Changing the file that opens automatically

Posted: Fri Dec 11, 2015 7:36 pm
by jerodkdunn
What if the pi refuses to connect to a network? I've used multiple routers and tried reinstalling the QLC+ image several times. Ran a standard noobs install to verify that the physical ethernet port worked fine. The qlc+ image refuses to connect to a network with ethernet. Without access to the web interface for making changes to the autostart, or any other feature I would use, the pi just acts like an underpowered version of the desktop app.


Any suggestions?

Re: Changing the file that opens automatically

Posted: Fri Dec 11, 2015 11:38 pm
by mcallegari
First, this is another topic than "Changing the file that opens automatically"
What if the pi refuses to connect to a network?
what does this even mean ? What is your network configuration on the RPi ? static IP ? DHCP ?
Without access to the web interface for making changes to the autostart, or any other feature I would use, the pi just acts like an underpowered version of the desktop app.
This is not true, since you can set an autostart project even without the web access. If you guys only read the documentation or try to understand how Linux works...

Please be more cooperative and less judgmental

Re: Changing the file that opens automatically

Posted: Fri Dec 11, 2015 11:57 pm
by jerodkdunn
With the fresh image it's set to the default static IP address. When I say it won't connect to a network, I mean that it simply doesn't appear on my network, even when I check my router to see devices connected. It won't ping out or perform an update. On "factory" settings the pi isn't accessible via ssh or the web interface.

The off that is provided in the email has nothing on changing the auto start project outside of using the web interface. When questions are asked about changing the auto start project people are referred to the web interface.

I do realize this is only a problem for me because I don't have a lot of experience with Linux, and I appreciate the work you've put into this. That's why I'm here on this forum asking questions.

Re: Changing the file that opens automatically

Posted: Fri Dec 11, 2015 11:57 pm
by mcallegari
jerodkdunn wrote:With the fresh image it's set to the default static IP address. When I say it won't connect to a network, I mean that it simply doesn't appear on my network, even when I check my router to see devices connected. It won't ping out or perform an update. On "factory" settings the pi isn't accessible via ssh or the web interface.
And in which class of IP is your home network configured ?
If it's not 192.168.0.x then it's obvious you won't be able to reach the RPi. This is basic principles of networking.
You need to temporarily change the IP of your computer to be in the same network of the RPi.
jerodkdunn wrote:The off that is provided in the email has nothing on changing the auto start project outside of using the web interface. When questions are asked about changing the auto start project people are referred to the web interface.
Again, this in not true and the user guide PDF gives you all the information you need to set an autostart project even not through the web interface.
I quote:
Once changes are applied, the currently loaded project will be copied into a file in the /root/.qlcplus folder called “autostart.qxw”.
At the next boot, QLC+ will detect the presence of the file and will load it automatically.
This means you can save a project from within the RPi, quit QLC+ and login into a console and copy the project you just saved into a file called /root/.qlcplus/autostart.qxw.
You don't even need to be connected to a network to do this.

Re: Changing the file that opens automatically

Posted: Sun Dec 13, 2015 2:44 am
by jerodkdunn
Thanks for the update. I feel like an idiot now. I made a file locally and used it to replace the autostart file.


I still can't reach the pi via the web interface though. I changed my laptops ip to be in the same class as the pi, but I still get a server not found prompt. My end goal is to attach the 7" touchscreen and leave it in the virtual console so that untrained volunteers can start simple scenes in a local venue. Does the latest image have support for the official touch screen?

Re: Changing the file that opens automatically

Posted: Sun Dec 13, 2015 2:44 am
by mcallegari
jerodkdunn wrote:I still can't reach the pi via the web interface though. I changed my laptops ip to be in the same class as the pi, but I still get a server not found prompt.
Have you tried to ping the RPi IP address from your computer ? If that doesn't work, you still have some network issue
jerodkdunn wrote:My end goal is to attach the 7" touchscreen and leave it in the virtual console so that untrained volunteers can start simple scenes in a local venue. Does the latest image have support for the official touch screen?
Yes it does.

Re: Changing the file that opens automatically

Posted: Sun Dec 13, 2015 2:44 am
by jerodkdunn
For some reason my router assigns everything 192.168.29.x. I originally ychanged my laptops ip to be 192.168.0.x, but that never worked. Set my laptop back to DHCP and changed the ip address of the pi to 192.168.29.252 and it worked like a champ. Thanks for everything.

Re: Changing the file that opens automatically

Posted: Sun Dec 13, 2015 2:44 am
by conradcliff
jerodkdunn wrote:For some reason my router assigns everything 192.168.29.x. I originally ychanged my laptops ip to be 192.168.0.x, but that never worked. Set my laptop back to DHCP and changed the ip address of the pi to 192.168.29.252 and it worked like a champ. Thanks for everything.
Simply changing your laptops IP address to the same subnet as the RPI wouldn't work as you found out. You would need to reconfigure the router to be on the subnet you wanted. You're method is of course just fine though :)