（1）整车动力性需求功率验算 1）最高车速对应的功率需求计算 最高车速时，车辆主要受到滚动阻力和风阻的影响，忽略坡度阻力的情况下，最 大需求功率 _ maxm vP 为 2 max max _ max ( ) 3600 21.15 d m v v C Av P mgf     ································ (4.1) 其中， max v 为最高车速；   为系统效率；m 为在原车整备质量基础上加载 165kg 后的质量。根据目标车型的基本参数可以得到在最高车速下的功率需求约为 45kW。 2）最大爬坡度对应的功率需求计算 以稳定车速 0 v 通过 max  的坡度时，车辆所需功率 0_ v P  为 0 2 minmin _ max max ( cos sin ) 3600 21.15 d v C Avv P mgf mg         ···················· (4.2) 取最大坡度为 30 度， max max arctan  。最低通过车速为 20km/h 时，所需功率为 36.3kW。 3）加速时间对应的功率需求计算 车辆加速过程中，所受到的阻力主要包括滚阻、风阻以及加速阻力，忽略坡路阻 力，加速后期所需功率最大，此时的加速功率需求 acc P 为 2 ( ) 3600 21.15 d acc f w j C Avv dv P P P P mgf m dt          ····················· (4.3) 其中， 为旋转质量换算系数； v为加速后期车速； dv dt 为加速后期加速度。 在初步验算过程中，为了简化计算，采用一种常用的等效方式表达加速过程中的 车速与加速末时车速和加速时间的关系，如式 4.4 所示[37] ( ) a m m t v v t  ································ ·············· (4.4) 其中， m v 为车辆加速后期车速； m t 为加速时间； a 为拟合系数，通常取为 0.5。 由此可得，加速时间需求功率为 3 2 1 ( ) 3600 1.5 52.875 7.2 m d m m acc m m m v C Av v P mgf t t m t      ························ (4.5) 初步估算得加速功率需求为 72.6kW，大于其他两个动力指标下的功率需求。 （2）基速比选择及电机功率需求计算

17.1 在线监控 17.1.1 切换主机的运转/停止状态 在进行测试与除错的过程中，须要经常性地改变主机的运行状态，而透过 ISPSoft，我们可轻易的进 行切换。在操作前，请确认目前 ISPSoft已可与主机正常联机，详细说明请参考第 2.4节。 于功能工具栏中点选 PLC 主机（P） > 运行（R），或按下图示工具栏的 图标可将主机切换至 RUN 的状态；而于功能工具栏中点选 PLC主机（P） > 停止（S），或按下图示工具栏的 图标 则可重新将主机切换至 STOP状态。 透过 ISPSoft 来切换主机的状态时，并不用考虑主机本体的 RUN/STOP 开关位置；且由 ISPSoft 下 达 RUN/STOP命令后，若再次切换主机本体的 RUN/STOP开关时还是可以变更主机的运行状态。 17.1.2 在线监控的功能与环境介绍 当 ISPSoft已可与主机正常联机后，我们便可经由在线监控模式来对 PLC 的执行状况进行监控。关于 主机与 ISPSoft之间的联机设定方式请参考第 2.4 节的内容。 在 ISPSoft中，在线监控的模式又可分为「装置监控」与「程序监控」。 监控模式 说明 装置监控 可透过监控表来实时监控主机目前的装置状态，且在此模式下，ISPSoft仅需更 新装置状态，因此目前 ISPSoft所开启的程序与主机内部的程序无须一致。 程序监控 在此模式下，系统会实时将程序的运作状况显示于程序画面中，也因此系统会要 求目前 ISPSoft所开启的程序必须与主机内部的程序一致。 *.装置监控模式可单独启动，而程序监控模式则必须伴随装置监控模式一起启动。

Cisco.Press.Cisco ASA PIX and FWSM Handbook 2nd Edition.pdf

第二版，oreilly,java servlet programming

图3.25 动力电池循环寿命与温度关系 从试验结果可以看出，动力电池的循环寿命随着使用环境温度的升高而逐渐减少。 另外，通过文献[123]的试验结果（如图 3.25（b）所示）还可以看出，在 20℃左右时， 电池的循环寿命次数达到最大。因而通常将动力电池的温度区间定义为 20~40℃左右。 3）放电深度（DOD）和倍率，放电深度和放电倍率是电池在使用过程中的两个 关键控制参数。处于不同放电深度下即 SOC 状态时的电池活性物质以及电解液浓度等 均有所不同，由此会对电池的电化学反应过程产生影响，多次循环后产生明显不同的 容量衰减性能；而放电倍率主要会影响电池的极化程度，放电倍率越大极化现象（极 化电势）即越明显，电池系统会越偏离平衡状态，由此带来电池极板的加速老化，缩 短电池寿命。 纯电动汽车用动力电池属于能量型电池，其正常的充放电倍率一般在±3C 以内， 在这样的放电倍率下，由放电倍率对循环寿命造成的影响基本可以忽略不计。文献[123] 针对 CBP2450 型号的动力电池组进行不同倍率下的循环放电试验结果如图 3.26 所示。 而在 HEV 的应用中，放电倍率可达到 10C，此时倍率的影响则不容被忽视[124]。 图3.26 不同充放电倍率对电池寿命的影响 为了验证放电深度对循环寿命的影响，文献[125]设计了如图 3.27（a）所示的循

