Egit 的使用手册

初学GE实例（YC09221）：一、数控柜：两个5槽机架；两个电源模块，IC693 PWR330；两台中央处理单元，IC693 CPU374；两个高速计数模块，IC693 APU300；两个BUS通讯模块，IC693 BEM331；一个DP通讯模块，IC693 PBM200；一个测温输入模块，HE693 RTD600；一个数字量输入模块，IC200 MDL640；一个数字量输出模块，IC200 MDL740；一个远程通讯模块，IC200 GBI001。

一台交换机。

二、操作台和3个信号台：每个柜子各一个远程通讯模块（IC200 GBI001）和自己输入输出模块。

三、要求：1、数控柜第一个5槽机架挂一个电源模块，一台CPU，一个高速计数模块，两个BUS 通讯模块和一个DP通讯模块；2、数控柜第二个5槽机架挂一个电源模块，一台CPU，一个高速计数模块，一个数字量输入模块，一个数字量输出模块和一个测温输入模块。

3、第一个CPU通过其中一个BUS通讯模块对数控柜、操作台和3个信号台的远程通讯模块进行Profibus连接。

4、两台CPU通过交换机和3跟网线，进行以太网连接。

一、新建工程点击“New Project”，弹出新建窗口，在第一行Project后边空白处输入工程名字，在第二行Project 后边的下拉菜单中选择“GE Fanuc Series 90-30 PLC”。

点击OK。

二、硬件配置新建工程之后，左边会出现下边的小窗口，图中的列表中，“ge008”是工程名字，“Target1”是插入的第一个PLC名字。

右键“ge008”可以选择添加多个PLC目标。

配置硬件：如图，右键“Main Rack”，点击“Replace Rack”，出现如下窗口，是选择主机架型号，有10槽的和5槽的（系统默认是10槽机架，此系统用的是5槽机架）。

选择5槽机架后，左边小窗口会变成如下窗口：如图，1后边的PWR为电源模块，2后边的Slot 1到Slot 5为主机架的5个槽，其中Slot 1为CPU，后边的4个槽根据实际安装模块配置。

REV 1.0/0607ENGGAThree-phase Synchronous Generators 三相同步发电机Operation & Maintenance Manual安装和维护手册安全指南EG发电机采用最新的发电机设计、生产工艺、质量控制理念，拥有出众性能、可靠质量、优质发电机。

敬请各位用户在使用前务必仔细阅读和理解本手册中有关发电机安装、使用和维护的内容。

安装、调试、检修必须由具备相关工作资格的专业人员进行，操作人员应能掌握正确的使用方法、安全操作，否则有可能引起严重的人员伤亡或设备损坏事故。

①警示标识本手册中使用和随发电机提供的警示和警告标识的含义如下，发电机组配套商应确保警示标签位置放置正确并清晰，标签含义如下：A．普通警告标识，可能会导致人员伤亡、设备损坏的危险Ｂ．电气危险标识，可能电气原因会导致人员伤亡的直接危险Ｃ．通用危险标识，可能会导致人员伤亡的直接危险② 发电机警告标签的位置目录1 概述1.1 标准1.2 发电机型号代表意义1.3 铭牌1.4 接收检查及储存2 发电机的使用环境2.1 使用环境2.2 发电机的容量修正3 发电机结构3.1 发电机的工作原理3.2 定子3.3 转子3.4 励磁系统4 安装4.1 安装环境4.2 安装4.3 转向4.4 接线4.5 接地、保护5 运行5.1 运行前的检查5.2 运行前的试验调整5.3 开机与停机5.4 并联运行6 维护和检修6.1 一般维护6.2 检修项目6.3 发电机的拆装6.4故障现象及排除6.5 A VR故障检修7 结构图结构图零件表本安装使用维护手册阐述了英格EG系列交流发电机的结构特点、性能原理、安装使用和维护检修。

