|
|
In this Topic Hide
| .TRACE vector_name [vector_name ...] graph_id |
Set up a trace. This is graph plot that is updated as the simulation runs.
Where
| vector_name | is the name of a net or pin |
| graph_id | is an integer between 1 and 999 to specify which graphs traces should use - see explanation below |
graph_id is an arbitrary number that makes it possible to direct traces to different graphs. Two traces with the same id will be always be put in the same graph. Traces from subsequent simulations with that id will also go to that graph if it still exists otherwise a new one will be created. To force two traces to go to separate graphs, use different id's. Note that it doesn't matter what the id's value actually is - it could be 1 or 100 - as long as traces that must go to the same graph use the same value.
Note that the AutoAxis feature available for normal plotting also works for Traces. So if a current and voltage trace are both directed to the same graph, separate axes will be created for them.
| .trace v1_p 1 q1#c 1 |
In the above example a voltage - v1_p - and a current - q1#c - will both be traced on the same graph. As they have different units, the AutoAxis feature will force the curves to two different y axes.
| .trace v1_p 1 q1#c 2 |
In this example the voltage and current traces will be directed to different graph sheets.
The .TRACE statement has now been largely superseded by the .GRAPH statement (see .GRAPH), which is much more flexible. However, the .TRACE statement is still useful for specifying multiple traces on a single line. .GRAPH can only specify one signal at a time.
|