The Scientist and Engineer's Guide to Digital Signal Processing Second Edition This book was written for scientists and engineers in a wide variety of fields: physics, bioengineering, geology, oceanography, mechanical and electrical engineering, to name just a few. The goal is to present practical techniques while avoiding the barriers of detailed mathematics and abstract theory.

Unity in Action Multiplatform game development in C#(2nd) 英文无水印原版pdf 第2版 pdf所有页面使用FoxitReader、PDF-XChangeViewer、SumatraPDF和Firefox测试都可以打开 本资源转载自网络，如有侵权，请联系上传者或csdn删除查看此书详细信息请在美国亚马逊官网搜索此书

2.1 纯电动汽车结构及运动力学特性 2.1.1 典型纯电动汽车结构及动力系统应用发展趋势 纯电动汽车的结构型式较为灵活，目前主要包括电机中央驱动和电动轮驱动两种。 其中，电动机中央驱动还包括有无传动轴的前驱、后驱等多种型式，而电动轮也分为 两轮和四轮驱动型式，包括轮边驱动和轮毂驱动两种。目前纯电动汽车仍处于产业化 的初级阶段，在传统内燃机汽车基础上进行电气化改装实现单能量源供电、单电机驱 动的结构型式仍最为普遍，该种方式可以较好的利用传统内燃机汽车的技术经验和产 品平台，通过较少的设计改进即可完成搭载式纯电动汽车的开发，以缩短样车开发的 周期，快速完成对纯电驱动技术的研究和验证。另外，在此基础上，也可以较为方便 的对电池布置以及专用减速器等进行有针对性的设计优化和二次开发，使其结构和设 计更适应纯电动汽车的技术特点，进一步优化整车性能。本文主要以该种车型作为研 究对象，其典型的整车及动力系统结构如图 2.1 所示。 整 流 器 升压 动力 电池 逆变 器 电机空调 减 速 系 统 低压附件DC/DC 电 网 图2.1 纯电动汽车整车及动力系统结构图

高清晰版奥本海默信号与系统第二版课后习题解答 Solutions.Manual.Signal.and.Systems.A.V.Oppenheim.2nd

