MVME7100-0163控制模块
。您应该可以物理访问驱动器，并且必须确保驱动器和机电系统易于控制（例如，您可以看到系统）。远程控制驱动器可能需要额外的预防措施，因此不建议这样做。使用DriveWindow，您可以主要通过两种方式控制驱动器：•浏览和使用原始控制项。•使用驱动器菜单和/或驱动器面板工具栏。我们建议您不要混合使用这两种方法，但也可以单独使用。例如，如果您使用驱动器菜单、驱动器上下文菜单或驱动器面板工具栏进行控制，请不要使用原始项来控制驱动器。为了能够通过DriveWindow控制驱动器，必须以可能的方式配置驱动器。此外，驱动器的操作员面板不能进行控制，即必须选择REM而不是LOC。另请参阅：驱动器菜单驱动器面板工具栏查看驱动器控制驱动器的状态5-2驱动器窗口2.通过原始控制项进行控制例如，您可以通过浏览浏览树窗格中的控制子树并将控制项写入浏览的项集中来控制任何驱动器。当您以这种方式控制驱动器时，DriveWindow会盲目操作-它只执行您要求它执行的操作。所以，你必须对驾驶有深入的了解。请注意，通常不使用布尔只写控件的实际值。因此，无论您在Control.Start上写ON还是OFF，都无所谓。如果驱动器处于正确的状态，仅需写入即可启动驱动器。所有检查都由驱动器完成。如果驱动器拒绝您编写的控件，则会收到错误消息。也可能是驱动器接受了您编写的控件，但默默地放弃了它。大多数新驱动器都有一个与外部控制相关的看门狗。若你们要用原始控制项来控制这样的驱动器，你们应该放上control。本地联机，锁定它以确保它保持联机，并将其写入on。所述过程控制驱动器并保持“心跳”。控制驱动器DriveWindow 2 5-3注意，因为DriveOPC通过内部写入控制来保持“心跳”。本地，ON值通常显示为质量不确定。要清除驱动器的故障记录器，请在浏览树窗格中浏览故障记录器的控制子树，并将其写入浏览项目集中的清除项目。清除故障记录器时，您不需要控制。你写的值无关紧要。仅写一次就可以清除故障记录器。另请参阅：控制驱动器浏览参数和信号更改参数2.获取和释放控制除清除故障记录器外，您需要获取驱动器的控制权，然后才能控制（即发送启动和停止等命令）驱动器。
personal injury or physical damage. You should have physical access to the drive, and you must be sure that the drive and the electromechanical system are clear to control (you can see the system, for example). Controlling a drive remotely may require extra precautions and is discouraged. With DriveWindow you can control drives principally in two ways: • Browsing and using the raw control items. • Using the Drive menu and/or the drive panel toolbar. We recommend that you do not mix the ways, but use exclusively either. For example, if you take control using the Drive menu, context menu of drive, or drive panel toolbar, do not use the raw items to control the drive. To be able to control a drive by DriveWindow, the drive has to be configured such a way that it is possible. Also, the operator panel of the drive must not have the control taken, i.e., REM must have been selected instead of LOC. See Also: Drive Menu Drive Panel Toolbar Viewing Status of Drives Controlling Drives 5-2 DriveWindow 2 1. Controlling by Raw Control Items You can control any drive by browsing the Control sub-tree in the browse tree pane and writing the control items in the browsed item set, for example. When you are controlling a drive this way, DriveWindow acts blindly - it just does what you ask it to do. So, you must have intimate knowledge about the drive. Note that the actual values of Boolean write-only controls are usually not used. So, it does not matter, whether you write ON or OFF to the Control.Start. The mere writing starts the drive, if it is in proper status. All checking is done by the drive. If the drive rejects the control you wrote, you get an error message. It may also be that the drive accepts the control you wrote, but discards it silently. Most new drives have a watchdog associated with external control. If you are going to control such a drive with the raw control items, you should put Control.Local on-line, lock it to be sure it stays on-line, and write ON into it. The procedure described takes control of the drive and keeps on the “heartbeat”. Controlling Drives DriveWindow 2 5-3 Note that because DriveOPC keeps the “heartbeat” on by internally writing to Control.Local, the ON value is usually shown with quality uncertain. To clear the fault logger of a drive, browse the Control sub-tree of Fault logger in the browse tree pane and write into the Clear item in the browsed item set. You need not to have taken control when clearing the fault logger. The value you write, does not matter. The mere writing clears the fault logger. See Also: Controlling Drives Browsing Parameters and Signals Changing Parameters 2. Taking and Releasing Control Except clearing a fault logger, you need to have control taken of a drive, before you can control (i.e., send commands like start and stop) it.
