User manual AMX CAFE DUET V1.8

[. . . ] instruction manual Café DuetTM Integrated Development Environment for NetLinx Duet (version 1. 8) User's Guide Software Software License and Warranty Agreement LICENSE GRANT. AMX grants to Licensee the non-exclusive right to use the AMX Software in the manner described in this License. This license does not grant Licensee the right to create derivative works of the AMX Software. The AMX Software consists of generally available programming and development software, product documentation, sample applications, tools and utilities, and miscellaneous technical information. [. . . ] · An example is: www. amx. com/device/switcher. · If the module is ever updated at some later date, this is the location that should be used (if present) to retrieve the updated JAR files. · An example is: www. amx. com/device/switcher/update. · A specification of native code contained within this module's JAR file. · The copyright information for this module. · An example is: Copyright (c) 2006 AMX Corporation. · A text description of the vendor. · An example is: AMX Corporation. · This section specifies any additional Device-specific/User-defined manifest items. · Add a manifest items by pressing the Add button or remove additional manifest items by placing a checkmark next to the entry and using the Remove button. · Manifest items are entered within the two fields in the following format: - The first field is the Header/Key (the header/key must be unique). · This section specifies the package names (with optional version specifications) that must be imported. These packages must be exported by other modules. · Add a package by pressing the Add button or remove packages by placing a checkmark next to the entry and using the Remove button. · Packages added by the Café Duet Module wizard should not be removed. · Fill the version fields with the specification version in the following format:'major. minor. micro' (include the periods between the numbers). · An example is: com. amx. duet. da or com. amx. duet. devicesdk; with the specification version of 1. 0. 0. · This section specifies the package names (with optional version specifications) that can be exported. · Add a package by pressing the Add button or remove packages by placing a checkmark next to the entry and using the Remove button. · Fill the version fields with the specification version in the following format:'major. minor. micro' (include the periods between the numbers). · If the package is repacked later, it must then be updated within the editor. Exported Packages must be unique among all modules. [. . . ] Refer to the Using NetLinx Studio to Transfer JAR Files section on page 37 for more information. If you use a 3-file format (UI. AXS, Main. AXS, or Comm. JAR), then ONLY the Build Active System and Build Workspace options are functional. The Build > Compile option is only available if the actual AXS file is open. If you have linked it only to your Workspace, use the Build > ActiveSystem option. Step 3 - Sending the file to the NetLinx Master 1. [. . . ]