CosNamingFT- A Fault-Tolerant CORBA Naming Service Lau Cheuk Lung, Joni da Silva Fraga e Jean-Marie Farines
Laboratório de Controle e Microinformática
Univ. Federal de Santa Catarina; Florianópolis - Brazil
lau, fraga, farines@lcmi.ufsc.br
Michael Ogg, Aleta Ricciardi
Information Science Research Center
Bell Laboratories; Murray Hill, NJ - USA
ogg, aleta@https://www.doczj.com/doc/a06481953.html,
Abstract
This paper describes the design and implementation of a fault-tolerant CORBA naming service - CosNamingFT. Every CORBA object is accessed through its Interoperable Object Reference (IOR), which is registered with the CORBA name service. The name service therefore is a critical gateway to all objects in a distributed system; to avoid having a single point of failure, the name service should be made fault-tolerant. CosNamingFT uses the GroupPac package [6], a CORBA-compliant suite of protocols, to replicate the name server. GroupPac services are built from Common Object Services that function as building blocks to implement fault-tolerant applications. This paper aims to demonstrate the usefulness of some of these object services and to demonstrate the importance of open solutions issues in replicating distributed objects.
Keywords: naming service, fault-tolerant, CORBA, open systems.
1.Introduction
A name service plays an important role in any distributed system. Roughly speaking, its primary role is to facilitate access to the system’s resources; it is a commonly known “meeting room” for objects, services, and resources. As defined by the CORBA (Common Object Request Broker Architecture) specifications, the name service is a critical gateway for all objects in a CORBA-based distributed system. All CORBA objects are registered with the name service, allowing them to be found and used by any other object in the system. Thus, each object that participates in a CORBA-based computation accesses the name service at least one: either to register itself via its IOR (Interoperable Object Reference), or to locate other CORBA objects’ IORs. One of the OMG’s (Object Management Group) Common Object Services (COSes) is a name service standard, called CosNaming [9, 10]. The CosNaming specification takes into account the portability, interoperability and reusability aspects that are important concepts in open systems. However, these specifications do not include requirements of fault tolerance that are very important for distributed systems.
One possible way to implement a fault-tolerant name service would to use the COS persistence service [10], a unique interface for persistent storage services for objects’states. We decided not to follow a persistence-based strategy due to concerns over recovery time for applications requiring more stringent availability; to recover from a crash, a new name service must be started and its state loaded from file.
Here, we describe CosNamingF T, a name service which adheres to the OMG’s CosNaming and uses primary-backup replication [2] to achieve fault tolerance. Primary-backup replication can provide continuous service availability (the degree of fault tolerance depends on the model of computation assumed), but cannot guarantee once-and-only-once semantics. Primary-backup replication has a shorter fail-over time than strategies based on persistence, and lower overhead than active replication strategies. We used the GroupPac package [6], a set of common object services for implementing various group-based communication models, for the primary-backup infrastructure. In addition, these service objects can be combined in different ways allowing the implementation of different fault tolerance schemes. This paper demonstrates the usefulness of these services as well as the possibility of obtaining open solutions for replicating distributed objects.
Proceeding of the 18th International Symposium on Reliable Distributed Systems - SRDS'99, IEEE Computer Society. Lausanne, Sui?a - Outubro de 1999.
At present, there is no sanctioned COS specification for fault-tolerant CORBA objects through replication and group-based processing, though this is expected within the year [11]. Electra [7] was an integration-based approach to build replicated CORBA objects, building the ORB on top of a group-communication subsystem, although any communication substrate could have been used (for example, an adaptor for TCP was as sensible as the original adaptor for Isis [1] and a later for Ensemble (originally called Horus) [14]). While Electra used Isis’s active replication model, this was an early implementation choice; Isis’s coordinator-cohort (passive replication) model could equally well have been used.
Eternal [8] is an interception-based approach, also making use of an existing group-communication subsystem, but in this case intercepting IIOP messages and mapping them to calls of the group-communication system. The advantage of this approach is that no modifications to the ORB are required; neither the ORB nor the objects need ever be aware of being intercepted. The shortcomings are that the approach is only possible if the host operating system permits interception. In both integration and interception, until there are OMG specifications for multicast and group communication semantics, both strategies must be considered “proprietary”.
The approach taken by the Object Group Service (OGS) [4] is most similar to ours, in that both adhere to the common object service model of the OMG. The primary difference is in how the group service itself is activated. In OGS the object’s interface explicitly inherits from the OGS Groupable interface:
interface FOO: mGroupAdmin:Groupable {
void m0();
};
This makes fault tolerance visible to application objects since they must be aware of the existence of the OGS objects to use their services. Application objects convey their invocations and responses, via the Dynamic Invocation Interface and the Dynamic Skeleton Interface, to their associated OGS objects, which then coordinate with each other to perform the operation on the replicas of the object and to return the results appropriately.
The GroupPac package [6] is a set of common object services for implementing various group-based communication models, for different fault tolerance strategies. In contrast to OGS, GroupPac does not require any explicit change to an application’s interface (e.g., it is not necessary to inherits any group service interface). Instead, to use GroupPac, the application create a instance of a portable interceptor (from CORBA spec), which implements the mechanisms to invoke GroupPac services. Fault tolerance is not visible to the application.
In Section 2 we present OMG’s CosNaming specification. Section 3 describes GroupPac and Section 4 describes the implementation of CosNamingFT with GroupPac. In Section 5 we resent some performance tests for CosNamingFT and comparisons with related work. https://www.doczj.com/doc/a06481953.html, Service in the CORBA
Specifications
OMG specifications are intended as a set of standards and concepts for distributed objects in open distributed environments. The heart of the CORBA standards is the Object Request Broker (ORB), which allows a remote object’s methods can be invoked transparently in heterogeneous distributed environments. Thus, an ORB is a communication channel for distributed objects. Interoperability between objects is achieved by specifying their interfaces with CORBA’s Interface Definition Language (IDL). Translating IDL specifications a host of programming languages (including C, C++, Ada, COBOL, Java) generates the necessary, language-specific interfaces and auxiliary support for object implementations.
To help in the development of distributed applications, OMG specifications included a set of object services that simplify the application designer’s task. Such COSes de-fine, for example, how exceptional events should be transmitted, how objects are located and named, how security is provided, or the semantics of transactions. In this way, the COSSes define basic functionality that frequently appears in many distributed applications.
2.1.The Common Object Name Service
The COS name service, commonly called CosNaming, defines how to resolve object names in a CORBA environment. An object is identified by its name and its object reference (i.e., its IOR). The object’s name corresponds to a set of characters ideally, but not necessarily, expressing a quality or a certain feature associated with it. The IOR is the data necessary to reach the object in a distributed system; it is a character sequence, that once properly converted provides the IP address information of the host, the port, and a local pointer for the object to be accessed and more control information related to the IOR itself. In the CosNaming specification, an association between name and IOR is called a name bindin g, which is defined within a naming contex t. Each naming context maintains its own set of name bindings; while names must be unique, a naming context permits multiple names to be associated with the same IOR. This multiplicity allows one to swap object instances on the fly, yet retain the same address of a desired service (in the same way, for example, that a
restaurant retains the same physical address irrespective of which of its wait-staff or cooks are on duty). We use NameContext throughout this paper to refer to the object that implements the functionality of the name service defined in CosNaming specifications.
H ost A N am ing C
H ost B
H
Figure 1. NameContext procedures for the support of client/server interactions.
Figure 1 presents a temporal diagram delineating the phases of interactions between the NameContext, and server and client objects. These phases cover the NameContext start-up, the installation of a server object’s IOR at the NameContext (binding procedure) and finally, the phase in which client object obtains the server object’s IOR.
A NameContext object in its starting state (step 1 in Figure 1) places its own IOR in a repository (a file in the file system), allowing it to be accessible to all CORBA objects. In our implementation, this repository is a directory that is accessible through an HTTP server (for example: http://www.lcmi.ufsc.br/?lau/io r), thereby allowing method invocations through the Internet. Thereafter, other CORBA objects can install their IORs. Figure 2. Getting the IOR of the NameContext.
For a server object to install its IOR with the NameContext, it finds the IOR of the NameContext through the resolve_initial_reference() method, which accesses the repository (Figure 1, step 2).The Java code implementing this step, is presented in Figure 2.
After getting the IOR of the NameContext, the application server can invoke this service for installing its own IOR and become available via CORBA to all objects in the system (Figure 1, step 3). The code in Figure 3 is how a server named Foo, of type App installs itself and binds its name/IOR with the NameContext.
Figure 3. Installing an IOR in the NameContext.
The client’s actions in invoking a method of the server are shown in Figure 1, steps 4-6. As with the server, the client must first obtain the NameContext’s IOR with the resolve_initial_references() method. In a CORBA system, a client must know, a priori, the name and type of the server it wishes to use. Thus, in the next step, the client invokes the NameContext to resolve this name. If the name exists in the NameContext, the client is returned the server’s IOR, and may thereafter invoke the server’s methods. Figure 4 contain the code fragment for these steps.
Figure 4. Client interactions for allowing invocations in the server object.
3. GroupPac Services and CosNamingFT Architecture
3.1. GroupPac Services
The GroupPac package [6] adheres to the OMG orientation in that it is a collection of common object services that provide support building and managing object replication. GroupPac is based on models and concepts specified by the OMG for common object services. In this philosophy, GroupPac provides a set of building blocks – object services – that can be arranged in different ways to arrive at different fault-tolerant schemes.All GroupPac object services are orthogonal and their interfaces are specified using the CORBA IDL.
T he se t o f o b je c ts se rv ice o f the G rou pP a c : S S : S ta rtu p S e rv ic e ;
S TS : S ta te T ra n sfe r S e rv ic e ; M S : M e m b e rship S e rv ic e ; F D S : F a ilu re D e te ctio n S e rv ic e ; G C S: G ro up C o m u nica tio n S e rv ic e .
C o nn e c to rs :
- H o riz o n ta l: In te rfa ce to co m m u ic a te o b je c ts o f the sa m e ty p e ;- V e rtica l: In te rfa ce to co m m u n ica te o b je c ts o f the d iffe re n ts ty p e s ;
Figure 5. Object services in GroupPac.
Figure 5 depicts the GroupPac Startup Service (SS),State Transfer Service (STS), Membership Service (MS),Failure Detection Service (FDS) and Group Communication Service (GCS). Each one of these object services has got a horizontal and a vertical interface: The former allows communications between object services of the same type; the latter is the way in which the service is made available to other objects in the system.
The SS object is responsible for creating the other package service objects. All other GroupPac service objects are, therefore, dependent on the SS. It is from this object that the necessary configuration for the support of a replicated application is built. The STS object provides functionality for transferring state from one object to another. Some means for transferring state is common to most middleware facilitating replication [1, 15]; it is also common in supporting object migration. The MS object is responsible for managing changes in composition to groups of objects. Ideally, membership changes should be transparent to an application, but there will always be a trade-off between blocking an application and the
completeness of the membership change propagation. The FDS object is concerned with detecting the (apparent)failures of objects in a group; obviously failure per se is not detected as much as the unresponsiveness of the object is measured. As expected, the MS object uses the FDS’s services: FDS suspicions are reported to the MS object,which then creates a membership list that no longer contains the suspected object. Finally, the GCS object supports various group communication primitives, such as FIFO, causal, or linear order multicasts within a group using point-to-point communications at the ORB level; it depends heavily on the MS object.
3.2. CosNamingFT
Our implementation of CosNamingFT follows the CORBA specifications for name services [10], while using GroupPac to add primary-backup fault tolerance.The primary CosNamingFT replica performs all client requests to the CosNamingFT service. These requests are not blocking in the sense that the primary updates the backups after having responded to the client. Of course,this admits the possibility of state inconsistency between the primary and its backups. In the worst case, a new service may have been registered with the primary CosNaming copy of which the backups are unaware; a request by a client for a registered service’s IOR is, in essence, a stateless operation, meaning there will be no significant state difference between the just-failed primary and its backups. The case in which the primary CosNamingFT copy fails before replying to its client is indistinguishable to blocking or non-blocking implementations of primary-backup replication.
Figure 6. GroupPac service blocks used in CosNamingFT.
After processing a request and performing the corresponding update to replicas, all the correct replicas that compose the CosNamingFT must keep the same context.
GroupPac services are incorporated within CosNamingFT transparently (Figure 6). Each CosNamingFT replica contains a copy of the SS, STS, MS, FDS and NameContext objects, all of which are located in the same Unix process. Each CosNamingFT replica is linked to the others by the grouping of its component GroupPac services. For example, in Figure 6, the MS object of each CosNamingFT replica form a group that supplies a membership service in the CosNamingFT.
3.2.1.Management Service
Between them, the FDS and MS groups supply information about the status (correct/faulty) of each CosNamingFT replica, and control the composition of the CosNamingFT replica members for the CosNamingFT service.
The FDS ‘detects’ replica crashes in the following manner. The FDS assumes non-blocking, reliable point-to-point communication between pairs in the FDS group; thus, the absence of an expected message cannot be due to its loss by the transmission medium, but may instead be indicative of something wrong with the sender. In Figure 7, each object of the FDS group periodically “pings” its partner (as determined by a virtual ring on the linear ordering the members of the group). If it does not receive a response within some tunable timeout period, it suspects its partner of having crashed and invokes the leave_group() method of the MS object in the primary replica.
Backup
Backup
Prim ary (R
Backup
Figure 7. The failure detection service.
This spurs the membership service into action, which uses a centralized, two-phase (three-phase in the worst case) commit protocol reach agreement with the other MS replicas on a new group composition [12]. The MS object of the primary CosNamingFT replica is the coordinator for the group of MS objects. Figure 8 shows a very simple instance of this protocol. The FDS object of replica R3 suspects replica R2and invokes leave_group(R2) of the primary replica. This activates the membership protocol, whereby the primary MS object attempts to discover which others remain in the group via the MS-to-MS method commit(). The response to a commit() method is a simple acknowledgement. After waiting for a predefined-defined timeout, the primary updates the list of active members based on the acknowledgements it received [14, 12] (which must constitute a majority of the previous view).
Backup (R2
Backup (R1
Prim ary (R
Backup
A ck
suspec t of R2
Figure 8. FDS and MS operation when replica R2 crashes.
When the primary replica is suspected of having ‘failed’, a new primary must be selected; the candidate preference list follows the order implemented by the virtual ring. In our scheme, the new primary, once ascertained, must install its IOR at the HTTP server. Figure 9 gives a simple example showing how a primary is replaced. Complete details on the reconstruction of the primary follow the procedure described in [12]. Once a new primary has been agreed upon, it installs its IOR at the HTTP server. Since the HTTP repository is unique, only one replica can have its IOR installed there, ensuring at most one replica is ever acting as the primary (recall that all activity involving the primary first checks the HTTP repository).
B a cku p (R
B a cku p (R P rim a ry (R B a cku p (R H TTP S e rve - IO R
B a cku p (R Figure 9. Determining a new primary copy.3.2.2. State Transfer Service
We use the GroupPac State Transfer Service (STS) to guarantee consistency among CosNamingFT replicas.Figure 10 illustrates the following steps in check-pointing states from primary to backups.
Figure 10. State Transfer Service.
4. CosNamingFT Implementation
Our implementation adheres to COSS/OMG specifications for the name service (CosNaming); no extension or modification has been made to the standard interface (Figure 11). The use of GroupPac services to implement CosNamingFT did not require any change in the COSS/OMG specifications. All services of this package are written in Java and the interfaces specified according to the IDL/OMG standard. We used Iona’s OrbixWeb [5], an ORB also written in Java giving us the benefit of OMG standards and Java portability.
Figure 11. CosNaming IDL.
Our implementation involves two software components: NameContextServant.jav a, which implements the CosNaming functionality described in the IDL specification, and NameContextServer.jav a,which is responsible for creating and starting the replicas of CosNamingFT including installing the primary’s IOR in the HTTP repository and starting GroupPac’s SS object. The NameContext interface is composed of
operations to connect (bind), to reconnect (rebind) or to disconnect (unbind) a name to an object, operations for reaching an object by using its name (resolve), and operations to create, destroy or list a context of names. In addition, up-call operations such as get_state() and set_state() are necessary for data transfers between the GroupPac services and the name service.
The IDL specifications for GroupPac services are presented in Figure 12. Each one of these interfaces is represented by a service object at runtime.
Figure 12. IDL for GroupPac services.
Each GroupPac service is a set of CORBA objects and as such communication between them is through the ORB. The IOR for each of these services (i.e., FDS, STS and SM) is stored in the AllServRefs structure of the MS. Access to these IORs is local and guaranteed by inheritance of the Membership Service interface. Thus, each service object can coordinate with its colleagues in the other CosNamingFT replicas by first getting the appropriate IOR from the remote CosNamingFT replica.
When a new replica tries to join to the group, its SS object creates (i.e., instantiates) the GroupPac service objects and puts its reference into ServiceRefs structure (Figure 12). Then, the SS object invokes the join_group() method of the primary MS object, sending the ServiceRefs structure. After the membership protocol has been executed and decided that the new replica can join the CosNamingFT group, the primary MS primary object disseminates the updated AllServRefs (including the ServiceRefs of the new member) to the other MS objects of the group by invoking the view_change() method.
The FDS service uses a simple “keep-alive” method, which each FDS group member invoking this method on its predecessor member of the virtual ring. An FDS member suspects its predecessor upon receiving a CORBA exception signaling a communication failure with the method invocation.
The Context variable is a Java hashtable and contains all object name-IOR bindings. The Context variable is the essential state that must be transferred to new NameContext group members, and that must be maintained consistently between the primary and its backups.
The STS methods get_state() and set_state() translate an object’s state (i.e., the Context variable) to or from a standard data format defined for state transfer using the STS. Since a Java hashtable is not defined within CORBA, we convert it to a sequence of bytes and treat it as a CORBA Any. In this way, when the STS object invokes the get_state() up-call in the NameContext object (Figure 10, step 5), it separates each binding in the Context variable and converts them to byte sequences.
To implement the interception shown in Figure 10 (step 2) we used OrbixWeb filters. A filter is a device that transparently traps the normal flow in a method invocation; it can be used to add functionality or extra control to a method call. The STS group within CosNamingFT is invoked using a post-marshalling filter to obtain the server object reply and extract the IOR of the primary replica.
5.CosNamingFT Performance Analyses
We now give performance measurements for CosNamingFT. These measurements were taken from the bind (install) and resolve (obtain) method invocations. We evaluate performance in scenarios with different degrees of replication. The execution environment is a local network (10 Mbps Ethernet) of heterogeneous
components: two Sun Ultra 1 running Solaris 2.5, one Axil 240 also running Solaris 2.5, one Pentium 100 and one Pentium 233 MMX, both running Linux and finally, one Pentium 233 MMX running Windows 95.
The tests consisted of one hundred bind operations and the same number of resolve operations. Figure 13 plots the response time as a function of replication degree using the average of these one hundred invocations for both operations. The bind operation curve shows a linear increase in the response time with degree of replication; the cost is about 7 milliseconds (ms). This occurs because the bind operation modifies the state of the NameContext object in the primary replica, making state updates necessary to each backup replica. As one would expect, the resolve operation is insensitive to replication degree.
Figure 13. CosNamingFT Performance.
The increase in slope between the fifth and sixth replicas for the bind operation is due to the sixth replica being run on the slower, Pentium 100 machine. A replication degree of three is more than likely sufficient for our purposes; we believe that 21.2 ms response time is indeed acceptable.
In comparison, the native OrbixWeb name service without replication executes bind and resolve operations in 2 ms.
The performance tests reported [7] for Electra’s replicatedname service were run on five Sparc 10 and four SparcStation 20 machines on a 10 Mbps Ethernet network, each running SunOS 4.1.3. Measurements indicated a per-replica overhead incurred by the bind operation of about 6 ms using Isis and about 1 ms using Horus/Ensemble. Well aware of the difficulties in comparing results given differences in hardware, operating systems, and so forth, we believe that the benefits seen in Electra over Ensemble are attributed to the highly-optimized group communication support provide by Ensemble underneath the ORB. In comparison, we implemented CosNamingFT service as a COSS object, with each GroupPac service object (e.g., membership, failure detection, communication) handled above the ORB. For instance, group communication is accomplished by CORBA-object to CORBA-object method invocations, which in OrbixWeb cost approximately 2 ms each (accessing to the HTTP server costs nearly 3 ms). This extra overhead is the reason for the relatively poor performance we observe, and is the cost of conforming to recommendations for common services in the CORBA specifications. Obviously, performance in this model is dependent on the ORB and could improve or deteriorate.
6.Conclusion
The original work on CosNamingFT was done in conjunction with the Nile project [3] at the University of Texas at Austin. Nile is a CORBA-based platform for integrated distributed processing of highly-parallel computations. The original model of fault-tolerant CORBA objects was jettisoned due to the immaturity of platforms, and a model based on COS persistence was adopted until more robust object replication strategies become available[13].
The work presented here aimed to verify the viability of implementing fault-tolerant mechanisms at the application level using standards-based middleware, open system concepts, and common object services. The implementation of this service may be used at no restriction on any CORBA platform allowing, for example, CORBA objects developed in C++ language or others to use this service.
The fault-tolerant extensions to CosNaming discussed here require no changes the CosNaming specification and may be used with no restrictions on any CORBA platform. The GroupPac services were inserted flexibly and transparently. The SS object defines which particular GroupPac object services are required to build the selected fault tolerance framework. Thus, whether one uses GroupPac services or not, there is no need to change the code that implements the name service itself. In addition, following OMG recommendations, all communication between object services is through the ORB and based on IIOP; we have used no communication mechanism that is not in compliance with this standard. OrbixWeb does restrict portability or restrict use of other CORBA/Java platforms. We believe the per-replica cost of our CosNamingFT implementation is not burden-some, though it will assuredly vary from ORB to ORB.
References
[1]K. P. Birman and R. van Renesse. Reliable Distributed
Computing with the Isis Toolki t. IEEE Computer Society
Press, 1994.
[2]N. Budhiraja, K. Marzullo, F. B. Schneider, and S.
Toueg. Distributed Systems (2nd Edition). Edited by S.
Mullende r, chapter 4. The Primary-Backup Approach.
Adison-Welsey, 1993.
[3] D. G. Cassel and M. Ogg. The Nile Project.
Descriptions, publications, and software available from
www.nile.cornell.ed u, 1999.
[4]P. Felber, R. Guerraoui, and A. Schiper. The
Implementation of a CORBA Object Group Service.
Theory and Practice of Object System s, 4(2):93–106,
1998.
[5]IONA Technologies, Ltd. OrbixWeb Programmer’s
Guide. Available from www.iona.co m, 1997.
[6]L. C. Lau, J. S. Fraga, and F. S. de Oliveira. Framework
to Support Implementing Fault Tolerant Applications in
CORBA. In Brasilian Symposium on Fault Tolerance -
SCTF 99. To appear. In Portuguese.
[7]S. Maffeis. A Fault-Tolerant CORBA Name Server. In
15th IEEE Symposium on Reliable Distributed System s,
pages 188–197, 1996.
[8]L. E. Moser, P. M. P. Melliar-Smith, and P. Narasimhan.
Consistent Object Replication in the Eternal System.
Theory and Practice of Object System s, 4(2):81–92,
1998.
[9]Object Management Group. The Common Object
Request Broker 2.0/IIOP Specification, Revision 2.0.
OMG Document 96-08-04. Available from
www.omg.or g, 1996.
[10]Object Management Group. CORBA Services: Common
Object Services Specification. OMG Document 97-xx-
yy. Available from www.omg.or g, 1997.
[11]Object Management Group. Fault-tolerant CORBA
Using Entity Redundancy (RFP). OMG Document 98-
04-01. Available from www.omg.or g, 1998.
[12] A. Ricciardi and K. Birman. Using Process Groups to
Implement Failure Detection in Asynchronous
Environments. In Tenth POD C, pages 341–351. ACM,
1991. (also Cornell University TR93-1328).
[13] A. Ricciardi, M. Ogg, and F. Previato. Experience with
Distributed Replicated Objects: The Nile Project. Theory
and Practice of Object System s, 4(2):107–117, 1998. [14]R. van Renesse, K. P. Birman, R. Friedman, M. Hayden,
and D. A. Karr. A Framework for Protocol Composition
in Horus. In 14th Principles of Distributed Computin g,
pages 80–89. ACM, 1995.
[15]R. van Renesse, K. P. Birman, and S. Maffeis. Horus: A
Flexible Group Communication System.
Communications of the AC M, 39(4):76–83, 1996.
习题1 选择题 (1) 一运动质点在某瞬时位于矢径),(y x r 的端点处，其速度大小为 (A)dt dr (B)dt r d (C)dt r d | | (D) 22)()(dt dy dt dx + [答案：D] (2) 一质点作直线运动，某时刻的瞬时速度s m v /2=，瞬时加速度2 /2s m a -=，则一秒钟后质点的速度 (A)等于零 (B)等于-2m/s (C)等于2m/s (D)不能确定。 [答案：D] (3) 一质点沿半径为R 的圆周作匀速率运动，每t 秒转一圈，在2t 时间间隔中，其平均速度大小和平均速率大小分别为 (A) t R t R ππ2, 2 (B) t R π2,0 (C) 0,0 (D) 0,2t R π [答案：B] 填空题 (1) 一质点，以1 -?s m π的匀速率作半径为5m 的圆周运动，则该质点在5s 内，位移的大小是 ；经过的路程是 。 [答案： 10m ； 5πm] (2) 一质点沿x 方向运动，其加速度随时间的变化关系为a=3+2t (SI)，如果初始时刻质点的速度v 0为5m·s -1，则当t 为3s 时，质点的速度v= 。 [答案： 23m·s -1 ] (3) 轮船在水上以相对于水的速度1V 航行，水流速度为2V ，一人相对于甲板以速度3V 行走。如人相对于岸静止，则1V 、2V 和3V 的关系是 。 [答案： 0321=++V V V ]
一个物体能否被看作质点，你认为主要由以下三个因素中哪个因素决定： (1) 物体的大小和形状； (2) 物体的内部结构； (3) 所研究问题的性质。 解：只有当物体的尺寸远小于其运动范围时才可忽略其大小的影响，因此主要由所研究问题的性质决定。 下面几个质点运动学方程，哪个是匀变速直线运动？ （1）x=4t-3；（2）x=-4t 3+3t 2+6；（3）x=-2t 2+8t+4；（4）x=2/t 2-4/t 。 给出这个匀变速直线运动在t=3s 时的速度和加速度，并说明该时刻运动是加速的还是减速的。（x 单位为m ，t 单位为s ） 解：匀变速直线运动即加速度为不等于零的常数时的运动。加速度又是位移对时间的两阶导数。于是可得（3）为匀变速直线运动。 其速度和加速度表达式分别为 2 2484 dx v t dt d x a dt = =+== t=3s 时的速度和加速度分别为v =20m/s ，a =4m/s 2。因加速度为正所以是加速的。 在以下几种运动中，质点的切向加速度、法向加速度以及加速度哪些为零哪些不为零？ (1) 匀速直线运动；(2) 匀速曲线运动；(3) 变速直线运动；(4) 变速曲线运动。 解：(1) 质点作匀速直线运动时，其切向加速度、法向加速度及加速度均为零； (2) 质点作匀速曲线运动时，其切向加速度为零，法向加速度和加速度均不为零； (3) 质点作变速直线运动时，其法向加速度为零，切向加速度和加速度均不为零； (4) 质点作变速曲线运动时，其切向加速度、法向加速度及加速度均不为零。 ｜r ?｜与r ? 有无不同?t d d r 和d d r t 有无不同? t d d v 和t d d v 有无不同?其不同在哪里?试举例说明． 解：（1）r ?是位移的模，?r 是位矢的模的增量，即r ?12r r -=，12r r r -=?； （2） t d d r 是速度的模，即t d d r ==v t s d d . t r d d 只是速度在径向上的分量. ∵有r r ?r =（式中r ?叫做单位矢），则 t ?r ?t r t d d d d d d r r r += 式中 t r d d 就是速度在径向上的分量，
变电所母线桥的动稳定校验 随着用电负荷的快速增长，许多变电所都对主变进行了增容，并对相关设备进行了调换和校验，但往往会忽视主变母线桥的动稳定校验，事实上此项工作非常重要。当主变增容后，由于阻抗发生了变化，短路电流将会增大许多，一旦发生短路，产生的电动力有可能会对母线桥产生破坏。特别是户内母线桥由于安装时受地理位置的限制，绝缘子间的跨距较长，受到破坏的可能性更大，所以应加强此项工作。 下面以我局35kV/10kv胡店变电所#2主变增容为例来谈谈如何进行主变母线桥的动稳定校验和校验中应注意的问题。 1短路电流计算 图1为胡店变电所的系统主接线图。(略) 已知#1主变容量为10000kVA，短路电压为7.42%，#2主变容量为12500kVA，短路电压为7.48%(增容前短路电压为7.73%)。 取系统基准容量为100MVA，则#1主变短路电压标么值 X1＝7.42/100×100×1000/10000＝0.742， #2主变短路电压标么值 X2＝7.48/100×100×1000/12500＝0.5984 胡店变电所最大运行方式系统到35kV母线上的电抗标么值为0.2778。 ∴#1主变与#2主变的并联电抗为： X12=X1×X2/(X1+X2)＝0.33125； 最大运行方式下系统到10kV母线上的组合电抗为： X＝0.2778+0.33125＝0.60875
∴10kV母线上的三相短路电流为：Id=100000/0.60875*√3*10.5，冲击电流：I sh=2.55I =23032.875A。 d 2动稳定校验 (1)10kV母线桥的动稳定校验： 进行母线桥动稳定校验应注意以下两点： ①电动力的计算，经过对外边相所受的力，中间相所受的力以及三相和二相电动力进行比较，三相短路时中间相所受的力最大，所以计算时必须以此为依据。 ②母线及其支架都具有弹性和质量，组成一弹性系统，所以应计算应力系数，计及共振的影响。根据以上两点，校验过程如下： 已知母线桥为8×80mm2的铝排，相间中心线间距离为210mm，先计算应力系数： ∵频率系数N f＝3.56，弹性模量E＝7×10.7 Pa，单位长度铝排质量M＝1.568kg/m，绝缘子间跨距2m，则一阶固有频率: f’=(N f/L2)*√(EI/M)=110Hz 查表可得动态应力系数β＝1.3。 ∴单位长度铝排所受的电动力为： f ph＝1.73×10-7I sh2/a×β＝568.1N/m ∵三相铝排水平布置，∴截面系数W＝bh2/6＝85333mm3，根据铝排的最大应力可确定绝缘子间允许的最大跨距为： L MAX=√10*σal*W/ f ph=3.24m ∵胡店变主变母线桥绝缘子间最大跨距为2m，小于绝缘子间的最大允许跨距。
电子电力课后习题答案 第一章电力电子器件 1.1 使晶闸管导通的条件是什么？ 答：使晶闸管导通的条件是：晶闸管承受正相阳极电压，并在门极施加触发电流（脉冲）。 或者U AK >0且U GK >0 1.2 维持晶闸管导通的条件是什么？怎样才能使晶闸管由导通变为关断？ 答：维持晶闸管导通的条件是使晶闸管的电流大于能保持晶闸管导通的最小电流，即维持电流。 1.3 图1－43中阴影部分为晶闸管处于通态区间的电流波形，各波形的电流最大值均为 I m ，试计算各波形的电流平均值I d1 、I d2 、I d3 与电流有效值I 1 、I 2 、I 3 。 解：a) I d1= Im 2717 .0 )1 2 2 ( 2 Im ) ( sin Im 2 1 4 ≈ + = ?π ω π π π t I 1= Im 4767 .0 2 1 4 3 2 Im ) ( ) sin (Im 2 1 4 2≈ + = ?π ? π π π wt d t b) I d2= Im 5434 .0 )1 2 2 ( 2 Im ) ( sin Im 1 4 = + = ?wt d t π π ? π I 2= Im 6741 .0 2 1 4 3 2 Im 2 ) ( ) sin (Im 1 4 2≈ + = ?π ? π π π wt d t c) I d3= ?= 2 Im 4 1 ) ( Im 2 1π ω π t d I 3= Im 2 1 ) ( Im 2 1 2 2= ?t dω π π 1.4.上题中如果不考虑安全裕量,问100A的晶阐管能送出的平均电流I d1、I d2 、I d3 各为多 少?这时，相应的电流最大值I m1、I m2 、I m3 各为多少? 解：额定电流I T(AV) =100A的晶闸管，允许的电流有效值I=157A,由上题计算结果知 a) I m1 35 . 329 4767 .0 ≈ ≈ I A, I d1 ≈0.2717I m1 ≈89.48A
习题1 1.1选择题 (1) 一运动质点在某瞬时位于矢径),(y x r 的端点处，其速度大小为 (A)dt dr (B)dt r d (C)dt r d | | (D) 22)()(dt dy dt dx + [答案：D] (2) 一质点作直线运动，某时刻的瞬时速度s m v /2=，瞬时加速度2 /2s m a -=，则一秒钟后质点的速度 (A)等于零 (B)等于-2m/s (C)等于2m/s (D)不能确定。 [答案：D] (3) 一质点沿半径为R 的圆周作匀速率运动，每t 秒转一圈，在2t 时间间隔中，其平均速度大小和平均速率大小分别为 (A) t R t R ππ2, 2 (B) t R π2,0 (C) 0,0 (D) 0,2t R π [答案：B] 1.2填空题 (1) 一质点，以1 -?s m π的匀速率作半径为5m 的圆周运动，则该质点在5s 内，位移的大小是 ；经过的路程是 。 [答案： 10m ； 5πm] (2) 一质点沿x 方向运动，其加速度随时间的变化关系为a=3+2t (SI)，如果初始时刻质点的速度v 0为5m·s -1，则当t 为3s 时，质点的速度v= 。 [答案： 23m·s -1 ] (3) 轮船在水上以相对于水的速度1V 航行，水流速度为2V ，一人相对于甲板以速度3V 行走。如人相对于岸静止，则1V 、2V 和3V 的关系是 。 [答案： 0321=++V V V ]
1.3 一个物体能否被看作质点，你认为主要由以下三个因素中哪个因素决定： (1) 物体的大小和形状； (2) 物体的内部结构； (3) 所研究问题的性质。 解：只有当物体的尺寸远小于其运动范围时才可忽略其大小的影响，因此主要由所研究问题的性质决定。 1.4 下面几个质点运动学方程，哪个是匀变速直线运动？ （1）x=4t-3；（2）x=-4t 3+3t 2+6；（3）x=-2t 2+8t+4；（4）x=2/t 2-4/t 。 给出这个匀变速直线运动在t=3s 时的速度和加速度，并说明该时刻运动是加速的还是减速的。（x 单位为m ，t 单位为s ） 解：匀变速直线运动即加速度为不等于零的常数时的运动。加速度又是位移对时间的两阶导数。于是可得（3）为匀变速直线运动。 其速度和加速度表达式分别为 2 2484 dx v t dt d x a dt = =+== t=3s 时的速度和加速度分别为v =20m/s ，a =4m/s 2。因加速度为正所以是加速的。 1.5 在以下几种运动中，质点的切向加速度、法向加速度以及加速度哪些为零哪些不为零？ (1) 匀速直线运动；(2) 匀速曲线运动；(3) 变速直线运动；(4) 变速曲线运动。 解：(1) 质点作匀速直线运动时，其切向加速度、法向加速度及加速度均为零； (2) 质点作匀速曲线运动时，其切向加速度为零，法向加速度和加速度均不为零； (3) 质点作变速直线运动时，其法向加速度为零，切向加速度和加速度均不为零； (4) 质点作变速曲线运动时，其切向加速度、法向加速度及加速度均不为零。 1.6 ｜r ?｜与r ? 有无不同?t d d r 和d d r t 有无不同? t d d v 和t d d v 有无不同?其不同在哪里?试举例说明． 解：（1）r ?是位移的模，?r 是位矢的模的增量，即r ?12r r -=，12r r r -=?； （2） t d d r 是速度的模，即t d d r ==v t s d d . t r d d 只是速度在径向上的分量. ∵有r r ?r =（式中r ?叫做单位矢），则 t ?r ?t r t d d d d d d r r r += 式中 t r d d 就是速度在径向上的分量，
电力电子技术期末考试 试题及答案 Coca-cola standardization office【ZZ5AB-ZZSYT-ZZ2C-ZZ682T-ZZT18】
电力电子技术试题 第1章电力电子器件 1.电力电子器件一般工作在__开关__状态。 2.在通常情况下，电力电子器件功率损耗主要为__通态损耗__，而当器件开关频率较高时，功率损耗主要为__开关损耗__。 3.电力电子器件组成的系统，一般由__控制电路__、_驱动电路_、_主电路_三部分组成，由于电路中存在电压和电流的过冲，往往需添加_保护电路__。 4.按内部电子和空穴两种载流子参与导电的情况，电力电子器件可分为_单极型器件_、_双极型器件_、_复合型器件_三类。 5.电力二极管的工作特性可概括为_承受正向电压导通，承受反相电压截止_。 6.电力二极管的主要类型有_普通二极管_、_快恢复二极管_、_肖特基二极管_。 7.肖特基二极管的开关损耗_小于_快恢复二极管的开关损耗。 8.晶闸管的基本工作特性可概括为__正向电压门极有触发则导通、反向电压则截止__。 9.对同一晶闸管，维持电流IH与擎住电流IL在数值大小上有IL__大于__IH 。 10.晶闸管断态不重复电压UDSM与转折电压Ubo数值大小上应为，UDSM_大于__Ubo。 11.逆导晶闸管是将_二极管_与晶闸管_反并联_（如何连接）在同一管芯上的功率集成器件。 的__多元集成__结构是为了便于实现门极控制关断而设计的。 的漏极伏安特性中的三个区域与GTR共发射极接法时的输出特性中的三个区域有对应关系，其中前者的截止区对应后者的_截止区_、前者的饱和区对应后者的__放大区__、前者的非饱和区对应后者的_饱和区__。 14.电力MOSFET的通态电阻具有__正__温度系数。 的开启电压UGE（th）随温度升高而_略有下降__，开关速度__小于__电力MOSFET 。 16.按照驱动电路加在电力电子器件控制端和公共端之间的性质，可将电力电子器件分为_电压驱动型_和_电流驱动型_两类。 的通态压降在1/2或1/3额定电流以下区段具有__负___温度系数，在1/2或1/3额定电流以上区段具有__正___温度系数。 18.在如下器件：电力二极管（Power Diode）、晶闸管（SCR）、门极可关断晶闸管（GTO）、电力晶体管（GTR）、电力场效应管（电力MOSFET）、绝缘栅双极型晶体管（IGBT）中，属于不可控器件的是_电力二极管__，属于半控型器件的是__晶闸管_，属于全控型器件的是_GTO 、GTR 、电力
母线电动力及动热稳定性计算 1 目的和范围 本文档为电气产品的母线电动力、动稳定、热稳定计算指导文件，作为产品结构设计安全指导文件的方案设计阶段指导文件，用于母线电动力、动稳定性、热稳定性计算的选型指导。 2 参加文件 表1 3 术语和缩略语 表2 4 母线电动力、动稳定、热稳定计算 4.1 载流导体的电动力计算 4.1.1 同一平面内圆细导体上的电动力计算
? 当同一平面内导体1l 和2l 分别流过1I 和2I 电流时（见图1），导体1l 上的电动力计 算 h F K I I 4210 π μ= 式中 F ——导体1l 上的电动力（N ） 0μ——真空磁导率，m H 60104.0-?=πμ； 1I 、2I ——流过导体1l 和2l 的电流（A ）； h K ——回路系数，见表1。 图1 圆细导体上的电动力 表1 回路系数h K 表 两导体相互位置及示意图 h K 平 行 21l l = ∞=1l 时，a l K h 2= ∞≠1l 时，?? ? ???-+=l a l a a l K h 2)(12 21l l ≠ 22 2) ()(1l a m l a l a K h ++-+= 22)()1(l a m +-- l a m =
? 当导体1l 和2l 分别流过1I 和2I 电流时，沿1l 导体任意单位长度上各点的电动力计 算 f 124K f I I d μ= π 式中 f ——1l 导体任意单位长度上的电动力（m N ）； f K ——与同一平面内两导体的长度和相互位置有关的系数，见表2。 表2 f K 系数表
4.1.2 两平行矩形截面导体上的电动力计算 两矩形导体（母线）在b ＜＜a ，且b ＞＞h 的情况下，其单位长度上的电动力F 的 计算见表3。 当矩形导体的b 与a 和h 的尺寸相比不可忽略时，可按下式计算 712 210x L F I I K a -=? 式中 F -两导体相互作用的电动力，N ； L -母线支承点间的距离，m ； a -导体间距，m ； 1I 、2I -流过两个矩形母线的电流，A ； x K -导体截面形状系数； 表3 两矩形导体单位长度上的电动力 4.1.3 三相母线短路时的电动力计算
电力电子技术答案 2-1与信息电子电路中的二极管相比，电力二极管具有怎样的结构特点才使得其具有耐受高压和大电流的能力？ 答：1.电力二极管大都采用垂直导电结构，使得硅片中通过电流的有效面积增大，显著提高了二极管的通流能力。 2.电力二极管在P 区和N 区之间多了一层低掺杂N 区，也称漂移区。低掺杂N 区由于掺杂浓度低而接近于无掺杂的纯半导体材料即本征半导体，由于掺杂浓度低，低掺杂N 区就可以承受很高的电压而不被击穿。 2-2. 使晶闸管导通的条件是什么？ 答：使晶闸管导通的条件是：晶闸管承受正向阳极电压，并在门极施加触发电流（脉冲）。或：uAK>0且uGK>0。 2-3. 维持晶闸管导通的条件是什么？怎样才能使晶闸管由导通变为关断？ 答：维持晶闸管导通的条件是使晶闸管的电流大于能保持晶闸管导通的最小电流，即维持电流。 要使晶闸管由导通变为关断， 可利用外加电压和外电路的作用使流过晶闸管的电流降 到接近于零的某一数值以下，即降到维持电流以下，便可使导通的晶闸管关断。 2-4图2-27中阴影部分为晶闸管处于通态区间的电流波形，各波形的电流最大值均为I m ，试计算各波形的电流平均值I d1、I d2、I d3与电流有效值I 、I 、I 。 πππ4 π4 π2 5π4a) b)c) 图1-43 图2-27 晶闸管导电波形 解：a) I d1= π21?π πωω4 )(sin t td I m =π2m I (122+)≈0.2717 I m I 1= ?π πωωπ 4 2 )()sin (21 t d t I m =2m I π 2143+≈0.4767 I m b) I d2 = π1?π πωω4)(sin t td I m =π m I ( 12 2 +)≈0.5434 I m I 2 = ? π π ωωπ 4 2) ()sin (1 t d t I m = 2 2m I π 21 43+ ≈0.6741I m c) I d3=π21?2 )(π ωt d I m =41 I m I 3 =? 2 2 ) (21π ωπt d I m = 2 1 I m 2-5上题中如果不考虑安全裕量,问100A 的晶阐管能送出的平均电流I d1、I d2、I d3各为多少?这时，相应的电流最大值I m1、I m2、 I m3各为多少? 解：额定电流I T(AV)=100A 的晶闸管，允许的电流有效值I=157A,由上题计算结果知 a) I m1≈4767.0I ≈329.35， I d1≈0.2717 I m1≈89.48 b) I m2≈ 6741 .0I ≈232.90, I d2≈0.5434 I m2≈126.56 c) I m3=2 I = 314, I d3= 4 1 I m3=78.5 2-6 GTO 和普通晶闸管同为PNPN 结构,为什么GTO 能够自关断,而普通晶闸管不能? 答：GTO 和普通晶阐管同为PNPN 结构，由P1N1P2和N1P2N2构成两个晶体管V1、V2，分别具有共基极电流增益 1α和2α， 由普通晶阐管的分析可得， 121=+αα是器件临界导通的条件。1 21＞αα+两个等效晶体管过饱和而导通；
《电力电子技术》试卷1答案 一、填空（每空1分，36分） 1、请在正确的空格内标出下面元件的简称： 电力晶体管GTR；可关断晶闸管GTO；功率场效应晶体管MOSFET；绝缘栅双极型晶体管IGBT；IGBT是MOSFET和GTR的复合管。 2、晶闸管对触发脉冲的要求是要有足够的驱动功率、触发脉冲前沿要陡幅值要高和触发脉冲要与晶闸管阳极电压同步。 3、多个晶闸管相并联时必须考虑均流的问题，解决的方法是串专用均流电抗器。 4、在电流型逆变器中，输出电压波形为正弦波，输出电流波形为方波。 5、型号为KS100-8的元件表示双向晶闸管晶闸管、它的额定电压为800V伏、额定有效电流为100A。 6、180°导电型三相桥式逆变电路，晶闸管换相是在同一桥臂上的上、下二个元件之间进行；而120o导电型三相桥式逆变电路，晶闸管换相是在不同桥臂上的元件之间进行的。 7、当温度降低时，晶闸管的触发电流会增加、正反向漏电流会下降；当温度升高时，晶闸管的触发电流会下降、正反向漏电流会增加。 8、在有环流逆变系统中，环流指的是只流经逆变电源、逆变桥而不流经负载的电流。环流可在电路中加电抗器来限制。为了减小环流一般采控用控制角α大于β的工作方式。 9、常用的过电流保护措施有快速熔断器、串进线电抗器、接入直流快速开关、控制快速移相使输出电压下降。（写出四种即可） 10、双向晶闸管的触发方式有Ⅰ+、Ⅰ-、Ⅲ＋、Ⅲ-四种。 二、判断题,（每题1分，10分）（对√、错×） 1、在半控桥整流带大电感负载不加续流二极管电路中，电路出故障时会出现失 控现象。（√） 2、在用两组反并联晶闸管的可逆系统，使直流电动机实现四象限运行时，其中 一组逆变器工作在整流状态，那么另一组就工作在逆变状态。（×） 3、晶闸管串联使用时，必须注意均流问题。（×） 4、逆变角太大会造成逆变失败。（×） 5、并联谐振逆变器必须是略呈电容性电路。（√） 6、给晶闸管加上正向阳极电压它就会导通。（×） 7、有源逆变指的是把直流电能转变成交流电能送给负载。（×） 8、在单相全控桥整流电路中，晶闸管的额定电压应取U2。（×） 9、在三相半波可控整流电路中，电路输出电压波形的脉动频率为300Hz。（×） 10、变频调速实际上是改变电动机内旋转磁场的速度达到改变输出转速的目的。 （√） 三、选择题（每题3分，15分）
筠连县分水岭煤业有限责任公司 井 下 高 压 电 缆 热 稳 定 性 校 验 计 算 书 巡司二煤矿 编制：机电科 筠连县分水岭煤业有限责任公司
井下高压电缆热稳定校验计算书 一、概述： 根据《煤矿安全规程》第453条及456条之规定，对我矿入井高压电缆进行热稳定校验。 二、确定供电方式 我矿高压供电采用分列运行供电方式，地面变电所、井下变电所均采用单母线分段分列供电方式运行，各种主要负荷分接于不同母线段。 三、井下高压电缆明细： 矿上有两趟主进线，引至巡司变电站不同母线段，一趟931线，另一趟925线。井下中央变电所由地面配电房10KV输入。 入井一回路：MYJV22-8.7/10KV 3*50mm2--800m(10KV) 入井二回路：MYJV22-8.7/10KV 3*50mm2--800m(10KV) 四、校验计算 1、井下入井回路高压电缆热稳定性校验 已知条件：该条高压电缆型号为，MYJV22-8.7/10KV 3*50mm2 ,800m，电缆长度为800m=0.8km。 （1）计算电网阻抗 查附表一，短路电流的周期分量稳定性为 电抗：X=0.072*0.8=0.0576Ω； 电阻：R=0.407*0.8=0.3256 Ω； (2)三相短路电流的计算
A Z I 5.174693305 .0310000 3v 3=?== ∞ （3）电缆热稳定校验 由于断路器的燃弧时间及固有动作时间之和约为t=0.05S; 查附表二得热稳定计算系数取K=142; 故电缆最小热值稳定截面为 23mm 51.2705.0142/5.17469t )/(min ===∞）（K I S Smin<50mm 2 故选用 MYJV 22 -8.7/10KV 3*50 电缆热稳定校验合格，符合要求。 附表一：三相电缆在工作温度时的阻抗值（Ω/Km ） 电缆截面S （mm 2 ） 4 6 10 16 2 5 35 50 70 95 120 150 185 240 交联聚乙烯 R 4.988 3.325 2.035 1.272 0.814 0.581 0.407 0.291 0.214 0.169 0.136 0.11 0.085 X 0.093 0.093 0.087 0.082 0.075 0.072 0.072 0.069 0.069 0.069 0.07 0.07 0.07 附表二 不同绝缘导体的热稳定计算系数 绝缘材料 芯线起始温度（° C ） 芯线最高允许温度（°C ） 系数K 聚氯乙烯 70 160 115（114） 普通橡胶 75 200 131 乙丙橡胶 90 250 143（142） 油浸纸绝缘 80 160 107 交联聚乙烯 90 250 142
0-1.什么是电力电子技术? 电力电子技术是应用于电力技术领域中的电子技术；它是以利用大功率电子器件对能量进行变换和控制为主要内容的技术。国际电气和电子工程师协会（IEEE）的电力电子学会对电力电子技术的定义为：“有效地使用电力半导体器件、应用电路和设计理论以及分析开发工具，实现对电能的高效能变换和控制的一门技术，它包括电压、电流、频率和波形等方面的变换。” 0-2.电力电子技术的基础与核心分别是什么? 电力电子器件是基础。电能变换技术是核心. 0-3.请列举电力电子技术的 3 个主要应用领域。 电源装置;电源电网净化设备;电机调速系统;电能传输和电力控制;清洁能源开发和新蓄能系统;照明及其它。 0-4.电能变换电路有哪几种形式?其常用基本控制方式有哪三种类型? AD-DC整流电;DC-AC逆变电路;AC-AC交流变换电路;DC-DC直流变换电路。 常用基本控制方式主要有三类：相控方式、频控方式、斩控方式。 0-5.从发展过程看，电力电子器件可分为哪几个阶段? 简述各阶段的主要标志。可分为：集成电晶闸管及其应用；自关断器件及其应用；功率集成电路和智能功率器件及其应用三个发展阶段。集成电晶闸管及其应用：大功率整流器。自关断器件及其应用：各类节能的全控型器件问世。功率集成电路和智能功率器件及其应用：功率集成电路（PIC），智能功率模块（IPM）器件发展。 0-6.传统电力电子技术与现代电力电子技术各自特征是什么? 传统电力电子技术的特征：电力电子器件以半控型晶闸管为主，变流电路一般 为相控型，控制技术多采用模拟控制方式。 现代电力电子技术特征：电力电子器件以全控型器件为主，变流电路采用脉宽 调制型，控制技术采用PWM数字控制技术。 0-7.电力电子技术的发展方向是什么? 新器件：器件性能优化，新型半导体材料。高频化与高效率。集成化与模块化。数字化。绿色化。 1-1.按可控性分类，电力电子器件分哪几类? 按可控性分类，电力电子器件分为不可控器件、半控器件和全控器件。 1-2.电力二极管有哪些类型?各类型电力二极管的反向恢复时间大约为多少? 电力二极管类型以及反向恢复时间如下： 1）普通二极管，反向恢复时间在5us以上。 2）快恢复二极管，反向恢复时间在5us以下。快恢复极管从性能上可分为快速恢复和超快速恢复二极管。前者反向恢复时间为数百纳秒或更长，后者在100ns 以下，甚至达到20~30ns，多用于高频整流和逆变电路中。 3）肖特基二极管，反向恢复时间为10～40ns。 1-3.在哪些情况下，晶闸管可以从断态转变为通态? 维持晶闸管导通的条件是什么? 1、正向的阳极电压； 2、正向的门极电流。两者缺一不可。阳极电流大于维持电流。
习题1 1.1选择题 (1) 一运动质点在某瞬时位于矢径),(y x r 的端点处，其速度大小为 (A)dt dr (B)dt r d (C)dt r d | | (D) 22)()(dt dy dt dx + [答案：D] (2) 一质点作直线运动，某时刻的瞬时速度s m v /2=，瞬时加速度2 /2s m a -=，则 一秒钟后质点的速度 (A)等于零 (B)等于-2m/s (C)等于2m/s (D)不能确定。 [答案：D] (3) 一质点沿半径为R 的圆周作匀速率运动，每t 秒转一圈，在2t 时间间隔中，其平均速度大小和平均速率大小分别为 (A) t R t R ππ2, 2 (B) t R π2,0 (C) 0,0 (D) 0,2t R π [答案：B] 1.2填空题 (1) 一质点，以1 -?s m π的匀速率作半径为5m 的圆周运动，则该质点在5s 内，位移的大小是 ；经过的路程是 。 [答案： 10m ； 5πm] (2) 一质点沿x 方向运动，其加速度随时间的变化关系为a=3+2t (SI)，如果初始时刻质点的 速度v 0为5m ·s -1 ，则当t 为3s 时，质点的速度v= 。 [答案： 23m ·s -1 ] (3) 轮船在水上以相对于水的速度1V 航行，水流速度为2V ，一人相对于甲板以速度3V 行走。如人相对于岸静止，则1V 、2V 和3V 的关系是 。 [答案： 0321=++V V V ]
1.3 一个物体能否被看作质点，你认为主要由以下三个因素中哪个因素决定： (1) 物体的大小和形状； (2) 物体的内部结构； (3) 所研究问题的性质。 解：只有当物体的尺寸远小于其运动范围时才可忽略其大小的影响，因此主要由所研究问题的性质决定。 1.4 下面几个质点运动学方程，哪个是匀变速直线运动？ （1）x=4t-3；（2）x=-4t 3+3t 2+6；（3）x=-2t 2+8t+4；（4）x=2/t 2 -4/t 。 给出这个匀变速直线运动在t=3s 时的速度和加速度，并说明该时刻运动是加速的还是减速的。（x 单位为m ，t 单位为s ） 解：匀变速直线运动即加速度为不等于零的常数时的运动。加速度又是位移对时间的两阶导数。于是可得（3）为匀变速直线运动。 其速度和加速度表达式分别为 2 2484 dx v t dt d x a dt = =+== t=3s 时的速度和加速度分别为v =20m/s ，a =4m/s 2 。因加速度为正所以是加速的。 1.5 在以下几种运动中，质点的切向加速度、法向加速度以及加速度哪些为零哪些不为零？ (1) 匀速直线运动；(2) 匀速曲线运动；(3) 变速直线运动；(4) 变速曲线运动。 解：(1) 质点作匀速直线运动时，其切向加速度、法向加速度及加速度均为零； (2) 质点作匀速曲线运动时，其切向加速度为零，法向加速度和加速度均不为零； (3) 质点作变速直线运动时，其法向加速度为零，切向加速度和加速度均不为零； (4) 质点作变速曲线运动时，其切向加速度、法向加速度及加速度均不为零。 1.6 ｜r ?｜与r ? 有无不同?t d d r 和d d r t 有无不同? t d d v 和t d d v 有无不同?其不同在哪里?试举例说明． 解：（1）r ?是位移的模，?r 是位矢的模的增量，即r ?12r r -=，12r r r -=?； （2） t d d r 是速度的模，即t d d r ==v t s d d . t r d d 只是速度在径向上的分量. ∵有r r ?r =（式中r ?叫做单位矢），则 t ?r ?t r t d d d d d d r r r += 式中 t r d d 就是速度在径向上的分量，
井下高压开关、供电电缆动热稳定性校验 一、-350中央变电所开关断路器开断能力及电缆热稳定性校验 1 23 G 35kV 2 Uz%=7.5△P N.T =12kW △P N.T =3.11kW S N.T =8MVA 6kV S1点三相短路电流计算： 35kV 变压器阻抗： 2 22.1. u %7.5 6.30.37()1001008z N T N T U Z S ?===Ω? 35kV 变压器电阻：2 22.1.22. 6.30.0120.007()8 N T N T N T U R P S =?=?=Ω 35kV 变压器电抗：10.37()X = ==Ω 电缆电抗：02(x )0.415000.08780 0.66()1000 1000i L X ??+?== =Ω∑ 电缆电阻：02(x )0.11815000.118780 0.27()1000 1000 i L R ??+?== =Ω∑ 总阻抗： 21.370.66) 1.06( Z ==Ω S1点三相短路电流：(3)1 3.43()d I KA === S2点三相短路电流计算： S2点所用电缆为MY-3×70+1×25，长400米，变压器容量为500KV A ，查表的：(2)2d I =2.5KA
S2点三相短路电流：32 d d =2.88I I KA = 1、架空线路、入井电缆的热稳定性校验。已知供电负荷为3128.02KV A ，电压为6KV ，需用系数0.62，功率因数cos 0.78φ=，架空线路长度1.5km ，电缆长度780m (1)按经济电流密度选择电缆，计算容量为 3128.020.62 2486.37cos 0.78 kp S KVA φ?= ==。 电缆的长时工作电流Ig 为239.25 Ig === A 按长时允许电流校验电缆截面查煤矿供电表5-15得MYJV42-3×185-6/6截面长时允许电流为479A/6kV 、大于239.25A 符合要求。 (2)按电压损失校验，配电线路允许电压损失5%得 60000.1300Uy V ?=?=，线路的实际电压损失 109.1L U COS DS φφ?====，U ?小于300V 电压损失满足要求 (3)热稳定性条件校验，短路电流的周期分量稳定性为 电缆最小允许热稳定截面积： 3 2min d =S I mm 其中：i t ----断路器分断时间，一般取0.25s ； C----电缆热稳定系数，一般取100，环境温度35℃，电缆温升不超过120℃时，铜芯电缆聚乙烯电缆熔化温度为130℃，电
第二章： 1.晶闸管的动态参数有断态电压临界上升率du/dt和通态电流临界上升率等，若 du/dt过大，就会使晶闸管出现_ 误导通_，若di/dt过大，会导致晶闸管_损坏__。 2.目前常用的具有自关断能力的电力电子元件有电力晶体管、可关断晶闸管、 功率场效应晶体管、绝缘栅双极型晶体管几种。简述晶闸管的正向伏安特性 答: 晶闸管的伏安特性 正向特性当IG=0时，如果在器件两端施加正向电压，则晶闸管处于正向阻断状态，只有很小的正向漏电流流过。 如果正向电压超过临界极限即正向转折电压Ubo，则漏电流急剧增大，器件开通。 随着门极电流幅值的增大，正向转折电压降低，晶闸管本身的压降很小，在1V左右。 如果门极电流为零，并且阳极电流降至接近于零的某一数值IH以下，则晶闸管又回到正向阻断状态，IH称为维持电流。 3.使晶闸管导通的条件是什么 答：使晶闸管导通的条件是：晶闸管承受正向阳极电压，并在门极施加触发电流（脉冲）。或：uAK>0且uGK>0。 4.在如下器件：电力二极管（Power Diode）、晶闸管（SCR）、门极可关断晶闸管 （GTO）、电力晶体管（GTR）、电力场效应管（电力MOSFET）、绝缘栅双极型晶体管（IGBT）中，属于半控型器件的是 SCR 。 5.晶闸管的擎住电流I L 答：晶闸管刚从断态转入通态并移除触发信号后，能维持导通所需的最小电流。 6.晶闸管通态平均电流I T(AV) 答：晶闸管在环境温度为40C和规定的冷却状态下，稳定结温不超过额定结温时所允许流过的最大工频正弦半波电流的平均值。标称其额定电流的参数。 7.晶闸管的控制角α（移相角） 答：从晶闸管开始承受正向阳极电压起到施加触发脉冲止的电角度,用a表示,也称触发角或控制角。
《电力电子技术》试卷 一．填空（共15分，1分/空） 1.电力电子技术通常可分为（）技术和（）技术两个分支。 2.按驱动电路信号的性质可以将电力电子器件分为（）型器件和（）型器件两类，晶闸管属于其中的（）型器件。 3.晶闸管单相桥式全控整流电路带反电动势负载E时（变压器二次侧电压有效值为U ，忽略主电路 2 各部分的电感），与电阻负载时相比，晶闸管提前了电角度δ停止导电，δ称为（）角，数量关系为δ=（）。 4.三相桥式全控整流电路的触发方式有（）触发和（）触发两种，常用的是（）触发。 5.三相半波可控整流电路按联接方式可分为（）组和（）组两种。 6.在特定场合下，同一套整流电路即可工作在（）状态，又可工作在（）状态，故简称变流电路。 7.控制角α与逆变角β之间的关系为（）。 二．单选（共10分，2分/题） 1．采用（）是电力电子装置中最有效、应用最广的一种过电流保护措施。 A.直流断路器 B. 快速熔断器 C.过电流继电器 2．晶闸管属于（）。 A.不可控器件 B. 全控器件 C.半控器件 3．单相全控桥式整流电路，带阻感负载（L足够大）时的移相范围是（）。 A．180O B.90O C.120O 4．对三相全控桥中共阴极组的三个晶闸管来说，正常工作时触发脉冲相位应依次差（）度。 A.60 B. 180 C. 120 5．把交流电变成直流电的是（）。 A. 逆变电路 B.整流电路 C.斩波电路 三．多选（共10分，2分/题） 1．电力电子器件一般具有的特征有。 A.所能处理电功率的大小是其最重要的参数 B.一般工作在开关状态 C.一般需要信息电子电路来控制 D.不仅讲究散热设计，工作时一般还需接散热器 2．下列电路中，不存在变压器直流磁化问题的有。 A.单相全控桥整流电路 B.单相全波可控整流电路 C.三相全控桥整流电路 D.三相半波可控整流电路 3．使晶闸管关断的方法有。 A.给门极施加反压 B.去掉阳极的正向电压 C.增大回路阻抗 D.给阳极施加反压 4．逆变失败的原因有。 A.触发电路不可靠 B.晶闸管发生故障 C.交流电源发生故障 D.换相裕量角不足 5．变压器漏抗对整流电路的影响有。 A.输出电压平均值降低 B.整流电路的工作状态增多 C.晶闸管的di/dt减小 D.换相时晶闸管电压出现缺口 四．判断（共5分,1分/题） 1.三相全控桥式整流电路带电阻负载时的移相范围是150O。（） 2.晶闸管是一种四层三端器件。（）
*作品编号：DG13485201600078972981* 创作者：玫霸* 筠连县分水岭煤业有限责任公司 井 下 高 压 电 缆 热 稳 定 性 校 验 计 算 书 巡司二煤矿
编制：机电科 筠连县分水岭煤业有限责任公司 井下高压电缆热稳定校验计算书 一、概述： 根据《煤矿安全规程》第453条及456条之规定，对我矿入井高压电缆进行热稳定校验。 二、确定供电方式 我矿高压供电采用分列运行供电方式，地面变电所、井下变电所均采用单母线分段分列供电方式运行，各种主要负荷分接于不同母线段。 三、井下高压电缆明细： 矿上有两趟主进线，引至巡司变电站不同母线段，一趟931线，另一趟925线。井下中央变电所由地面配电房10KV输入。 入井一回路：MYJV22-8.7/10KV 3*50mm2--800m(10KV) 入井二回路：MYJV22-8.7/10KV 3*50mm2--800m(10KV) 四、校验计算 1、井下入井回路高压电缆热稳定性校验 已知条件：该条高压电缆型号为，MYJV22-8.7/10KV 3*50mm2 ,800m，电缆长度为800m=0.8km。 （1）计算电网阻抗 查附表一，短路电流的周期分量稳定性为
电抗：X=0.072*0.8=0.0576Ω； 电阻：R=0.407*0.8=0.3256 Ω； (2)三相短路电流的计算 （3）电缆热稳定校验 由于断路器的燃弧时间及固有动作时间之和约为t=0.05S; 查附表二得热稳定计算系数取K=142; 故电缆最小热值稳定截面为 Smin<50mm2故选用 MYJV22 -8.7/10KV 3*50 电缆热稳定校验合格，符合要求。 附表一：三相电缆在工作温度时的阻抗值（Ω/Km）
20××－20××学年第一学期期末考试 《电力电子技术》试卷(A) （时间90分钟 满分100分） （适用于 ××学院 ××级 ××专业学生） 一、 填空题（30分,每空1分）。 1．如下器件：电力二极管（Power Diode ）、晶闸管（SCR ）、门极可关断晶闸管（GTO ）、电力晶体管（GTR ）、电力场效应管（电力MOSFET ）、绝缘栅双极型晶体管（IGBT ）中，属于不可控器件的是________，属于半控型器件的是________，属于全控型器件的是________；属于单极型电力电子器件的有________，属于双极型器件的有________，属于复合型电力电子器件得有 ________；在可控的器件中，容量最大的是________，工作频率最高的是________，属于电压驱动的是________，属于电流驱动的是________。（只写简称） 2．单相桥式全控整流电路中，带纯电阻负载时，α角移相范围为 _，单个晶闸管所承受的最大正向电压和反向电压分别为 和 ；带阻感负载时，α角移相范围为 ，单个晶闸管所承受的最大正向电压和反向电压分别为 和 。 3．直流斩波电路中最基本的两种电路是 和 。 4．升降压斩波电路呈现升压状态时，占空比取值范围是__ _。 5．与CuK 斩波电路电压的输入输出关系相同的有 、 和 。 6．当采用6脉波三相桥式电路且电网频率为50Hz 时，单相交交变频电路的输出上限频率约为 。 7．三相交交变频电路主要有两种接线方式，即 _和 。 8．矩阵式变频电路是近年来出现的一种新颖的变频电路。它采用的开关器件是 ；控制方式是 。 9．逆变器按直流侧提供的电源的性质来分，可分为 型逆变器和 型逆变器。 10．把电网频率的交流电直接变换成可调频率的交流电的变流电路称为 。 二、简答题（18分,每题6分）。 1．逆变电路多重化的目的是什么？如何实现？串联多重和并联多重逆变电路各应用于什么场合？ 2．交流调压电路和交流调功电路有什么异同？ 3．功率因数校正电路的作用是什么？有哪些校正方法？其基本原理是什么？ 三、计算题（40分，1题20分，2题10分，3题10分）。 1．一单相交流调压器，电源为工频220V ，阻感串联作为负载，其中R=0.5Ω，L=2mH 。 试求：①开通角α的变化范围；②负载电流的最大有效值；③最大输出功率及此时电源侧的功率因数；④当2πα＝时，晶闸管电流有效值，晶闸管导通角和电源侧功率因数。 2．.三相桥式电压型逆变电路，工作在180°导电方式，U d =200V 。试求输出相电压的基波幅值U UN1m 和有效值U UN1、输出线电压的基波幅值U UV1m 和有效值U UV1、输出线电压中7次谐波的有效值U UV7。 3 ．如图所示降压斩波电路E=100V ，L 值极大，R=0.5Ω，E m =10V ，采用脉宽调制控制方式，T=20μs ，当t on =5μs 时，计算输出电压平均值U o ，输出电流平均值