Unable to get intrinsic transistor current idi in keysight ads using Cree Transistor model

[rd_dinesh]

I'm getting the above warning. I feel it was due to this, i was unable to find idi in my dataset.
How to resolve this issue?
Thanks.

 

[BigBoss]

What are exactly you trying to do ? To measure drain current ?

 

[dick_freebird]

I always start my SPICE debug by opening the log file and searching for
the complaint-text or bits of it. From what I see, seems like a results
probe - instance, or command line - has a typo in the what-to-probe.
Don't know how ADS likes to do that, but there's thread to follow in
either the log, the netlist (expanded?) or both.

 

[rd_dinesh]

What are exactly you trying to do ? To measure drain current ?

I came to know that we can directly use the expressions vds and idi to get the intrinsic drain voltage and drain current of the transistor, these are provided by the vendor and they are directly available in the dataset.

--- Updated May 13, 2023 ---

I always start my SPICE debug by opening the log file and searching for
the complaint-text or bits of it. From what I see, seems like a results
probe - instance, or command line - has a typo in the what-to-probe.
Don't know how ADS likes to do that, but there's thread to follow in
either the log, the netlist (expanded?) or both.

didn't get exactly what you are saying.

 

[BigBoss]

I came to know that we can directly use the expressions vds and idi to get the intrinsic drain voltage and drain current of the transistor, these are provided by the vendor and they are directly available in the dataset.

--- Updated May 13, 2023 ---

didn't get exactly what you are saying.

You cannot measure all those intrinsic quantities of an active device. If you use this option " Show Operating Point" with deeper hierarchy , you can see some deeper currents and voltages as text. Not more..

 

[dick_freebird]

What I meant was, find the line where that error-trapped assignment
statement exists, and inspect its syntax and whether that syntax
embodies the actual, proper name of the device and the param of
interest. You know, debug.

Maybe you just forgot some curly braces on an argument line for
the transistor device or model statement, or something. Won't
know until you look, and look close.

Try a more basic simulation like just placing and stimulating the
device, .op, print something you know is legit. Get fancy with
parameters / variables later. There's always a chance that a model
from elsewhere, needs detailed param-name or param-set
massaging. Or that how x1.x2.device[result] wants to be specified,
varies between contol languages (SPICE-compatible-"ish"?).

The complaint to me sorta smells like you tried to put an
expression where a plain argument (constant or param) was
expected, and maybe needed a "value of" form (like ={blah} instead
of =blah . But that's for you to dissect.