D12 / R70 — Project, network and control checks
Blank fields: record only actual settings and observed results.
Date / event / technician:
D12: identification / firmware / dbCAN-ID / rack location:
R70: identification / firmware / Host Name:
ArrayCalc / R1 / operating system versions:
ArrayCalc file / R1 file / revision and rollback copy:
Loudspeaker models, order and quantity / channel grouping:
Speaker setup / LINE or ARC / audio patch:

NETWORK BEFORE TESTING
Computer network interface / IP / subnet mask / DHCP or manual mode:
R70: actual IP / subnet mask / DHCP or manual mode:
DHCP server / assigned or reserved address, where applicable:
Observed IP conflicts and how they were verified:
ON / LAN / ERR / CAN indicators:
R70 web access: address used / observed result:
R70 detection in R1 / expected and detected D12s:
CAN topology / both ends / terminations / identified cables:
Firewall rules checked / configured TCP port / UDP:

PROJECT–RACK ASSIGNMENT
Project ID / expected physical D12 / identification using Wink:
Matches and differences in models, channels, loudspeakers and groups:
MUTE state before sending configuration:
Test signal / agreed level / destination heard:

ONE CHANGE
Previous value / proposed change / reason / test window:
If changing LAN Parameters: new settings and planned restart:
Web access / control detection result after the change:
Audio result checked separately:
What was ruled out / what remains unresolved:
Final state / restored settings / rollback file:

References: R70 Manual 1.4 EN, §§3.2–3.6 pp.12–16;
R1 official, User interface and Service functions; ArrayCalc official,
Product description; TI 385 10.4 en §3 p.8.
An active control session does not confirm the audio patch.
Do not initiate Factory Default or network changes as a test during a show.