The Updated Q-SYS System Overview: (Automation)

In this blog, I will talk about a completely remade version of the Q-Sys (Automation) system, but this will be a general overview; in the next blogs, I will discuss details such as the schematic and UCIs.


Some Basic Knowledge

Networking

We utilize a Q-Sys core 110f running two Ethernet ports, 

  • LAN A - Private Network (Venue Applications and etc)
  • LAN B - Gateway

Licences
Our core was manufactured before the introduction of licenses, so we already have features such a UCI-Deployment and the Scripting Engine. 

(I genuinely don't know how others do it without the scripting engine. I use it basically everywhere.)


Periferals

    Due to these peripheral displays, Q-Sys has to stay on version 9.13.1 LTSC, as these devices are now discontinued and are no longer supported in the latest version, which is very unfortunate

  • TSC-7w
  • TSC-7t
W = Wall mounted, T = Tabletop



System Overview

What does my system do?

The system provides centralized management of an integrated A/V environment, including audio, lighting, and partial video control. Authorized users can utilize configurable automation functions to streamline operations and enhance accessibility, and manage current systems.


The A in A/V

(Audio)






    All audio sources are routed through Q-SYS for mixing before being output to the LA4X amplifiers. This configuration allows complete control over gain structure, pre-fader levels, and signal processing modules, while also serving as a diagnostic platform for maintenance and troubleshooting through UCI portals.

    Also performing in control territories, being responsible for powering Receivers via GPIO and Amplifiers via Network protocols.

  • This allows a direct cut-off case of audio errors.
  • Prevents Unauthorized Access to equipment usage.
  • Complete control over Audio Inputs and Outputs


The V in A/V

(Video)






    My system doesn't directly manage Video Streams, as we don't have the equipment to implement such workflows. Instead, we manage:

  • Confidence Displays   (Via Network)
  • Projectors                    (Via Network)
  • Motorized backdrops  (Via GPIO)

The Invisible L in A/V

(Lighting)






    My system uses parts of the old system LUA to manage DMX lighting over a networking protocol called (sACN), which uses multicast to spread this signal all over the network for gateways to receive it.

  • Communicates with 3 Universes
  • Can transmit non-flooding sACN data over multicast
  • Fully customizable, just like the ETC-Ion Xe
  • Can remove priority, take priority, etc.
As another measure of Authorization, Advanced Lighting controls can be used only if enabled Via Q-SYS, but things such as House Lighting can be enabled by anyone via the Old Strand Wall button or the Light Icon on the Login Screen of Q-SYS
So the lighting console, aka ETC Ion, cannot perform any stage lighting at all until the LEDS are powered on Via Q-Sys, which also bypasses the Strand C21 priority, preventing further disagreements between what should be on or off.


Security

    Through a completely customized Login UI. Q-Sys logs all users who've logged into the Unit via the Event Logger in Q-SYS Reflect or the Administrator UCI (Later explained).

With a custom Login UCI, I can completely customize what each user sees, including administrator-only tools, Testing environments, etc. 
  • With each user receiving their own key that only they are to know, and not share. They can log in to their respective accounts and gain the permissions given to that specific account.
  • Things such as Day-Passes can be made for guest users or Events that last 24hours, but can be modified to last any amount of time from down to 10 seconds to 1 year. (It is literally completely Customizable!)
With my custom Admin UCI and Q-Sys Reflect. I can remotely monitor activity, sound, lighting, etc. I can log people in and out, view consoles, perform troubleshooting, maintenance and etc. 
"Be still, and know that I am God"
You quite literally have complete control, which can be accessed only via Q-Sys reflect, which is protected via my own Domain Email with multi-factor auth. Or via the Venue network itself, which would require you to first gain access to the network, then be approved by the networking administrator,(aka me) with access time being able to be customized, so a user might only be able to be connected for a period of time before losing all accsess and leases, and only after all that, then they use another password to access the UCI.


You quite literally have complete control, which can be accessed only through:

  1. Q-Sys reflects, which is protected via my own Domain Email with multi-factor auth.

  2. Connect to the Venue network itself, and use the Q-Sys Viewer 
    1. Which would require you to first gain access to the network
    2. Then, be approved by the networking administrator (aka me) to join the network
      • With access time being able to be customized, a user might only be able to be connected for a period of time before losing all access and leases. 
    3. And only after all that, then they use another password to access the UCI.
Is this overkill for the environment? 
Very.

But is it fun? 
Yes.

Next blog will cover the UCIs!
Thank you for reading.

Comments

Popular posts from this blog

Restoration Of Floor Plans & schematics

Why Lighting Sucks. (When done wrong)

DMX Issue Resolved : (Lighting)