10. Click Next to continue to the Product Registration dialog (FIG. 3). Enter a First and
Last Name, and e-mail address before proceeding.
FIG. 2 Caf Duet - Previous installation detected screen
FIG. 3 Caf Duet Setup License Registration screen
11. Click Next after this information has been completely entered to proceed. 12. In the License Registration dialog (FIG. 4), enter the Serial Number. The serial
number is printed on the Caf Duet CD case. This serial number will work on only one PC. Once the Serial Number has been entered and a license key retrieved from AMX, you cannot install the software on a different PC using the same serial number. The serial number entered here is transmitted to AMX for verification. You must have an active Internet connection to complete this step. After the serial number is registered, AMX generates a License Key for this installation and locks the serial number to the target PC. The license key is transmitted back to your computer and then validated. Only after the license key is validated will the installation proceed.
FIG. 4 Caf Duet Setup License Registration screen
Should the license key not match, an on-screen dialog (FIG. 5) informs you that the serial number given is either invalid or already in use on another machine. If you believe that you have received this message in error, use the dialogs information to contact AMX for further assistance.
FIG. 5 Caf Duet Serial Number Registration Error screen
13. Once the license registration process has completed, the successful registration dialog
(FIG. 6) is displayed, containing the information entered in the previous two dialogs, including the entered Name, e-mail, Serial Number, and License Key retrieved from AMX. Keep this information available (for possible future support use).
14. Click the Next button to complete the installation.
If there is a failure during the registration process, contact AMX Technical Support for assistance.
FIG. 6 Caf Duet Setup Successful License Registration screen
15. Click the Next button in the Program Manager Group screen. This screen allows you
to select the Program Manager group where you wish Caf Duet to reside.
16. From the Shortcuts screen, select whether to install a Desktop shortcut, and click
17. The last screen indicates a successful installation of the application. Clicking the

Next button finalizes the installation process and launches the Caf Duet application.
If Caf Duet is uninstalled, only the application is removed. Usercreated files will remain on the PC, in the Caf Duet directory.
The JRE (Java 2 Runtime Environment) is installed as part of the installation executable. The Cafe Duet readme.txt file (located in C:\Program Files\ AMX Control Disc\Cafe Duet) is also installed as part of the installation executable and provides a description of the application and gives a version number. The JRE readme.txt file (located in C:\Program Files\ AMX Control Disc\Cafe Duet\Jre) provides a description of the JRE and gives a version number.
Launching Caf Duet 1. Double-click the Cafe Duet icon to launch the application. If selected during the
installation process, the icon appears on your desktop.
2. Once Caf Duet begins to run, a Workspace Launcher appears on-screen (FIG. 7) and
asks you to select a workspace location. Use the Browse button to choose a folder location where the projects will be stored. To maintain a selected directory as the default location for project storage even after the session ends, select the Use this as the default and do not ask again field.
FIG. 7 Workspace Launcher - Select a workspace screen
Overview of the Duet Plug-in

Application Preferences

