User manual AMX I!-MACROMANAGER

[. . . ] S o l u t i o n s Software Limited Agreement LIMITED WARRANTY LIMITED WARRANTY. AMX Corporation warrants that the SOFTWARE will perform substantially in accordance with the accompanying written materials for a period of ninety (90) days from the date of receipt. Any implied warranties on the SOFTWARE and hardware are limited to ninety (90) days and one (1) year, respectively. Some states/countries do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you. [. . . ] Deleting macros will not delete all references to the macro, only the macro itself. i!-MacroScheduler stores the schedule information in a file called MMSchedule. bin located in the doc:\user\schedule directory. All event information will be stored in this file and recalled during power up. Any event scheduled by the user is stored and will not be lost during a power cycle. The scheduling engine will always attempt to read the MMSchedule. bin file on start up. If you are loading a new program containing macro scheduling into an old master that used to have macro scheduling, you should use FTP to browse the NetLinx master's file system and delete the old schedule file. Otherwise, the old scheduling information will be automatically loaded. NetLinx Master firmware (build 130 or greater) supports up to 199 macros. i!-MacroManager 1 Introduction 2 i!-MacroManager Programming i!-MacroManager Programming i!-MacroManager i!-MacroManager is implemented as a series of NetLinx modules to simplify adding macro functionality to your program. To add any of the i!-MacroManager modules to your program, simply add the module definition and all it's parameters to your code and integrate the sample touch panel pages for that module into your touch panel design. One simple way of doing this is to save the i!-MacroManager test file as an include file that you can include into your main program. To integrate the touch panel pages, copy each page and popup page from the i!-MacroManager test touch panel file and paste it into your design. After copying the popup pages to the new file, you will need to create the necessary popup groups and group the popup properly. As an option you can base your design on the i!-MacroManager test touch panel file. If the channel and variable text codes for i!-MacroManager conflict with existing channel or variable text codes, you can move i!-MacroManager to another device using Power Assign and editing the touch panel devices in the include file. In order to use i!-MacroManager, you will need to program and define a series of actions through i!-ConnectLinx. The i!-ConnectLinxEngineMod module is included with i!-MacroManager and some simple examples appear in the i!-MacroManager test file. For complete documentation on i!-ConnectLinx, download the i!-ConnectLinx install from the AMX web site. Once the i!-ConnectLinx programming has been established, choose which i!-MacroManager features you want to include in your program and add the corresponding module code and pages. The following list describes the i!-MacroManager modules: i!-MacroEngineMod This is the macro engine module. This module executes macros and must always be included for any i!-MacroManager functions. This module requires the i!-ConnectLinxEngineMod module. i!-MacroEditorMod This is the macro editor module. Without this module, i!-MacroScheduler cannot run schedules based on sunrise/sunset. Complete documentation for i!-TimeManager can be downloaded from the AMX website. Programming i!-MacroEngineMod i!-MacroEngineMod appears on the NetLinx bus as a NetLinx device. [. . . ] Run event number and re-schedule the event (if it can be rescheduled). Cancel event from running today and re-schedule the event (if it can be rescheduled) Set Date format European format: Day/Month/Year Set Date format US format: Month/Day/Year Set Time format to 12 hour format: [01-12]:[00-59] [AM, PM] Set Time format to 24 hour (military) format: [00-23]:[00-59] Turn on unsolicited feedback. As today's event lists change, they will be sent (see string section below). (Default) Reset the schedule engine to re-schedule all events and re-build the event list for today. [. . . ]