TRICONEX 2290614底座模块,使用配置教程
如果硬件从目标1配置，逻辑/配置通电源和数据源均设置为“始终来自闪存”，存储在闪存，然后从目标2进行逻辑和硬件配置逻辑/配置电源均设置为“始终来自RAM”，即存储在RAM中，并且有良好的电池，然后在循环电源时程序员可能会显示逻辑和硬件配置不正确相同的解决方法是清除Flash，然后存储逻辑和目标2的硬件配置。
TRICONEX 2290614底座模块WinLoader在中未检测到PC COM端口升级PAC系统CPU时使用在以下情况下，WinLoader不会检测PC的COM端口是否已在使用中：试图连接到PACSystems CPU以执行固件升级如果端口已在使用中，则显示状态“正在尝试”连接“后跟”等待目标。“要继续升级，
按下“abort”（中止）按钮并断开另一个正在运行的应用程序使用COM端口。
WinLoader在运行时不显示错误无法与PACS CPU串行连接如果WinLoader无法连接到尝试连接到PACS系统CPU以执行固件升级。如果电缆在物理上没有连接到CPU或如果CPU的串行端口未配置为与WinLoader相同的波特率。在这种情况下，Winloader显示状态“正在尝试连接”，然后是“等待目标”继续升级后，按“中止”按钮并纠正电缆或波特率背景
超过恒定扫描时间故障为功率循环后产生当CPU配置为恒定扫描时（已连接电池）CPU进行电源循环，CPU记录恒定的扫描时间超出控制器故障表中的故障。可以多次调用SVC_REQ 57（逻辑驱动写入非易失性存储器）导致CPU使看门狗定时器跳闸并进入停止模式。可以调用SVC_REQ 57的次数需要考虑许多变量，软件看门狗超时值是多少，数据量是多少写入时，扫描的时间、非易失性存储（闪存）的使用期限等应用程序尝试过频繁地写入闪存，CPU可能会遇到
等待前一个写入操作完成时看门狗超时。逻辑驱动的读/写闪存服务请求不适用于高频率使用。GE Intelligent Platform建议限制通话次数至SVC_REQ 57，每次扫描一次调用，以避免导致
看门狗超时和由此产生的停止-暂停转换。
If the Hardware Config from Target 1, with Logic/Configuration Power-up
Source and Data Source both set to “Always from Flash,” is stored in
Flash, then Logic and Hardware Config from Target 2, with
Logic/Configuration Power-up Source both set to “Always from RAM,” is
stored to RAM and there is a good battery, then when power is cycled
the programmer may show that Logic and Hardware Config are not
equal. The remedy is to clear Flash and then store the Logic and
Hardware Config from Target 2.
WinLoader does not detect PC COM port in
use when upgrading PACSystems CPU
WinLoader does not detect if a PC's COM port is already in use when
attempting to connect to a PACSystems CPU to perform a firmware
upgrade. If the port is already in use it displays the status "trying to
connect" followed by "waiting for target." To proceed with the upgrade,
press the "abort" button and disconnect the other application that is
using the COM port.
WinLoader does not display error when it
can't connect serially with PACS CPU
WinLoader does not display an error message if it cannot connect to the
PACS CPU when attempting to connect to a PACSystems CPU to
perform a firmware upgrade. This occurs if the cable is physically not
connected to the CPU or if the CPU's serial port is not configured for the
same baud as WinLoader. In this case Winloader displays the status
"trying to connect" followed by "waiting for target." To proceed with the
upgrade, press the "abort" button and correct the cable or baud rate
setting.
Constant Sweep Time Exceeded fault is
generated after power cycle
When the CPU is configured for Constant Sweep (battery is connected)
and the CPU is power cycled, the CPU logs a Constant Sweep Time
Exceeded fault in the Controller fault table.Multiple calls to SVC_REQ 57 (Logic Driven Write to Nonvolatile Storage) could
result in the CPU tripping the watchdog timer and going to STOP-HALT mode.
The number of calls to SVC_REQ 57 that can be made requires consideration of
many variables, what the software watchdog timeout value is, how much data is
being written, how long the sweep is, age of nonvolatile storage (flash), etc. If the
application attempts to write to flash too frequently, the CPU could experience a
watchdog timeout while waiting for a preceding write operation to complete.
The Logic Driven Read/Write to Flash service requests are not intended for high
frequency use. GE Intelligent Platforms recommends limiting the number of calls
to SVC_REQ 57 to one call per sweep to avoid the potential of for causing a
watchdog timeout and the resulting transition to Stop-Halt.
