LTwiki-Wiki for LTspice - User contributions [en]

Talk:Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-10T00:05:41Z

115.128.26.31: Created page with ' Can somebody move the text to article ".Param and Curly Brackets" into a folded sub page of text to allow for multiple linked entries Dont know how to created a linked page y…'

Can somebody move the text to article ".Param and Curly Brackets"
into a folded sub page of text to allow for multiple linked entries

Dont know how to created a linked page yet

Thanks

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-10T00:03:31Z

115.128.26.31:

Add items as subpages (rather than details at this page level)

== .Param and Curly Brackets ==
.param

One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ?

Beginning with the simplest definition, LT doesn't require curly brackets

.param res1 = 1000

This could be used to define a resistor of 1000 Ohms

However, in the real world, a parameter sometimes needs to be defined from other parameters.

To get results and not pull errors within LT, it becomes useful to use curly brackets.
Without them - you can only nest (calculated) .param values, one parameter calculation deep.

Going any deeper (where one calculation depends on another etc) will invite LTspice to complain with an error.

'''Correct Method { doesn't pull errors }'''

<nowiki>
*</nowiki> Comment line : Calculate capacitance

<nowiki>*</nowiki> -------------------------------------

.param length = {3e-2}

.param width = {4e-3}

.param area = {length * width}

.param gap = {40e-6}

.param Eo = {8.85e-12}

