The Original Q-Sys Version (Schematics): (Automation)

The first version was very basic, with minimal functionality and effort being put into the system. It was left undermaintained for years to the point actually held back our system from being able to showcase its full potential.

Below will be a video of UI in a slideshow Manor.




Let's start with the Schematic Analysis


Audio Schematic

Here we are shown 3 actual components

  • Physical Line in Connections
  • Mixer (Audio Routing)
  • Physical Line Out Connections

Line In

    In The Physical Line Connections, the Pro Console Connections are 4 inputs that are derived from the output ports of a (DiGiCo D2 Rack)

The Mic 1-4 are actually nonexistent. I assume that those mics are equipment that was taken when the Church left, that instead of being routed and managed by the Pro-Console, it was instead managed by Q-Sys instead. 


Mixer

    Test Feed is the Pink Noise, White noise, Sine generators, etc, that Q-Sys provides to test the audio system flow. Nothing unusual, it's the basis of every A/V setup in Q-Sys. So we have those 4 non-existent Mics that serve 0 purpose flowing in, and the Pro-Console filling out the rest of the ports.

    The Bottom MutePA inputs are what mute the outputs of the mixer, basically preventing audio flow when either the PA is being broadcast over the venue or if the Fire Alarm goes off.


Line Out

    Very simple setup, Audio comes in, is mixed and routed, and then flows out through these outputs into an amplifier.


Over-all, this is a very simple setup, nothing really needs to be changed here apart from removing the mics.


FINSIHED




Control Schematic


This gets slightly more complicated, but not too crazy.

Lighting
    Universe 1, 2, and 3. These are Lua Scripts that control the routing for DMX Data across the 3 universes using a custom sACN (Streaming ACN) transmitter.
  • Utilizing Global Named Controls to control DMX 0-255
  • custom sACN (Streaming ACN) transmitter
  • Broadcasts over Port 5568


When it comes down to the actual transmission








  • Converts Lua table of numbers into a byte script suitable to send over UDP
  • Each 0-255 number becomes a single byte










  • DMX updates every 30ms







  • SocketTimer closes and reopens the UDP socket every 5 seconds to prevent socket issues with continuous streaming.






  • Creates a UDP socket for sending the Data via sACN









  • Updates Multicast IP
  • Reads what universe to send to
  • Changes apply dynamically over universes



