← Curriculum
AV InstituteAV Institute LLC
02Week 2 · 5–7 hours

Programming & Control Basics

Control systems, processors, and program logic

Move from signals to behavior. Learn how a commercial AV control system works, the transport types it uses (serial, IP, relay, IR), the programming primitives that drive it, and how to express a room's behavior as logic you can program.

Key Competency

Write room control logic and explain how a control system talks to devices.

AV Institute
AV Institute · Week 2Programming & Control Basics
Practical Lab

Build a Conceptual Room-Control Sequence

Est. 90 minCompetency: Define inputs, outputs, and feedback for a room control program.

Learning objectives

  • List the inputs (buttons) and outputs (device commands) for a room.
  • Define the feedback the program needs from each device.
  • Write the Start and Shutdown sequences as pseudocode.
  • Map each UI element to a variable and a feedback source.

Lab brief & instructions

Without any specific vendor, design the control for a single conference room with a display, a switcher, a DSP, a screen lift, and a touchpanel. Produce the inputs, outputs, and feedback that a program would need.

Deliverables

  1. 1An input table: button | event | what it should do.
  2. 2An output table: device | command | transport.
  3. 3A feedback table: device | status queried | how the UI uses it.
  4. 4Start and Shutdown pseudocode with state transitions.
  5. 5A list of error states and how each is shown on the panel.
Equipment-free alternative

Use a spreadsheet or notebook. The value is in the tables, not the tool. If you can write the I/O and feedback tables for this room, you can program it on any platform.

Implementation checklist

  • ✓Inputs, outputs, and feedback tables complete.
  • ✓Start/Shutdown pseudocode includes state transitions.
  • ✓Each UI element mapped to a variable and a feedback source.
  • ✓At least three error states defined and surfaced.

Downloadable study guide

study-guide.txtcopy-paste ready
01. Lab outputs: input table, output table, feedback table, Start/Shutdown pseudocode, error states.
02. Map every UI element to a variable and the device feedback that updates it.
03. Define error states (display no response, network loss, source missing).