The LogiDraft Canonical Example

What this is

The canonical example is a single, stable reference workflow that shows how LogiDraft behaves when parameters drive geometry. It exists so every new user can start from the same known model and see the system respond in predictable, repeatable ways.

Use it to learn the mental model, confirm expected behavior, and share a consistent reference when asking questions or debugging changes.

What you'll learn

  • How block definitions and block references work together.
  • How parameters and variables cascade through nested blocks.
  • How formulas drive geometry, text, and component selection.
  • How lookup tables and directives control conditional outputs.
  • How a single parameter change propagates across sheets.

Open the example

Open the document in the editor to explore the live parametric model.

Open the Canonical Example

How to use it

  1. Open the example in the workspace.
  2. Select a block reference and change a parameter like quantity or voltage.
  3. Observe updates across geometry, text tags, and nested sub-blocks.
  4. Inspect formulas and lookup tables that drive the changes.

Canonical Example: Motor Control Panel (MCP)

This canonical example demonstrates a complete parametric workflow using a Motor Control Panel (MCP) block. The document contains two finished sheets (UNIT1/UNIT2) and one shared MCP definition. Parameters, variables, states, directives, and a lookup table drive downstream geometry and component selection.

Free for everyone. Opens in the workspace.

What this example contains

  • Two sheets: UNIT1 and UNIT2
  • One MCP block reference on each sheet
  • Each instance uses different parameter values
  • Downstream geometry/text/sub-blocks update automatically

Important mental model: Configure designs by editing block references on sheets. Edit block definitions only when you want to change the logic.

Walkthrough (10–15 minutes)

1) Compare the two sheet outputs

  • Switch between UNIT1 and UNIT2
  • Same MCP definition, different instance parameters
  • Differences are driven by intent, not manual edits

2) Inspect the MCP block reference (recommended workflow)

  • Select the MCP block on a sheet and review its parameters
  • Motor_Voltage (208/460/575) and Control_Voltage (24/120)
  • Motor_Qty (1/2) and Control_Type (Remote/Push Button)
  • Try this: change Motor_Qty from 1 → 2 and confirm the contactor section toggles automatically.
  • Change Motor_Qty or Control_Type and observe updates

3) Observe propagation (what updates when intent changes)

  • Text tags update (for example, voltage labels)
  • Nested sub-blocks update
  • Conditional geometry toggles where applicable

4) Open the MCP block definition (logic inspection)

  • Definitions define intent and logic; references configure instances
  • MCP injects three sub-blocks: Control_Transformer, MCP_Contactor, MCP_Controls

5) Inspect derived variable: Control_VA

  • Derived from Motor_Voltage and Motor_Qty
  • Compute once, reuse everywhere (passed into nested blocks)

6) MCP_Contactor: directive-driven conditional geometry

  • MOTORS parameter
  • Motor_Boolean variable (MOTORS == 2)
  • Insert directive toggles geometry based on Motor_Boolean

7) MCP_Controls: state-driven configuration

  • Type parameter (Remote/Push Button)
  • State selection formula: (Type)
  • Switching Type changes the active state and geometry
  • Note: MCP_Controls.Type is driven by the parent MCP.Control_Type.

8) Control_Transformer: lookup-driven fuse sizing

  • Params: Primary_Voltage, Secondary_Voltage, VA
  • Vars: Primary_FLA, Secondary_FLA
  • Primary_Fuse uses LUT_EXACT on FUSE_CHART mapping VA + voltage → fuse size
  • Lookup table is stored in the block definition

9) Fuse block: parameter-to-text injection

  • Fuse param: AMPERAGE
  • AMPERAGE injected into a text tag

10) Duplicate an instance on the sheet

  • Duplicate MCP reference
  • Override parameters per instance
  • Definition stays shared; instances differ

Concepts demonstrated

  • Parameters
  • Variables
  • States
  • Lookup Tables
  • Directives
  • Injection

Editing guidance

  • Edit block references to configure designs.
  • Edit block definitions to change logic/behavior.
  • If grips are disabled, the geometry is likely parameter-driven—change the parameter instead.

You're done when: one parameter change updates multiple outputs (text, nested blocks, conditional geometry) without manual edits.

Where to go next

  • Help & User Guide for step-by-step onboarding and reference topics.
  • Blocks to learn how definitions, references, and parameters fit together.
  • Support if you need help or want to share feedback.