Difference between revisions of "WHO=0 - Scenarios"
Jump to navigation
Jump to search
| Line 47: | Line 47: | ||
|} | |} | ||
| + | {| class="wikitable" style="float:left; margin-left: 30px;" | ||
| + | ! style="text-align:left;"| WHERE | ||
| + | ! style="text-align:left;"| Address | ||
| + | |- | ||
| + | |01..99 | ||
| + | |Control Panel 01 to 99 | ||
| + | |} | ||
{| style="width:100%; border:1px solid #EEEEEE; background-color:#FFFFCC" | {| style="width:100%; border:1px solid #EEEEEE; background-color:#FFFFCC" | ||
Revision as of 18:43, 21 November 2014
What is a scenario?
A scenario is a list of simple commands, stored in a scenario device like F420 (max. 16 scenarios) or IR 3456 (max. 20 scenarios). More and smarter scenarios can be stored in a scenario device like MH200 or the newer model MH200N. These smart scenario devices support event- and time-driven scenarios, even with IF-THEN-ELSE clauses.
Examples
Scenarios are launched in a similar way like lighting commands:
*0*5*89## launch scenario #5, connected to address 89 *0*9*48#4#02## launch scenario #9, connected to address 48 on interface 2
Since a scenario is just a list of commands, they don't have a status and therefore you can't do a status request on a scenario.
Programming a scenario
WHAT Table
| WHAT | Description |
|---|---|
| 1..16 1..20 |
Scenario 1 to 16 (F420) Scenario 1 to 20 (IR 3456) |
| 40#x | Start recording scenario x |
| 41#x | Stop recording scenario x |
| 42 | Delete all scenarios |
| 42#x | Delete scenario x |
| 43 | Lock scenario module |
| 44 | Unlock scenario module |
| 45 | Scenario module not available |
| 46 | Memory full |
| WHERE | Address |
|---|---|
| 01..99 | Control Panel 01 to 99 |
| WHO Table | WHO=1 - Lighting |
