In this Topic Hide
Safe Operating Area (SOA) is not a separate analysis mode, but a feature that can be enabled with DC or Transient analyses. With SOA testing, you can set maximum and minimum limits for any simulation quantity and the simulator will display when those limits are violated.
To use SOA testing, you must do two things:
Three schematic symbols are provided that allow the definition of simple limit tests that report the following:
Each of these symbols can be edited in the usual way. Each has three parameters that specify
Run the simulation in the normal way. If there are any violations, the results will be reported in the location or locations specified in the Results to: section.
The simulator control .SETSOA allows much more sophisticated definitions for SOA limits. In particular, you can define limits for all devices belonging to a specified model. Suppose that you are using a BJT model that has a Vcb limit of 15V. While you could place a differential voltage watch device across each instance of this model, this would be time consuming and error prone. Instead, you can define a single .SETSOA control that refers to the model name of the device. The simulator will then automatically set up the limit test for every instance of that model.
You would usually enter a .SETSOA control in the schematic editor's F11 window. See Manual Entry of Simulator Commands for details. Refer to Simulator Reference Manual/Command Reference/.SETSOA for details about .SETSOA .
It is also possible to set up an SOA specification for a model within the .MODEL control. Again, see Simulator Reference Manual/Command Reference/.MODEL.
|