Canonical explanations and fixes for tscircuit toolchain error signatures.
The tscircuit DRC engine emits a pcb_trace_missing_error when a logical trace defined in the schematic lacks a corresponding physical layout path on the board. This usually indicates that the autorouter failed to find a valid path due to congestion or obstacles.
A design rule check error indicating that two vias on a printed circuit board are placed closer than the required minimum clearance distance.
The tscircuit compiler emits this diagnostic when a schematic component, trace, or net connection attempts to reference a port that does not exist on the specified symbol.
The simulation_unknown_experiment_error diagnostic is emitted when a tscircuit simulation engine encounters an analysis or experiment type it does not recognize, resulting in an error element within the Circuit JSON artifact.
Emitted in the compiled Circuit JSON when a user-provided component property fails validation or does not match the expected format.
An electrical rules check diagnostic generated by @tscircuit/checks when a component pin marked as requiring a connection is left floating without any assigned source traces.
This diagnostic indicates that a trace was declared with selectors that could not be resolved to any valid ports. The tscircuit compiler emits this error during evaluation when trace endpoints fail to match existing components or pins.
A diagnostic indicating that a component port assigned to a net lacks a physical trace connection on the PCB.
Emitted when incompatible I2C pins, such as Serial Data (SDA) and Serial Clock (SCL), are erroneously connected to the same electrical network.
The circuit builder encountered an unhandled exception or unexpected payload (e.g., HTML instead of JSON) while querying an external parts registry.
A Design Rule Check (DRC) error indicating that the distance between a PCB trace and a via is less than the required minimum clearance.