eldo_user

Specifying Simulation Output
Plotting Safe Operating Area Limits
This will probe/plot all .SETSOA commands related to device name device.
• SOA output quantity for SOA identifier:
.probe|.plot SOA(full_name)
This will probe/plot a specific .SETSOA command as soon as full_name is a valid fully
qualified .SETSOA identifier. The default naming rule for a fully qualified identifier is:
where:
o
o
o
##
device is the device name when the SOA applies to a device.
FileName is the name of the netlist file containing the SOA.
Line is the line number of the SOA in the associated netlist file.
For example:
.probe tran SOA(XM7.M1#test.cir#13)
This will probe the .SETSOA command in line 13 of netlist file test.cir for device M1
inside instance XM7.
To change the format of the identifier, see “Modifying the SOA Identifier Format” on
page 344.
The PROBE keyword of the .CHECKSOA command can be used to save all output quantities
(waveforms) specified in .SETSOA commands, but it does not create SOA assertion buses.
EZwave displays SOA violations as an assertion bus that contains the simulated waveform(s),
related to the .SETSOA statements, upon which they rely.
Table 8-4 summarizes the graphic elements for SOA limits used in the EZwave graph window:
Table 8-4. Graphic Elements for SOA Limits
Graphic Element Cursor Label Meaning
Blue line inactive SOA is inactive
Green line active SOA is active
Red line fail SOA failed
Green triangle active_pass SOA passed
Red triangle with horizontal red
line below
Inverted red triangle with
horizontal red line above
fail_failDown
fail_failUp
SOA failed, crossed the lower
boundary
SOA failed, crossed the upper
boundary
342
Eldo® User's Manual, 15.3