SUMMARY
  1. Converts Q-SYS Named Controls into DMX channel values. (Didn't cover)
  2. Supports multiple priority levels for controlling DMX. (Didn't cover)
  3. Packages DMX data according to E1.31 (sACN) standard.
  4. Sends DMX over UDP multicast to the correct universe.
  5. Updates continuously with a timer.
  6. Handles socket resets to ensure reliability.
  7. Supports dynamic universe changes.

The Lighting Group represents the Global Named Controls that the Universe Lua Scripts check for. The LX presets block is simply a recorded state of those controls, so you can create presets, record them, and allow for easy customization of lights based on those controls that the user can change. 
(Only for Designer, not implemented for User)

FINSIHED







Touch Panels


The Yellow Blocks are the Physical Touch Panels that the user is to use.
(T is for table-mounted)
(W is for wall-mounted)
  • TSC-7w
  • TSC-7t
The Script block on the left implements UCI Changes (Switching the console from one UI to another)
If you aren't savvy in Q-SYS. There are two things: a UCI, which is a User Control Interface. Think of this as a binder, and then the pages inside the binder, which are just pages.


UCI - Binder
Pages - Pages in a Binder


The block on the left handles the assignment of a different binder to these Panels. For example, the Church and School settings are different UCIs, but Audio and Video are pages on that UCI.

The Logout handles returning both UCIs to the Main UCI, which is where you select what mode to go into.

FINSIHED







GPIO
On the Core, there are GPIO Phoenix connectors that allow 3rd party applications to either receive or output to the Core.


Let's focus on the GPIO Out first.
    The Projection screen block is a custom control block that simply creates controls. When either one is pressed, it sends an output through such a GPIO port
  • Screen 1 would send an output to raise the screen
  • Screen 2 would send an output to lower the Screen
    The processing of these signals is handled by the Unit that is receiving the output, which, in this case, processes them as a simple trigger to start lowering or raising, based on what input it received.

    The RackPower simply sends an output to the MiddleAtlantic Power Surge bar telling it what state to be in, either On or Off.



GPIO In
    In our first 2 Digital Inputs, it receives a Signal from the Fire Alarm, and then the Intercom. It's up to Q-SYS on how it interprets this signal; in this case, the Fire Alarm is a trigger, and so is the Page.
  • Both Inputs toggle only last as long as the actual input itself, so if the PA is active only for 15 seconds, that input is only active for 15 seconds, and the same for the fire alarm.

FINSIHED






Simple Console Mute

First, let's talk Logic (OR)
    It takes that toggle input from either the FireAlarm or Intercom, and it sends an output to MutePA, which you'll find in the Audio Schematic. In that case, it mutes the Outputs to that Mixer for the duration of whatever is passing through that Logic Or.

In the UCI, you'll see a Console mute button











Just like before with the Projector Screen, this is a custom control. The Mute console button is a toggle button, so as long as it's toggled, it mutes the output of the mixer


FINSIHED






Panasonic Projector
    This is a LUA Script that manages turning the projector off and on. Let's review the Code.










  • It creates a TCP socket with the Projector IP and Port
  • It attempts to connect every 5 seconds until the connection is successful








  • Handles Connection states, errors, etc





  • Connects to the projector and builds a PJ-Link





  • Sends the command after 0.1s.
  • Disconnects after 0.5s to prevent lingering TCP connections.









  • Requests information such as what lamps are on
  • Handles Projector's power state
  • Handles the logic for both lamps based on mode/etc









  • Wrapper function that calls the toDev() with the proper PJ-Link command.





Picture Slightly Cut Off
  • Triggers projector Powering Off & On



Uses staggered timers to poll:
  • Active lamp (0.1s)
  • Lamp 2 status (1s)
  • Lamp 1 hours (2s)
  • Lamp 2 hours (3s)
  • Power state (4s)
Prevents sending all commands at once, avoids TCP collisions or overwhelming the projector.


SUMMARY
  1. Handles TCP connection and communication.
  2. Formats and sends PJ-Link commands
  3. .Reads responses and updates projector state in UI.
  4. Wrappers to query specific projector info.
  5. Respond to UI toggles to turn projector on/off.
  6. Queries lamps, hours, and power sequentially with timers.

Confidence Monitors & Amps go through a Very Similar Script, so I will not be covering those.



FINSIHED







System Power
  • Rack Power - Send an output to the GPIO to tell the Rack to Turn Off or On
  • AmpsOnFb - Reports Whether the Amplifiers Are On
  • AmpsOffFb - Reports Whether the Amplifiers are Off

If ChurchPwr were to enable (same for SchoolPwr)
  • The Amplifiers would be sent a trigger to turn on
  • The RackPower would be sent a Toggle to turn on






























Script toggles School and Church power:
  • Enable - turns on amps/racks, sets audio source, disables Disable button.
  • Disable - turns off amps/racks, resets audio, disables Enable button.
Keeps buttons mutually exclusive and logs actions.




The Issues with these Schematics.

  • The Projector is unable to properly connect and overloads the system with Errors, taking up a lot of resources.
  • The Confidence Monitors Script is also reliable for a similar issue within the code
  • The Lighting Universe contains improper information, causing routing issues leading to fixtures not functioning (Easy Fix)
    • This is still a really good Script and can be easily fixed to continue usage.

  • There is a lot of overcomplexity in things such as Enabling Rack Power and splitting it into different buttons. A lot of stuff can be removed, even know it's already very basic.
  • This is using outdated Code that could be replaced with (From Manufacturer-made Plugins that are guaranteed to work with proper networking)
  • It is not scalable, and based on how work was done, if anyone were to upgrade it, it would become very disorganized

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)