1 概述1.1 标准发电机符合下列国际和相关国家标准：I.E.C 60034-1 国际电工委员会标准BC5000 英国标准NEMA MG21 美国标准C.S.A C22-2 加拿大标准VDE 0530 德国标准GB755 中国标准1.2 发电机型号意义：EG发电机的型号按照以下方式命名例如：EG280S—120NEG---表示EG系列发电机280---表示发电机的机座号（160、225、280、315、355、400、500）S---表示机座的长短（M、L）120---表示发电机的容量带，KWN---表示发电机的改进、用途，N---新改进的NEW系列；H---船用系列；B---变形产品1.3 铭牌发电机铭牌位于驱动端右侧机体上。

等离子气割机操作手册- 1 -昆山乾坤机电设备有限公司Tel：0512 5755 6782 Fax：0512 5751 7072- 2 -昆山乾坤机电设备有限公司Tel ：0512 5753 6908Fax ：0512 5751 7072第一章安 全阅读手册(r e a d i n g t h e m a n u a l )阅读并详细了解切割机操作手册以及用户安全需求。

如果用户有其它需求，请与昆山乾坤机电设备有限公司技术部联系。

危险机械(d a n g e r o u s m ac h i n a r y )自动化设备的操作和维修具有潜在的危险，应该小心预防以免造成人身伤害。

小心手或手指被绞入运动着的设备，以造成伤害。

尽量远离工作着的设备，运用面板键盘或远程界面来对设备施加影响。

当操作和维修机器的时候，不要穿太宽松的衣服。

高压危险(h i g h v o l t a g e)小心电击，根据安装程序和规格说明书进行安全的设备安装。

通电后，不要接触电缆或电线。

只有受过培训的维修人员才能打开设备。

产品清单(p r o d u c t l i s ti n g )“P ”型控制器，“V ”型控制器。

两种产品均满足C E 和U L 安全标准。

第二章综 述简介(o v e r v i e w )：该控制器是一种多轴数控系统，专为形状切割机设计。

它是金属加工工业的最新产品。

我们设计的中心目标是易于使用，可编程软键简化了面板设计而且功能更强大。

C ++及M F C 技术的运用，使人机界面更加人性化。

随着精细等离子和激光技术的出现，控制器对切割设备的定位更加精确。

英特儿奔腾微处理器使控制器的定位能力更加出众而精确。

随着数字定位环和速度环的运行，在允许的速度范围内，机器运行更加平稳，并精确的知道切割设备的编程定位。

在切割期间，你可以通过动态的“Z o o m （放大缩小）”功能查看整个切割过程。

该控制器可以用于几乎所有的二维切割台。

Historain安装使用说明一、软件安装放入安装盘，等待自动运行，出现安装画面如下图点击Next，进入下一画面，如图点击Yes，进入下一画面，如图把所有选项全部选上，然后点击Next，进入下一画面，如图点击Next，进入下一画面，如图选择Select All，然后点击Next，进入下一画面，如图选择Select All，然后点击Next，进入下一画面，如图然后点击Next，进入下一画面，如图输入Destination后，点击Next，进入下一画面，如图一直点击Next，直到安装完成，重新启动计算机。

二、软件使用1、iFIX系统采集运行iFIX系统点击“开始”—“程序”—“Proficy Historian 3.1”—“Histortian Administrator”如下图点击“开始”—“程序”—“Proficy Historian 3.1”—“Start iFIx collector”如下图在Histortian Administrator中点击Tags选项，如下图点击Add Tags From Collector，在Collector选择选项中ADMINIST-385202_iFIX，然后点击Browse，所有的Tags将会出现。

选择所要添加的Tags，然后点击AddSelected Tags。

如下图点击Search Historain Tag Datebase 然后点击OK，已选择的Tags就会出现。

如下图在Tags上点击鼠标右键，选择最后一个选项，Tags的实时数据就会显示出来，如下图2、模拟OPC采集双击opcsimul.exe，打开模拟系统。

点击“开始”—“程序”—“Proficy Historian 3.1”—“Histortian Administrator”如下图点击“开始”—“程序”—“Proficy Historian 3.1”—“Start OPC CollectorSurpass.Emluator”，如下图在Histortian Administrator中点击Tags选项，如下图点击Add Tags From Collector，在Collector选择选项中ADMINIST-385202_OPC _Surpass_Emluator，然后点击Root，所有的Tags将会出现。