Introduction This book describes the TCP/IP protocol suite, but from a different perspective than other texts on TCP/IP. Instead of just describing the protocols and what they do, we'll use a popular diagnostic tool to watch the protocols in action. Seeing how the protocols operate in varying circumstances provides a greater understanding of how they work and why certain design decisions were made. It also provides a look into the implementation of the protocols, without having to wade through thousands of lines of source code. When networking protocols were being developed in the 1960s through the 1980s, expensive, dedicated hardware was required to see the packets going "across the wire." Extreme familiarity with the protocols was also required to comprehend the packets displayed by the hardware. Functionality of the hardware analyzers was limited to that built in by the hardware designers. Today this has changed dramatically with the ability of the ubiquitous workstation to monitor a local area network Mogul 1990. Just attach a workstation to your network, run some publicly available software (described in Appendix A), and watch what goes by on the wire. While many people consider this a tool to be used for diagnosing network problems, it is also a powerful tool for understanding how the network protocols operate, which is the goal of this book. This book is intended for anyone wishing to understand how the TCP/IP protocols operate: programmers writing network applications, system administrators responsible for maintaining computer systems and networks utilizing TCP/IP, and users who deal with TCP/IP applications on a daily basis. Organization of the Book We take a bottom-up approach to the TCP/IP protocol suite. After providing a basic introduction to TCP/IP in Chapter 1, we will start at the link layer in Chapter 2 and work our way up the protocol stack. This provides the required background for later chapters for readers who aren't familiar with TCP/IP or networking in general. This book also uses a functional approach instead of following a strict bottom-to-top order. For example, Chapter 3 describes the IP layer and the IP header. But there are numerous fields in the IP header that are best described in the context of an application that uses or is affected by a particular field. Fragmentation, for example, is best understood in terms of UDP (Chapter 11), the protocol often affected by it. The time-to-live field is fully described when we look at the Traceroute program in Chapter 8, because this field is the basis for the operation of the program. Similarly, many features of ICMP are described in the later chapters, in terms of how a particular ICMP message is used by a protocol or an application. We also don't want to save all the good stuff until the end, so we describe TCP/IP applications as soon as we have the foundation to understand them. Ping and Traceroute are described after IP and ICMP have been discussed. The applications built on UDP (multicasting, the DNS, TFTP, and BOOTP) are described after UDP has been examined. The TCP applications, however, along with network management, must be saved until the end, after we've thoroughly described TCP. This text focuses on how these applications use the TCP/IP protocols. We do not provide all the details on running these applications. Readers This book is self-contained and assumes no specific knowledge of networking or TCP/IP. Numerous references are provided for readers interested in additional details on specific topics. This book can be used in many ways. It can be used as a self-study reference and covered from start to finish by someone interested in all the details on the TCP/IP protocol suite. Readers with some TCP/IP background might want to skip ahead and start with Chapter 7, and then focus on the specific chapters in which they're interested. Exercises are provided at the end of the chapters, and most solutions are in Appendix D. This is to maximize the usefulness of the text as a self-study reference. When used as part of a one- or two-semester course in computer networking, the focus should be on IP (Chapters 3 and 9), UDP (Chapter 11), and TCP (Chapters 17-24), along with some of the application chapters. Many forward and backward references are provided throughout the text, along with a thorough index, to allow individual chapters to be studied by themselves. A list of all the acronyms used throughout the text, along with the compound term for the acronym, appears on the inside back covers. If you have access to a network you are encouraged to obtain the software used in this book (Appendix F) and experiment on your own. Hands-on experimentation with the protocols will provide the greatest knowledge (and make it more fun). Systems Used for Testing Every example in the book was run on an actual network and the resulting output saved in a file for inclusion in the text. Figure 1.11 (p. 18) shows a diagram of the different hosts, routers, and networks that are used. (This figure is also duplicated on the inside front cover for easy reference while reading the book.) This collection of networks is simple enough that the topology doesn't confuse the examples, and with four systems acting as routers, we can see the error messages generated by routers. Most of the systems have a name that indicates the type of software being used: bsdi, svr4, sun, solaris, aix, slip, and so on. In this way we can identify the type of software that we're dealing with by looking at the system name in the printed output. A wide range of different operating systems and TCP/IP implementations are used: BSD/386 Version 1.0 from Berkeley Software Design, Inc., on the hosts named bsdi and slip. This system is derived from the BSD Networking Software, Release 2.0. (We show the lineage of the various BSD releases in Figure 1.10 on p. 17.) Unix System V/386 Release 4.0 Version 2.0 from U.H. Corporation, on the host named svr4. This is vanilla SVR4 and contains the standard implementation of TCP/IP from Lachman Associates used with most versions of SVR4. SunOS 4.1.3 from Sun Microsystems, on the host named sun. The SunOS 4.1.x systems are probably the most widely used TCP/IP implementations. The TCP/IP code is derived from 4.2BSD and 4.3BSD. Solaris 2.2 from Sun Microsystems, on the host named solaris. The Solaris 2.x systems have a different implementation of TCP/IP from the earlier SunOS 4.1.x systems, and from SVR4. (This operating system is really SunOS 5.2, but is commonly called Solaris 2.2.) AIX 3.2.2 from IBM on the host named aix. The TCP/IP implementation is based on the 4.3BSD Reno release. 4.4BSD from the Computer Systems Research Group at the University of California at Berkeley, on the host vangogh.cs.berkeley.edu. This system has the latest release of TCP/IP from Berkeley. (This system isn't shown in the figure on the inside front cover, but is reachable across the Internet.) Although these are all Unix systems, TCP/IP is operating system independent, and is available on almost every popular non-Unix system. Most of this text also applies to these non-Unix implementations, although some programs (such as Traceroute) may not be provided on all systems. Typographical Conventions When we display interactive input and output we'll show our typed input in a bold font, and the computer output like this. Comments are added in italics. Also, we always include the name of the system as part of the shell prompt (bsdi in this example) to show on which host the command was run. Throughout the text we'll use indented, parenthetical notes such as this to describe historical points or implementation details. We sometimes refer to the complete description of a command in the Unix manual as in ifconfig(8). This notation, the name of the command followed by a number in parentheses, is the normal way of referring to Unix commands. The number in parentheses is the section number in the Unix manual of the "manual page" for the command, where additional information can be located. Unfortunately not all Unix systems organize their manuals the same, with regard to the section numbers used for various groupings of commands. We'll use the BSD-style section numbers (which is the same for BSD-derived systems such as SunOS 4.1.3), but your manuals may be organized differently. Acknowledgments Although the author's name is the only one to appear on the cover, the combined effort of many people is required to produce a quality text book. First and foremost is the author's family, who put up with the long and weird hours that go into writing a book. Thank you once again, Sally, Bill, Ellen, and David. The consulting editor, Brian Kernighan, is undoubtedly the best in the busin...