DSQC602 模块卡件
参考存储器
从字节边界开始(位置=(8 n) +1),则不写入部分数据。▪ 如果数据不是从字节边界开始(位置=(8n) +1)且数据超过配置的参考存储器8位或更多位时,部分数据从起始位置写入起始位置之后的下一字节边界。▪ 如果数据不是从字节边界开始(位置=(8n) +1),并且数据超过配置的参考存储器小于8位,则部分数据从状态位置写入配置的参考内存的末尾。对于“写入PLC内存”命令,当将数据写入目标PLC时可能会发生这种情况。对于读取PLC内存或读取交换命令,当将从目标控制器接收的数据写入本地CPU内存时,可能会发生这种情况。如果EGD命令状态指示故障,逻辑应用程序不得使用返回到本地CPU的任何数据。为避免将部分数据写入本地或远程PLC,请确保位存储器数据传输不超过相应PLC的配置参考存储器大小。请勿在不正确的插槽中使用CPU。如果RX3i CPU放置在其配置的插槽以外的插槽中,以太网接口的操作会中断。
以太网异常日志事件
可能会发生各种以太网异常日志事件,例如(事件=02H,条目2=0030H或0035H或0039H或001eH或001fH)或(事件=08H,条目2=000bH)。10 RX3i以太网接口模块IPI IC695ETM001-JX GFK-2332Z 2017年11月限制和开放问题主题描述当以太网接口出现致命闪烁代码时未记录CPU故障当以太网接口发生致命闪烁代码后,CPU不会记录任何控制器或I/O故障。应用程序应监控LAN接口OK状态位,以检测模块丢失。EGD I/O在重载下具有意外变化EGD I/O具有间歇性意外变化。对于生产交换,EGD样品可能会偶尔延迟生产期或更长时间。清除大型硬件配置可能会导致日志事件08/20 A日志事件08H,条目2=0020H,当清除了大型硬件配置并且传输在其他服务器连接上处于活动状态时,可能会发生。可以安全地忽略此日志事件。复位按钮复位按钮动作不同于其他PACSystems以太网产品。在RX3i以太网模块上,模块通电时按钮的状态可以改变重启按钮的行为。在正常操作下,按下按钮会产生上升沿信号,触发模块重启。然而,如果在电源激活时按下按钮(在接通电源之前按下按钮或在重启后继续按住按钮),则按钮的功能将反转。当稍后释放按钮时,检测到“错误”上升沿,从而触发不适当的模块重启。这在其他PACSystems以太网产品上不会发生。EGD命令偶尔返回0x54A0的COMMREQ状态字值偶尔返回
Reference memory
Starting from the byte boundary (position=(8 n)+1), no partial data will be written. ▪ If the data does not start from the byte boundary (position=(8 n)+1) and the data exceeds 8 or more bits of the configured reference memory, part of the data is written to the next byte boundary after the start position from the start position. ▪ If the data does not start from the byte boundary (position=(8 n)+1), and the data exceeds the configured reference memory by less than 8 bits, part of the data is written to the end of the configured reference memory from the status position. For the Write to PLC Memory command, this can happen when writing data to the target PLC. For reading PLC memory or reading exchange commands, this may happen when the data received from the target controller is written to the local CPU memory. If the EGD command status indicates a failure, the logical application must not use any data returned to the local CPU. To avoid writing some data to the local or remote PLC, make sure that the bit memory data transfer does not exceed the configuration reference memory size of the corresponding PLC. Do not use the CPU in an incorrect slot. If the RX3i CPU is placed in a slot other than its configured slot, the operation of the Ethernet interface will be interrupted.
Ethernet Exception Log Events
Various Ethernet exception log events may occur, such as (event=02H, entry 2=0030H or 0035H or 0039H or 001eH or 001fH) or (event=08H, entry 2=000bH). 10 RX3i Ethernet Interface Module IPI IC695ETM001-JX GFK-2332Z November 2017 Restricted and Open Issues Topic Description When the Ethernet interface has a fatal flash code, no CPU failure is recorded When the Ethernet interface has a fatal flash code, the CPU will not record any controller or I/O failure. The application should monitor the LAN Interface OK status bit to detect a module loss. EGD I/O has unexpected changes under heavy load EGD I/O has intermittent unexpected changes. For production exchange, EGD samples may occasionally delay the production period or longer. Clearing a large hardware configuration may result in log event 08/20 A, log event 08H, entry 2=0020H. This may occur when the large hardware configuration is cleared and the transmission is active on other server connections. This log event can be safely ignored. The action of the reset button is different from that of other PACSystems Ethernet products. On the RX3i Ethernet module, the status of the button when the module is powered on can change the behavior of the restart button. Under normal operation, pressing the button will generate a rising edge signal and trigger the module to restart. However, if the button is pressed while the power is active (either before turning on the power or after restarting), the function of the button will be reversed. When the button is released later, an "error" rising edge is detected, triggering an improper module restart. This will not happen on other PACSystems Ethernet products. The EGD command occasionally returns the COMMREQ status word value of 0x54A0