DO880-1工控卡件，ABB英文使用说明
EGD命令可能返回COMMREQ状态9590H（=内部错误）当无法定位网络上的远程设备。
重度EGD服务器上的生产/消费可能导致EGD命令超时服务器设备上极大量的EGD生产和/或消耗可能导致当另一个设备尝试发送EGD时，EGD命令超时错误发送到该服务器的命令。如果EGD命令必须抢占正常生产，您可以将“gcmd\u pri”高级用户参数设置为2（参见GFK-2224，附录A）。
DO880-1工控卡件注意，这样做可能会延迟EGD交换的生产。SRTP服务器错误可能导致通道客户端超时PACSystems以太网接口中的SRTP服务器可能会遇到各种远程Series 90客户端断开SRTP连接，然后建立新连接。这可能会导致意外的通道超时错误0190H或0290H。
以太网异常日志中的SRTP服务器错误被标识为事件=2；条目2可以是001cH或0021H。当EGD命令尝试对位模式参考进行写入操作时内存范围（%I，%Q；%T，%M，%SA，%SB，%SC），其中数据量如果写入超过该引用内存的配置大小，则命令将返回故障状态，但部分数据可能会写入参考存储器。写入的部分数据量取决于起始位内存位置数据长度如下：
▪ 如果数据开始于字节边界（位置=（8*n）+1），则不会生成部分数据书面的
▪ 如果数据不是从字节边界开始（位置=（8*n）+1）和数据超过配置的参考内存8位或更多，部分数据为从起始位置写入到起始后的下一个字节边界地方▪ 如果数据不是从字节边界开始（位置=（8*n）+1）和数据超过配置的参考内存8位以下，部分数据为从声明位置写入到配置的参考内存的末尾。对于写入PLC内存命令，当将数据写入目标PLC。对于读取PLC内存或读取交换命令，可能会发生这种情况将从目标控制器接收的数据写入本地内存时。这个如果EGD命令状态指示失败。为避免将部分数据写入本地或远程控制器，请确保位内存数据传输不会超过配置的参考内存大小适当的控制器。
EGD Commands may return COMMREQ Status 9590H (= internal error) instead
of the expected B190H (= Can’t locate remote node) when unable to locate a
remote device on the network.
Very heavy EGD
production/consumption at server
may cause EGD command timeouts
Very heavy EGD production and/or consumption at a server device may cause
EGD command timeout errors when another device attempts to send EGD
commands to that server. If EGD commands must preempt normal production,
you may set the “gcmd_pri” Advanced User Parameter to 2 (see GFK-2224,
Appendix A). Note that by doing so, EGD exchange production may be delayed.
SRTP server errors can cause
timeouts at channels client
The SRTP Server in the PACSystems Ethernet Interface can encounter various
errors when the remote Series 90 client takes down an SRTP connection and then
establishes a new connection. This can cause unexpected channel timeout errors
0190H or 0290H at the client.
The SRTP server errors in the Ethernet exception log are identified as Event = 2;
Entry 2 may be 001cH, or 0021H. When an EGD Command attempts a write operation to a bit-mode reference
memory range (%I, %Q; %T, %M, %SA, %SB, %SC) where the amount of data
be written exceeds the configured size of that reference memory, the command
will return failure status but partial data may be written into the reference memory.
The amount of partial data written depends upon the starting bit memory location
and the data length as follows:
▪ If data starts on a byte boundary (location = (8*n) + 1), no partial data is
written.
▪ If data does not start on a byte boundary (location = (8*n)+1) and data
exceeds the configured reference memory by 8 or more bits, partial data is
written from the starting location to the next byte boundary after the starting
location.
▪ If data does not start on a byte boundary (location = (8*n)+1) and data
exceeds the configured reference memory by less than 8 bits, partial data is
written from the stating location to the end of configured reference memory.
For a Write PLC Memory command, this can occur when writing data into the
target PLC. For Read PLC Memory or Read Exchange commands, this can occur
when writing data received from the target controller into the local memory. The
logic application must not use any data returned to the local controller if the EGD
command status indicates failure.
To avoid writing partial data to the local or remote controller, be sure that bit
memory data transfers do not exceed the configured reference memory sizes at
the appropriate controller.
