The stop command will add a breakpoint to the debug list.
stop [before | at | after num] [when expr1 op expr2] ...When the condition is true, simulation will stop, and can be resumed, after clearing the breakpoint, with the resume command. The breakpoints can be cleared with the delete command, and listed with the status command. The panel brought up by the Trace button in the Tools menu can also be used to manipulate breakpoints.
The first clause specifies the user output points at which the break is in effect. If an after clause is given, the simulation will stop after num points. The at clause stops only at num points, and the before clause stops only before num points. These are useful in conjunction with a when clause or can be omitted. If a when clause is included, at each point, the expr1,2 expressions will be evaluated and expr1 op expr2 will be checked, and if it is true, the simulation will stop. If more than one when or after clause is put on one line, the conjunction of the conditions is checked. The ops are relational operators from the list below. Note that for this command, < and > do not denote IO redirection.
|eq or =||equal to|
|ne or < >||not equal to|
|gt or >||greater than|
|lt or <||less than|
|ge or > =||greater than or equal to|
|le or < =||less than or equal to|
If a stop command is given at the prompt in interactive mode, it is placed in a global list, and activity will persist until deleted (with the delete command). If the command is given in a file, the command will be added to a list for the current circuit, and will apply only to that circuit. Thus, for example, a WRspice file can contain lines like
*# stop when ...and the action will be performed as that circuit is run, but the ``stop when ...'' directive will not apply to other circuits.