Tips for Saber Users in the Simulation of Power Electronic Circuits
我喜欢玩音乐游戏英语作文
我喜欢玩音乐游戏英语作文As a music lover, I have always enjoyed playing music games. It's a fun way to combine my love for music with my passion for gaming. Music games have become increasingly popular over the years, and there are now a wide variety of games available for all types of music lovers.One of my favorite music games is Guitar Hero. This game allows players to simulate playing a guitar by using a plastic guitar-shaped controller. The game features a variety of popular songs, and players must hit the correct notes at the right time to score points. I love the feeling of pretending to be a rockstar, and the challenge ofhitting the notes correctly keeps me engaged.Another music game that I enjoy playing is Dance Dance Revolution. This game requires players to step on different arrows on a dance pad in time with the music. It's a great way to get some exercise while having fun and listening to music. I always feel energized and happy after a round ofDDR.Recently, I've also been playing a lot of Beat Saber. This game is played with virtual reality headsets and controllers, and requires players to slash through blocksin time with the music. It's a unique and immersive experience, and I love how it combines music with technology.Playing music games has not only been a fun pastime for me, but it has also helped me improve my musical abilities. By playing Guitar Hero, I've become more familiar with guitar chords and rhythms. And by playing DDR, I've become more coordinated and aware of my body movements. Music games have also introduced me to new genres of music and artists that I may not have discovered otherwise.In conclusion, music games are a great way to combine two passions music and gaming. They are fun, engaging, and can even help improve musical abilities. Whether you prefer guitar simulation games, dance games, or virtual reality experiences, there is a music game out there for everyone.。
基于BUCK电路的新型软开关电路设计
工业技术DOI：10.16660/ki.1674-098X.2019.13.128基于BUCK电路的新型软开关电路设计周浩文 李迁(上海电机学院 上海 201306)摘 要：本文对采用N沟道增强型MOSFET作开关器件的Buck电路进行了软开关的设计和仿真。
用到的方案是准谐振充放电模式，使MOSFET漏源极两端的电压能在栅极触发脉冲到来前变为零，使开关管能进行零电压开通。
这样就能有效地实现Buck电路的软开关，提高电路的效率。
最后利用Saber仿真软件，对设计的软开关控制策略进行了仿真验证，结果与预期相符合。
关键词：降压变换器 软开关 Saber仿真中图分类号：TM46 文献标识码：A 文章编号：1674-098X(2019)05(a)-0128-07Abstract: This article presents a soft switching method of the Buck converter which uses the N channel enhancement type MOSFET as the switch and the simulation. The design is quasi resonant charging and discharging mode which makes the D-S voltage become zero before the gate trigger pulse come, so the MOSFET can operate in a zero voltage turn-on mode. In this way, it can effectively realize the soft switching of Buck converter and improve the efficiency of the circuit. Finally I use the saber software to do the simulation and receive the expected result.Key Words：Buck converter; Soft switching; Saber simulatio1 引言1.1 研究背景自从软开关技术出现之后，经历了发展期和完善期，软开关电路也是层出不穷，迄今为止，各式各样的软开关拓扑仍不断涌现[1]。
saber仿真软件tdsa模块使用说明
tdsa tdsa (MX-Scan)Associated Symbols:tdsaLicense Requirements:MODEL_SYNTHESISPart Category:Analog Model Synthesis Templates Related Topics:Analog Model Synthesis Overview Functional DescriptionThe tdsa template uses sine wave stimulus techniques to obtain phase and gain information for a large-signal circuit. You connect the output as a source for the design under test, and the input to the output of the design. When you run a transient analysis, tdsa simulates the design, measures its output, and calculates phase and gain information, which it stores in a plot file. It also offers an optional bandpass input filter, and includes a source for a standard AC analysis.Template Description SectionsConnection PointsSymbol PropertiesPost-Processing InformationModel DescriptionUsage NotesExampletdsa Connection PointsName Type Descriptionoutp electrical positive output of sinusoidal source outm electrical negative output of sinusoidal source inp electrical positive input for measurements inm electrical negative input for measurements enbl logic_4enable input for frequency sweepMX Scan (tdsa)tdsa tdsa Symbol PropertiesPropertyprimitive Description:This symbol calls the templatetdsa. The template will create anAC or complex plot file for thecircuit under test during atransient analysis. This is notmeant to replace the standard ACanalysis, but to allow AC resultsto be obtained for circuits thatwill not work with the standardAC analysis. An example isswitching circuits.WARNING! Since a template andnot the simulator creates the plotfile, analyses with looping (suchas vary and mc) will not functionas expected. Only the AC dataobtained from the last loop will bein the plot file created by the tdsatemplate.ref Description:Suffix appended to a templatename that uniquely identifies apart in a schematic.Default: If not specified will be assignedby Schematic Capture ToolExampleCan be any alpha-numeric stringInput:fbegin Description:Starting frequency value for thefrequency sweep. A value isrequired and it must be > 0.Default (units):value required (Hz)ExampleInput:100fend Description:Ending frequency value for thefrequency sweep. A value isrequired and it must be > 0.Default (units):value required (Hz)ExampleInput:10kpfile Description:Name of the plot file created bytdsa template. File identifier(suffix) identifying AC plot fileshowing the frequency responsedetermined by tdsa.Default(units):ac_tdsaExample Input: Can be any alpha-numeric string in quotes. ac_1 Plot file generated: design.ac_1Propertytdsa ampl Description:Peak amplitude of output sinewave relative to DC offset.Default (units): 100m (V)ExampleInput:200moffset Description:Offset voltage of the outputwaveform.Default (units): 0 (V)ExampleInput:2npoints Description:Number of frequency steps totake during the frequency sweepfrom fbegin to fend. Must be aninteger > 0.Default (units): 100 (—)Example Input: 200Propertymode Description:Type of frequency sweep to beperformed.Default (units):logswp (—)Values:linswp Linear spacing offrequency points. All points areequally spaced from fbegin tofend.logswp Log base 10 spacing offrequency points. All points areequally spaced on a log scale.rlogswp1-log base 10 spacing offrequency points. Distribution ofpoints is weighted toward fendon a log scale.Example Input:logswpPropertytdsa max_err Description:Maximum error allowed forwriting data to the plot file andgoing to the next frequency pointin the sweep. Error is calculatedfor gain and phase and both mustbe less then max_err to continueon to next frequency point. Mustbe > 0.Default (units): 0.01 (—)ExampleInput:0.005max_nper Description:Maximum number of periodsallowed before switching to thenext frequency point, even if theerror is larger then max_err.Data gets written to the plot fileand a warning is sent to thescreen. Must be an integer >= 3.Default (units): 30 (—)Example Input: 40Propertymin_nper Description:Minimum number of periodsrequired before switching to thenext frequency even if the error isless than max_err. Must beinteger >= 3 and < max_nper.Default (units): 3 (—)ExampleInput:4min_tspp Description:Minimum number of time stepstaken during a period. Forcircuits with very little switchingyou need to insure a reasonablenumber of time steps are takenper period. Must be >= 20. Thisaffects the accuracy of the phaseinformation obtained. A largernumber increases the accuracybut can slow down the simulation.Default (units): 40 (—)Example Input: 35Propertytdsa a0 Description:The gain of the input bandpassfilter. Can be positive or negativeif you want to invert the inputsignal.Default (units): 1 (—)ExampleInput:1q0 Description:The quality factor of the inputbandpass filter. A larger valuewill cause longer settling timesand longer simulations. Thequality factor effects thebandwidth of the filter as well asthe settling time.Quality = Center Frequency/BandWidthDefault (units): 10 (—)Example Input: 10Propertyfilter Description:The input signal can be ranthrough a second order bandpassfilter. The gain and qualityfactors are controlled by theparameters a0 and q0. The centerfrequency of the filter changes asthe frequency is swept fromfbegin to fend. For circuits withswitching and/or Non-linearcomponents the prefilter shouldbe used to filter out unwantedharmonics. If the circuit undertest already has filtering then useof the input filter is optional.Default (units): yes (—)Values: yes(Filter the input signal)no(Do not Filter the input signal)Example Input: noPropertyac Description:Specify parameters for a standardAC analysis.Default (units): [mag=1,phase=0] (V, degrees)ExampleInput:1,0enbl_init Description:Used to internally enable thetdsa. If _1 is specified, then thetdsa will be enabled even thoughthe enable pin is not connected.Other values imply the tdsa isnot enabled. If the enable pin isconnected, then events on thatpin will override the effect of theinternal enable.Default: _1Values:_0 logic 0_1 logic 1_x logic x_z logic zExample Input: _xPropertytdsa Post Processing InformationName Type Units Descriptionvin V input differential voltage (vin =v(inp) - v(inm))vout V output differential voltage (vout =v(outp) - v(outm))gain_err V calculated gain error for the inputsignalphase_err rad calculated phase error for the inputsignalcycle_cnt—number of complete sine waveperiods taken to obtain a gain andphase error less than max_err tdsa_info—grouping of signals (vin, vout,gain_err, phase_err,cycle_cnt)tdsa Model DescriptionThe tdsa template uses sine wave stimulus techniques to obtain phase and gain information for a circuit. Note that output impedance is zero and input impedance is infinite. A sine wave from the output stimulates the circuit under test. The output response from the circuit under test is measured and phase, gain information are calculated.tdsa The on/off input is digital and turns a sweep on or off. Each time on/off goes high a new sweep is started. Keep in mind that any previous sweep data will be deleted. If you want to perform multiple sweeps you need to halt the simulation alter the pfile parameter of the tdsa template and then restart the simulation.To use the template connect the output of our source to the portion of the circuit under test that you want to stimulate. Then connect the input or measurement pins to the output of the circuit under test that you want the AC results for. If you leave the on/off input unconnected the sweep will start at the beginning of the tr analysis. Otherwise the sweep will start when on/off goes high.A set of signals have been grouped together under the name tdsa_info. These can be useful in determining what is actually happening during the tr analysis. Use the extraction command to extract these signals and view them after the tr analysis has completed.tdsa Usage NotesThe tdsa template is useful for performing an AC analysis in cases where the standard analysis techniques do not produce useful information (some examples are switching power supplies, sigma delta A/D converters, and mixed technology systems). The template has a set of output ports for simulating a design and a set of input ports for measuring the response of the design. It also has an enable port (labeled ON/OFF on the symbol) to which you can connect a device to control how and when it is enabled.During a transient (time domain) simulation, the template stimulates the design with a sine wave over a range of frequency points. For each frequency, it measures the output of the design and calculates the phase shift and gain. From the data points generated for all the frequencies it constructs a frequency response, which it writes to a plot file. Normally, good results can be produced for signal attenuation down to -80 dB.By adjusting the max_err, max_nper and min_nper arguments, you can instruct the tdsa template how to determine when and if it has a reliable response from the design and when to move on to the next frequency point. By setting the offset property value to match the steady-state voltage level of the circuit, you can maintain the design’s typical operating conditions while it is being simulated (tdsa detects a measurable response only when the signal from the circuit crosses this threshold value).When you invoke the simulator on a design that includes tdsa, or change the values of the properties of tdsa, it calculates the maximum and estimated TEnd (Time End) for the simulation, and alerts you with a message on the screen. As the simulation run proceeds, status messages tell you how much of the simulation period has elapsed. When you compare this to the “real” time that has elapsed, you can estimate how long it will take your computer to complete the entire simulation run. This is useful information (particularly for switched systems) for simulation runs that can take hours, depending on the switching frequency and the sweep arguments.tdsa Because a template is creating the plot file (rather than the simulator), the analyses with looping (such as “vary” or “Monte Carlo”) do not produce multi-segment signals in the plot file, unlike a plot file generated by the simulator. Only the AC data obtained from the last loop is recorded in the plot file created by tdsa. If you want to perform multiple frequency sweeps during the same simulation session, rename the plot files between sweeps to avoid overwriting the previously-generated one.The tdsa template automatically halts a simulation when the frequency sweep is completed. You can stop a sweep before the last frequency point is reached by using the enbl input (labeled ON/OFF on the symbol). If you do this, the simulation continues but stops taking measurements. The simulation also stops if tdsa cannot obtain valid results due to a lack of threshold crossings on the measurement input.Several tdsa arguments affect accuracy and simulation time: npoints determines how many frequency points will bemeasured. Increasing this value increases theresolution of the results, but also increasesimulation time.max_err sets the maximum allowable error of the phase and gain. It is calculated by keeping a running averageof the last 3 phase and gain measurements andcomparing it to the current phase and gain. Whenthe calculated measurement error is belowmax_err, data is written to the plot file and thenext frequency point is started.Large-signal systems may produce unwanted harmonics. You can use the bandpass filter to remove these unwanted harmonics from the input waveform. The filter automatically changes its center frequency to each frequency point during the sweep. The filter section uses a second-order filter of the form:max_nper and min_nper sets upper and lower bounds on the number of periods tdsa can continue generating a signal at a given frequency . If npoints is large, the error insome circuits will be less than max_err within 3 to4 periods. However, the phase and gain error is stillaffected by values from the previous frequency .Setting min_nper = 5 ensures that all the phaseand gain values used to calculate the phase andgain error are based on the current frequency value.The max_nper argument is supplied to help limitsimulation times. It overrides the max_errargument, causing the template to go to the nextfrequency , even if the calculated measurement erroris still too large.min_tspp sets minimum time steps per period, which affectsthe accuracy of the phase. Because tdsa calculatesphase information from zero crossings, the moretime steps per period, the more accurate the zerocrossing calculation. Increasing this number yieldsmore accurate phase information but slowssimulation. The default value of 40 gives goodresults for most circuits.tdsaThe arguments a0 and q0 let you control filter gain and quality, respectively. The bandwidth is determined by f0/q0, so a larger q0narrows the bandwidth, but increases the input settling time, which can increase simulation time. In some switched circuits, if the switching noise is large compared to the stimulus signal, a high q0 value can actually reduce simulation time.If you do not connect the enbl input (labeled ON/OFF on the symbol) and you set the argument enbl_init to a value of _1 (enabling tdsa), it initiates a frequency sweep at the beginning of a transient simulation. If you connect the enbl input, it controls when a sweep starts and stops.If no threshold crossings occur for the input signal at a given frequency, tdsa cannot obtain accurate AC data, and does not write any data to the plot file for that frequency point. If this occurs, a warning message is sent and the simulation proceeds to the next frequency point. This can happen if you set tdsa to take large frequency steps (a small npoints value) and/or you set the max_nper value too low. If tdsa skips three consecutive frequency points due to lack of threshold crossings, it assumes no valid phase and gain information can be obtained after that point, at which time it halts the simulation and alerts you with a warning message.。
ae中saber的用法 -回复
ae中saber的用法-回复Title: A Comprehensive Guide to the Usage of "Saber" in the Spanish LanguageIntroduction:Understanding the usage of "saber" in the Spanish language is crucial for learners and enthusiasts. This verb carries a wide range of meanings, uses, and conjugations. In this article, we will explore in detail the various forms of "saber," from its fundamental definition to its diverse applications in different contexts.1. Definition of Saber:"Saber" is a Spanish verb that means "to know." It denotes possessing knowledge or information about a particular subject or fact. It implies understanding, awareness, or familiarity with something. Additionally, "saber" also conveys the ability or skill to do something.2. Basic Conjugation of Saber:Saber is an irregular verb whose conjugation often deviates from regular verb patterns. Here is the basic conjugation of "saber" in the present indicative tense:- Yo sé (I know)- Tú sabes (You know)- Él/Ella/Usted sabe (He/She/You know)- Nosotros/Nosotras sabemos (We know)- Vosotros/Vosotras sabéis (You all know)- Ellos/Ellas/Ustedes saben (They/You all know)3. Using Saber in Different Contexts:3.1. Facts or Information:In its most common usage, "saber" is employed to express factual knowledge about a subject, often followed by an infinitive or a noun clause. For example:- Sé que Juan vive en España. (I know that Juan lives in Spain.)- ¿Sabes dónde está el supermercado? (Do you know where the supermarket is?)3.2. Skills and Abilities:"Saber" can also denote a skill or ability. In this context, it is often followed by an infinitive verb to indicate proficiency. Here are a few examples:- Él sabe tocar la guitarra. (He knows how to play the guitar.)- Nosotras sabemos nadar muy bien. (We know how to swim very well.)3.3. Expressing Awareness:Another important usage of "saber" is to convey awareness or familiarity with certain facts, particularly when discussing matters of general knowledge. For instance:- Todos saben quién es el presidente. (Everyone knows who the president is.)- Él no sabía que hoy era mi cumpleaños. (He didn't know today was my birthday.)Verb phrase construction:4.1. Future Tense - Ir + a + infinitive:In Spanish, the construction "ir + a + infinitive" is often used to express future actions. When combined with "saber," it conveys that one is aware or has foreknowledge of an event or intention. For example:- Ella va a saber la verdad pronto. (She is going to find out the truth soon.)- Nosotros vamos a saber los resultados del examen mañana. (We are going to know the exam results tomorrow.)4.2. Past Actions - Saber + preterite:To express that someone "found out" or "came to know" something in the past, the verb "saber" is conjugated in the preterite tense. For example:- Supe la noticia ayer. (I found out the news yesterday.)- Supimos lo que pasó después. (We found out what happened later.)5. Idiomatic Expressions:Besides its primary usages, "saber" is also incorporated into numerous idiomatic expressions, further showcasing its versatility in the Spanish language. Some commonly used expressions include:- Saber de memoria: To know by heart.- Saber a poco: To taste bland or lacking flavor.- Saber Dios: Only God knows.Conclusion:The verb "saber" is an essential part of the Spanish language, encompassing a broad spectrum of meanings and applications.From denoting factual knowledge to expressing skills, and even indicating awareness, the uses of "saber" are diverse and fascinating. By understanding its various conjugations and contexts, learners can develop a comprehensive command of the verb, allowing them to communicate with greater precision and fluency in Spanish.。
一种反激式开关电源的设计与仿真
第38卷第4期计算机仿真2021年4月文章编号：1006 -9348(2021 )04 -0083-06一种反激式开关电源的设计与仿真王强\王槐生U，田宏伟1(1.苏州大学应用技术学院，江苏苏州215325;2.苏州大学电子信息学院，江苏苏州215006)摘要：为实现小功率开关电源的小型化、高效化和低成本，提出了一种基于电流型PW M芯片UC3842控制下双路输出的反激式开关电源。
研究了电源的拓扑结构和工作原理，详细分析了EM1滤波器和整流滤波电路、功率变换电路、PW M控制电 路、反馈检测电路的关键参数和设计过程。
利用Sabei•软件的仿真工具箱搭建了电路闭环仿真模型，模拟反激式电路的环路控制，实现两路直流输出5V/1A和15V/1A，效率髙达90%。
仿真结果证明了设计的正确性和可行性。
关键词.•开关电源;反激式;电路设计;建模与仿真中图分类号:TP391.9 文献标识码：BDesign and Simulation of a Flyback Switching Power SupplyWANG Qiang1,WANG Huai - sheng12 ,TIAN H ong-w ei1(1. Applied Technology College,Soochow University,Suzhou Jiangsu 215325 ,China；2.School of Electronic and Information Engineering,Soochow University,Suzhou Jiangsu 215006,China)A B S T R A C T：For the r e a l ization of small switching power supply miniaturization,high efficiency,and low cost,a f l yback switching power supply controlled dual output was designed based on the current - mode P W M chip U C3842.The topological structure and working principle of the power supply were studied.The key parameters and the design process of EMI f i l t e r s and r e c t i f i e r f i l t e r circuit,power conversion circuit,PWM control circuit,feedback detection c i rc u i t were analyzed in ing the simulation toolbox of Saber software t o build the closed - loop simulation mode l simulating the loop control of the flyback c i r c u i t and achieving the two - channel DC output of 5V/1A and 15 V/1A,the efficiency can reach 90%.The simulation resu l t s prove the correctness and f e a s i b i l i t y of the design.K E Y W O R D S：Switching power supply； Flyback； Circuit design； Modeling and simulationi引言近年来，随着电子电路仿真技术应用领域的不断扩展，对仿真技术也提出新的要求，如何提高仿真的可靠性和准确性，提高建模和仿真的效率对于电子电路设计具有重要意义[|]。
PSpice仿真软件使用指南说明书
April 2016© 2013Cadence Design Systems, Inc. All rights reserved.Portions © Apache Software Foundation, Sun Microsystems, Free Software Foundation, Inc., Regents of the University of California, Massachusetts Institute of T echnology, University of Florida. Used by permission. Printed in the United States of America.Cadence Design Systems, Inc. (Cadence), 2655 Seely Ave., San Jose, CA 95134, USA.Product PSpice contains technology licensed from, and copyrighted by: Apache Software Foundation, 1901 Munsey Drive Forest Hill, MD 21050, USA © 2000-2005,Apache Software Foundation. Sun Microsystems, 4150 Network Circle, Santa Clara, CA 95054 USA © 1994-2007, Sun Microsystems, Inc. Free Software Foundation, 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA © 1989, 1991, Free Software Foundation, Inc. Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, © 2001, Regents of the University of California. Daniel Stenberg, © 1996 - 2006, Daniel Stenberg. UMFPACK ©2005,TimothyA.Davis,UniversityofFlorida,(**************.edu).KenMartin,WillSchroeder,Bill Lorensen © 1993-2002, Ken Martin, Will Schroeder, Bill Lorensen. Massachusetts Institute of Technology, 77 Massachusetts Avenue, Cambridge, Massachusetts, USA © 2003, the Board of Trustees of Massachusetts Institute of Technology. All rights reserved.Trademarks: Trademarks and service marks of Cadence Design Systems, Inc. contained in this document are attributed to Cadence with the appropriate symbol. For queries regarding Cadence’s trademarks, contact the corporate legal department at the address shown above or call 800.862.4522.Open SystemC, Open SystemC Initiative, OSCI, SystemC, and SystemC Initiative are trademarks or registered trademarks of Open SystemC Initiative, Inc. in the United States and other countries and are used with permission.All other trademarks are the property of their respective holders.Restricted Permission: This publication is protected by copyright law and international treaties and contains trade secrets and proprietary information owned by Cadence. Unauthorized reproduction or distribution of this publication, or any portion of it, may result in civil and criminal penalties. Except as specified in this permission statement, this publication may not be copied, reproduced, modified, published, uploaded, posted, transmitted, or distributed in any way, without prior written permission from Cadence. Unless otherwise agreed to by Cadence in writing, this statement grants Cadence customers permission to print one (1) hard copy of this publication subject to the following conditions:1.The publication may be used only in accordance with a written agreement between Cadence and itscustomer.2.The publication may not be modified in any way.3.Any authorized copy of the publication or portion thereof must include all original copyright,trademark, and other proprietary notices and this permission statement.4.The information contained in this document cannot be used in the development of like products orsoftware, whether for internal or external use, and shall not be used for the benefit of any other party, whether or not for consideration.Disclaimer: Information in this publication is subject to change without notice and does not represent a commitment on the part of Cadence. Except as may be explicitly set forth in such agreement, Cadence does not make, and expressly disclaims, any representations or warranties as to the completeness, accuracy or usefulness of the information contained in this document. Cadence does not warrant that use of such information will not infringe any third party rights, nor does Cadence assume any liability for damages or costs of any kind that may result from use of such information.Restricted Rights: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR52.227-14 and DFAR252.227-7013 et seq. or its successor.ContentsBefore you begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 How to use this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 What this user’s guide covers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 PSpice overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Add-on options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 PSpice Smoke Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 PSpice Advanced Optimizer Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 PSpice Advanced Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 SLPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 If you don’t have the standard PSpice A/D package . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Comparison of the different versions of PSpice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 If you have PSpice Lite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Minimum hardware requirements for running PSpice: . . . . . . . . . . . . . . . . . . . . . . . . 32 PSpice Samples and T utorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Part one: Simulation primer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 1Things you need to know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 What is PSpice? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Analyses you can run with PSpice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Basic analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Advanced multi-run analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Analyzing waveforms with PSpice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 What is waveform analysis? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Using PSpice with other programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Using design entry tools to prepare for simulation . . . . . . . . . . . . . . . . . . . . . . . . . . 47What is the PSpice Stimulus Editor? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 What is the PSpice Model Editor? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Files needed for simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Files that design entry tool generates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Other files that you can configure for simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Files that PSpice generates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Directory structure for analog projects in Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 How are files configured at the design level maintained in the directory structure for analog projects? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 How are files configured at the profile level maintained in the new directory structure for analog projects? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 What happens when I convert an analog project that uses a design from another project or from another location? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 What should I do if the schematic for a converted analog project uses FILESTIM n parts from the SOURCE library? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Design Entry HDL libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Reference Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Local libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 PSpice model libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 The cds.lib file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Encrypting PSpice Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Using PSpiceEnc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Using Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722Simulation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Example circuit creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Using Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Using Design Entry HDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Using Design T emplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Finding out more about setting up your design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Running PSpice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Performing a bias point analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Using the simulation output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Finding out more about bias point calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99DC sweep analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Setting up and running a DC sweep analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Displaying DC analysis results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Finding out more about DC sweep analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 T ransient analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Finding out more about transient analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 AC sweep analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Setting up and running an AC sweep analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 AC sweep analysis results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Finding out more about AC sweep and noise analysis . . . . . . . . . . . . . . . . . . . . . . . 122 Parametric analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Setting up and running the parametric analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Analyzing waveform families . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Finding out more about parametric analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Performance analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Finding out more about performance analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Part two: Design entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1383Preparing a design for simulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Checklist for simulation setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 T ypical simulation setup steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Advanced design entry and simulation setup steps . . . . . . . . . . . . . . . . . . . . . . . . . 141 When netlisting fails or the simulation does not start . . . . . . . . . . . . . . . . . . . . . . . . 142 Using parts that you can simulate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Vendor-supplied parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Passive parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Breakout parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Behavioral parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Simulating asymmetric parts in PSpice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Simulating homogenous parts in PSpice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Specifying values for part properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Using global parameters and expressions for values . . . . . . . . . . . . . . . . . . . . . . . . . . 158Global parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Defining power supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 For the analog portion of your circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 For A/D interfaces in mixed-signal circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Defining stimuli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Analog stimuli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Digital stimuli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Things to watch for . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Unmodeled parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Unconfigured model, stimulus, or include files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Unmodeled pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Missing ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Missing DC path to ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854Creating and editing models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 What are models? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 How are models organized? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Model libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Model library configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Global vs. design vs. profile models and libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Nested model libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 PSpice-provided models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Model library data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Device characteristic curves-based models vs. Template-based models . . . . . . . . 195 T ools to create and edit models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Ways to create and edit models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Using the Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Ways to use the Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Running the Model Editor alone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Starting the Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Creating models using the Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Creating models based on device characteristic curves . . . . . . . . . . . . . . . . . . . . . 203Creating models based on PSpice templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Importing an existing model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Enabling and disabling automatic part creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Running the Model Editor from the schematic editor . . . . . . . . . . . . . . . . . . . . . . . . 215 Model creation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Example: Creating a PSpice model based on device characteristic curves . . . . . . . 219 Example: Creating template-based PSpice model . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Editing model text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Example: editing a Q2N2222 instance model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Using the Create Subcircuit Format Netlist command (Capture only) . . . . . . . . . . . . . . 237 Changing the model reference to an existing model definition . . . . . . . . . . . . . . . . . . . 239 Reusing instance models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Reusing instance models in the same schematic . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Making instance models available to all designs . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Configuring model libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 The Configuration Files tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 How PSpice uses model libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Adding model libraries to the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Changing the model library scope from profile to design, profile to global, design to global and vice versa . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Changing model library search order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Changing the library search path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Handling smoke information using the Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Adding smoke information to PSpice models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Creating template-based PSpice models with smoke information . . . . . . . . . . . . . . 256 Using the Model Editor to edit smoke information . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Examples: Smoke . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Adding smoke information to the D1 diode model . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Adding smoke information to the OPA_LOCAL operational amplifier model . . . . . . 259 Smoke parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Diode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Bipolar Junction Transistors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Magnetic Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Ins Gate Bipolar T ransistor (IGBT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Junction FET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Operational Amplifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268MOSFET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 Voltage Regulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Darlington T ransistor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2735Creating parts for models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 What’s different about parts used for simulation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Ways to create parts for models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Preparing your models for part creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Starting the Model Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Using the Model Editor to create parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Batch mode of part creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Interactive mode of part creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Creating Design Entry T ool parts for all models in a library . . . . . . . . . . . . . . . . . . . . . . 282 Using batch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Using interactive mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Setting up automatic part creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Creating parts in the batch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Creating parts using interactive mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Basing new parts on a custom set of parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Editing part graphics (Capture only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 How Capture places parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Defining grid spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 Attaching models to parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Defining part properties needed for simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 PSPICETEMPLATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 IO_LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 MNTYMXDL Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 PSPICEDEFAULTNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3216Analog behavioral modeling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Chapter overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Overview of analog behavioral modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 The ABM part library file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Placing and specifying ABM parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Net names and device names in ABM expressions . . . . . . . . . . . . . . . . . . . . . . . . . 326 Forcing the use of a global definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 ABM part templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Control system parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Basic components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Limiters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Chebyshev filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Integrator and differentiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 T able look-up parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Laplace transform part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Math functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 ABM expression parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 An instantaneous device example: modeling a triode . . . . . . . . . . . . . . . . . . . . . . . 353 PSpice-equivalent parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Implementation of PSpice-equivalent parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Modeling mathematical or instantaneous relationships . . . . . . . . . . . . . . . . . . . . . . 358 Lookup tables (ET ABLE and GT ABLE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Frequency-domain device models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Laplace transforms (LAPLACE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364 Frequency response tables (EFREQ and GFREQ) . . . . . . . . . . . . . . . . . . . . . . . . . 366 Cautions and recommendations for simulation and analysis . . . . . . . . . . . . . . . . . . . . . 369 Instantaneous device modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Frequency-domain parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Laplace transforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 T rading off computer resources for accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Basic controlled sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Creating custom ABM parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375。
Saber软件仿真流程
4.关于变量的分层传递
关于这个问题,我曾在我的博客文章《滤波器电路仿真》和《滤波器电路仿真续》中仔细介绍过,有兴趣的网友可以去查查看.
今天来谈谈sketch中如何布线的问题,这个问题不太复杂,在这里只是对布线方法和过程做omponent的方法主要有两种,一种直接利用PartGallery的search功能去搜索,只要清楚的知道所需模型的名称,就可以在search中输入查找,如果Saber的模型库中有该器件的模型,则会在下面显示出来.如果下图所示,是查找运算放大器NE5532的结果.需要注意的是,不同的尾缀主要是器件封装上的区别.但有一种例外,以_sl结尾的属于前面介绍过的SL库,这种模型没有MC和STRESS特性,但仿真速度很快.
今天来讨论一下如何在Sketch找到合适的器件.对一张原理图来讲,要完成对它的分析验证,首先是需要保证原理图中的各个元器件在Saber模型库中都有相应的模型;其次要保证在Sketch中绘制的原理图与原图的连接关系一致;再者就是根据目标系统的工作特点,设置并调整相应的分析参数.这三个条件都达到,应该能得到一个不错的分析结果.一张原理图中需要的模型涉及很多,但不管怎样,其所对应的模型正如我前面介绍的那样,只有template和component两种.对于需要设置参数template模型,需要去PartGallery中寻找;而component模型则直接可以利用PartGallery的search功能或者Parametric Search工具进行进行查找.
Saber的空间矢量PWM实现方法
第24 卷 第3期 2010 年 6 月
空军雷达学院学报 Journal of Air Force Radar Academy
U4 (1 0 0)
Ⅰ
U0
Ⅴ
(0 0 0)
U7 (1 1 1)
Ⅳ
T2
Uref
Ⅲ T1
Ⅱ
轴
U1 (0 0 1)
于 仿 真 模 型 ，它 能 提 供 与 精 度 相 关 的 参 数 ，具 有 很 高的仿真精度 1 ．此外，Saber 还提供了适合于建立 混合仿真模型的硬件描述语言— MAST 语言，用
U5 (1 0 1)
UA = U
UB = sin 60°U sin 30°U
(9)
UC = sin 60°U sin 30°U
取 x = sign UA + 2sign UB + 4sign UC，求得的 x 值 即为
扇区号．
2）计 算 开 关 电 压 矢 量 作 用 的 时 间
开关电量矢量作用时间根据所在扇区的常数
矩 阵 和 式 (7) 计 算 得 到 ．
图1
Ⅵ U6
(1 1 0)
电压空间矢量
户可以建立满足自己需要的模型 2 ．本文对传统的 SVPWM 算法进行改进，并用 MAST 语言编译了 SVPWM 模块．为了验证模块的正确性，将模块应 用于三相电压型 PWM 整流器的系统仿真电路．
Uk =
2 3
Ud
j
e
k
13
k = 1, 2,
电磁发射用脉冲电源的设计
毕业设计(论文) 设计(论文)题目：电磁发射用脉冲电源的设计电磁发射用脉冲电源的设计摘要随着电磁发射技术的不断发展，其在国防建设以及国民生产中的应用也越来广泛。
高功率脉冲电源作为电磁发射技术的主要组成部分，也越来越受到人们的关注。
为了满足空间电磁发射技术的需要，高精度脉冲电源系统就显得非常重要，而脉冲电源的主电路拓扑结构的设计就成了一个重要的研究问题。
本论文主要介绍了电磁发射仿真实验中的脉冲电源系统的主电路的拓扑结构、特性，并运用saber电路仿真软件对主电路进行理论仿真。
主要完成的工作有：1.建立了脉冲电源主电路的数学模型：介绍了毫秒级（精确到百微秒级）脉冲电源系统的组成以及重要元件和相关参数进行介绍，同时分析了各个元件在主电路中所起到的作用，同时指明各元件的选择依据，通过理论上的软件仿真，从而确定了脉冲电源系统中各功率元件的参数。
2.通过在saber电路仿真软件中对脉冲电源的电路拓扑结构的仿真，获得电路中不同线路电流、电压随着时间的变化曲线，从而确定它们在短时间内（毫秒或者微秒级）的变化效果，并对此进行分析，通过调节，最终获得最佳的脉冲电源主电路拓扑结构以符合电磁发射对脉冲电源的要求。
关键词：电磁发射、脉冲电源、拓扑结构、仿真With the design of pulse power electromagnetic launchABSTRACTWith the continuous development of electromagnetic launch technology, its application in national defense construction and national production are more widely. High power pulse power as the main part of the electromagnetic launch technology, is becoming more and more get the attention of people.In order to meet the needs of space electromagnetic launch technology, high precision pulse power system is very important, and the design of the main circuit topology of pulse power supply is an important research question. This paper mainly introduced the electromagnetic emission experiments of pulse power system of main circuit topology structure, properties, and using saber circuit simulation software simulation was carried out on the main circuit theory. The main works are as follows:1. Established the mathematical model of pulse power main circuit: Introduces the composition of millisecond pulse power supply system and introduces the important components and related parameters, and analyzes the various elements play a role in the main circuit, at the same time, indicate the components selection basis,through the theory of software simulation, which determine the pulse power supply power components of the system parameters.2. Through the saber in the circuit simulation software simulation of pulse power supply circuit topology, different line current and voltage in the circuit are obtained with the change of time curve, to identify them in a short period of time (milliseconds or microsecond) change effect, and by, adjusting, finally get the best pulse power main circuit topology structure to conform to the requirements of the electromagnetic emission of pulse power supply.Key words: electromagnetic launch, pulse power, topology structure, simulation目录摘要 (I)第一章绪论 (1)1.1 课题的背景及意义 (1)1.1.1电磁发射技术的发展及背景意义 (1)1.1.2脉冲电源的背景和意义 (2)1.2课题的研究现状 (3)1.2.1电磁发射技术的国内外研究现状及应用 (3)1.2.2脉冲电源的应用及研究现状 (5)1.3课题的应用前景 (10)1.4 电磁发射用脉冲电源的设计课题的研究意义 (11)1.5本文结构 (12)第二章脉冲电源的原理 (13)2.1等效模型在电源电路中的应用 (13)2.2电磁发射对脉冲电源的要求 (16)2.3本文采用的脉冲形成系统的形式 (18)2.4脉冲电源的设计要求 (19)2.5本章小结 (19)第三章脉冲电源的结构 (20)3.1概述 (20)3.2脉冲电源总体结构 (21)3.3脉冲电源的单个模块拓扑结构 (22)3.4脉冲电源的单个模块中各元器件的参数选择 (24)3.4.1储能电容器的参数设计 (24)3.4.2续流支路吸能电阻R (24)3.4.3调波电抗器L (25)3.4.4放电开关 (25)3.5脉冲电源的多个模块模型 (26)3.5.1多个模块串联结构拓扑 (26)3.5.2利用Marx发生器开关管 (28)3.6本章小结 (29)第四章脉冲电源单个模块结构的saber仿真 (30)4.1仿真电路的制定和元器件参数的选择 (30)4.2初始步长和瞬态分析终止时间的设置 (30)4.3仿真结果分析 (31)4.3.1脉冲电流波形 (31)4.3.2各支路电流和电压波形 (33)4.4本章小结 (36)第五章总结和展望 (37)参考文献 (38)致谢 (41)南京工业大学本科生毕业设计（论文）第一章绪论1.1 课题的背景及意义1.1.1电磁发射技术的发展及背景意义伴随着物理技术不断的进步和发展，使目前发射装置如大炮、火箭等类型的发射器已经不能满足现代人类对发射能力需求的更高要求，正是在此情况下产生了新一代超高速的电磁发射推进技术。
saber调用外部C程序仿真
作者 : 陈锋使用saber调用外部C程序共有三步：1. 用MAST语言编写一个template，其实就是一个saber和外部程序的接口。
可以用记事本编写，保存成*.sin文件2. 在saber中新建一个symbol，跟上面的template建立连接，以后仿真的时候用的就是这个symbol。
保存成*.ai_sym3. 用VC编写一个算法，并生成动态链接库*.dll下面具体介绍上面三步：举一个例子：做一个2倍器，就是输出是输入信号的2倍。
算法在C程序里，template是接口，这个例子中是单值传输，多值传输的时候会有不同，后面介绍。
1. 先编写一个template#MAST语言中注释用“#”符号，不是“//”element template xjtu in1 out1 = k #template是声明字不可缺，xjtu是这个模块名input nu in1 #in1 是输入，out1是输出，换行不用“；”output nu out1number k = 1{foreign number PWM() #外部程序声明，单值传输要number 后面还要括号out1 = PWM(k*in1) #程序调用很随意，单值传输可以直接给输出调用}写完后，保存成xjtu.sin #文件名要和模块名一致2. saber中建一个symbolnew->symboltools->drawing tolls画一个symbol属性里面添加一项primitive 名字就用刚才template的名字xjtu，saber就会自动为这两个建立连接完成之后保存为xjtu.ai_sym3.用VC建一个动态连接库的工程头文件加三个#include <stdio.h>#include <math.h>#include "saberApi.h" /* Specify the complete path here to"<saber_home>/include/saberApi.h" */saberApi.h 这个头文件到saber文件夹里去找后面一定要加下面一段，直接照抄，不要多也不能少。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Tips for Saber Users in the Simulation of Power Electronic Circuits By: Ahmed ElasserRensselaer Polytechnic InstituteDepartment of Electric Power EngineeringTroy,NY,12180E-mail: elassa@Abstract: In this article, some useful tips for Saber users are described for successful simulation of power electronic circuits. The tips described were tried on power electronic converters operating at frequencies as high as 40kHz and a maximum power of 10kW. The simulation was done on a Sun Sparc station with 16Meg of real Memory. All the tips described here arefor the 3.1a Version using the human interface.1 Writing an Appropriate Netlist: (for human interface version)Usually writing a Saber netlist is the easiest thing to do for any Saber User. However, there are many ways to write an appropriate netlist. First of all you should include in your netlist shorts if you want to measure the current in the branches instead of the zero dc voltages. However, this may not be the best way especially in the case of templates with their own internal current. You may also want to specify the value of the series resistance for the c and l templates. To do this more efficiently, you have to specify a value for the built-in series resistor. This specification allows you to have a more realistic model without adding an external resistance. In case of the capacitor, when you do not specify a value for the built in (Electrical Serial Resistance) E.S.R, the number of nodes is reduced which leads to a corresponding saving in the simulation time.In some cases, the addition of shorts or zero-dc voltages is not necessary because you can get the current by specifying them in the SIGLIST. When you are only interested in getting the waveforms from Saber and not the details of the commutations, it is much better to replace the semiconductors with the ideal switches. There is a variety of switches implemented in the Saber Template Library.It is also better to specify the group of the diode or the semiconductor in the netlist, especially when you are operating at high frequencies (e.g diode.1 e1 e2=group=high_speed). You can also specify some parameters of the model like the saturation current or the distribution. Keep in mind that it is much better to replace the semiconductors with behavioral switches, as many as you can, because this gives you an idea about the functioning of the converter. Some components like the IGBT are not very appropriate to use especially at high frequencies. Actually the IGBT model used by Saber is highly non linear and thus requires a lot of simulation time. It is much easier to use either digital switches like the sw_l4, pwm_l4, the behavioral switch, or the state-spaced averaged models.It is also useful to replace the control circuit by pulse voltage sources. In the case of switching power supplies you can replace the switch and its control by one element.2 Ways of running Saber:Usually when you want to run Saber for an application, you startby a dc analysis and then the transient analysis. In some cases the transient does not take a lot of time but in many converters the transientis very long and takes several thousand clock cycles before reaching the steady state. As we are not very interested in this numerical transient, it is advisable to run it as fast as possible and to get rid of it.One way to do that is to take a big TIME STEP and a large Truncation Error. Generally a truncation error of 0.001 is more than sufficient. In some cases it is even possible to specify a truncation error of 0.1. It is also important that you specify certain parameters during the dc analysis (e.g. you can specify the value of the output voltage and save a lot of timefor the simulator to reach that point).The SIGSET command is also useful in this case. It allows you to create an initial point to start the dc or the TRansient analysis. Notethat SIGSET does not work in conjunction with the simulation. Analternative to it is the use of the option HOLDNODES which works in conjunction with the simulation of the dc analysis. You may want to specify not to release HOLD after the dc analysis in order to help the dc simulation converge more quickly and/or easily. When RELHOLDnodes is set to yes, it will solve the dc holding the nodes to the specified values. When finished, it will automatically use the final point of the dc analysis as an initial point to solve a normal dc. This option is valid only when a steady-state solution exists. When there is no steady solution, one has to set RELHOLD to NO. This is true in the case of oscillators. However, you have to be careful when using the HOLDNODES because it may result in a differentresult than the SIGSET, especially in case of circuits with parasitic elements such as inductors or capacitors. The SIGSET command specifies only the value of the node voltage while the HOLDNODES imposes the voltage and the current. SIGSET is essentially an initial point editor, and as such, has no validity with regards to simulation.Another important thing to consider is the files created by Saberfor each analysis. In general if you are not interested in extracting the initial point or any variables from any level of hierarchy not already in the SIGList for the PLotfile(s), you do not need to keep the data file. Therefore it is easy to tell Saber to ignore it simply by giving an underscore `_' instead of a name in the transient analysis menu. Ie,``DF _'' The same thing applies for the plot file. You may only needto keep the initial point and the end point. Ie, TRIP and TREP.After completing the transient and reaching the steady state, a good accuracy is needed in order to have a very good result. For best accuracy, TruncationERRor may be set to 0.1m and the TruncationERRorTYPE to ALL for the version 3.2. (For previous release use STATIC.) It may be helpful to increase the DENSITY to 16 or 32 or even in some cases to 64. Generally a time step of 0.001u is good enough for power electronic converters operating at high frequencies (up to 50 kHz). However, it is not a critical parameter since Saber uses a variable-size timestep which automatically adjusts the timestep in order to keep to the accuracy settings (eg, TruncationERror). Keep in mind to use for each transient the previous result. This is possible by using the CONTinue menu and CONTinue TRansient with the appropriate TimeEnd.3 Avoiding Troubles with Saber: (Transient Analysis)In some cases and even with all the precautions taken, you may run in trouble and get an error message. The error message may be one of the followings:1 SINGULAR JACOBIAN MATRIX2 ALGORITHM NO NON LINEAR SOLUTION3 PL DATABASE EOF4 CLASS-OPEN-FILEOne way to get around the first error if it has happened during the transient analysis is to run Saber with the hierarchy flattened:Saber -d flat file.sinThis usually fixes the problem. If the problem has not been fixed, try to fix it either by increasing the density or by reducing the truncation error and the time step. It is also sometimes useful to change the timeresolution of the simulator. You may also need to alter parameter values so that various instances of a template type don't have too wide of a range of values (e.g c.1=1p; c.2 =1 #Farad). This problem may also arise from choosing a very small TimeStep relative to TimeEnd because of the wide difference of time constants (stiff system).The second error is usually fixed by the adjustment of thetruncation error and the density. A couple of other things to do in this case is:1. Switch to the first order integration method.2. switch to the Trapezoidal integration method.However, the last two methods may not be very accurate if theconverter is operating at high frequencies.When you get the message PL DATABASE EOF, you have to run again the simulation for a few cycles. It is also possible to fix the problem by editing the ASCII *.p1.* file and changing the value for npoints (near the bottom of the file) to a slightly smaller value. Therefore, you will avoid the need to resimulate.Whenever you get the error CLASS-OPEN FILE you need to check your disk quota because you went over it.In some cases you may need to run the simulation step by step and after each step use the old transient end point (TRep) as your new transient initial point (TRip). When you are using IDEAL SWITCHES instead of real models of the semiconductors, you have to be aware that the ON resistance of the switch should be finite. Theoretically you can use a zero ON resistance and an infinite OFF resistance but it is advisable to give a small ON resistance and a big value but finite for the OFF resistance. The same thing applies to the rise time and the fall time of many templates like the pulse template. The Rise and Fall times must be strictly positive.。