HIEE200130R2 AFC094AE01机器人卡件
2019年8月推出14 CPE400是的，带有PME硬件配置CPE330是的，带PME硬件组态CPE302/CPE305/CPE310是的，有PME硬件构型CPE100/CPE115不支持1.3.10 SRTP不活动超时从6.00版开始，PACSystems以太网接口支持与任何PAC机器版（PME）PLC编程器的安全实时传输协议（SRTP）服务器连接上的非活动超时检查。在服务器连接断开之前，其他程序员无法从监视器模式切换到编程器模式。通过非活动超时检查，当指定的超时间隔内连接上没有活动时，以太网接口将删除已放弃的SRTP服务器连接及其所有资源。如果没有SRTP非活动超时，则被放弃的SRTP服务器连接将持续到基础TCP连接超时（通常为7分钟）。所有网络PME编程器连接最初使用30秒的SRTP非活动超时值（由“vconn_out”AUP参数设置）。PME程序员可以覆盖指定服务器连接上的初始超时值。通常，PME程序员将SRTP非活动超时设置为20秒。非活动超时值为零将禁用SRTP非活动超时检查。SRTP服务器使用5秒的内部非活动超时分辨率。这有两个效果。首先，任何非零的非活动超时值（由AUP参数设置或在编程器连接上覆盖）都将舍入为下一个5秒的倍数。此外，任何单个连接的实际SRTP非活动超时检测可能会增加5秒。实际非活动检测时间永远不会小于指定值。注意：SRTP非活动超时仅适用于通过SRTP的编程器连接。它不会影响HMI或SRTP通道。1.4以太网冗余操作冗余IP功能允许将单个IP地址分配给两个以太网模块，其中两个模块位于配置为冗余系统的两个不同PLC中。此功能已集成到产品线中，如下所示：CPU嵌入式以太网冗余支持通过以太网模块（ETM001 Jx或ETM001 Kxxx）CPL410所有固件版本不支持CPE400嵌入式以太网需要CPU固件版本9.30不支持PACSystems™ RX3i和RSTi EP TCP/IP以太网通信用户手册第1节GFK-2224Y 2019年8月简介15 CPE330嵌入式以太网需要CPU固件版本8.70支持的CPE302/CPE305/CPE310不支持不支持的CPE100/CPE115不支持的不支持的CRU320不支持除了正常唯一（直接）IP地址之外，还配置了冗余IP地址每个接口。在任何时候，共享冗余IP地址的两个以太网接口中只有一个可以使用冗余IP地址；这是“活动”单元。当PLC CPU发出命令时，该以太网接口激活冗余IP地址，并开始响应冗余IP地址以及其直接IP地址。活动单元继续响应冗余IP地址，直到命令其停用冗余IP或直到以太网接口确定其已失去与PLC CPU的通信。
August 2019 Introduction 14 CPE400 Yes, with PME Hardware Configuration CPE330 Yes, with PME Hardware Configuration CPE302/CPE305/ CPE310 Yes, with PME Hardware Configuration CPE100/CPE115 Not supported 1.3.10 SRTP Inactivity Timeout Starting with Release 6.00, the PACSystems Ethernet interface supports inactivity timeout checking on Secure Real-Time Transport Protocol (SRTP) server connections with any PAC Machine Edition (PME) PLC programmer. Until the server connection is removed, other programmers cannot switch from Monitor to Programmer mode. With inactivity timeout checking, the Ethernet interface removes an abandoned SRTP server connection and all its resources when there is no activity on the connection for the specified timeout interval. Without the SRTP inactivity timeout, an abandoned SRTP server connection persists until the underlying TCP connection times out (typically 7 minutes). All network PME programmer connections initially use an SRTP inactivity timeout value of 30 seconds (as set by the "vconn_tout" AUP parameter). PME programmers can override the initial timeout value on a specified server connection. Typically, the PME programmer sets the SRTP inactivity timeout to 20 seconds. An inactivity timeout value of zero disables SRTP inactivity timeout checking. The SRTP server uses an internal inactivity timeout resolution of 5 seconds. This has two effects. First, any non-zero inactivity timeout value (either set by AUP parameter or overridden on the programmer connection) is rounded up to the next multiple of 5 seconds. Additionally, the actual SRTP inactivity timeout detection for any individual connection may vary up to an additional 5 seconds. The actual inactivity detection time will never be less than the specified value. Note: The SRTP inactivity timeout applies only to programmer connections over SRTP. It does not affect HMI or SRTP channels. 1.4 Ethernet Redundancy Operation The Redundant IP feature allows a single IP address to be assigned to two Ethernet modules, where the two modules are in two different PLCs configured as a redundant system. This functionality has been integrated into the product line, as follows: CPU Embedded Ethernet Redundancy Support Support via Ethernet Module (ETM001-Jx or ETM001-Kxxx) CPL410 All firmware versions Not supported CPE400 Embedded Ethernet requires CPU Firmware Version 9.30 Not supported PACSystems™ RX3i and RSTi-EP TCP/IP Ethernet Communications User Manual Section 1 GFK-2224Y August 2019 Introduction 15 CPE330 Embedded Ethernet requires CPU Firmware Version 8.70 Supported CPE302/CPE305/ CPE310 Not supported Not supported CPE100/CPE115 Not supported Not supported CRU320 Not supported Supported The Redundant IP Address is configured in addition to the normal unique (direct) IP address of each interface. Only one of the two Ethernet interfaces that share the Redundant IP address may use the Redundant IP address at any time; this is the “active” unit. When commanded by its PLC CPU, this Ethernet interface activates the Redundant IP address and starts responding to the Redundant IP address in addition to its direct IP address. The active unit continues responding to the Redundant IP address until it is commanded to deactivate the Redundant IP or until the Ethernet interface determines that it has lost communications with the PLC CPU.