.param Capa = { (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

The answer (from the error log ) is:
capa_: capa=2.95e-012

To see the results in LTspice
Use the Error Log (a better name would have been the results log)

'''Incorrect method (pulls errors)'''

.param length = 3e-2

.param width = 4e-3

.param area = length * width

.param gap = 40e-6

.param Eo = 8.85e-12

.param Cap = (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

Error:
Warning Can't resolve .param cap=(eo * gap)area)

The quickest way to check a calculation before you commit it to a library
is to create a section of text within the LT schematic.
Set the text as LTspice directive (command) ,
then run the schematic

'''Finding the measure results of a simulation'''
Check your results in the error log
Found from the toolbar :
View/Spice error Log

'''Suggestion:'''
Set the Tools/Control panel/ Operation / Generate Expanded Listing
and tick (yes) to see a more comprehensive output listing - helps with debugging

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-10T00:03:08Z

115.128.26.31:

Add items as subpages (rather than details at this page level)

== .Param and Curly Brackets ==
.param

One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ?

Beginning with the simplest definition, LT doesn't require curly brackets

.param res1 = 1000

This could be used to define a resistor of 1000 Ohms

However, in the real world, a parameter sometimes needs to be defined from other parameters.

To get results and not pull errors within LT, it becomes useful to use curly brackets.
Without them - you can only nest (calculated) .param values, one parameter calculation deep.

Going any deeper (where one calculation depends on another etc) will invite LTspice to complain with an error.

'''Correct Method { doesn't pull errors }'''

<nowiki>
*</nowiki> Comment line : Calculate capacitance

<nowiki>*</nowiki> -------------------------------------
.param length = {3e-2}

.param width = {4e-3}

.param area = {length * width}

.param gap = {40e-6}

.param Eo = {8.85e-12}

.param Capa = { (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

The answer (from the error log ) is:
capa_: capa=2.95e-012

To see the results in LTspice
Use the Error Log (a better name would have been the results log)

'''Incorrect method (pulls errors)'''

.param length = 3e-2

.param width = 4e-3

.param area = length * width

.param gap = 40e-6

.param Eo = 8.85e-12

.param Cap = (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

Error:
Warning Can't resolve .param cap=(eo * gap)area)

The quickest way to check a calculation before you commit it to a library
is to create a section of text within the LT schematic.
Set the text as LTspice directive (command) ,
then run the schematic

'''Finding the measure results of a simulation'''
Check your results in the error log
Found from the toolbar :
View/Spice error Log

'''Suggestion:'''
Set the Tools/Control panel/ Operation / Generate Expanded Listing
and tick (yes) to see a more comprehensive output listing - helps with debugging

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-10T00:02:46Z

115.128.26.31:

Add items as subpages (rather than details at this page level)

== .Param and Curly Brackets ==
.param

One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ?

Beginning with the simplest definition, LT doesn't require curly brackets

.param res1 = 1000

This could be used to define a resistor of 1000 Ohms

However, in the real world, a parameter sometimes needs to be defined from other parameters.

To get results and not pull errors within LT, it becomes useful to use curly brackets.
Without them - you can only nest (calculated) .param values, one parameter calculation deep.

Going any deeper (where one calculation depends on another etc) will invite LTspice to complain with an error.

'''Correct Method { doesn't pull errors }'''

<nowiki>
*</nowiki> Comment line : Calculate capacitance
<nowiki>*</nowiki> -------------------------------------
.param length = {3e-2}

.param width = {4e-3}

.param area = {length * width}

.param gap = {40e-6}

.param Eo = {8.85e-12}

.param Capa = { (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

The answer (from the error log ) is:
capa_: capa=2.95e-012

To see the results in LTspice
Use the Error Log (a better name would have been the results log)

'''Incorrect method (pulls errors)'''

.param length = 3e-2

.param width = 4e-3

.param area = length * width

.param gap = 40e-6

.param Eo = 8.85e-12

.param Cap = (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

Error:
Warning Can't resolve .param cap=(eo * gap)area)

The quickest way to check a calculation before you commit it to a library
is to create a section of text within the LT schematic.
Set the text as LTspice directive (command) ,
then run the schematic

'''Finding the measure results of a simulation'''
Check your results in the error log
Found from the toolbar :
View/Spice error Log

'''Suggestion:'''
Set the Tools/Control panel/ Operation / Generate Expanded Listing
and tick (yes) to see a more comprehensive output listing - helps with debugging

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-10T00:00:53Z

115.128.26.31:

Add items as subpages (rather than details at this page level)

== .Param and Curly Brackets ==
.param

One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ?

Beginning with the simplest definition, LT doesn't require curly brackets

.param res1 = 1000

This could be used to define a resistor of 1000 Ohms

However, in the real world, a parameter sometimes needs to be defined from other parameters.

To get results and not pull errors within LT, it becomes useful to use curly brackets.
Without them - you can only nest (calculated) .param values, one parameter calculation deep.

Going any deeper (where one calculation depends on another etc) will invite LTspice to complain with an error.

'''Correct Method { doesn't pull errors }'''

** Comment line : Calculate capacitance
** -------------------------------------
.param length = {3e-2}

.param width = {4e-3}

.param area = {length * width}

.param gap = {40e-6}

.param Eo = {8.85e-12}

.param Capa = { (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

The answer (from the error log ) is:
capa_: capa=2.95e-012

To see the results in LTspice
Use the Error Log (a better name would have been the results log)

'''Incorrect method (pulls errors)'''

.param length = 3e-2

.param width = 4e-3

.param area = length * width

.param gap = 40e-6

.param Eo = 8.85e-12

.param Cap = (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

Error:
Warning Can't resolve .param cap=(eo * gap)area)

The quickest way to check a calculation before you commit it to a library
is to create a section of text within the LT schematic.
Set the text as LTspice directive (command) ,
then run the schematic

'''Finding the measure results of a simulation'''
Check your results in the error log
Found from the toolbar :
View/Spice error Log

'''Suggestion:'''
Set the Tools/Control panel/ Operation / Generate Expanded Listing
and tick (yes) to see a more comprehensive output listing - helps with debugging

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-10T00:00:18Z

115.128.26.31:

Add items as subpages (rather than details at this page level)

== .Param and Curly Brackets ==
.param

One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ?

Beginning with the simplest definition, LT doesn't require curly brackets

.param res1 = 1000

This could be used to define a resistor of 1000 Ohms

However, in the real world, a parameter sometimes needs to be defined from other parameters.

To get results and not pull errors within LT, it becomes useful to use curly brackets.
Without them - you can only nest (calculated) .param values, one parameter calculation deep.

Going any deeper (where one calculation depends on another etc) will invite LTspice to complain with an error.

'''Correct Method { doesn't pull errors }'''

* Comment line : Calculate capacitance
* -------------------------------------
.param length = {3e-2}

.param width = {4e-3}

.param area = {length * width}

.param gap = {40e-6}

.param Eo = {8.85e-12}

.param Capa = { (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

The answer (from the error log ) is:
capa_: capa=2.95e-012

To see the results in LTspice
Use the Error Log (a better name would have been the results log)

'''Incorrect method (pulls errors)'''

.param length = 3e-2

.param width = 4e-3

.param area = length * width

.param gap = 40e-6

.param Eo = 8.85e-12

.param Cap = (Eo * gap) / area}

.MEAS Capa_ PARAM Capa

Error:
Warning Can't resolve .param cap=(eo * gap)area)

The quickest way to check a calculation before you commit it to a library
is to create a section of text within the LT schematic.
Set the text as LTspice directive (command) ,
then run the schematic

'''Finding the measure results of a simulation'''
Check your results in the error log
Found from the toolbar :
View/Spice error Log

'''Suggestion:'''
Set the Tools/Control panel/ Operation / Generate Expanded Listing
and tick (yes) to see a more comprehensive output listing - helps with debugging

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-09T23:39:54Z

115.128.26.31:

Add items as subpages (rather than details at this page level)

== .Param and Curly Brackets ==
.param

One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ?

Beginning with the simplest definition, LT doesn't require curly brackets

.param res1 = 1000

This could be used to define a resistor of 1000 Ohms

However, in the real world, a parameter sometimes needs to be defined from other parameters.

To get results and not pull errors within LT, it becomes useful to use curly brackets.
Without them - you can only nest (calculated) .param values, one parameter calculation deep.

Going any deeper (where one calculation depends on another etc) will invite LTspice to complain with an error.

'''Correct Method { doesn't pull errors }'''

* Comment line : Calculate capacitance
* -------------------------------------
.param length = {3e-2}
.param width = {4e-3}
.param area = {length * width}
.param gap = {40e-6}
.param Eo = {8.85e-12}
.param Capa = { (Eo * gap) / area}
.MEAS Capa_ PARAM Capa

The answer (from the error log ) is:
capa_: capa=2.95e-012

To see the results in LTspice
Use the Error Log (a better name would have been the results log)

'''Incorrect method (pulls errors)'''

.param length = 3e-2
.param width = 4e-3
.param area = length * width
.param gap = 40e-6
.param Eo = 8.85e-12
.param Cap = (Eo * gap) / area}
.MEAS Capa_ PARAM Capa

Error:
Warning Can't resolve .param cap=(eo * gap)area)

The quickest way to check a calculation before you commit it to a library
is to create a section of text within the LT schematic.
Set the text as LTspice directive (command) ,
then run the schematic

'''Finding the measure results of a simulation'''
Check your results in the error log
Found from the toolbar :
View/Spice error Log

'''Suggestion:'''
Set the Tools/Control panel/ Operation / Generate Expanded Listing
and tick (yes) to see a more comprehensive output listing - helps with debugging

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-09T23:38:52Z

115.128.26.31:

Add items as subpages (rather than details at this page level)

== .Param and Curly Brackets ==

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-09T23:37:30Z

115.128.26.31:

Add items as subpages (rather than details at this page level)

[.Param and Curly Brackets {} ]

Hints on using individual LTspice commands and things the Help Manual sometimes may not help you with

2009-08-09T23:37:11Z

115.128.26.31: Created page with ' Add items as subpages (rather than details at this page level) .Param and Curly Brackets {} '

Add items as subpages (rather than details at this page level)

[[.Param and Curly Brackets {} ]]

Main Page

2009-08-09T23:34:28Z

115.128.26.31:

<big>'''Welcome to LT Wiki!'''</big>

Please use this wiki to create helpful topics related to LTspice. For complete information about LTspice, please join the Yahoo group at [http://tech.groups.yahoo.com/group/LTspice/]. They are a great user group with a vast amount of helpful files and useful tips.

[[Most frequently asked questions for beginners]]

[[B sources (complete reference)]]

[[B sources (common examples)]]

[[Convergence problems?]]

[[SPICE and LTspice Courseware and Tutorials]]

[[LTspice Hot Keys]]

[[Adding a permanent component to LTspice]]

[[Hints on using individual LTSpice commands and the things the Help Manuals sometimes may not help you with]]

Hints on using individual LTSpice commands and the things the Help Manuals don't tell you about

2009-08-09T23:33:31Z

115.128.26.31:

.param

One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ?

Beginning with the simplest definition, LT doesn't require curly brackets

.param res1 = 1000

This could be used to define a resistor of 1000 Ohms

However, in the real world, a parameter sometimes needs to be defined from other parameters.

To get results and not pull errors within LT, it becomes useful to use curly brackets.
Without them - you can only nest (calculated) .param values, one parameter calculation deep.

Going any deeper (where one calculation depends on another etc) will invite LTspice to complain with an error.

'''Correct Method { doesn't pull errors }'''

* Comment line : Calculate capacitance
* -------------------------------------
.param length = {3e-2}
.param width = {4e-3}
.param area = {length * width}
.param gap = {40e-6}
.param Eo = {8.85e-12}
.param Capa = { (Eo * gap) / area}
.MEAS Capa_ PARAM Capa

The answer (from the error log ) is:
capa_: capa=2.95e-012

To see the results in LTspice
Use the Error Log (a better name would have been the results log)

'''Incorrect method (pulls errors)'''

.param length = 3e-2
.param width = 4e-3
.param area = length * width
.param gap = 40e-6
.param Eo = 8.85e-12
.param Cap = (Eo * gap) / area}
.MEAS Capa_ PARAM Capa

Error:
Warning Can't resolve .param cap=(eo * gap)area)

The quickest way to check a calculation before you commit it to a library
is to create a section of text within the LT schematic.
Set the text as LTspice directive (command) ,
then run the schematic

'''Finding the measure results of a simulation'''
Check your results in the error log
Found from the toolbar :
View/Spice error Log

'''Suggestion:'''
Set the Tools/Control panel/ Operation / Generate Expanded Listing
and tick (yes) to see a more comprehensive output listing - helps with debugging

Hints on using individual LTSpice commands and the things the Help Manuals don't tell you about

2009-08-09T23:29:12Z

115.128.26.31: Created page with '.param One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ? The simplest definition doesn't …'

.param

One of the more confusing aspects of using .param (at least when I began using LT) was where and when do you use the curly barckets {} ?

The simplest definition doesn't require curly brackets

.param res1 = 1000

Which could be used to define a resistor of 1000 Ohms

But sometimes a parameter needs to be defined from other parameters,

Here it becomes more accurate to use curly brackets.
Without the curly brackets - you can only nest (calculated) param valaues 1 deep
Going any deeper (one calculation depnds on another etc) LT will pull errors

'''Correct Method { doesn't pull errors }'''

* Comment line : Calculate capacitance
* -------------------------------------
.param length = {3e-2}
.param width = {4e-3}
.param area = {length * width}
.param gap = {40e-6}
.param Eo = {8.85e-12}
.param Capa = { (Eo * gap) / area}
.MEAS Capa_ PARAM Capa

The answer (from the error log ) is:
capa_: capa=2.95e-012

To see the results in LTspice
Use the Error Log (a better name would have been the results log)

'''Incorrect method (pulls errors)'''

.param length = 3e-2
.param width = 4e-3
.param area = length * width
.param gap = 40e-6
.param Eo = 8.85e-12
.param Cap = (Eo * gap) / area}
.MEAS Capa_ PARAM Capa

Error:
Warning Can't resolve .param cap=(eo * gap)area)

The quickest way to check a calculation before you commit it to a library
is to create a section of text within the LT schematic.
Set the text as LTspice directive (command) ,
then run the schematic

'''Finding the measure results of a simulation'''
Check your results in the error log
Found from the toolbar :
View/Spice error Log

'''Suggestion:'''
Set the Tools/Control panel/ Operation / Generate Expanded Listing
and tick (yes) to see a more comprehensive output listing - helps with debugging

Main Page

2009-08-09T23:00:30Z

115.128.26.31: