Circuit Mind’s AVE takes schematic review beyond connection checks
Illustrative image: Mikhail Nilov on Pexels
Circuit Mind has introduced AVE to review schematics against component datasheets, application notes and company rules. It extends automated checking into operating requirements that can be violated even when every net is connected correctly.
The company says AVE can examine existing ECAD schematics as well as designs produced through its own platform. Multiple agents investigate potential issues, with a quality check before findings reach the user. Its platform documentation describes results linked to the affected component, connection and supporting source.
A conventional electrical rules check can flag an unconnected pin or a conflict between declared pin types. A device may still be connected correctly and driven outside its permitted conditions during startup, shutdown or a particular operating mode. Reviewing that requires information about how the circuit will be used as well as how it is wired.
A powered interface can fail during shutdown
Take an interface between two independently switched power domains. During normal operation, the signal levels and supply voltages can be compatible. Turn one domain off while the other continues driving and the receiving input is now being exercised under a different set of conditions. Whether that is permitted depends on the parts, their input structures and the specified limits.
An automated reviewer would need to know which supply disappears first and whether the driver remains active, then examine the protection or isolation in the circuit. Retrieving an absolute maximum table would supply only part of the evidence. This is an illustrative review case, not a reported AVE test result.
Datasheet requirements can also vary with mode, package and temperature, with a qualifying condition given elsewhere in the document. Dropping that condition while retaining the number produces a plausible finding that may be wrong for the circuit being reviewed.
Linking the result to the source allows the reviewer to examine that reasoning. The relevant limit and its conditions need to be visible together; otherwise a confident explanation can be surprisingly difficult to challenge.
What did the review cover?
Circuit Mind’s quality checking stage is intended to reduce weak findings. Assessing the system also requires a way to examine missed faults. Few false alarms would be encouraging, but they would not establish whether the system had checked a particular failure mode at all.
The review record needs to identify the documents and rules applied. A revised datasheet may change a limit; a field failure may prompt a new company rule. Two reviews of the same schematic could then reach different conclusions for reasons unrelated to the design itself.
Keeping the document revision and circuit assumption with each finding would make later changes easier to investigate. A component substitution or altered power sequence could trigger a review of the affected checks, rather than leaving someone to reconstruct why the original design had passed.
