MVME297-128模塊控制器
該操作由DriveWindow線程使用非活動(dòng)項(xiàng)完成。7.1.4在線所有在線值（驅(qū)動(dòng)器狀態(tài)刷新、項(xiàng)目集窗格中的在線項(xiàng)目等）的處理方式相同，但有幾個(gè)組，因此有幾個(gè)DriveOPC線程處理它們。驅(qū)動(dòng)器狀態(tài)刷新、驅(qū)動(dòng)器面板工具欄、監(jiān)視器以及項(xiàng)目集窗格中當(dāng)前可見(jiàn)的項(xiàng)目集都有活動(dòng)組。當(dāng)前可見(jiàn)項(xiàng)目集以外的組未處于活動(dòng)狀態(tài)。高級(jí)信息DriveWindow 2 10-23這些值由DriveOPC線程讀取，該線程還調(diào)用DriveWindow中的建議接收器。在advice接收器中，緩存值，并將消息發(fā)布到DriveWindow線程，然后由該線程繪制值。在線項(xiàng)目在活動(dòng)組中處于活動(dòng)狀態(tài)。7.1.5運(yùn)行監(jiān)視器在其他方面，運(yùn)行監(jiān)視器的處理方式與所有其他在線項(xiàng)目相同，但DriveWindow中有一個(gè)額外的測(cè)量緩沖區(qū)。高級(jí)信息10-24 DriveWindow 2 7.1.6暫停監(jiān)視器當(dāng)監(jiān)視器暫停時(shí)，數(shù)據(jù)仍會(huì)收集到測(cè)量緩沖區(qū)中，但在監(jiān)視器繼續(xù)運(yùn)行之前，DriveWindow中的緩存不會(huì)更新。7.1.7寫(xiě)入值始終寫(xiě)入設(shè)備。寫(xiě)入的值也被緩存，但質(zhì)量被標(biāo)記為不確定。DriveWindow會(huì)立即從設(shè)備中讀取值（如果可以讀?。?，因此很少看到不確定的質(zhì)量。然而，DriveOPC可能知道項(xiàng)目之間的某些連接（例如，控制和狀態(tài)項(xiàng)目），其中寫(xiě)入一個(gè)項(xiàng)目也會(huì)更改另一個(gè)項(xiàng)目的值。DriveOPC在其緩存中進(jìn)行內(nèi)部更改，這也會(huì)導(dǎo)致其他項(xiàng)目的質(zhì)量不確定，但DriveWindow不會(huì)立即對(duì)其進(jìn)行讀取。下文中未顯示回讀，但其執(zhí)行方式與更新中的相同。7.1.8控制。本地項(xiàng)目控制。本地在DriveOPC中有特殊處理。請(qǐng)注意，并非所有驅(qū)動(dòng)器都有此項(xiàng)。高級(jí)信息DriveWindow 2 10-25項(xiàng)目的目的是通過(guò)DriveWindow獲取和釋放控制。當(dāng)值ON寫(xiě)入項(xiàng)目時(shí)，將采取控制。但是，許多驅(qū)動(dòng)器都有一個(gè)看門(mén)狗，它要求在10秒內(nèi)刷新ON值，否則驅(qū)動(dòng)器會(huì)出現(xiàn)故障，面板丟失。除了正常向項(xiàng)目寫(xiě)入值外，DriveOPC在讀取項(xiàng)目時(shí)也會(huì)在內(nèi)部寫(xiě)入ON值，邏輯如下：?從設(shè)備讀取項(xiàng)目（并緩存）。?如果讀取值為ON，并且自上次寫(xiě)入ON值后已過(guò)0.5秒，則重新寫(xiě)入值ON（并以不確定的質(zhì)量緩存）。由于DriveOPC在內(nèi)部讀取活動(dòng)組中的周期性活動(dòng)項(xiàng)目，因此只要在DriveWindow的項(xiàng)目集窗格中鎖定并使項(xiàng)目聯(lián)機(jī)，看門(mén)狗就可以保持活動(dòng)狀態(tài)。但是，如果您要使用驅(qū)動(dòng)器面板工具欄，當(dāng)控制被獲取時(shí)，它也會(huì)執(zhí)行同樣的操作，我們不建議將項(xiàng)目也放到項(xiàng)目集窗格中。
The operation is done by a DriveWindow thread using inactive items. 7.1.4 On-line All on-line values (drive status refresh, on-line items in the item sets pane, etc.) are handled the same way, but there are several groups and thus several DriveOPC threads handling them. There are active groups for the drive status refresh, the drive panel toolbar, the monitor, and for the item set currenlty visible in the item sets pane. Groups for other than the currently visible item set are not active. Advanced Information DriveWindow 2 10-23 The values are read by the DriveOPC thread, which also calls back the advise sink in DriveWindow. Within the advise sink, the values are cached, and a message is posted to a DriveWindow thread, which then draws the values. The on-line items are active in an active group. 7.1.5 Running Monitor A running monitor is otherwise handled the same way as all other on-line items, but there is an additional measuring buffer within DriveWindow. Advanced Information 10-24 DriveWindow 2 7.1.6 Paused Monitor While a monitor is paused, the data is still collected into the measuring buffer, but the cache within DriveWindow is not updated until the monitor is continued. 7.1.7 Writing Values are always written to the device. The written value is also cached, but quality is marked uncertain. DriveWindow reads immediately the value back (if it is readable) from the device, so the uncertain quality is rarely seen. However, DriveOPC may know some connections between items (control and status items, for example), in which writing an item also changes the value of another item. DriveOPC does the change internally in its cache, which causes the quality of the other item to be uncertain, too, but the immediate read-back by DriveWindow is not done for it. The read-back is not shown in the following, but it is done the same way as in update. 7.1.8 Control.Local The item Control.Local has a special handling within DriveOPC. Note that not all drives have this item. Advanced Information DriveWindow 2 10-25 Purpose of the item is to take and release control by DriveWindow. When the value ON is written to the item, control is taken. However, many drives have a watchdog, which requires the ON value to be refreshed within 10 seconds, otherwise the drive faults with panel loss. In addition to writing values normally to the item, DriveOPC internally also writes the ON value, when the item is read, with the following logic: ? The item is read from the device (and cached). ? If the read value is ON, and 0.5 seconds has elapsed since the ON value was written last time, value ON is re-written (and cached with quality uncertain). Because DriveOPC internally reads cyclically active items in an active group, a watchdog can be kept alive just by locking and putting the item on-line in the item sets pane in DriveWindow. However, if you are going to use the drive panel toolbar, which does the same thing when control is taken, we do not recommend putting the item on-line in the item sets pane, too.
