MVME4600脉冲输入卡件
选择ABB。从Select OPC Server（选择OPC服务器）对话框中选择SMP，然后单击OK（确定）。OPC Server DriveWindow 2 7-37现在您可以在浏览树窗格中看到连接到DDCS/UDP设备的驱动器。如果要查看用于连接到DDCS网络的设备类型和设备的IP地址（如果有），请浏览浏览树窗格中的“属性”->“通信”，并查看项目集窗格中浏览的项目集。另请参阅：DDCS/UDP设置连接到OPC服务器OPC服务器7-38 DriveWindow 2 7.2 DDCS/UDP配置请注意，如果DDCS/UDP的配置包含无效值，对话框中的“确定”按钮将变灰。通信组它包含：•DDCS/UDP组，用于启用或禁用所选当前配置的DDCS/UDP通信。通常，默认情况下禁用DDCS/UDP通信。•用于设置广播搜索方法的按钮（近设备和Intranet设备）。OPC服务器DriveWindow 2 7-39 UDP端口组它包含：•Number，这是用于DDCS/UDP通信的PC UDP端口号。所定义的端口不得被PC的防火墙阻止。请注意，如果默认端口61332被阻止，则配置对话框的查找功能将不起作用，因为查找始终使用端口61332。•选择，允许在连接时另一个应用程序保留已定义的端口号的情况下搜索并使用空闲端口。搜索范围为49152…65535。这意味着该范围内的任何端口都不能被PC设备忙组的防火墙阻止。当连接到NETA-21时，需要一段时间才能进入DDCS网关模式。Device Busy（设备忙）组定义此等待的设置：•wait Timeout（等待超时）是电脑等待NETA-21进入网关模式的最长时间。•轮询间隔定义PC在进入DDCS网关模式时检查NETA-21忙状态的频率。OPC服务器7-40 DriveWindow 2设备主控组一次只能有一个应用程序使用DDCS/UDP设备的DDCS网络。客户端请求设备的主控权。只有拥有主控权的客户端才能使用DDCS网络。所有其他都被设备拒绝。但是，如果在指定时间内没有DDCS流量，设备将自动释放主控权。设备主控权组定义此行为的设置：•看门狗超时是DDCS/UDP设备在DDCS流量停止时自动释放主控权之前等待的时间。•强制意味着连接的客户端获得主控权，即使另一个客户端已经拥有主控权。这意味着其他客户端不能再通过DDCS网络进行通信。通常，在客户机崩溃而未释放其主控权的情况下，您使用强制。远程子网大小组远程子网的大小为2z，其中z是远程掩码中的零位数。因为远程子网设备是通过查询IP和远程子网指定的子网中的每个IP地址来搜索的，所以对于大型子网，启动时间可能非常长。
Select ABB.SMP from the Select OPC Server dialog box and click OK. OPC Server DriveWindow 2 7-37 Now you see the drives connected to the DDCS/UDP devices in the browse tree pane. If you want to see the device type used for connecting to a DDCS network and the IP address of the device (if it has one), browse to Properties -> Communication in the browse tree pane and look at the browsed item set in the item sets pane. See Also: DDCS/UDP Settings Connecting to OPC Server OPC Server 7-38 DriveWindow 2 7.2 DDCS/UDP Settings Note that if a DDCS/UDP setting contains an invalid value the OK button in the dialog box is grayed. Communication group It contains: • DDCS/UDP group, which is used to enable or disable DDCS/UDP communication for the selected Current configuration. Typically, DDCS/UDP communication is disabled by default. • Buttons (Near Devices and Intranet Devices) for settings of the broadcast search methods. OPC Server DriveWindow 2 7-39 UDP Port group It contains: • Number, which is the PC UDP port number used for DDCS/UDP communication. The port defined must not be blocked by the firewall of the PC. Note that if the default port 61332 is blocked, the Find functionality of the configuration dialog boxes does not work because Find always uses port 61332. • Selection, which allows searching and using a free port in case the defined port number is reserved by another application at connection time. The search range is 49152...65535. It means that none of the ports in the range must be blocked by the firewall of the PC. Device Busy group When connection to a NETA-21 is made, it takes time before it enters into the DDCS gateway mode. The Device Busy group defines settings for this wait: • Wait Timeout is the maximum time that the PC waits for a NETA-21 going to the gateway mode. • Poll Interval defines how often the PC checks the busy status of a NETA-21 while it is going to the DDCS gateway mode. OPC Server 7-40 DriveWindow 2 Device Mastership group Only one application can use the DDCS network of a DDCS/UDP device at a time. The client requests mastership of the device. Only the client having mastership can use the DDCS network. All others are rejected by the device. However, if there is no DDCS traffic for a specified time, the device automatically releases the mastership. The Device Mastership group defines settings for this behaviour: • Watchdog Timeout is the time that the DDCS/UDP device waits before it automatically releases the mastership when DDCS traffic ceases. • Force means that the connecting client gets the mastership even if another client already has it. It means the other client can no more communicate through the DDCS network. Typically you use forcing in a case where a client has crashed and not freed its mastership. Remote Subnet Size group Size of a remote subnet is 2z , where z is number of zero bits in the Remote Mask. Because remote subnet devices are searched by querying each IP address in the subnet specified by IP and Remote Subnet, start-up time may be very long for large subnets.
