產(chǎn)品細節(jié)介紹
Reliance 57c443a接口模塊
PCM鈷個砞）底板髯訊逾時值為5秒。PCM向CPU發(fā)送請求后，PCM在等待CPU返回響應時應用此超時。在里面大多數(shù)情況下，CPU將在5秒超時內(nèi)做出良好響應；然而，在某些情況下，CPU可能需要5秒以上的時間以響應。這些情況僅限于程序的加載或存儲和/或配置-特別是當程序中的塊大于8 KB。包含EXE塊的文件夾（同樣是*.EXE文件>8KB）最有可能導致問題。
確保PCM不要觀察背板超時，必須加載文件（使用termf）到PCM。該文件必須是名為CPU.ENV的二進制文件。
這個該文件的內(nèi)容如下（所有值都在十六進制）：一旦二進制文件CPU。ENV（如下）已創(chuàng)建，請使用termf加載CPU。ENV至PCM。然后執(zhí)行PCM軟復位。
之后執(zhí)行軟復位，PCM背板通信超時時間應為10秒。
注意安全CPU。執(zhí)行硬重置時，將不使用ENV文件在PCM上。使用CPU。ENV文件駐留在PCM中，軟件每次PCM硬復位后必須執(zhí)行復位。是意識到可以從梯形圖應用；
因此，應用程序可以修改為在電源關閉后處理所需的PCM復位定時器操作注意定時器（ONDTR、TMR和OFDTR）用于并非每次掃描都調用的程序塊中。
計時器在子塊調用之間累積時間，除非它們被重置。
這意味著它們的功能類似于在程序中使用掃描速度比主程序塊中的定時器慢得多。
對于長時間處于非活動狀態(tài)的程序塊應該以這樣一種方式進行編程，以解釋此捕獲向上功能。
與此相關的是由于使用JUMP指令。
跳過的計時器將無法趕上并將因此，不要像以前那樣積累時間執(zhí)行每次掃描。
恒定掃描恒定掃描時間（使用時）應至少設置為10大于正常掃描時間毫秒，以避免監(jiān)測或執(zhí)行在線更改時出現(xiàn)任何過掃描情況程序員。如果掃描設置不夠高。一致的過掃描條件可能導致編程器與RX7i失去通信。
大量COMMREQ發(fā)送到一次掃描中的模塊會導致故障發(fā)送給相同掃描中的給定板可能會導致模塊軟件故障記錄在控制器故障表中。
故障組為MOD_OTHR_SOFTWR（16t，10h），錯誤代碼為COMMREQ_MB_FULL_START（2）。發(fā)生這種情況時，“FT”輸出也將設置功能塊的。為了防止這種情況，發(fā)給給定板的COMMREQ應分布在多個掃描，以便只有有限數(shù)量（通常為8或更少）的COMMREQ在每次掃描中發(fā)送到給定的板。
此外應檢查FT輸出參數(shù)是否有錯誤。如果FT輸出為設置（表示檢測到錯誤），COMMREQ可以是由應用程序邏輯重新發(fā)布。
communications timeout
The PCM has a default backplane communications timeout value of 5 seconds. After the PCM has sent a request to the CPU, the PCM applies this timeout while waiting on a response back from the CPU. In most cases, the CPU will respond well within the 5–second timeout; however, in certain instances the CPU can take longer than 5 seconds to respond. These cases are limited to LOADs or STOREs of program and/or configuration -especially if blocks in the program are larger than 8 KBytes. Folders containing EXE blocks (again with *.EXE files >8 KBytes) are most likely to cause problems. To ensure that the PCMs do not observe backplane timeouts, a file must be loaded (using termf) to the PCM. The file must be a binary file named CPU.ENV. The contents of this file are as below (all values are specified in hexadecimal): Once the binary file CPU.ENV (below) is created, use termf to load CPU.ENV to the PCM. Then execute a soft reset of the PCM. After executing the soft reset, the PCM’s backplane communications timeout should be 10 seconds. CAUTION The CPU.ENV file will not be used when a hard reset is performed on the PCM. With the CPU.ENV file resident in the PCM, a soft reset must be performed after every hard reset of the PCM. Be aware that it is possible to issue a soft reset COMMREQ from the Ladder Diagram application; therefore, the application can be modified to handle the required reset of PCMs after a power cycle of the system
Timer operation
Care should be taken when timers (ONDTR, TMR, and OFDTR) are used in program blocks that are NOT called every sweep. The timers accumulate time across calls to the sub-block unless they are reset. This means that they function like timers operating in a program with a much slower sweep than the timers in the main program block. For program blocks that are inactive for large periods of time, the timers should be programmed in such a manner as to account for this catch up feature. Related to this are timers that are skipped because of the use of the JUMP instruction. Timers that are skipped will NOT catch up and will therefore not accumulate time in the same manner as if they were executed every sweep.
Constant sweep
Constant Sweep time, when used, should be set at least 10 milliseconds greater than the normal sweep time to avoid any oversweep conditions when monitoring or performing on-line changes with the programmer. Window completion faults will occur if the constant sweep setting is not high enough. A consistent over sweep condition can cause the programmer to lose communications with the RX7i. Large number of COMMREQs sent to module in one sweep causes faults A large number of COMMREQs (typically greater than 8) sent to a given board in the same sweep may cause Module Software faults to be logged in the Controller fault table. The fault group is MOD_OTHR_SOFTWR (16t, 10h) and the error code is COMMREQ_MB_FULL_START (2). When this occurs, the “FT” output of the function block will also be set. To prevent this situation, COMMREQs issued to a given board should be spread across multiple sweeps so that only a limited number (typically 8 or less) of COMMREQs are sent to a given board in each sweep. In addition, the FT output parameter should be checked for errors. If the FT output is set (meaning an error has been detected), the COMMREQ could be re-issued by the application logic.
公司主營產(chǎn)品圖展示
產(chǎn)品優(yōu)勢
1：國外專業(yè)的供貨渠道，具有價格優(yōu)勢
2：產(chǎn)品質量保證，讓您售后無憂
3：全國快遞包郵
4：一對一服務
公司主營范圍簡介
PLC可編程控制器模塊，DCS卡件，ESD系統(tǒng)卡件，振動監(jiān)測系統(tǒng)卡件，汽輪機控制系統(tǒng)模塊，燃氣發(fā)電機備件等，優(yōu)勢品牌：Allen Bradley、BentlyNevada、ABB、Emerson Ovation、Honeywell DCS、Rockwell ICS Triplex、FOXBORO、Schneider PLC、GE Fanuc、Motorola、HIMA、TRICONEX、Prosoft等各種進口工業(yè)零部件、歐美進口模塊。
產(chǎn)品廣泛應用于冶金、石油天然氣、玻璃制造業(yè)、鋁業(yè)、石油化工、煤礦、造紙印刷、紡織印染、機械、電子制造、汽車制造、塑膠機械、電力、水利、水處理/環(huán)保、鍋爐供暖、能源、輸配電等等
