26390603-BS工控模块备件
解决的CPU问题
主题描述BOOL数组参数化块参数的使用如果用户创建一个长度大于1的BOOL参数化块，然后使用该BOOL阵列的元素作为期望非布尔值（如MOVE_INT）的函数块的参数，PLC将正常工作，不再产生CPU软报警。MOVE和SHFR WORD功能块现在在256字节边界正确工作移位寄存器功能块调用长度大于256字节的数据，先前在256个字节边界错误地移动了数据。256字节边界处的数据元素被移位到下一个元素，覆盖了该元素，而该元素又被移位到了下一个。这导致数据元素在256字节边界处被复制，而不是移位。如果源和目标数据区域在256字节边界重叠，则数据移动功能块调用也表现出类似的行为。这些问题在此版本中已修复。BIT_SEQ功能块功能不正确在以前的版本中，如果BIT_SEQ-功能块被重置，并且一个参数被传递到N参数中，固件将当前步骤设置为N值，而不首先检查N的有效性，然后，对应于当前步长的位将被设置为1。然而，如果N的值在位定序器的有效范围之外，则位设置将不在位定程器的当前边界内。在当前版本中，固件检查N的有效性，并将该值限制在位序列器的有效范围内。
CPU problems solved by this revision
The topic describes the use of BOOL array parameterized block parameters. If the user creates a BOOL parameterized block with a length greater than 1, and then uses the elements of the BOOL array as the parameters of a function block with an expected non boolean value (such as MOVE_INT), the PLC will work normally and no CPU soft alarm will be generated. MOVE and SHFR WORD function blocks now work correctly on the 256 byte boundary. The shift register function block calls data with a length greater than 256 bytes. Previously, data was moved incorrectly on the 256 byte boundary. The data element at the 256 byte boundary is shifted to the next element, overwriting the element, and the element is shifted to the next one. This causes the data element to be copied at the 256 byte boundary instead of shifted. If the source and target data areas overlap at the 256 byte boundary, the data movement function block call also shows a similar behavior. These issues have been fixed in this release. BIT_ SEQ The function of the function block is incorrect. In the previous version, if BIT_ SEQ - The function block is reset, and a parameter is passed to the N parameter. The firmware sets the current step to the N value without first checking the validity of N, and then the bit corresponding to the current step will be set to 1. However, if the value of N is outside the valid range of the bit sequencer, the bit setting will not be within the current boundary of the bit sequencer. In the current version, the firmware checks the validity of N and limits the value to the valid range of the bit sequencer.
解决的CPU问题主题描述
用户内存在正常电源关闭后未损坏之前很少出现“损坏的用户内存”故障的应用程序将不再产生此故障。Modbus函数#5和#15功能校正Modbus功能#5现在只影响指定位，而不影响同一字节中的其他位。Modbus功能#15现在只影响指定的位。编程器连接不再断开以前，在编程器被广泛用于监控数据和/或进行在线更改的情况下，PLC CPU偶尔会断开连接并无法重新连接。这将不再发生。CPU未检测到电池电量不足或缺失。电池电路阻塞二极管偶尔会有过多的泄漏，当电池电量不足时，允许电池电量不足检测电路指示电池电量不足。这是通过降低为泄漏电流提供路径的电路中的电阻值来固定的。 解决的CPU问题主题描述通电后的TOD时钟现在更新TOD时钟，以在断电和通电时与CPU的内部实时时钟相匹配。这将防止通电时TOD时钟时间出现明显的“跳跃”。%S11上使用的过渡触点一旦触发，%S11（OVR_PRE）上使用的转换触点将只传递一次扫描的电源，而不是多次扫描。蓄电池故障报告蓄电池故障已更改，因此在清除后不会再次发生。此行为与Series 90-70 CPU的行为类似。这将使电池丢失时更容易清除故障定位参考。
Topic description of CPU problems solved
Applications that rarely experience a "corrupted user memory" failure before the user memory is damaged after a normal power off will no longer experience this failure. Modbus Function # 5 and # 15 Function Correction Modbus Function # 5 now only affects finger positioning, not other bits in the same byte. Modbus Function # 15 now affects only the specified bits. Before the programmer connection is no longer disconnected, when the programmer is widely used for monitoring data and/or making online changes, the PLC CPU occasionally disconnects and cannot reconnect. This will not happen again. The CPU does not detect a low or missing battery. The battery circuit blocking diode occasionally has excessive leakage. When the battery is low, the low battery detection circuit is allowed to indicate that the battery is low. This is fixed by reducing the resistance value in the circuit that provides the path for the leakage current. The topic "CPU problems solved" describes that the TOD clock after power on now updates the TOD clock to match the internal real-time clock of the CPU during power off and power on. This will prevent a significant "jump" in the TOD clock time when powered on.% Once the transition contact used on S11 is triggered, the conversion contact used on% S11 (OVR_PRE) will only pass the power for one scan, not multiple scans. Battery Fault reports that the battery fault has changed and will not occur again after clearing. This behavior is similar to that of the Series 90-70 CPU. This will make it easier to clear the fault location reference when the battery is lost.
