Lesson 2.1

Trace, classify, hand off

GCL+ is structured text (BASIC-like) in the controllers — read it output-backwards: find writes to your point, read the surrounding logic (401's law, text form).
The enteliWEB program viewer shows live GCL+ with values annotated — the text equivalent of a live canvas: your trace instrument, no certification needed to read.
Loops in code are 401's loops; IF blocks and state variables are 402's machinery in text.
Priorities are standard BACnet — the ignoring point has a higher writer (306).
Boundary: read and trace freely; edits belong with certified programmers — your handoff cites program names and line references.

Service boundary: GCL+ edits belong with Delta-certified programmers — your reading access via the viewer is for diagnosis, and your line-referenced handoff makes edits fast.

LAB — the mixed-building drill

Identification: from the evidence pack (photos, screens, board labels), identify the Delta Controls generation and architecture present.
Navigation: on the demo/simulated front end, locate a given point, its trend, its schedule, and its override state within a time box.
Reading: trace one supplied program excerpt against its sequence (expected/observed/delta per 303) and classify the seeded deviation: equipment vs programming vs design.
Handoff: write the service note a Delta Controls-certified tech could act on immediately.

Pass: identification correct; navigation within the box; deviation classified with reasoning; handoff note professional.

LAB DEMO VIDEO

Instructor walkthrough — navigating the Delta Controls front end + one trace

[ ~12 min ]

The Delta native-BACnet stack — single-protocol architecture: enteliWEB → controllers (MS/TP + IP branches) → room devices incl. O3 hub; GCL+ live-viewer inset showing annotated code; standard-priority-array badge