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.
