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
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.
Control Schematic
This gets slightly more complicated, but not too crazy.
- 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.
- Converts Q-SYS Named Controls into DMX channel values. (Didn't cover)
- Supports multiple priority levels for controlling DMX. (Didn't cover)
- Packages DMX data according to E1.31 (sACN) standard.
- Sends DMX over UDP multicast to the correct universe.
- Updates continuously with a timer.
- Handles socket resets to ensure reliability.
- Supports dynamic universe changes.
- TSC-7w
- TSC-7t
- Screen 1 would send an output to raise the screen
- Screen 2 would send an output to lower the Screen
- 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.
- It creates a TCP socket with the Projector IP and Port
- It attempts to connect every 5 seconds until the connection is successful
- 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.
- Triggers projector Powering Off & On
- Active lamp (
0.1s) - Lamp 2 status (
1s) - Lamp 1 hours (
2s) - Lamp 2 hours (
3s) - Power state (
4s)
- Handles TCP connection and communication.
- Formats and sends PJ-Link commands
- .Reads responses and updates projector state in UI.
- Wrappers to query specific projector info.
- Respond to UI toggles to turn projector on/off.
- Queries lamps, hours, and power sequentially with timers.
Confidence Monitors & Amps go through a Very Similar Script, so I will not be covering those.
- 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
- The Amplifiers would be sent a trigger to turn on
- The RackPower would be sent a Toggle to turn on
- Enable - turns on amps/racks, sets audio source, disables Disable button.
- Disable - turns off amps/racks, resets audio, disables Enable button.
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
Comments
Post a Comment