10.06.2016 Views

eldo_user

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Simulator Compatibility<br />

Hybrid Compat Mode<br />

My netlist<br />

.compat<br />

.subckt fooh 1<br />

r1 1 0 '-1.0*sqrt(-4)' $ comment<br />

i1 1 0 1m<br />

.ends<br />

.endcompat<br />

.subckt foo 1<br />

r1 1 0 'sqrt(4.0)' ! comm<br />

i1 1 0 1m<br />

.ends<br />

x1 1 foo<br />

x2 2 fooh<br />

.op<br />

.extract dc v(1)<br />

.extract dc v(2)<br />

.end<br />

In this example, the subcircuit fooh is run in compatibility mode. The remainder of the circuit is<br />

run in native Eldo mode.<br />

Files that are included with .LIB or .INCLUDE between .COMPAT and .ENDCOMPAT are<br />

handled in compat mode. In the following example, the content of the included files, file2 and<br />

file3, are handled in compat mode:<br />

.compat<br />

.include file2<br />

.lib file3 TT<br />

.endcompat<br />

You can use hybrid compat mode (.COMPAT/.ENDCOMPAT blocks) together with -<br />

compmod or -compnet arguments (or equivalent options). Locally inside the block the<br />

compatibility mode applies to both models and syntax, and outside the block it applies only to<br />

models or syntax respectively.<br />

Note<br />

If hybrid compat mode (.COMPAT/.ENDCOMPAT blocks) is used together with the -<br />

compat argument (or equivalent option) Eldo outputs a warning notifying that the<br />

.COMPAT command has been specified even though compat mode is already enabled.<br />

Limitations<br />

• The commands .COMPAT and .ENDCOMPAT can not be specified inside .ALTER<br />

sections.<br />

• In compat mode, analyses are run in the sequence they are listed in the .cir file. However<br />

this is not the case for analysis commands inside .COMPAT/.ENDCOMPAT blocks.<br />

For example:<br />

.tran 1n 10n<br />

.tran 1n 20n<br />

Eldo® User's Manual, 15.3 163

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!