Trace the sensor circuit
- Open sheet 2 and identify B1, its supply/return cross-page references and its OUT connection to X2.
- Follow the reference from X2 to A1 on sheet 1. Inspect the PLC DI 0 function.
Check your result
The signal route is B1 OUT → X2 → A1 I0.0, with a separately documented supply and return.
Inspect cable and IO metadata
- Select the three W1 connections and review Cable, Core, Color and cross-section: cores 1/BN, 2/BU and 3/BK.
- Select the PLC input function and inspect Address I0.0 and Signal Part detected.
Check your result
Each cable core is uniquely allocated and the PLC signal is named.
If you get stuck: Address/terminal choices must match your selected PLC and sensor. This example does not establish a vendor pinout or input-common compatibility.
Read the generated schedules
- Open Reports → Cables to inspect W1's three cores. Choose Terminals to inspect X2's two endpoints.
- Choose PLC IO to locate I0.0, Part detected and its current sheet reference. Review Checks for duplicate addresses or core reuse.
Check your result
The cable, terminal and PLC reports agree with the drawing connections.
Keep a documentation snapshot
- Update the document revision/date when issuing a new drawing set, then export Documentation ZIP.
- Keep the editable project separately so subsequent changes can regenerate its reports.
Check your result
The ZIP contains the current source and reports with a hash manifest.
If you get stuck: Cable schedules describe explicit point-to-point assignments. Cable lengths, harness routing and terminal bridge/accessory allocation are not calculated.