概述
SmartStep应用通过使用测试组的概念帮助最大限度地提高测试效率。测试组包含操作变量和被控变量。测试组可以根据项目阶段和数据需求被放入几种不同的模式。下表显示了测试组请求开关（STGREQ）以及对应模式的简要说明。
| 测试组请求开关(ST GREQ) | 描述 |
|---|---|
| TEST | 该模式在一时间里仅对一个MV进行阶跃测试。中、高频脉冲将被叠加在主测试信号中。这是收集测试数据的主要模式。 |
| TEST NO-PULSE | 该模式除了中、高频脉冲抑制异常外与TEST模式完全相同。 |
| SUSPEND | 没有测试动作被启动。在这种模式下，智能向导应用继续监控CVs以防复位模式需要。 |
| CORRECTING | 模式用于在CV限制内驱动装置。由CV违反准则自动触发。可能需要用户将装置过渡到“测试就绪”工作点。 |
| REPOSITION | 模式用于在CV限制内驱动装置。由CV违反准则自动触发。可能需要用户将装置过渡到“测试就绪”工作点。 |
| CONTROL | 全类DMCplus控制模式。在项目交付使用阶段使用。 [注：该模式不能较长时间使用。DMCplus的某些功能不可用。] |
| LAB | 手动实验模式是一个用于将工厂驱动向特定工作点的修正控制模式。在协调不同工厂操作点实验样本收集时非常有用。 |
测试组配置
当SmartStep technology选项启用后，测试组在Aspen DMCplus Config中指定。配置测试组时请遵守以下规则：
•一个SmartStep应用必须至少有一个测试组。
•一个测试组必须至少包含一个MV和一个CV
•每个MV必须属于且仅属于一个测试组
•每个CV可能属于零个或多个测试组
当某一组处于测试模式(TEST或TEST NO-PULSE)时，被控变量将被监控是否违反约束。如果违反了约束则该组将自动投入重新定位(REPOSITION)模式。此外，如果一给定的被控变量违反了限制，含该变量的所有测试组都将投到重新定位(REPOSITION)模式。当为一个应用设计测试组时，这个概念是一个重要的考虑因素。
约束处理
当某一组处于测试模式(TEST或TEST NO-PULSE)时，被控变量将被监控是否违反约束。如果违反了约束则测试将启动一系列行动纠正违反约束。
•测试将尝试STCMFLAG多个单校正动作以纠正违反约束。
•测试组将会切换到修正(CORRECTING)模式，并使用多变量控制措施分立动作以纠正违反约束。
•测试组将会切换到定位(REPOSITION)模式，并使用多变量控制措施纠正违反约束。
此外，如果一给定的被控变量触发校正(CORRECTING)或重新定位(REPOSITION)模式条件，则含该变量的所有测试组都将投到校正(CORRECTING)或重新定位(REPOSITION)模式。当为一个应用设计测试组时，这个概念是一个重要的考虑因素。
附原文：
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
