SIMULATION ERRORS
Overview
Simulation errors are generated by PROSPICE rather than by the schematic module, so they occur after a netlist has been successfully generated and its models linked. They are reported under the title SIMULATION ERROR LOG.
Some of them are fatal, meaning the simulation does not run at all. Others are warnings, and the run continues with whatever the simulator could make of the circuit. The severity indicator alongside each message in the log tells you which you are looking at, and it is worth checking, because a warning early in the log is often the real explanation for an odd result later on.
Analogue Simulation Errors
Device Type Not Recognized
The message is fatal, and the simulation stops at once:
<part> - device type '<type>' not recognized!
Either you have specified a primitive type that is not supported, or a model file has done so. The part named at the front of the message is where to look.
Could Not Find Probe
Could not find probe named <name> in <file>
You have referenced a probe or voltage generator that does not exist. Where a current is wanted, remember that you must use an IPROBE object, which is in SYSTEM.LIB, and that you cannot reference a current probe gadget. For interactive simulation the equivalent object is RTIPROBE, in REALTIME.LIB.
Cannot Open SPICE Source File
This one is a warning rather than an error, and it is written in lower case:
cannot open SPICE source file <file>
The source file named in a SPICEMODEL or SPICEFILE property could not be located. It should be in the design's own folder, or in one of the folders listed under System > System Settings in the field User Simulation Model and Module Folders. Check the extension as well as the name: if you leave the extension off, .MOD is assumed.
Cannot Find Library Model
Cannot find library model '<name>'
The subcircuit or model you have specified does not exist in the library you named. Note that this message is reported on the SPICE model linkage diagnostic channel, so it does not appear at all if you have turned that channel off. See Controlling What the Log Records.
Model DLL Not Found
The message is fatal, and it carries a Windows error code:
External model DLL "<file>" not found. GLE=0x<code>.
The specified VSM model DLL could not be loaded. It should be in the design's own folder or in one of the folders listed under System > System Settings in the field User Simulation Model and Module Folders.
The value after GLE= is the Windows error code returned when the load was attempted, and it is worth reading rather than ignoring. A file that is genuinely absent gives a different code from one that is present but cannot be loaded, and the second case is the more common of the two: it usually means the DLL itself depends on something that is missing, or that it was built for the wrong architecture.
A related warning, Batch mode model creation function(s) not found in <file>., means the DLL loaded but does not export the entry points needed for a graph based run.
No DC Path to Ground
Net <net> has no DC path to ground.
One message is produced for each affected net, and the net name inside it is a link: click it to jump to that net on the schematic. The message is reported on the DC path analysis diagnostic channel.
If part of your circuit is not grounded, the simulator cannot resolve its voltage relative to ground, and it is as simple as that. Nodal analysis works out every voltage with respect to a reference node, so a section of circuit with no conducting route back to that reference has no defined answer.
This is discussed further under Ground and Power Rails.
Digital Simulation Errors
The digital simulator reports one failure family of its own: contention, where a net is driven to conflicting states by two or more outputs at the same time. Three messages cover it.
These messages are reported on the Digital logic contentions diagnostic channel. At the default level only the first contention on any given net is reported, so one message does not mean it happened once. Raising that channel to Full Trace instead reports every state the net passes through, as Contention state <state> on net <net>., which is what you want when you need to know exactly when the conflict starts and stops.
The net name in every one of these messages is a link, so the fastest route to the cause is to click it and look at what is driving the net.
Contention, the strengths that produce it and the states a digital net can take are described under The Digital Simulation Paradigm.
Mixed Mode Errors
Where analogue and digital parts share a net, each net is first classified as analogue, digital or both, and interface models are inserted at the boundaries. Problems in that process produce the messages below. Most of them are reported on the Mixed mode net type analysis and Mixed mode interface models diagnostic channels, so they appear only when those channels are set to Full Trace.
See Mixed Mode Interface Models (ITFMOD).
Script Model Errors
Scriptable generators and script models are compiled before the simulation starts, and a script that will not compile reports its own family of messages naming the line and the construct at fault.
See Also: