PLC控制的变频电梯系统的设计.docx

《PLC控制的变频电梯系统的设计.docx》由会员分享，可在线阅读，更多相关《PLC控制的变频电梯系统的设计.docx（47页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、 毕业设计说明书（论文）毕业实践任务书课题名称 PLC控制的变频电梯系统的设计 指导教师 职 称 专业名称 班 级 学 生 姓 名 学 号 课题需要完成的任务：电梯控制的基本思路是当电梯上升下降时，在上升下降的同时，要顾和到等待时间、加速时间，人性化的设计。在上升时，有人按了上升按钮，则要在经过的时候停止，开门；下降时亦相同。系统主要通过变频器，PLC，曳引电机，按钮四部分构成。按钮相连PLC的I/O口，按下按钮的时候，PLC将信号转换为了模拟信号，传给变频器，变频器改变曳引电机的转向。其中曳引电机的速度改变。主要完成任务如下：（1） 三菱公司的FX2N-80MR-D模拟量扩展模块的程序设计（

2、2） 变频器控制的程序设计课题计划：x.xx.x 熟悉课题，准备资料； x.xx.x 设计硬件； x.xx.x 编写毕业设计论文； x.xx.x 准备毕业答辩。计划答辩时间：xxxx年x月x日x日 xxxxxx（分院、系部）xxxx年xx 月xx日外文翻译INDUSTRIAL AND COLLABORATIVE CONTROL SYSTEMS- A COMPLEMENTARY SYMBIOSIS Looking at todays control system one can find a wide variety of implementations. From pure industria

3、l to collaborative control system (CCS) tool kits to home grown systems and any variation in-between. Decisions on the type of implementation should be driven by technical arguments Reality shows that financial and sociological reasons form the complete picture. Any decision has its advantages and i

4、ts drawbacks. Reliability, good documentation and support are arguments for industrial controls. Financial arguments drive decisions towards collaborative tools. Keeping the hands on the source code and being able to solve problems on your own and faster than industry are the argument for home grown

5、 solutions or open source solutions. The experience of many years of operations shows that which solution is the primary one does not matter, there are always areas where at least part of the other implementations exist. As a result heterogeneous systems have to be maintained. The support for differ

6、ent protocols is essential. This paper describes our experience with industrial control systems, PLC controlled turn key systems, the CCS tool kit EPICS and the operability between all of them.FUNCTIONALITY The ever lasting question why control systems for accelerators and other highly specialized e

7、quipment are often home grown or at least developed in a collaboration but only in rare cases commercial shall not be answered here. We try to summarize here basic functionalities of different controls approaches.Front-end Controller One of the core elements of a control system is the front-end cont

8、roller. PLCs can be used to implement most of the functions to control the equipment. The disadvantage is the complicated access to the controls properties. For instance all of the properties of a control loop like the P, I and D parameter, but also the alarm limits and other additional properties m

9、ust be addressed individually in order to identify them in the communication protocol and last not least in the display-, alarm- and archive programs. In addition any kind of modifications of these embedded properties is difficult to track because two or more systems are involved. This might be one

10、strong argument why control loops are mainly implemented on the IOC level rather than PLCs. I/O and Control Loops Complex control algorithms and control loops are the domain of DCS alike control systems. The support for sets of predefined display and controls properties is essential. If not already

11、available (like in DCS systems) such sets of generic properties are typically specified throughout a complete control system (see namespaces). Sequence/ State programs Sequence programs can run on any processor in a control system. The runtime environment depends on the relevance of the code for the

12、 control system. Programs fulfilling watchdog functions have to run on the front-end processor directly. Sequence programs for complicated startup and shutdown procedures could be run on a workstation as well. The basic functionality of a state machine can be even implemented in IEC 61131. Code gene

13、rators can produce C code which can be compiled for the runtime environment. Supported Hardware The support for field buses and Ethernet based I/O is a basic functionality for SCADA type systems it is commercially available from any SCADA system on the market. The integration of specific hardware wi

14、th specific drivers and data conversion is the hard part in a commercial environment. Open APIs or scripting support sometimes help to integrate custom hardware. If these tools are not provided for the control system it is difficult if not impossible - to integrate custom hardware. New industrial st

15、andards like OPC allow the communication with OPC aware devices and the communication between control systems. One boundary condition for this kind of functionality is the underlying operating system. In the case of OPC it is bound to DCOM which is a Microsoft standard. UNIX based control systems ha

16、ve a hard time to get connected. Only control systems supporting multiple platforms can play a major role in a heterogeneous environments. As a result the limited support for custom- or specialized hardware may give reason for the development of a new control system.1.Graphic Synoptic displays are t

17、he advertising sign for any control system. Commercial synoptic displays come with a rich functionality and lots of special features. Starting to make use of all these features one will find out that all individual properties of the graphic objects must be specified individually. Since SCADA systems

18、 must be generic they cannot foresee that an input channel does not only consist of a value but also consists of properties like display ranges and alarm values. Defining all of these properties again and again can be a pretty boring job. Some systems allow to generate prototypes of graphic objects.

19、 These prototype or template graphics are complex and need a specialist to generate them. DCS or custom synoptic display programs can make use of the common set of properties each I/O point provides. This predefined naming scheme will fill in all standard property values and thus only require to ent

20、er the record or device name into the configuration tool. A clear advantage for control systems with a notion of I/O objects rather than I/O points.2.Alarming Alarms are good candidates to distinguish between different control system architectures. Those systems which have I/O object implemented als

21、o provide alarm checking on the front-end computer. Those systems which only know about I/O points have to add alarm checking into the I/O processing. While the I/O object approach allows to implement alarm checking in the native programming language of the front-end system, I/O point oriented syste

22、ms typically have to implement this functionality in their native scripting language. This is typically less efficient and error prone because all properties must be individually configured. This leads to a flood of properties. Not only the error states for each I/O point wind up to be individual I/

23、O points but also the alarm limits and the alarm severity of each limit must be defined as I/O points if it is desired to be able to change their values during runtime. Besides this impact on the configuration side the processing and forwarding of alarms makes the difference between SCADA and DCS sy

24、stems. Since SCADA systems inherently do not know about alarms, each alarm state must be polled either directly from the client application or in advanced cases from an event manager which will forward alarm states to the clients. In any case a lot of overhead for just checking alarm limits. DCS sys

25、tem again have the advantage that clients can either register themselves for alarm states und thus get the information forwarded or are configured to send alarmchanges to certain destinations spread around the control system. The latter case is only possible for systems which in total are configured

26、 with all the nodes taking part in the controls network. 3.Trending and Archiving Trending has become an important business in control systems architectures. Trends are necessary to trace error conditions or for post mortem and performance analysis of the controlled plant. Besides some custom implem

27、entations which are capable to store the data of complete control objects, most of the trending tools archive scalar data. Additional features like conditional trending or correlation plots make up the difference between individual implementations. 4.Programming Interfaces With respect to open progr

28、amming interfaces PLCs and DCS systems have a common strategy. They are running reliably because theres no way to integrate custom code which could interfere with the internal processing. As a consequence the customer has to order specials - which are extremely expensive or forget about it and use t

29、he system as a black box. Since SCADA systems by definition must be able to communicate with a variety of I/O subsystems they already have some built in APIs which allow to integrate custom functionality. Specially collaborative systems need a certain openness to fulfill all the requirements from va

30、rious development groups. Programming interfaces on all levels like font-end I/O, front-end processing, networking etc. are mandatory. A clear advantage for this type of system. 5.Redundancy If redundancy means the seamless switch which takes over all the states and all the values of the I/O and all

31、 states of all programs currently running, it is a domain of only a few DCS systems. Custom or CCS implementation do not provide this kind of functionality. Maybe because of the immense effort and the fact that it is only required in rare cases. Besides processor redundancy, redundant networks or I/

32、O subsystems are available for certain commercial DCS systems. Again a domain which is not covered by SCADA or CCS implementations. CONCLUSIONS Depending on the size and the requirements for a controls project the combination of commercial solutions and solutions based on a collaborative approach is

33、 possible in any rate between 0 and 100 percent. This applies for all levels from implementation to long term support. Special requirements on safety issues or a lack of manpower might turn the scale commercial. The necessity to interface special hardware, special timing requirements, the having the

34、 code in my hands argument or the initial costs for commercial solutions will turn the scale collaborative. As long as collaborative approaches like EPICS stay up to date and run as stable and robust as commercial solutions, both will keep their position in the controls world in a complementary symb

35、iosis.工业控制系统和协同控制系统当今的控制系统被广泛运用于许多领域。从单纯的工业控制系统到协同控制系统（CCS），控制系统不停变化，不断升级，现在则趋向于家庭控制系统，而它则是这两者的变种。被应用的控制系统的种类取决于技术要求。而且，实践表明，经济和社会因素也对此很重要。任何决定都有它的优缺点。工业控制要求可靠性，完整的文献记载和技术支持。经济因素使决定趋向于协同工具。能够亲自接触源码并可以更快速地解决问题是家庭控制系统的要求。多年的操作经验表明哪个解决方法是最主要的不重要，重要的是哪个可行。通过于异类系统的存在，针对不同协议的支持也是至关重要的。本文介绍工业控制系统，PlC contr

36、olled turn key系统，和CCS工具，以和它们之间的操作。功能持续不断的问题，如为了什么控制系统的加速器和其他高度专业化的设备联合协同发展。但是，在极少数情况下，只通过商业的立场时难以回答的。在这里，我们试图总结不同控制方法的基本功能。前端控制器： 对控制系统的核心要素之一，是前端控制器。PLCs可用于实施控制功能的设备。它的缺点就是复杂，难以达到控制属性。例如确定通信协议和最后在显示、报警和归档方案，一个控件的所有属性像P，I和D参数，还有报警限制和其他附加的属性必须得到解决。另外，这些嵌入式属性修改是很难寻觅，因为了其中涉和两个或者两个以上轨道系统这可能是一个有力的论据是，为了什

37、么控制回路主要实施在IOC层面，而不是PLCs层面。I / O和控制回路:复杂的控制算法和控制回路和域名DCS控制系统一样。对显示和控件的属性的支持是必不可少的。频率/国家计划:在控制系统中，频率程序可以运行任何处理器。运行时环境取决于相关代码。控制系统程序直接履行运行前端处理器的监控。为了复杂的启动和关闭处理程序设立的频率程序也可以运行工作站。国家机器的基本功能在IEC 61131中得到了落实。编码发电机可以产生C代码。硬件支持:对现场总线和起源于I / O的Ethernet的支持是为了SCADA系统服务的一个基本功能。所有SCADA系统在市场商业运作中是可行的。配置特定驱动器和数据转换器的

38、集成硬件在商业环境中是一个难点。开放API或者脚本支持有时有助于整合用户的硬件。如果不向控制系统提供这些工具，就很难整合客户硬件。新的工业标准，如OPC，和OPC设施联系，还和控制系统之间互相联系。这种功能的基本条件是强调操作系统。在这种情况下，OPC更趋向于微软的DCOM标准。基于控制系统的UNIX很难互相相连。只有支持多平台的控制系统可以在异构环境中发挥主要功能。通过于为了客户或者专业硬件的支持有限，所以新的控制系统有理通过得到发展。除了前后系统，操作接口在控制系统的兼容过程中有重要的功能。因为了个人呢工具通过不同的团队开发，所以协作实现的工具包可能变动。1.图形天气显示是任何控制系统的广

39、告招牌。商业天气显示也有着丰富的功能和许多特色。开始使用所有这些特征，所有这些功能的使用人会发现，所有个别属性的图形对象要分别指定。一个输入通道不只通过物业的价值决定的，而且更通过包括像展出范围和报警值决定的。一再分辨所有性能可能是个非常乏味的工作。有些系统产生图形原型对象。这些原型图形或者模板很复杂，但需要一个专家来生产。DCS或者自定义天气显示程序使用常见的I / O点属性集。这个预定义的命名方案填写标准的属性值，所以只需要进入记录，或者设备名称进入配置工具。2.报警系统警报可以很好的区分不同的控制系统架构。实现I / O对象的这些系统在前后端电脑提供警报检查。只能读懂I / O点的系统在

40、I / O处理过程中添加了警报检查。I / O对象途径在前后端系统的本土项目语言安插了警报检测。，I / O点导向系统通常要在他们的脚文本语言中实现这种功能。这是通常效率较低且容易出错，因为了所有属性必须被单独配置，这导致了一系列特性。不仅为了每个I / O点的错误状态结束是个人的I / O点，但报警限值和每个报警的轻重，应当限制定义为了I / O点，如果它希望能够改变运行值。这种影响在SCADA和DCS系统之间也形成了影响。SCADA系统本就读不懂报警系统。DCS系统的优势在于管理人员既可以登记警报状态，从而提前得到信息，控制蔓延到在控制系统周围的变化。后一种情况是唯一可能的系统。3.趋势和

41、归档趋势已成为了控制系统架构中的一个重要的业务。趋势是必要的跟踪误差条件。实现的数据存储有能力储存完整控制目标，大部分的趋势工具标量数据存档。附加特性如条件趋向或者相关情节在个人实施起了影响。4.编程接口关于开放编程接口，PLC和DCS系统有相同策略。他们运行可靠，因为了他们没有办法整合 可定制的合作去干涉内部处理。所以，客户定制精品，这个极其昂贵的。通过于SCADA系统必须能够 与多种I / O子系统相连已经在API上建立了I / O子系统以整合 自定义功能。协作系统尤其需要一定的开放性以实现各种发展组织的要求。所有级别的编程接口，例如前后端I / O，前后端处理过程和网络等，是强制性的。5

42、.冗余如果冗余是指管理所有国家，I / O所有值无缝道岔当前正在运行，它是一个域，只有少数集散系统。自定义或者CCS实施不提供这种功能。也许是因为了巨大努力和事实，它是只需要在罕见的事例。此外，处理器冗余，或者多余的网络，或者I / O子系统是为了一定的商业集散控制系统指定的。结论这适用于长远的技术支持。在安全问题上的特殊需要或者人力资源的缺乏可能会扩大商机。接口专业硬件，掌控在手的谈判或者商业解决方案的初始成本有可能促使大规模的合作。只要如EPICS的协作途径，保持最新并运行如商业方案一样稳定和强劲，它们就能在互补共生的控制世界中占有一席之地。毕业设计调研报告 可编程控制器（PLC）是以微处

43、理器为了基础，综合计算机、通信、联网以和自动控制技术而开发的新一代工业控制设备。PLC在我国的发展与应用已有 30 多年的历史，现在它已经广泛应用于国民经济的各个工业生产领域，成为了提高传统工业装备水平和技术能力的重要设备和强大支柱。随着全球一体化经济的发展，努力发展PLC在我国的大规模应用，形成具有自主知识产权的PLC技术，应该是广大技术人员努力的方向。 PLC问世于 20 世纪 60 年代，当时的PLC功能都很简单，只有逻辑、定时、计数等功能；硬件方面用于PLC的集成电路还没有投入大规模工业化生产， CPU 以分立元件构成；存储器为了磁心存储器，存储容量有限；用户指令一般只有二三十条，还没

44、有成型的编程语言；机型单一，没有形成系列。一台PLC最多只能替代 200300 个继电器构成的控制系统，在体积方面，与现在的PLC相比，可以说是庞然大物。我国研制生产的传感器、变送器、调节器、实行器等,基本上能显示过程状态,实现调节意图,最终命令实行器完成对工艺流程的调节要求。 进入 21 世纪，PLC仍保持旺盛的发展势头，并不断扩大其应用领域，如为了用户配置柔性制造系统（ FMS ）和计算机集成制造系统（ CIMS ）。目前PLC主要向两个方向扩展：一是综合化控制系统，它已经突破了原有的PLC的概念，将工厂生产过程控制与信息管理系统密切结合起来，甚至向上为了 MES 和 ERP 系统准备了技

45、术基础，这种发展趋势会使得举步为了艰的 ERP 系统有了坚实的技术基础，从而会带来工业控制的一场变革，实现真正意义上的电子信息化工厂；二是微型PLC异军突起，体积如手掌大小，功能可覆盖单体设备和整个车间的控制功能，并具备联网功能，这种微型化的PLC使得控制系统可将触角延伸到工厂的各个角落。随着世界经济一体化进程的加快，在技术发展的同时，发达国家更加注重了对PLC的知识产权的保护，国际大型PLC制造商纷纷加入了PLC的国际标准化组织，他们利用许多技术标准建立了符合他们经济利益的技术保护壁垒。 PLC的运用，让各种工业场所都离不开。例如本次的毕业设计，运用到PLC和变频器，形成一个完整的电梯系统。

46、而现代的电梯，也都离不开PLC和变频器。PLC控制的变频电梯系统的设计摘要：电梯的运行是一个繁琐的过程，作为了一种我们生活中经常用到的交通工具，其性能的好坏主要通过拖动系统、控制系统的性能决定。为了了可以达到安全、便捷、舒适、高效和自动化运行，不止需要良好的拖动系统以外，还要有一套完善、可靠的控制系统。为了了克服传统的继电器构成的系统接触点多，故障几率高，可靠性差和体积巨大等不足，使用PLC来达到对电梯的自动控制。通过理论的分析，PLC不止能实现对开关量的逻辑控制，还有数学运算、数据处理、运动控制、模拟量PID控制、通信等功能，完全可以取代继电器控制系统。本篇文章介绍的电梯的调速是通过变频来进

47、行调速的。现今，在运动控制领域里变频调速得到广泛的应用。因为了变频调速可以实现平滑调速，调速精度可与直流电动机相媲美。大功率晶体管的开发使变频器的造价越来越低，从成本和性能考虑使用PLC对变频器控制去达到变频调速。在这个设计中的电梯主要对各种呼梯信号和当时的运行状态进行整体分析，再确定下一个工作状态。为了此，它要求具有自动定向、顺向截梯、反向保号、外呼记忆、自动开/关门、停梯消号、自动平层、检修慢速和安全保护等功能，大大提升了电梯的安全性和实用性。关键词：电梯 变频器 控制系统 PLC毕业设计说明书目录第一章 绪论111.1 电梯的定义和发展历程111.2 电梯品种多样性111.3 电梯的基本

48、构成11第二章 PLC的简介和其系统基本结构142.1 PLC的通过来和发展142.2 PLC的基本结构142.3 PLC的工作原理152.4 PLC的I/O系统16第三章 变频电梯总体方案设计183.1 设计的指导思想和步骤183.2 PLC控制电梯系统的基本结构183.3 电梯电力拖动系统方案的选择183.4 拖动部分的选择183.4.1 变极调速系统183.4.2 交流调压调速系统193.4.3 变压变频调速系统193.5 控制部分的选择20第四章 变频电梯的硬件设计214.1 系统总体结构214.2 对重设备的设计214.3 主电路的设计和元件型号的选择214.3.1 电源容量的设计214.3.2 曳引电机的设计224.4 门电机的设计224.5 电源部分的设计