EGit TutorialJonas HelmingMaximilian KoegelJanuary 2013Table of Contents1.EGit Tutorial (2)2.Installing EGit in Eclipse (2)3.EGit Configuration (3)4.Creating Local Repositories (3)mit (5)6.Adding Files (7)7.Reverting Changes (7)8.Revert via Compare (8)9.Revert via Reset (8)10.Cloning Repositories (9)11.Creating Branches (13)12.Merge (14)13.Resolving Conflicts (14)14.Fetch and Pull (15)15.Push (15)16.Synchronize (15)17.History View (16)18.Creating Patches (16)19.Repository View (16)20.Additional Information (17)21.Index (17)22.Reset Types (18)eful pages (18)1. EGit TutorialThis tutorial guides you through the essential use cases for EGit, in addition to notes on how to install, configure and create your first repositories. The tutorial is targeted at developers with a basic knowledge of Git processes. Please help us to keep this tutorial up-to-date by reporting any issues or questions.2.Installing EGit in EclipseEGit is already included in the Eclipse Juno Release, so you do not need to install it. If you use an older version of Eclipse, open the Eclipse Wizard to install new software Help => Install New Software. Insert /egit/updates after Work with: and hit Return. Select Eclipse EGit as a child from Eclipse Team Git Provider. You don't have to install any other plugins. Click Next and confirm your selection in the following window by pressing Next again. Finally, accept the terms of use and the license agreement and click Finishto start the installation. After the installation has finished restart Eclipse.3.EGit ConfigurationEvery commit in EGit will include the user's name and his email-address. These attributes can be set in the Preferences-window Window => Preferences. Navigate to Team => Git => Configuration and hit the New Entry... Button. Enter as Key and your name as Value and confirm. Repeat this procedure with user.email and your email address and click OK in the Preferences window. The username and email should be the same you use for your git account, ie. your GitHub account.4.Creating Local RepositoriesOne major advantage of Git compared to SVN or CVS is that you can easily create local repositories, even before you share them with other people. In this way, you can version your work locally. First, you have to create a project that you want to share via your local repository. For later purposes it would be useful to add some files, e.g. a Java class to your project.After you have created your project, select the context menu by right clicking it and navigate to Team => Share Project... . Select Git as the repository type and hit Next. In the following window select your project, hit the Create Repository-button and click Finish. The repository will be assigned automatically.The newly created repository will be empty, although the project is assigned to it. (Note the changed icons: the project node will have a repository icon, the child nodes will have an icon with a question mark, ignored fil es, e.g. the bin directory, won’t have any icons at all.) Before you can commit the files to your repository, you need to add them. Simply right click theshared project's node and navigate to Team => Add . After this operation, the question mark should change to a plus symbol. To set certain folders or files to be ignored by Git, e.g. the bin folder, right click them and select Navigate => Ignore . The ignored items will be stored in a file called gitignore , which you should add to the repository. The last thing to do iscommit the project by right clicking the project node and selecting Team => Commit... from the context menu. In the Commit wizard, all files should be selected automatically. Enter a commit message (the first line should be headline-like, as it will appear in the history view) and hit the Commit button. If the commit was successful, the plus symbols will have turnedinto repository icons.5. CommitNow you can start to modify files in your project. To save changes made in your workspace to your repository, you will have to commit them. After changing files in your project, a ">" signwill appear right after the icon, telling you the status of these files is dirty. Any parent folder of this file will be marked as dirty as well.If you want to commit the changes to your repository, right click the project (or the files you want to commit) and select Team => Commit... . This will open a new window, allowing you to select the files you want to commit. Before you can commit the files, you will have to enter a commit message in the upper textbox. After you're done, click Commit to commit the selected files to your repository.Note that the status of the changed file is Mod., not staged. By staging the files before you commit (see the section “Additional Information”), you can change the status to Modified (and the dirty sign to a staged icon).If you later realize that your previous commit was incomplete (e.g. you missed committing a file) or your commit message was wrong, you might want to use Amend previous commit. This will merge the current commit and the previous commit into one, so you don't have to perform an extra commit (and maybe cause confusion). However, this should only be used if the previous commit hasn't already been published to a shared repository.Another option is Show untracked files. By checking this checkbox, new files you created but did not add yet, will be available for you to select in the Commit window.6. Adding Fil esTo add a new file to the repository, you will have to create it in your shared project first. The new file will, again, appear with a question mark.Right click it and navigate to Team => Add . The question mark will turn into a plus symbol and the file will be tracked by Git, but it is not yet committed. All of the file's parent folders should now have a symbol that looks like an asterisk indicating that it is ‘staged’ (more on that later). In the next commit, the file will be added to the repository and the plus symbol will turn into a repository icon. The repository icons of all the file's parents (packages/project...) will turn into staged icons. EGit also allows selecting untracked files to be added in the commit dialog if you turn on the option “Show untracked files”. Inthis case, they will be added and committed at the same time.7. Reverting ChangesIf you want to revert any changes, there are two options. You can compare each file you want to revert with the HEAD revision (or the index, more on that later) and undo some or all changes done. Second, you can hard-reset your project, causing any changes in the working directory to be reverted.8.Revert via CompareRight click the file you want to revert and select Compare With => HEAD Revision. This will open a comparison with the HEAD Revision, highlighting any changes done. If you want to completely revert your file, hit the Copy All Non-Conflicting Changes from Right to Left-button in the Java Source Compare toolbar. If you only want to revert several lines, select each line individually and hit the Copy Current Change from Right to Left button (in the toolbar) for each line. To complete the Revert operation, you will have to save either the comparison or your local copy of the file.9.Revert via ResetTo reset all changes made to your project, right click the project node and navigate to Team => Reset... . Select the branch you want to reset to (if you haven't created any other branches, there will be just one) and choose Hard as a reset type. By confirming this operation, all changes will be reset to this branch's last commit, including all changes done in the workspace (and index, more on that later). Be careful with this option as all changes in your workspace will be lost.10. Cl oning RepositoriesNote:For this and some of the following sections (especially Fetch/Push), you might want to use https://to create your own remote repository. Public repositories are free at GitHub and performing the actions might help you gain some insights.In order to checkout a remote project, you will have to clone its repository first. Open the Eclipse Import wizard (e.g. File => Import), select Git => Projects from Git and click Next. Select “URI” and click next. Now you will have to enter the repository's location and connection data. Entering the URI will automatically fill some fields. Complete any other required fields and hit Next. If you use GitHub, you can copy the URI from the web page.Select all branches you wish to clone and hit Next again.Hit the Clone...button to open another wizard for cloning Git repositories.Choose a local directory to save this repository in.To import the projects, select the cloned repository and hit Next. Select Import Existing Project s and hit Next. Please note that there needs to be existing projects in your repository, and if you use your own repository it might be empty. In the following window, select all projects you want to import and click Finish. The projects should now appear in the Navigator/Package Explorer. (Note the repository symbol in the icons indicating that the projects are already shared.)11.Creating BranchesTo create a new branch in your repository, right click a shared project and navigate to Team => Switch to => New Branch... from the context menu. Select the branch you want to createand enter a name for the new branch.a new branch from, hit New branch.the newly created branch, select it and click Checkout12.MergeTo merge one branch into another, you will have to checkout the branch you want to merge with. Right click the project node and navigate to Team => Merge... . Select any branch (other than the checked out branch) and hit Merge.The merge will execute and a window will pop-up with the results. The possible results are Already-up-to-date, Fast-forward, Merged, Conflicting, Failed. A Conflicting result (see image below) will leave the merge process incomplete. You will have to resolve the conflicts (see next section). A Failed result may occur when there are already conflicting changes in the working directory.13.Resolving ConflictsIf your merge resulted in conflicts (note the red symbols on the file icons), you will have to resolve these manually. Open the conflicting files and scroll to the conflicting changes marked with “<<<<<<<”After you are finished the manual part of the merge, you will have to tell Git that the conflicts are resolved. To do so, Add the files and Commit to complete your merge.14.Fetch and PullWhen cloning remote repositories, git creates copies of the branches as local branches and as remote branches. A Fetch operation will update the remote branches only. To update your local branches as well, you will have to perform a Merge operation after fetching. The operation Pull combines Fetch and Merge. To perform a Fetch, select Team => Fetch From... from the project's context menu. Enter the repository you want to fetch branches from. (If you cloned this repository, the remote branch will be selected as default.) In the following window you will have to select what you want to fetch. As default, all branches are selected. The result of the Fetch-operation will be shown in a final confirmation window. Follow the same steps to apply a Pull.15.PushLocal changes made to your local branches can be pushed to remote repositories causing a merge from your branches into the branches of the remote repository (X pulls from Y is the same as Y pushes to X). The Push-wizard is pretty much the same as the Fetch-wizard. First, right click the project node and navigate to Team=> Push... . Enter the repository you want to push your branches to (the default for this will be the same as the Fetch-default if you didn't configure a Push-default) and hit Next. Choose the branches you want to push or click Add all branches spec if you want to push all branches. You can also select branches you want to delete from the remote repository. If you are done hit Finish. A final window will show the results of the Push.16.SynchronizeComparisons between your workspace and the local repository or between the current branch and others and are done via the Synchronize-operation. If you right click Team => Sychronize Workspace, your local workspace will be compared with the current branch showing uncommitted changes. If you select Team => Advanced => Synchronize... . , you can select other branches to compare your current branch with. In this case you can also include local uncommitted changes.To compare the branches you may want to switch to the Synchronizing perspective, where you can get a more detailed view of several changes. Here is an example of a Synchronize operation in the Synchronizing perspective:17.History ViewTo show any shared file's history, right click it and select Team => Show in History. This will open the History View, giving an overview of the commits and allowing you to perform several actions (compare, creating branches/tags, reset...). Every commit you select comes up with a revision comment and revision details. The revision comment (bottom left corner) includes parents, children, commit message and changes whereas the revision details (bottom right corner) name the changed files and the actions performed upon them (A=ADD,M=MODIFY, D=DELETE). Selecting a file in the revision details will scroll the revision comment to the changes to that file.18.Creating PatchesAny patch can only include one commit that is from a parent to its child (if a child has just one parent, you cannot merge so you will need to patch). To create a patch you have to open the History View first (see previous section). Right click a commit you want to create a patch for (this must be a child with exactly one parent) and select Create Patch....Select either Clipboard or File and hit Next and click Finish. The resulting patch can be applied to the parent commit via Team => Apply Patch....19.Repository ViewThe repository view is useful when working with branches/tags and executing operations on them, as well as handling remote repositories and getting an overview of all your repositories. To open this view, select Team => Show in Repositories View from any file's context menu.20.Additional InformationIcon Decorations/Signsignored: The repository treats these files as if they were non-existent (e.g. the bin-directory by default). Add a .gitignore file or Team => Ignore to ignore a file.untracked: Any file known, but not yet recorded. To track a file, add it or select theShow untracked files-option in the commit-wizard and commit it directly.tracked: Any file known to and recorded by the repository.added: Any file known to the repository, but not yet committed. Perform a Commit to change this file's status to tracked.removed: Any file that should be removed from the repository. For this icon to appear Team => Untrack has to be performed. By deleting the file from the workspace, thefile will disappear (and therefore no icon will appear). However, it will still be removed from the repository with the next commit.dirty: Any tracked file with changes that have not yet been added to the index.staged: Any tracked file with changes that are already included in the index.partially-staged: Any tracked file with changes, where some changes are alreadyincluded in the index, and others that are not yet added.conflicted: Any file where the merge result caused a conflict. Resolve the conflicts and perform an Add operation to change this file's status.assume-valid: Any modifications won't be checked by Git. This option can be activated via Team => Assume unchanged. However, it can only be turned off via the command line. Performing a Reset operation resets this status as well.21.IndexThe index, sometimes referred to as staging area, is an area between the working directory and the repository. Any change made to any file will change this file's status to dirty (see above). Any dirty file can be added to the index with an Add operation. The file's status changes to staged. You can compare files to the index and reset the index without resetting the workspace. In the original Git, files had to be added to the index before performing a Commit operation. This is not necessary in EGit, as Team => Commit allows you to commit unstaged changes.22.Reset TypesYou can reset your current branch to any other branch, tag or commit you want. Right click any commit in the History View and select Reset. There are three options available: Soft:The current branch's tip will point to this branch/tag/commit. Changes in the index and working directory, however, won't be reset.Mixed:Same as a soft reset, only that the current index will be replaced by the selectedbranch/tag/commit's index. The working directory stays unchanged.Hard:All changes will be reverted to the selected branch/tag/commit. Uncommitted changes will be lost, therefore this operation has to be confirmed.eful pages∙To create your own remote repositories and perform operations on them, you might want to register at https://. As long as your repository is public, github isfree.∙ A tutorial with more information on certain options and actions:/EGit/User_GuideFor more information, contact us:Email: e4@/munich。

GAMIT/GLOBK软件使用手册一软解介绍GAMIT软件最初由美国麻省理工学院研制, 后与美国SCRIPPS海洋研究所共同开发改进。

该软件是世界上最优秀的GSP定位和定轨软件之一, 采用精密星历和高精度起算点时, 其解算长基线的相对精度能达到10-9量级, 解算短基线的精度能优于1mm, 特点是运算速度快、版木更新周期短以及在精度许可范围内自动化处理程度高等, 因此应用相当广泛。

GAMIT软件由许多不同功能的模块组成, 这些模块可以独立地运行。

按其功能可分成两个部分: 数据准备和数据处理。

此外, 该软件还带有功能强大的shell程序。

目前，比较著名的GPS数据处理软件主要有美国麻省理工学院（MIT）和海洋研究所（SIO）联合研制的GAMIT/GLOBK软件、瑞士伯尔尼大学研制的BERNESE软件、美国喷气推进实验室（JPL）研制的GIPSY软件等。

GAMIT/GLOBK和BERNESE软件采用相位双差数据作为基本解算数据，GIPSY软件采用非差相位数据作为基本解算数据，在精度方面，三个软件没有明显的差异，都可得到厘米级的点位坐标精度。

相比较而言，GIPSY软件为美国军方研制的软件，国内只能得到它的执行程序，在国内，它的用户并不多，BERNESE软件需要购买，它的用户稍微多一点，GAMIT/GLOBK软件接近于自由软件，在国内拥有大量用户。

GLOBK软件核心思想是卡尔曼滤波（卡尔曼滤波理论是一种对动态系统进行数据处理的有效方法, 它利用观测向量来估计随时间不断变化的状态向量），其主要目的是综合处理多元测量数据。

GLOBK的主要输人是经GAMIT处理后的h-file和近似坐标, 当然,它亦己成功地应用于综合处理其它的GPS软件（如Bernese和GIPSY）产生的数据以及其它大地测量和SLR 观测数据。

GLOBK的主要输出有测站坐标的时间序列、测站平均坐标、测站速度和多时段轨道参数，GLOBK可以有效地检验不同约束条件下的影响, 因为单时段分析使用了非常宽松的约束条件，所以在GLOBK中就可以对任一参数强化约束。

GAMIT/GLOBK软件使用手册一软解介绍GAMIT软件最初由美国麻省理工学院研制, 后与美国SCRIPPS海洋研究所共同开发改进。

该软件是世界上最优秀的GSP定位和定轨软件之一, 采用精密星历和高精度起算点时, 其解算长基线的相对精度能达到10-9量级, 解算短基线的精度能优于1mm, 特点是运算速度快、版木更新周期短以及在精度许可范围内自动化处理程度高等, 因此应用相当广泛。

GAMIT软件由许多不同功能的模块组成, 这些模块可以独立地运行。

按其功能可分成两个部分: 数据准备和数据处理。

此外, 该软件还带有功能强大的shell程序。

目前，比较著名的GPS数据处理软件主要有美国麻省理工学院（MIT）和海洋研究所（SIO）联合研制的GAMIT/GLOBK软件、瑞士伯尔尼大学研制的BERNESE软件、美国喷气推进实验室（JPL）研制的GIPSY软件等。

GAMIT/GLOBK和BERNESE软件采用相位双差数据作为基本解算数据，GIPSY软件采用非差相位数据作为基本解算数据，在精度方面，三个软件没有明显的差异，都可得到厘米级的点位坐标精度。

相比较而言，GIPSY软件为美国军方研制的软件，国内只能得到它的执行程序，在国内，它的用户并不多，BERNESE软件需要购买，它的用户稍微多一点，GAMIT/GLOBK软件接近于自由软件，在国内拥有大量用户。

GLOBK软件核心思想是卡尔曼滤波（卡尔曼滤波理论是一种对动态系统进行数据处理的有效方法, 它利用观测向量来估计随时间不断变化的状态向量），其主要目的是综合处理多元测量数据。

GLOBK的主要输人是经GAMIT处理后的h-file和近似坐标, 当然,它亦己成功地应用于综合处理其它的GPS软件（如Bernese和GIPSY）产生的数据以及其它大地测量和SLR观测数据。

GLOBK的主要输出有测站坐标的时间序列、测站平均坐标、测站速度和多时段轨道参数，GLOBK可以有效地检验不同约束条件下的影响, 因为单时段分析使用了非常宽松的约束条件，所以在GLOBK中就可以对任一参数强化约束。

E-IDC1B Analog Single Input Mini Module Installation SheetOperationThe E-IDC1B Analog Single Input Mini Module is an analog addressable device used to connect a normally open, alarm, supervisory, or monitor type dry contact initiating device circuit (IDC) to a control panel. This module is designed for Class B circuit operation.The device address is set using the two rotary switches located on the front of the module. One device address is required.The module is factory set to operate as an alarm-latching device. When the NO contact of an initiating device is closed, an alarm signal is sent to the control panel and the alarm condition is latched at the module.Additional device types are available through front panel programming or the configuration utility. For additional information, refer to the documents listed on the control panel label.LEDsThe provides two status LEDs. The LEDs are visible from the back of the module.Figure 1: LED location1. Red LED: Alarm/active2. Green LED: Normal InstallationWARNINGS• This module does not operate without electrical power.As fires frequently cause power interruption, discussfurther safeguards with the local fire protectionspecialist.• This module does not support conventional two-wire smoke detectors.Note: The module is shipped from the factory as an assembled unit; it contains no user-serviceable parts and should not be disassembled.To install the module:1. Verify that all field wiring is free of opens, shorts, andground faults.2. Make all wiring connections as discussed in “Wiring”and shown in Figure 3.3. Set the required device address. For example, to set thedevice address for 21, set the TENS switch (marked 0to 12) to 2 and the ONES switch (marked 0 to 9) to 1.See Figure 2.The devices can be addressed from 01 to 129. Paneladdressing may vary.4. Position the module into the electrical box, behind thedevice to which it connects.Figure 2: Module address112345612111098709123456781. Insert screwdriver here© 2013 UTC Fire & Security. All rights reserved. 1 / 2 P/N 3101190 • REV 03 • REB 25JAN13WiringWire in accordance with NFPA 72 and CAN/ULC-S524,Standard for the Installation of Fire Alarm Systems and inaccordance with the local authorities having jurisdiction.Be sure to observe the polarity of the wires as shown inFigure 3.All wiring is power-limited and supervised.This module does not support two-wire smoke detectors.Figure 3: Module wiringkΩ1. Refer to the control panel technical reference manual for wiringspecifications2. Wire nut or other listed splice connector or terminal block3. Style B (Class B)4. Typical NO initiating deviceSpecificationsVoltageIDC maximum Communication line maximum 10 VDC at 350 µA 20.6 V peak-to-peakCurrentStandbyActivated 350 µA 500 µAGround fault impedance 10 kΩInitiating device circuit (IDC)EOL resistor value Circuit resistance Circuit capacitance 47 kΩ, (P/N EOL-47)50 Ω (25 Ω per wire), max.0.1 µF, max.Operating environmentTemperature Relative humidity 32 to 120°F (0 to 49°C)0 to 93%, noncondensingStorage temperature range –4 to 140°F (–20 to 60°C) Regulatory informationManufacturer Edwards, A Division of UTC Fire & SecurityAmericas Corporation, Inc.8985 Town Center Parkway, Bradenton, FL34202, USAYear ofmanufactureThe first two digits of the product serial number(located on the product identification label) arethe year of manufacture.EnvironmentalclassUL: Indoor dryNorth AmericanstandardsUL 864; CAN/ULC-S526Contact informationFor contact information, see our Web site:.2 of 2 P/N 3101190 • REV 03 • ISS 25JAN13。