概述
SmartStep應(yīng)用通過使用測試組的概念幫助最大限度地提高測試效率。測試組包含操作變量和被控變量。測試組可以根據(jù)項目階段和數(shù)據(jù)需求被放入幾種不同的模式。下表顯示了測試組請求開關(guān)（STGREQ）以及對應(yīng)模式的簡要說明。
| 測試組請求開關(guān)(ST GREQ) | 描述 |
|---|---|
| TEST | 該模式在一時間里僅對一個MV進行階躍測試。中、高頻脈沖將被疊加在主測試信號中。這是收集測試數(shù)據(jù)的主要模式。 |
| TEST NO-PULSE | 該模式除了中、高頻脈沖抑制異常外與TEST模式完全相同。 |
| SUSPEND | 沒有測試動作被啟動。在這種模式下，智能向?qū)?yīng)用繼續(xù)監(jiān)控CVs以防復(fù)位模式需要。 |
| CORRECTING | 模式用于在CV限制內(nèi)驅(qū)動裝置。由CV違反準則自動觸發(fā)?？赡苄枰脩魧⒀b置過渡到“測試就緒”工作點。 |
| REPOSITION | 模式用于在CV限制內(nèi)驅(qū)動裝置。由CV違反準則自動觸發(fā)?？赡苄枰脩魧⒀b置過渡到“測試就緒”工作點。 |
| CONTROL | 全類DMCplus控制模式。在項目交付使用階段使用。 [注：該模式不能較長時間使用。DMCplus的某些功能不可用。] |
| LAB | 手動實驗?zāi)Ｊ绞且粋€用于將工廠驅(qū)動向特定工作點的修正控制模式。在協(xié)調(diào)不同工廠操作點實驗樣本收集時非常有用。 |
測試組配置
當(dāng)SmartStep technology選項啟用后，測試組在Aspen DMCplus Config中指定。配置測試組時請遵守以下規(guī)則：
?一個SmartStep應(yīng)用必須至少有一個測試組。
?一個測試組必須至少包含一個MV和一個CV
?每個MV必須屬于且僅屬于一個測試組
?每個CV可能屬于零個或多個測試組
當(dāng)某一組處于測試模式(TEST或TEST NO-PULSE)時，被控變量將被監(jiān)控是否違反約束。如果違反了約束則該組將自動投入重新定位(REPOSITION)模式。此外，如果一給定的被控變量違反了限制，含該變量的所有測試組都將投到重新定位(REPOSITION)模式。當(dāng)為一個應(yīng)用設(shè)計測試組時，這個概念是一個重要的考慮因素。
約束處理
當(dāng)某一組處于測試模式(TEST或TEST NO-PULSE)時，被控變量將被監(jiān)控是否違反約束。如果違反了約束則測試將啟動一系列行動糾正違反約束。
?測試將嘗試STCMFLAG多個單校正動作以糾正違反約束。
?測試組將會切換到修正(CORRECTING)模式，并使用多變量控制措施分立動作以糾正違反約束。
?測試組將會切換到定位(REPOSITION)模式，并使用多變量控制措施糾正違反約束。
此外，如果一給定的被控變量觸發(fā)校正(CORRECTING)或重新定位(REPOSITION)模式條件，則含該變量的所有測試組都將投到校正(CORRECTING)或重新定位(REPOSITION)模式。當(dāng)為一個應(yīng)用設(shè)計測試組時，這個概念是一個重要的考慮因素。
附原文：
Overview
A SmartStep application uses the concept of test groups to help maximize testing efficiency. A test group consists of manipulated variables and control variables. The group can be put into several different modes depending on the stage of the project and the data desired. The following table shows the test groups request switch (STGREQ) along with a brief description of the mode.
| Test Group Request (STGREQ) | Description |
|---|---|
| TEST | This mode will step test one manipulated variable at a time. High and medium frequency pulses will be superimposed on the main test signal. This is the primary mode for collecting test data. |
| TEST NO-PULSE | This mode is identical to TEST mode with the exception that high and medium frequency pulses are suppressed. |
| SUSPEND | No test moves initiated. In this mode, the SmartStep application continues to monitor the CVs in case REPOSITION mode is necessary. |
| CORRECTING | Mode used to drive the plant within CV limits. Automatically triggered by CV violation criteria. May be requested by the user to transition the unit into a "test-ready" operating point. |
| REPOSITION | Mode used to drive the plant within CV limits. Automatically triggered by CV violation criteria. May be requested by the user to transition the unit into a "test-ready" operating point. |
| CONTROL | Full DMCplus-like control mode. Used during the commissioning stages of the project. [Note: this mode cannot be used for extended periods of time. Some features of DMCplus are not available.] |
| LAB | Manual Lab mode is a modified control mode used to drive the plant to a specific operating point. Useful for coordinating the collection of lab samples at different plant operating points. |
Group configuration
Test groups are specified in Aspen DMCplus Config after the SmartStep technology option is enabled. Observe the following rules when configuring test groups:
?There must be at least one test group in a SmartStep application
?A test group must contain at least one MV and one CV
?Each MV must belong to one and only one test group
?Each CV may belong to zero or more test groups
When a group is in a test mode (TEST or TEST NO-PULSE) then the control variables are monitored for constraint violations. If a violation occurs then the group will automatically be put into REPOSITION mode. Furthermore, if a given control variable violates limits then every group that it belongs to will be put into REPOSITION mode. This concept is a key consideration when designing test groups for an application.
Constraint handling
When a group is in a test mode(TEST or TEST NO-PULSE) then the control variables are monitored for constraint violations. If a violation occurs then the tester will initiate a series of actions to correct the violation.
The tester will attempt STCMFLAG number of single correcting moves to correct the violation.
The test group will switch to CORRECTING mode and use multivariable control action with discrete moves to correct the violation.
The test group will switch to REPOSITION mode and use multivariable control action to correct
the violation.
Furthermore, if a given control variable triggers the need for CORRECTING or REPOSITION mode then every group that it belongs to will be put into CORRECTING or REPOSITION mode as well.
This concept is a key consideration when designing test groups for an application.
2015.10.19
