5SHX2645L0002工控DCS系统备件
PLC编程软件
写入闪存当将非常大的程序写入闪存时，可能需要增加Windows PLC编程程序请求超时值，以避免收到请求超时消息。25秒的上限通常是令人满意的存储大型配置。IC693 PLC通常支持系统中的20个DSM314模块。系统中的其他模块（如APM和GBC模块）可以减少该数量。如果使用读取参考表或故障表的数据报，也可以进一步减少。如果同时存储配置和用户程序，则LD程序中C块或C逻辑程序的存在也可能影响系统中可能包括的DSM314模块的数量。如果存储失败，可以通过首先存储逻辑程序，然后在单独的存储请求中存储配置来解决这个问题。支持的模块的数量可以通过CPU用户存储器的大小进一步减少。基于DOS的编程器无型号检查无型号检查功能不支持将311、313、321、323或331配置存储到9.0版或更高版本的CPU。同时加载和存储当连接多个编程器时，如果一个编程员启动了存储操作，而加载操作已经在进行中，则加载请求将失败。清除参考表时，不会清除转换表。通过编程器清除参考表时，不会清除转换表。4重要产品信息GFK-1512M此固件版本解决的问题（10.60）CPU无法处理11K字节的智能模块初始化文件使用新版Horner PBM和新版VersaPro，这两个版本都创建并预期11K字节初始化文件，逻辑分析器跟踪显示从模块上的SI30接收的数据不正确。也就是说，通过背板的数据已损坏。配置的加载或验证工作正常，因此PLC内的数据似乎正确。
管理器日志
加载大型（>32K）DSM zip文件失败加载大于32K到364（存储在SNP上）失败，出现以下站点管理器日志。=log>>使用有效RAM信息初始化日志上次清除日期时间事件计数条目0 限制和开放问题ALG220/221模块的时间问题可能导致CPU读取的AI值不正确IC693ALG220/221F（及更早版本），其中板卡报告的实际%AI值可能表现出不稳定的行为（版本F及更早的版本可能显示此问题；该问题已在版本G或更高版本中修复）。应用于板卡的输入范围内的某些电流或电压水平可能导致%AI值报告错误。问题源于使用特定的光耦，这些光耦可能会显示这些CPU35x/36x模块的时序问题。（注意：CPU 341、331、321、313和311未出现此问题。）如果包含对智能模块的DOIO功能块调用的梯形图重复置于运行然后停止模式，则IC693 PLC将产生致命故障。CPU发现问题，其中包含对DOIO功能模块的调用的梯形将导致PLC耗尽系统内存。这是在PLC多次转换到运行模式并返回到停止模式时引起的。如果存储了配置，系统内存将被释放，PLC将恢复正常运行。IC693 PLC CPU在存储具有大配置的文件夹期间可能会发生致命故障IC693可编程逻辑控制器CPU在存储配置特别大的文件夹期间会产生致命故障。如果同时存储程序和配置，或者在存储过程中存在来自编程器的数据报，这可能会使情况变得更糟。PID积分贡献PID积分贡献在积分率为0或1的情况下计算不正确。存储到CPU352的CPU360配置可能会导致致命故障如果CPU360组态文件存储到CPU 352，PLC可能会在转换到运行模式时产生致命故障。从无效闪存部件读取可能会导致看门狗超时如果读取损坏的闪存部件，可能会触发PLC上的看门狗计时器。这可以通过完成有效的闪存来解决。
PLC programming software
Write to flash memory When writing a very large program to flash memory, you may need to increase the Windows PLC programming program request timeout value to avoid receiving a request timeout message. The upper limit of 25 seconds is usually a satisfactory storage large configuration. IC693 PLC usually supports 20 DSM314 modules in the system. Other modules in the system (such as APM and GBC modules) can reduce this number. If the datagram of reading reference table or fault table is used, it can also be further reduced. If the configuration and user programs are stored at the same time, the existence of the C block or C logic program in the LD program may also affect the number of DSM314 modules that may be included in the system. If the storage fails, you can solve this problem by first storing the logical program and then storing the configuration in a separate storage request. The number of supported modules can be further reduced by the size of the CPU user memory. The DOS based programmer no model check No model check function does not support storing 311, 313, 321, 323, or 331 configurations to a 9.0 or later CPU. Simultaneous loading and storage When multiple programmers are connected, if a programmer starts the storage operation and the loading operation is already in progress, the loading request will fail. When the reference table is cleared, the conversion table is not cleared. When the reference table is cleared through the programmer, the conversion table is not cleared. 4 Important product information GFK-1512M The problem solved by this firmware version (10.60) The CPU cannot process the 11K byte initialization file of the intelligent module. The new version of Horner PBM and the new version of VersaPro are used. Both versions create and expect 11K byte initialization files. The logic analyzer tracks that the data received from the SI30 on the module is incorrect. That is, the data passing through the backplane is damaged. The loading or verification of the configuration works correctly, so the data in the PLC appears to be correct.
Manager Log
Failed to load a large (>32K) DSM zip file Loading more than 32K to 364 (stored on the SNP) failed. The following site manager logs appear= Log>>Using valid RAM information to initialize the log, the last cleared date, time, event count entry 0, limit and open issues. The time issue of the ALG220/221 module may cause the AI value read by the CPU to be incorrect. IC693ALG220/221F (and earlier versions). The actual% AI value reported by the board may show unstable behavior (version F and earlier versions may show this problem; this problem has been fixed in version G or later versions). Some current or voltage levels within the input range applied to the board may cause% AI values to report errors. The problem stems from the use of specific optocouplers, which may display timing problems of these CPU35x/36x modules. (Note: CPU 341, 331, 321, 313, and 311 do not have this problem.) If the ladder containing the call to the DOIO function block of the intelligent module is repeatedly placed in the run then stop mode, the IC693 PLC will generate a fatal fault. The CPU found a problem with a ladder that contains calls to DOIO function modules that will cause the PLC to run out of system memory. This is caused when the PLC switches to the operation mode several times and returns to the stop mode. If the configuration is stored, the system memory will be released and the PLC will resume normal operation. The IC693 PLC CPU may have a fatal failure when storing a folder with a large configuration. The IC693 PLC CPU may have a fatal failure when storing a folder with a very large configuration. If the program and configuration are stored at the same time, or if there are datagrams from the programmer in the stored procedure, this may make the situation worse. PID integral contribution The PID integral contribution is not calculated correctly when the integral rate is 0 or 1. The CPU 360 configuration stored in CPU 352 may cause a fatal failure. If the CPU 360 configuration file is stored in CPU 352, the PLC may cause a fatal failure when switching to the operation mode. Reading from an invalid flash part may cause the watchdog to timeout. If a damaged flash part is read, the watchdog timer on the PLC may be triggered. This can be solved by completing effective flash memory.
