TRICONEX 9662-810端子使用方法
發(fā)送到給定電路板的大量COMMREQ（通常大于8）相同的掃描可能會導(dǎo)致控制器中記錄模塊軟件故障故障表。也將設(shè)置功能塊。為了防止這種情況，向給定的電路板應(yīng)分布在多個掃描中，以便只有有限的向每個電路板中的給定電路板發(fā)送的COMMREQ數(shù)量（通常為8個或更少）打掃此外，應(yīng)檢查FT輸出參數(shù)是否存在錯誤。如果設(shè)置FT輸出（意味著檢測到錯誤），COMMREQ可以由應(yīng)用程序邏輯重新發(fā)布。
TRICONEX 9662-810端子使用方法C塊標(biāo)準(zhǔn)數(shù)學(xué)函數(shù)do未設(shè)置錯誤否在C塊中，標(biāo)準(zhǔn)數(shù)學(xué)函數(shù)（例如sqrt、pow、asin、acos）不設(shè)置errno如果輸入無效，則不要返回正確的值假如在極少數(shù)情況下，VDD100、VAL132或VME-1182A模塊可能無法配置在電力在很短的時間內(nèi)反復(fù)循環(huán)之后。IO丟失將產(chǎn)生模塊故障。在極少數(shù)情況下，這也可能導(dǎo)致其他模塊無法配置，不會產(chǎn)生額外的模塊故障損失。這些額外的故障可能導(dǎo)致與以太網(wǎng)接口的通信失敗。用戶可以通過關(guān)閉電源至少5分鐘來從這兩種情況中恢復(fù)秒，然后恢復(fù)電源。這將提供足夠的“休息時間”，以確保所有模塊都能正常通電。
模塊在固件期間未重置升級RX7i當(dāng)前不會在故障后重置系統(tǒng)中的任何其他模塊固件升級。這可能會導(dǎo)致模塊故障丟失智能模塊。無法通過進(jìn)行通信一些第三方序列卡PACS系統(tǒng)串行端口不適用于某些第三方串行卡。的COMMREQ狀態(tài)不正確程序名無效PACSystems的程序名始終為“LDPROG1”。當(dāng)另一個程序名用于COMMREQ訪問%L內(nèi)存，錯誤是生成的是05D5，它是無效的塊名。停止和運(yùn)行模式轉(zhuǎn)換優(yōu)先事項(xiàng)PACSystems CPU接收在停止和運(yùn)行模式之間切換的請求來自許多不同的來源。這些包括（但不限于）利潤機(jī)器版、HMIs、用戶應(yīng)用程序和運(yùn)行/停止開關(guān)。自從模式更改請求有許多潛在來源，可以在另一個模式更改請求正在進(jìn)行時接收新的模式更改請求。出現(xiàn)這種情況時，CPU評估新模式更改請求的優(yōu)先級正在進(jìn)行模式更改。如果新模式更改請求具有與已在進(jìn)行的優(yōu)先級相同或更高，CPU轉(zhuǎn)換為新模式，而不是正在進(jìn)行的模式。然而，如果新模式改變請求的優(yōu)先級低于正在進(jìn)行的請求，新模式請求為丟棄，CPU完成正在進(jìn)行的模式更改。
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.
C Block standard math functions do
not set errno
In C Blocks, standard math functions (e.g. sqrt, pow, asin, acos) do not set errno
to the correct value and do not return the correct value if an invalid input is
provided.In rare instances, a VDD100, VAL132, or VME-1182A module may not configure
after power has cycled repeatedly in a very brief period of time. A Loss of IO
Module fault will be generated.
In extremely rare instances, this may also cause other modules to fail to configure,
without generating additional loss of module faults. These additional failures may
cause communication with the Ethernet Interface to fail.
The user can recover from either of these cases by turning off power for at least 5
seconds and then restoring power. This will provide sufficient "off-time" to ensure
that all modules can power up properly.
Modules not reset during firmware
upgrades
The RX7i currently does not reset any other modules in the system after a
firmware upgrade. This may result in Loss of module faults being generated for
smart modules.
Unable to communicate through
some third party serial cards
PACS Systems serial ports do not work with some third party serial cards.
Incorrect COMMREQ status for
invalid program name
The program name for PACSystems is always "LDPROG1". When another
program name is used in a COMMREQ accessing %L memory, the error that is
generated is a 05D5, which is an invalid block name.
STOP and RUN mode transition
priority
The PACSystems CPU receives requests to change between stop and run mode
from many different sources. These include (but are not limited to) Proficy
Machine Edition, HMIs, the user application, and the RUN/STOP switch. Since
there are many potential sources for a mode change request, it is possible to
receive a new mode change request while another is already in progress.
When this occurs, the CPU evaluates the priority of the new mode change request
with the mode change that is in progress. If the new mode change request has an
equal or higher priority than the one already in progress, the CPU transitions to
the new mode instead of the one in progress. If, however, the new mode change
request has a lower priority than the one in progress, the new mode request is
discarded and the CPU completes the mode change that is in progress.
