BlockSim 8: State Change Triggers: Difference between revisions
Jump to navigation
Jump to search
Dingzhou Cao (talk | contribs) |
Dingzhou Cao (talk | contribs) |
||
Line 1: | Line 1: | ||
==State Change Triggers == | ==State Change Triggers == | ||
=== Description === | === Description === | ||
*Standard blocks can have state change triggers enabled by checking "Enable State Change Triggers (SCT)" property in a standard block/event properties. | |||
*When a block has state change triggers enabled, it can be set to start each simulation in an OFF state. In this case, unless some event turns the block ON, the block will remain down for the entire simulation. | |||
*The user can turn a block ON that is in an OFF state by associating a maintenance group with the options "Activate when an item in the maintenance group goes down" or "Activate when an item in the maintenance group is restored" | |||
*The user can turn a block OFF that is in an ON state by associating a maintenance group with the options "Deactivate when an item in the maintenance group goes down" or "Deactivate when an item in the maintenance group is restored" | |||
*This feature allows to mimic standby containers in COLD standby. However, blocks do not have to be in a parallel configuration so additional flexibility is allowed from traditional containers. In addition, maintenance groups can be associated with subdiagram blocks so that complex standby configurations can be modeled. | |||
*State change triggesr also allow modeling dependent shut downs. | |||
*Upon restoration of a Block, the user must select between one of the following State Upon Repair choices: Always On, Always Off, Default On Unless SCT Overridden, Default Off Unless SCT Overridden |
Revision as of 22:00, 25 July 2011
State Change Triggers
Description
- Standard blocks can have state change triggers enabled by checking "Enable State Change Triggers (SCT)" property in a standard block/event properties.
- When a block has state change triggers enabled, it can be set to start each simulation in an OFF state. In this case, unless some event turns the block ON, the block will remain down for the entire simulation.
- The user can turn a block ON that is in an OFF state by associating a maintenance group with the options "Activate when an item in the maintenance group goes down" or "Activate when an item in the maintenance group is restored"
- The user can turn a block OFF that is in an ON state by associating a maintenance group with the options "Deactivate when an item in the maintenance group goes down" or "Deactivate when an item in the maintenance group is restored"
- This feature allows to mimic standby containers in COLD standby. However, blocks do not have to be in a parallel configuration so additional flexibility is allowed from traditional containers. In addition, maintenance groups can be associated with subdiagram blocks so that complex standby configurations can be modeled.
- State change triggesr also allow modeling dependent shut downs.
- Upon restoration of a Block, the user must select between one of the following State Upon Repair choices: Always On, Always Off, Default On Unless SCT Overridden, Default Off Unless SCT Overridden