Configuration of the Caf Duet application preferences is accomplished via the Duet Preferences and Manifest Editor - Preferences dialogs, as described in the following sub-sections.
Setting up the Caf Duet Preferences 1. From the menu bar, select Window > Preferences > Duet (FIG. 8).
FIG. 8 Preferences dialog - Duet Preferences
All directory and file locations are set to their default parameters. The four available Caf Duet general settings are: Platform Directory: location of the Duet platform (including the Device SDK and the Duet Platform JAR files (API). NetLinx Compiler Path: location of the NetLinx Compiler executable. Module Export Directory: location where the module is packed (refer to the Packing a Module section on page 29 for more information). Persist the Device Class Metadata during the process of packing the module: by default this option is selected. When working with other AMX Software, this option provides the ability to collect Device Class information such as: Device Class functions, function parameters, etc., so that future AMX applications can make smart decisions based on that previously obtained metadata.
Caf Duet v1.6 - Users Guide 9
- If this option is not selected then the Device Class metadata information is not collected; which in turn speeds-up the Module packing process. - Another result of disabling this option is that the JAR Export - Select Methods dialog (FIG. 20) is then prevented from being displayed. This can be helpful during the development phase, but remember to turn this option back on when you are ready to release your module. This generated metadata is very important to the Visual Architect application when building its system.

Manifest Editor field information.
Creating a Duet Module Project
1. Select File > New > Project to launch the New Project Wizard. The first dialog in the
wizard is the New Project dialog.
2. In the New Project - Select dialog, choose the Duet Modules entry from the left
window, and Duet Module Project in the right window (FIG. 10).
3. Click Next to continue to the New Duet Module Project dialog (FIG. 10). 4. In the New Duet Module Project dialog, enter a descriptive name for the new project
(up to 55 alpha-numeric characters). Note that by default, the Create new project in workspace option is selected. If you want to change this directory location you must first select the Create Project from existing source option and then click the Browse button to change this directory.
New Project - Select dialog
New Duet Module Project dialog
FIG. 10 Creating a new Duet Module project
The fields and options in this dialog include:
Project name: The Project name field must not be empty nor can it be a single period character ("."). It must not end in a period character nor can it contain any of the following characters: \\, /, :, *, ?, ", <, >, |. This field can not contain the following names as they are reserved device names for the platform: aux, clock$, com1, com2, com3, com4, com5, com6, com7, com8, com9, con, lpt1, lpt2, lpt3, lpt4, lpt5, lpt6, lpt7, lpt8, lpt9, nul, prn. An example is: amxswitcher. This refers to the directory in which the new module project will be created (indicated in the read-only Directory field). Create new project in workspace: When selected, the New Project Wizard creates a new project with the specified name within the workspace. Create project from existing source: When selected, you are specifying the location from which the New Project Wizard will retrieve an existing project. Use the Browse button to navigate to the location of an existing project. These selections determine which type of compiler compliance your project will use. Use default compiler compliance: When selected, the New Project Wizard creates a new project using the default compiler compliance. The default compiler compliance can be configured from within the Compiler Preferences page which is accessed by selecting the blue Configure default. link located to the right of this option. Use a project specific compliance: When selected, you are given the option of selecting the compiler compliance from the drop-down list of available options.

Device-Category Select the control method used by the device that the module is being developed for (IR, Serial, Relay, IP, IP & Serial, or Other). Text is required within this field.

Device-Revision

Enter the firmware version used by the target device (up to 55 alpha-numeric characters). Text is required within this field. An example is:1.0.0 (revision 1.0.0 of the device firmware). The version must be in the format: major.minor.micro (where major, minor, and micro are numbers). The Module-Version information is used to indicate that something has been changed in the driver (ex. a fix) whereas the Device-Revision indicates something has changed in the underlying driver's protocol (indicating a device firmware change). An increment of the Device-Revision mandates an increment of the Module-Version; but an increment of Module-Version does not necessarily mean a change to the Device-Revision. Refer to the Regenerating the Project files section on page 33 for those procedures necessary to regenerate the project files after a change to the firmware version information. Enter the Device Global Unique Identification. This optional information is provided by some manufacturers.

Device-GUID

Click Next to save the device information and module settings, and continue to the New Duet Module - Duet Module Devices dialog.
Generating a new device class
Select from a list of available Duet devices to generate a new device class, in the Duet Module Devices dialog (FIG. 13).
Package Name By default, this field is populated with "com.make.model.revision"; it must be a valid Java package name. If the user chooses to overwrite this information, the devices package name (up to 255 alpha-numeric characters) should be unique to this module.Text is required within this field. An example is: com.amx.switcher.v1_0_0 (where you are controlling an AMX switcher). The class name for this field is pre-generated with a combination of the make and model entered on the previous Duet Module Content dialog. Note: The Class Name (up to 255 alpha-numeric characters) is recommended to start with an uppercase letter. Text is required within this field. An example is: AMXSwitcher.

The specific model number of the device being configured. This field can hold up to 255 alpha-numeric characters. This field cannot be empty. You can enter a series of devices by separating each with a comma (see example below). Examples are: AMXSwitcher995 or AMXSwitcher123, AMXSwitcher456. This drop-down list provides choices for the control method used by the device. Available choices are: IR, Serial, Relay, IP, IP & Serial, or Other. This field cannot be empty. A choice must be made. The firmware version installed within the device being used. This field can hold up to 55 alpha-numeric characters and is required. The version must be in the following format: major.minor.micro (where these are numbers). An example is: 1.0.0 (revision/version 1.0.0 of the device firmware). The Module-Version information is used to indicate that something has been changed in the driver (ex. a fix) whereas the Device-Revision indicates something has changed in the underlying driver's protocol (indicating a device firmware change). An increment of the Device-Revision mandates an increment of the Module-Version; but an increment of Module-Version does not necessarily mean a change to the Device-Revision. Refer to the Regenerating the Project files section on page 33 for those procedures necessary to regenerate the project files after a change to the firmware version information. The device parent class. This field is pre-populated by the application. An example of an SDKClass is: com.amx.duet.devicesdk.Switcher. This field cannot be empty and must be a valid Java Type name. The parent class of the device interface. This field is pre-populated by the application. An example of an SDKInterface is: com.amx.duet.devicesdk.ISwitcher. This field cannot be empty and must be a valid Java Type name. This is a fully qualified name of the device class. The class name is chosen within the Wizard. This field information is generated by the application. An example of this device class is: com.amx.switcher.v1_0_0.AMXSwitcher. This field cannot be empty and must be a valid Java Type name.

Device-Category:

Device-Revision:

Device-SDKClass:

Device-SDKInterface:

Device-Class:

Device-Interface: The interface name for the device class. Refer to the Procedures for using the Extract Interface dialog section on page 27 for the procedures necessary to populate this field. This field is optional but if used must be a valid Java Type name. The number of available device channels. The device channel range is between 255 and 65535 (default is 255). The number of available device levels. Most devices use 8 levels or less, with the exception of the following devices which use the nearest "8" boundary as their default: - Video Projector and Monitor use levels 1-14 (default 16) - Camera uses level 1-30 (default 32) - HVAC users level 1-38 (default 40) - PoolSpa uses levels 1-42 (default 48) - Weather users levels 1-48 (default 48) Specifies the type of UI required for a given module. This is an advanced file type used by the Visual Architect application. An example of a template file name is: [device#SecurityNapcoGemini]Security This is an abbreviation for Device Global Unique Identification. This optional information is provided by some manufacturers. Displays the current version of Duet Firmware loaded on your target Master. This value is preset as v3.00.316, but if you use later firmwarespecific functionality (associated to later versions) this field must be updated to conform to that later version of your target Masters Duet firmware. This information can be found within the NetLinx Device API Reference or Utility API Reference documentation (within the Class Type and Since tag sections). Not updating this field information can cause both the runtime to both the target Master and the firmware-specific functionality not to work properly. It is a comma separated list of JAR file path names (inside the module) that should be searched for items such as classes and resources. The (.) specifies the module itself. An example is: /jar/http.jar. The contact address for the vendor (if necessary). An example is: 3000 Research Drive Richardson, TX 75082 or www.amx.com. This is a short description of this module. An example is: Duet Module for AMX Switcher. This is a URL used to document this module. 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 modules JAR file.

Module-Vendor: Device-Specific/UserDefined Manifest Items:

Import Packages:

Export Packages:

File Dependencies:

Import Services: This section specifies the services the module may use. Add a service by pressing the Add button or remove services by placing a checkmark next to the entry and using the Remove button. Pressing the Add button displays the Selection needed dialog. This dialog allows you to select the services you want to import. Click OK to save your selections and return to the Duet Manifest Editor. An example is: org.osgi.service.log. The leader (shown to the left of the entry) is intended for use by the server side management tools. This section specifies the services the module may register. Add a service by pressing the Add button or remove services by placing a checkmark next to the entry and using the Remove button. Pressing the Add button displays the Selection needed dialog. This dialog allows you to select the services you want to export. Press the OK button to save your selections and return to the Duet Manifest Editor. An example is: org.osgi.service.http. The leader (shown to the left of the entry) is intended for use by the server side management tools. This dialog provides all the services available for either import or export. Press the Select All to choose all displayed services. Press the Deselect All to remove the checkmark for alongside all available services. Press the More button to begin searching for more available services and display the Choose Services dialog (refer below for more information). Press the OK button to save your selections and return to the Duet Manifest Editor. This dialog provides all the packages available for either import or export. Press the Select All to choose all displayed services. Press the Deselect All to remove the checkmark for alongside all available packages. Press the OK button to save your selections and return to the Duet Manifest Editor. This dialog provides a listing of all available services. The Open Type field allows you enter a letter and then have the service listing locate only those entries that match. If you enter an N, the list changes to show all entries beginning with the letter N. Enter the letters na and the list only shows those entries that begin with na. The green C icons within the service listing represent Classes. The purple I icons within the service listing represent Interfaces. To add the new service, select the entry and press the OK button to return to the Export Services section of the Manifest Editor where your new selection is now shown. Multiple selections are permitted.

Export Services:

Service Selection dialog:
Package Selection dialog:

Choose Services dialog:

Component Editor

This editor defines the pre-populated Component Interfaces and their Port Assignments. The interfaces are based on the parent device. Some example Switcher Component Interfaces are: ISwitcherComponent, IVolumeComponent, and IGainComponent. This editor allows you to specify the number of ports per component; starting at 1. Open this editor (FIG. 17) by double-clicking on the components.xml file in the META-INF folder in the Package Explorer view (FIG. 15) or by right-clicking on the file and selecting Open with > Component Editor.

Editable

Non-editable

FIG. 17 Component Editor

The Port assignment/Index listings are ordered and cant be modified. A zero (0) means there is no port assignment.
Component Interfaces: This section of the editor provides a listing of all pre-populated interfaces (based on the parent device). The purple I icons represent Interfaces. Select an Interface from within this section of the editor to begin configuring/ altering the Port Assignments. Interface Details: This section of the editor defines the port assignments for the Interfaces selected from within the Component Interfaces listing. Port assignments are ordered and cant be modified. An entry of zero (0) means there is no port assignment.
Procedures for using the Extract Interface dialog
1. Before starting, save any changes to your Editor prior to continuing. 2. Right-click a Java file from the Package Explorer view (FIG. 15) and select
Duet > Extract Interface to open the Extract Interface dialog (FIG. 18) or click the Interface toolbar button ( ). If there are any unsaved changes in an active editor, the Save all modified resources dialog (FIG. 18) prompts you to save any changes made to the module prior to continuing. Press OK to save your changes and continue extracting the interface. Select the Always save all modified resources automatically prior to refactoring option to automatically save all changes and suppress this dialog the next time you choose the Extract Interface option.
Save all modified resources dialog
Extract Interfaces dialog
FIG. 18 Save all modified resources and Extract Interface dialogs
Using the Extract Interface dialog 1. Configure the parameters and members to declare in the interface:
Interface name: Name of the device interface. Change references to the class.: Select this option to alter all instances of the word AMXSwitcher within the code to IAMXSwitcher. Declare interface method as public: Select this field to make the interface methods become public. Declare interface method as abstract: Select this field to make the interface methods become abstract. Members to declare in the interface: Select the methods (in the original class) which you want to have declared within the interface. Use the Select All/ Deselect All buttons to select/deselect all entries in this dialog. Preview: Allows you to preview your selections within the code, as presented within the Extract Interface preview window (FIG. 19).

Interface files should NOT be encrypted (since Interface files do not contain implementation).
5. Choose an export destination for the compressed JAR file by pressing the Browse
button from within the Select the export destination - JAR file field. Either type in a valid external file system path and name for the JAR file (either new or existing) or use the Browse button to select a file location using the Browse Navigator dialog. This field is pre-populated with the location of the default directory: C:/Program Files/Common Files/AMXShare/Duet/Module/XXX.jar. The name of the JAR file must match the name used in the Module-Name Manifest entry. The project name determines the name of the default generated Comm stub file which MUST MATCH the JAR file that is generated along with the Comm file listed in the Define_Module call for NetLinx users.
This default location can be modified from within the Module Export Directory field located within the Duet Preferences dialog (refer to the Setting up the Caf Duet Preferences section on page 9 for more details).
6. Choose whether to compress the JAR file (and contents contained therein) by placing
a checkmark next to the Compress the contents of the JAR file radio box. This selection remains active until it is later deselected.
7. Choose whether to overwrite any previous instance of a similarly named JAR file
(within the same export directory) without being prompted for approval by placing a checkmark next to the Overwrite existing files without warning radio box. This selection remains active until it is later deselected.
8. Press the Finish button to complete the packing of the modules JAR file to the
destination folder. The next step is to open NetLinx Studio and import the saved JAR file.

Quick Packing the Module

Quick Packing is a command procedure that mimics the Pack Module action.
You must first Pack the Module before being able to use this feature. Packing properties are not saved when Duet is simply closed, but rather only packing the Module saves these packing properties. Refer to the previous Packing a Module section on page 29 for more information.
If you do not use the Pack the Module action first, you will get an error message that states: "You have to pack the module first to cache the session property into memory".
Regenerating the Project files
Making an alteration to the Duet Manifest Editors Device-Revision field information can affect several aspects of your current project. An example of this need can be seen if you have to change your switchers firmware from 1.0.1 to 1.0.2 because of a new firmware release. Rather than taking the time to navigate every affected field and parameter, regenerating the project automates this update process, and makes these changes effective within a few seconds. This is not limited only to the Device-Revision field but is also a way of "synching-up" the information found within the Manifest Editor fields and the data located within the NetLinx Stub file. The following steps outline a sample regeneration based on a change to a devices firmware revision:

1. Open this editor by double-clicking on the manifest.duetmf file from the META-INF
folder in the Package Explorer view or right-clicking on the file and selecting Open with > Duet Manifest Editor.
2. Update the firmware version information (given in a X.X.X format) within the
Device-Revision field of the Module Manifest Items section.
3. Regenerate the project by either clicking the Regenerate icon (
) from below the Main menu or right-click anywhere within the Package Explorer view and from the on-screen context-sensitive menu select Duet > Regenerate. The affected items are: Package name NetLinx Stub filename Content within the NetLinx Stub file
Duet Manifest Editor field items affected/updated: - Module-Name - Module-Version - Device-Activator - Device-Class - Device-Interface (if available) - Export-Package
4. Confirm that all of the above components have been properly updated.
Using NetLinx Studio to Transfer JAR Files
1. Launch NetLinx Studio version 2.4 (or higher). 2. Press the Workspace tab to open the Workspace window (located on the right-side of

the application).

3. Right-click on the Module folder (located within the Workspace window) and select
Add Existing Module File.
4. From within the Add Existing Module File dialog:
Either type in a valid external file system path and name for the JAR file (either new or existing) or use the Browse button to select a file location using the Browse Navigator dialog. This location of the default export module directory is: C:/Program Files/Common Files/AMXShare/Duet/Module/. The default module folder should contain a JAR file for use during this import process.
5. Use the Files of Type drop-down listing and choose Duet Module Files (*.jar) to
display all available JAR files found within this directory. The default selection of this field is Source Files (*.axs). This must be changed to *.jar files.
6. Press the Open button once youve made your JAR file selection. A File Properties
dialog then appears to confirm the JAR file information prior to addition.

Caf Duet is a purchased application and requires a valid license. If you do not have a valid key, you will not be able to view any updates within the WebUpdate listing of downloadable files or be allowed to install the application updates.
Follow these procedures to download and install any updates from within the Caf Duet application:
1. If you have not already done so, create an AMX.COM user account and login to
confirm a successful activation. Refer to the AMX WebUpdate Help file for specific sign-up, login, and download procedures.
2. Select Help > AMX Web Update to launch the AMX Web Update application. 3. If your WebUpdate program requires an update, the installer will automatically
launch and the new setup executable will begin the process of updating this application. Refer to the WebUpdate on-line help for details and instructions.
Updating of the WebUpdate program is not optional. If a new WebUpdate version exists, it is required, and must be done prior to any Duet updates. It is the first update downloaded and also the first update installed.
WebUpdate uses the serial number, license number, and hard drive ID on the PC and compares it to the registered information found on the WebUpdate Server. If there is a match, you will be presented with the updates to Caf Duet and allowed to download the file. If there is not a match between the sources, you will not be presented with the Caf Duet updates and therefore will be unable to install the files.
If you have a valid license, but at some future point replace your hard drive, you must contact AMX to update your information before being able to further use WebUpdate. The hard drive ID is part of the information used to confirm the validity of the Caf Duet license and update rights.
4. Once youve confirmed that you WebUpdate application is up to date, select Help >
AMX Web Update to launch the AMX WebUpdate application.
5. If there are new updates available for Duet, you will be notified of such within the

AMX WebUpdate popup.

6. Click OK from within this popup to begin the installation process. If there are no new
updates available, this popup will display the following message: No updates are required at this time. If WebUpdate has not already done so, you may be asked to close Caf Duet in order to make any necessary updates to the application.
7. After the completion of the update process, launch the Caf Duet application and
confirm your updates have been properly installed by navigating to the Help > About Caf Duet dialog where you can confirm any version updates.

Creating a Sample Module

This section describes the creation of a sample module, from initial wizard development to the final NetLinx compile process. For more detailed information, refer to the Building JAVA Device Modules Using Caf Duet course provided by AMX University. This three-day course for programmers uses the AMX Caf Duet software to develop communication modules for third party devices. J2ME and OSGI are discussed in detail along with AMX JAVA Classes, methods, and components.
Obtaining Pre-configured AMX Duet Modules
AMX provides pre-configured Duet modules through the InConcert section of the amx.com website. These modules allow you to begin using the files in NetLinx Studio.
1. Log into the www.amx.com website. 2. Navigate to the InConcert Resource Center section of the website by clicking on the
InConcert button from the AMX navigation menu.
3. Read the License Agreement, and click the I Accept button. If you select I Do Not
Accept, you are directed to a page indicating the proprietary nature of the information.
4. Enter the name of the manufacturer in the Manufacturer field. 5. Click the Search button. Look for the Duet Module Icon (FIG. 22) to appear within
the AMX Systems column. This indicates there is a pre-configured Duet Module for this device.

FIG. 22 Module Legends

6. In the Control Method column, select the corresponding control method for your
target device. This action launches the Device Model Details dialog.
7. Click on the Downloads link (from the left frame) to populate the right frame with all
of the available download files for that devices control method.
8. Click on the ZIP file to download the necessary files to your computer. 9. Open the ZIP file and locate the JAR file (for a Cafe Duet project). 10. Download/extract the contents into either of these locations:
In the working directory (within Studio). Linked to the Workspace under the available Module folder (within Studio).
Caf Duet v1.6 - Users Guide 39
In the central Caf Duet module directory, as defined in Settings > Preferences (Application Preferences section on page 9).
11. Import the JAR file into NetLinx Studio by using the procedures outlined within the
Using NetLinx Studio to Transfer JAR Files section on page 34.
12. Continue with the procedures outlined within the Using SNAPI and Duet Modules in NetLinx Studio section on page 47.
Creating a New Duet Module
Step 1 - Run the Module Wizard 1. Double-click the Cafe Duet icon to launch the application. By default, the icon

appears on your desktop.

2. From the Main menu, select File > New > Project to open a series of wizard-based configuration windows. 3. From within the New Project - Select dialog, choose Duet Module (from the left
window pane) and Duet Module Project (from the right window pane).

Step 2 - Adding Necessary Plumbing
The following procedures setup and prepare the module for use:
1. If you expect 2-way communication with your device add Implements
IDataListener to the public class.

Find the line:

public class AmxSwitcher extends Switcher {

and change it to:

public class AmxSwitcher extends Switcher implements IDataListener {

Created Package

FIG. 24 Package Explorer view showing created packages
Caf Duet flags this change and responds by stating it needs more information.
2. Click on the warning icon to begin the resolution process. Doing so causes a list of

options to appear.

3. Double click on import 'com.amx.duet.core.master.netlinx.IDataListener'.
This adds another import statement to make the code available. There is still an unresolved issue. IDataListener needs certain methods to be implemented. Click on the warning icon again and choose to add the implemented method. The handleDataEvent( )method is then added as a result.
4. Next, obtain the NetLinx D:P:S address for the device you are trying to control. This
information is available in at least two ways: In the constructor for AmxSwitcher, it is passed as the parameter nd. At this point, just store the value in a field declared as a NetLinxDevice. At any point, the value can be obtained with the method call getNetLinxDevice( ).
5. Since the main purpose of the module is to talk to one device, it is recommended that
you create a global variable to store this information in.
6. Just under the declaration of the class, you can create your global variable (in this
example: dvActual) like this:
public class AmxSwitcher extends Switcher implements IDataListener { NetLinxDevice dvActual;

then in the constructor:

public AmxSwitcher(BundleContext bctxt, NetLinxDevice nd, Properties props) { dvActual = nd;
Now dvActual has the handle for the specific interface your device is connected to. The code is generated in the following order (step 7 then step 8).
7. You need to make the Duet module inform the NetLinx Master that it would like to
receive incoming strings (from the controlled device). In the method doAddNetLinxDeviceListeners( ), add the following line:
protected void doAddNetLinxDeviceListeners() { dvActual.addDataListener(this); }
8. Finally, to also ensure that your device will function alongside the NetLinx
Interpreter, also add the following text: If you want the NetLinxDevice initialized, in the method doNetLinxDeviceInitialization( ), add the following line:
protected boolean doNetLinxDeviceInitialization() { return true; } //to receive INFO log messages this.setDebugState(INFO);
Step 3 - Adding the Device Specific Code

Step 3 - Sending the file to the NetLinx Master 1. From the Main menu, navigate to Build > Active System. This begins the process of
compiling the NetLinx project. Verify the application has successfully compiled the project.
2. Once the NetLinx program has successfully compiled (0 errors 0 warnings), from the
main menu, navigate to Tools > File Transfer to open the File Transfer dialog. If there are leftover files from a previous transfer, click the Remove All button.
3. Press Add to add files for transfer to the target Master. This process opens up a Select
Files for File Transfer dialog.
4. From within the Current Workspace tab navigate down the Projects hierarchy until
you find the tkn file specific to your NetLinx Studio project.
5. Place a checkmark next to the tkn file specific to this active project. This should
place a checkmark alongside all options corresponding to this project.
6. Press OK to accept your selection and return to the main File Transfer dialog. 7. Press Send to begin the upload process to the target Master. You should see several
files pending, including a few.jar files.

Appendix - Metadata

Device metadata should be associated with a Duet module in order to determine the context and usage cases for the module. The metadata can be used in conjunction with AMX's device database in order to help build control system programs automatically. Below is a table which provides a listing of the available device metadata types and their specific properties. Device Metadata
Devices: Amplifier: Audio Conferencer: Property Name: Support-Discrete-Power Num-Speed-Dial-Indexes Num-Dialers Support-Discrete-Power Audio Mixer: Num-Inputs Num-Outputs Audio Processor: Num-Inputs Num-Outputs Support-Discrete-Power Audio Tape: Num-Tape-Desks Record-Capable Support-Discrete-Power Audio Tuner Device: Supported-Bands Support-Discrete-Power Camera: Digital Media Decoder: Digital Media Encoder: Digital Media Server: Support-Discrete-Power Support-Discrete-Power Support-Discrete-Power Support-Discrete-Power Property Type: Default Value: Boolean Integer Integer Boolean Integer Integer Integer Integer Boolean Integer Boolean Boolean String Boolean Boolean Boolean Boolean Boolean String Boolean String Boolean false false blank blank blank blank false 1 true false FM, AM false false false false false TV false TV false

PH: FAX: E: WEB: ADD: POST:
MULLUMBIMBYHIRE&SALES PARTYPRICES0266844850 enquire@mullumhire.com.au www.event-hire.com.au 73STATIONST,MULLUMBIMBY.NSW.2482 POX723,MULLUMBIMBY.NSW.2482 COCKTAILFURNITURE CoffeeTable1.2Mx.45M Ottomansinglewhite BenchSeatwhite&stainlesssteel DryBar BarStools DayBeds TABLES TRESTLE 1.8mx.76mseats8(6') 2.4mx.76mseats10(8') 2.4mx1.2mbanquetsets12 Trestleextensionlegspair ROUND 1.8mdiaseats10(6') 1.5mdiaseats8(5') 1.2mdiaseats6(4') 0.9mdiaseats4(3') TABLELINENwhiteonly 1.8MTrestle 2.4MTrestle l 1.5MRound 1.8MRound Othersizesavailableonrequest Napkinswhitelinen TeaTowel CHAIRS FoldingChairwhite BistroChairPremiumwhiteplastic BistroChairwhiteplastic BistroChairgreenplastic MISCELLANEOUS BaliFlags WeddingArch BalloonPump GarbageBinswithliner Lecturntimber Gas9kg Gas4.5kg BALLOONSHelium "C"size4550balloons "D"size95100balloons "G"size290300balloons LatexBalloons(incribbon) BalloonsHeliumfilled
MARQUEESSTRUCTUREWHITE10M W/SILK 10mx9m 900 1,305 10mx12m 1,080 1,560 10mx15m 1,350 1,950 10mx18m 1,620 2,340 10mx21m 1,890 2,730 10mx24m 2,160 3,120 MARQUEESSTRUCTUREWHITE6M 6mx6m 6mx9m 6mx12m 6mx15m 765 1,080 6mx18m 915 1,293 MARQUEESFRAMEDWHITE6M 6mx6m 6mx9m 6mx12m 6mx15m HITOPPAGODAMARQUEE 6mx6mwalls+$4mx4mwalls+$Umbrellasgreen2.7M b ll 35 MARQUEEWALLS&LIGHTING Whitewall3m 25 Clearwall3m 30 MARQUEEPEG&POLEWHITE 8mx20m 800 8mx14m 600 8mx8m 400 MARQUEEPEG&POLEBLUE/WHITE 7mx9m 350 QUICKSHADELT.BLUE 6mx3m(+$50withwalls) 3mx3m(+$25withwalls) MARQUEELIGHTING Ricepaperlanterns FairyLights Dimmer FLOORING,CARPETS&STAGES Marqueeflooringpersqm RedCarpetrunner3.6m RedCarpetrunner7.2m Stage2.4mx1.2mx300mmH Stage2.4mx1.2mx600mmH Stage2.4mx1.8mx600/900mmH
$40.00 $30.00 $60.00 $20.00 $15.00 $120.00
$14.00 $16.00 $18.00 $15.00 $18.00 $16.00 $14.00 $12.00 $9.00 $9.00 $13.00 $13.00 $1.10 $1.10

$7.50 $3.00 $2.50 $2.50

20 POA 10
$20.00 $40.00 $15.00 $15.00 $40.00 $40.00 $25.00

70 125

$70.00 $115.00 $280.00 $0.40 $2.50
GLASSWARE Cocktail/Martini155ml ChampagneFlutePrincessa130ml WineGlassPrincessa230ml Hiball180ml ScotchGlass MiddiePilsner235ml MiddieStandard ShotGlass Smallwaterglass Carafe1.25L JugBeer/Water CHINAWAREAustralianFine DinnerPlateLarge310mm DinnerPlateMedium260mm SidePlate150mm Soup/PastaPlate Soup/PastaBowl SweetBowl AsianSoupBowl AsianNoodleBowl Butterdish SmallSauceDish Cup&Saucer CoffeeMug MilkJugsmall100ml SugarBowl Salt/PepperDishdivided Salt/PepperShakerset PlattersLarge PlattersSmall l ll CUTLERY&SERVINGUTENSILS KnifeMelroseMain/Entre ForkMelroseMain/Entree DessertSpoonMelrose SoupSpoonMelrose CakeForkMelrose TeaspoonMelrose CutleryCafKFS WeddingcakeKnife ServingTrowel ServingSpoon&Forkset ServingTongs ServingSpoonLarge/Ladle Ladle IceTongs TABLE&BARWARE MilkJugstainlesssteel TeaPotstainlesssteel IceBucketstainlesssteel WineCooler CocktailShaker PunchBowl&LadleGlass SaladBowlblack/clear/stainless SaladBowllargestainless Traystimberserving Trays/Plattersstainlesslarge Trays/Plattersstainlesssmall TraysDrinknonslip WineCooler
$0.80 $0.60 $0.60 $0.55 $0.55 $0.60 $0.55 $0.50 $0.50 $2.20 $3.50 $0.90 $0.60 $0.55 $0.55 $0.75 $0.55 $0.55 $0.55 $0.50 $0.50 $0.60 $0.60 $0.80 $0.80 $0.50 $1.80 $9.00 $7.00 $0.35 $0.35 $0.35 $0.35 $0.35 $0.35 $0.35 $3.50 $2.20 $2.20 $2.20 $1.50 $1.20 $1.50 $1.50 $4.00 $6.00 $4.00 $4.00 $9.00 $3.00 $4.00 $3.00 $4.00 $3.00 $6.00 $3.00
COOKING/PREPEARING/SERVING BBQ4Burner(inc.gas) BBQ2Burner(inc.gas) GasBurner1ring GasBurner2ring GasBurner3ring RodSpitGas/Elect(inc.gas) BasketSpitGas/Elect(inc.gas) DeepFryer2Basket UrnElectric10L UrnElectric20L UrnGas20L ChaferTrayincludesfuel Pie/FoodWarmer BainMarieglassfront6tray BainMarieglassfront8tray BainMarieTraysGastronorms StainlessSteelboilerstainless18L WaterCooler CoffeePlunger CoffeePerculator100cup CoffeeMakerpouroverdrip COOLING MobileCoolroomwalkin Fridge/Freezer250L Fridge/Freezer390L Fridge220L FridgeBar Freezer150L IceBox150L IceTub Fan HEATING Terrace/PatioHeater(nogas) ColumnHeater(nogas) Brazier(wood) GasFiredelectricFanHeater(noga LIGHTINGANDSOUND PASystem4CHMixer600W PASystemportable80W PartyLightsfestoonx8M Partylightsfestoonx20M FairyLights50M FloodLight1500Wonstand FloodLights2x500Wonstand FloodLightssingle200W StrobeLight BlackLight MirrorBall&2pinspots TrafficLights&Chaser LighteffectOrbiter LightEffectExercet LightEffectDuet SmokeMachine Powerboards ExtensionLeads