analog-canvas (cascode-ai) errors
19 recurring problems engineers report in analog-canvas (cascode-ai), ranked by impact.
#17 by errors trackedECAD
Recurring analog-canvas (cascode-ai) errors, by impact
- 1On Spectre import a library block called without its body came back as a generic subcircuit with pins P1 to Pn, landing a DAC's wires on the wrong nets, and on export the DAC contract names VIN and VOUT while the artwork uses IN and OUT.ECAD · Agent failure · 1 report74
- 2A gate whose cell draws its own ground came back from import as a plain block and lost its label, because the import stripped a pin from every caller too early.ECAD · Agent failure · 1 report66
- 3A netlist round trip dropped a source's unprinted waveform settings and an op-amp's rail values because the SPICE card does not print them.ECAD · Agent failure · 1 report66
- 4A part the author never named came back from a netlist round trip named X1 with an extra record for its printed card.ECAD · Agent failure · 1 report66
- 5A schematic editor's part colours did not survive a round trip through its netlist format because the format could not carry a style; background paint still is not exported.ECAD · Agent failure · 1 report66
- 6After a round trip through the RNL format, diodes pointed at an undefined DIODE model and ngspice stopped, because the editor's own exported stand-in card was mistaken for the author's model and suppressed itself; NMOS/PMOS and NPN/PNP had the same bug.ECAD · Agent failure · 1 report66
- 7Drawing an op-amp supply pin whose net was already set in Properties showed a bare pin that the netlist still joins, and that is now refused until the net goes back to Auto.ECAD · Agent failure · 1 report66
- 8Imported drawings could join terminals the netlist keeps on separate nets, then either passed electrical comparison and threw at display time or arrived as a project the editor refused to save, while the import looked fine both ways.ECAD · Agent failure · 1 report66
- 9Importing a netlist back into the schematic editor dropped the entire GND rail of a two-stage op amp (9 wires and 6 junctions) because the format reads GND as ground while the editor kept it as a net with that name; varactors, tunable resistors and BJTs came back as plain parts because pin names did not match (1/2 vs P1/P2).ECAD · Agent failure · 1 report66
- 10Importing RNL files, the printed netlist gained a second ground pin, GND beside VSS, that the file never had; five circuits were refused or imported with a changed netlist.ECAD · Agent failure · 1 report66
- 11More netlist round-trip loss: power labels came back as plain pins placed away from the circuit so rails drew thin, and cells gained ground pins their drawings never had because the export adds them and the import kept them.ECAD · Agent failure · 1 report66
- 12Netlist import used to fail outright or drop the whole drawing over small things like a name over 128 characters, and an unknown typesetting value silently reset to default.ECAD · Agent failure · 1 report66
- 13Netlist round trips dropped SPICE expressions and parameters, including a flat deck's .param lost on import.ECAD · Agent failure · 1 report66
- 14Reading a netlist back added VDD/VSS pins to cells whose drawing never had them, because the netlist ties gate rails itself.ECAD · Agent failure · 1 report66
- 15The import guard only kept a drawing when the drawn circuit matched the plain SPICE import of the same files, but for three circuits the plain import misreads the file, so good drawings were refused.ECAD · Agent failure · 1 report66
- 16The Spectre netlist printed values the way SPICE reads them, but 100fF and 1MegΩ are not valid Spectre, and 1M means milli in SPICE but mega in Spectre: the same number a billion times off depending on which simulator reads it.ECAD · Agent failure · 1 report66
- 17The SPICE/RNL export printed only cells reachable from the top, so any cell nothing calls lost its drawing on the round trip.ECAD · Agent failure · 1 report66
- 18Redrawing 1,355 analog circuits through an agent CLI, about 50 drawing reports said a figure's net name had to be changed because SPICE cannot hold a comma, so VEA,OUT became VEAOUT on the drawing, and the ask is a display alias so the drawing shows what the figure shows and the netlist keeps a legal name.ECAD · Agent failure · 1 report58
- 19SPICE prints a bracketed pin as SEL3_ and the import named pins by the printed port, so bracketed pin names came back wrong after a round trip, the third round-trip fix in this series.ECAD · Agent failure · 1 report58
How it fails
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.