Table of Contents

Introduction.. 1
Whats New in this Release.. 1
Caf Duet version 1.6 features... 1 Duet SDK features supported in this release.. 2
Caf Duet Minimum System Requirements.. 2
Supported operating systems... 2 PC requirements... 2
NetLinx Master Requirements.. 3 Installing NetLinx Studio... 3 Installing Caf Duet... 3

Launching Caf Duet... 8

Overview of the Duet Plug-in.. 9
Application Preferences... 9
Setting up the Caf Duet Preferences.. 9 Setting up the Manifest Editor Preferences.. 10
Creating a Duet Module Project.. 11
Defining the Module... 14 Generating a new device class.. 16 Overriding or Implementing Methods.. 17

Duet Perspective.. 18

Creating your own perspective.. 20
Duet Manifest Editor.. 21 Component Editor... 26 Procedures for using the Extract Interface dialog.. 27
Using the Extract Interface dialog.. 28
Caf Duet v1.6 - Users Guide
Creating NetLinx-compliant Java Files.. 29
Compiling the Module Stub..29 Packing a Module...29 Quick Packing the Module...33
Regenerating the Project files.. 33 Using NetLinx Studio to Transfer JAR Files. 34 Downloading the Project Files to a Target Master. 35 Using AMX WebUpdate to update the Plug-in.. 35
Creating a Sample Module... 39
Obtaining Pre-configured AMX Duet Modules.. 39 Creating a New Duet Module.. 40
Step 1 - Run the Module Wizard..40 Step 2 - Adding Necessary Plumbing..42 Step 3 - Adding the Device Specific Code..44 Step 4 - Compile and Pack Process...46 Step 5 - Regenerating Project files (if a change is made).46
Using SNAPI and Duet Modules in NetLinx Studio.. 47
Step 1 - Using SNAPI and NetLinx Studio..47 Step 2 - The Compile Process - NetLinx Studio preparation.47 Step 3 - Sending the file to the NetLinx Master..48
Appendix - Metadata... 49

Introduction

With Caf DuetTM, AMX opens the door to a broad knowledge base and vast programming resources by integrating JavaTM and NetLinx technologies. This NetLinx Duet architecture extends the power of your existing NetLinx systems long into the future and expands the capabilities of your future projects. As a plug-in to the main Eclipse application, Caf Duet provides a unique dual-interpreter environment that supports either NetLinx or Java programming, or both. The Standard NetLinx API (SNAPI) router keeps NetLinx and Java in perfect sync. Caf Duet module development is fast and efficient within the Caf Duet Integrated Development Environment (IDE), using the Duet Software Development Kit (SDK). The Duet SDK includes a module Wizard with several device-specific Application Program Interfaces (APIs) to streamline module creation. Additionally, you can leverage the CDC/Foundation Class Library of over 750 high-level native Java language classes to simplify the programming of todays most complex applications and interface modules. Prerequisite to the installation of Caf Duet is the presence of NetLinx Studio v2.4 (or higher) on your PC. If you have not already installed NetLinx Studio, you will be prompted to do so before installing Caf Duet. This is to ensure that you are using the latest NetLinx Compiler to build and extract the module files.

Whats New in this Release
Caf Duet version 1.6 features
Functionality has been added which now supports AMXs new Visual Architect software application. During the Modules packing process, a new dialog is displayed to let the users choose what methods the current module will support. This collected metadata is then used by other AMX applications, such as Visual Architect, to automatically build control system programs. A new Manifest Entry "UI-Template" has been added to the Manifest Editor to specify 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.
Duet SDK features supported in this release
This release of Caf Duet supports the following Device Module Application Programming Interfaces (items marked with an asterisk (*) are new devices within the 1.6 release):
Device Module Application Programming Interfaces
Amplifier (*) Audio Conferencer Audio Mixer Audio Processor Audio Tape AudioTuner Device Camera Digital Media Decoder (*) Digital Media Encoder (*) Digital Media Server (*) Digital Satellite System Digital Video Recorder Disc Device Document Camera HVAC Keypad Light Monitor Motor MultiWindow PoolSpa PreAmp Surround Sound Processor Receiver Security System Sensor Device Settop Box Slide Projector Switcher Text Keypad TV Utility VCR Video Conferencer Video Processor Video Projector Video Wall (*) Volume Controller Weather
Caf Duet Minimum System Requirements
Supported operating systems
Windows XP Professional (service pack 1 or greater) Windows 2000 Professional (service pack 4 or greater)

PC requirements

Pentium II 450 MHz processor (minimum); 700 MHz or faster recommended 150 MB of free disk space (minimum); 200 MB recommended 128 MB (RAM) installed for Windows 2000 or 256 MB for Windows XP VGA display with a minimum screen resolution of 800 x 600 Windows-compatible CD-ROM drive Windows-compatible mouse (or other pointing device)
NetLinx Master Requirements
NXC-ME260/64 or NI-Series Integrated Controllers Running Master firmware version 3.XX build 317 (or higher)
Installing NetLinx Studio
NetLinx Studio is used to setup a System number, obtain/assign the IP/URL for the connected NetLinx Master, transfer firmware KIT files to the Master, and use JAR files created by Caf Duet. If you are installing NetLinx Studio on a Windows XP or 2000 machine, you must have Administrator rights to install and run all required System files. In NetLinx Studio, select Help > About to check the version number of the NetLinx Studio application currently installed. In order to install Caf Duet, Studio must be version 2.4 (or higher). If you have not already installed the latest version of NetLinx Studio on your PC:

1. Download the latest version of NetLinx Studio from www.amx.com > Tech Center
> Downloadable Files > Application Files > NetLinx Studio 2.4.
2. Save the file to a known location on your PC. 3. Once the entire setup file has been downloaded to your machine, locate and doubleclick on the file called NS2Setup.exe to begin the installation process. Do not launch (open) the file from the web.
4. Select both the default locations and installation settings. 5. Click OK once the install process has completed. You will be prompted to restart

your machine.

Installing Caf Duet
This section describes installing Caf Duet. You must have an active Internet connection to complete the installation.
1. Verify that NetLinx Studio v2.4 (or higher) is already installed on the target PC. 2. Insert the Cafe Duet CD into your PCs CD tray. The installation executable
(Setup_CafeDuet.exe) launches automatically and begins the installation wizard. If there is a problem launching the wizard, this file can be found on the root of the CDs directory.
3. If the latest version of NetLinx Studio is not detected the user is presented with the
following dialog (FIG. 1). If this case, the only option is to click the Exit Setup button to exit the installation process, install the latest version of NetLinx Studio, and then restart the installation of Caf Duet.
Caf Duet v1.6 - Users Guide 3
FIG. 1 Caf Duet Setup Termination screen
The first screen displayed during a normal install is the Welcome screen, containing various warnings and notices for the user.
4. Click the Next button to continue to the License Agreement screen. 5. Read the License Agreement, and select I Agree to accept the terms and conditions
(and enable the Next button). Only after selecting I Agree will the Next button become enabled.
6. Click Next to continue the installation process. 7. From the Select Cafe Duet Installation Location screen, click Next to accept the
default Caf Duet folder location (C:\Program Files\AMX Control Disc\Cafe Duet).

Click the Browse button to select a different directory for the installation. If the hard drive selected has less than 125MB of free space, you will be prompted to select another installation directory or abort the current installation.
8. If a previous version of Caf Duet is detected on the target machine, the user is given
a visual notification (FIG. 2) and given the option to either uninstall the previous and then continue with the current installation process or exit the setup process.
9. Click Next to continue with the installation of the new version.
If the hard drive location selected on the previous screen has less than 150MB of free space, the user will receive Insufficient Disk screen. The only option from this screen is to return to the previous screen and select another installation directory or abort the installation process.
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).

Click Next to save your changes and continue to the New Duet Module Project - Override/ Implement Methods dialog.
FIG. 13 New Duet Module Project - Duet Module Devices dialog
Overriding or Implementing Methods
Within the Override/Implement Methods dialog (FIG. 14), you can choose whether to either override or implement specific default device functions. Click to place a checkmark adjacent to a function to override its default state. Only override a method if you do not want the default base-class behavior. If a base-class method is empty (i.e. has no implementation), do not call it from your source code, since it might have an implementation in the future that is inconsistent with your code.
FIG. 14 New Duet Module Project - Override/Implement Methods dialog
From within the Module group, the handleAdvancedEvent() and passthru() entries are recommended selections for all devices, as is the selection of the dispose() entry ONLY for IP devices (used for thread cleanup and such). Another recommendation is to select nothing within the Object group.
Method listing Provides a field with methods organized either by type/class or alphabetically. This display is dependent on whether the Group methods by types radio box is selected. This option determines how the methods are displayed for use. Select this option to organize and display the methods by type. De-select this option to display the methods alphabetically.

Group methods by type

Select All: places a checkmark adjacent to each listing entry. Deselect All: removes any checkmarks adjacent to each listing entry. Click the Finish button to save your wizard configurations, set your build paths, and create your project. Click Yes to confirm the use of the Duet Perspective (project default). You can also select not to receive this message in the future.

Duet Perspective

Once the wizard has created a new project, the Duet Perspective is displayed (FIG. 15). This display is the default layout view for the application. The main elements of this perspective are described below: Package Explorer: this window shows the Java element hierarchy of the Duet projects in your Workspace. The element hierarchy is derived from the projects build paths. For each project, its source folders and referenced libraries are shown within the on-screen tree. Editors: this window provides a display area for the various available editors such as: The Duet Manifest Editor is opened by double-clicking on the manifest.duetmf file from META-INF folder in the Package Explorer view or right-clicking on the file and selecting Open with > Duet Manifest Editor. The manifest.duetmf file is similar to an ini file in the sense that it is used by the Master to find a file and load it. This editor outlines both the Module and User-Defined Manifest Items, as well as any imported/exported packages or services. See the Duet Manifest Editor section on page 21 for details.

Module-ContactAddress:
Module-Description: Module-DocURL: Module-UpdateLocation:

Module-NativeCode:

Module-Copyright: The copyright information for this module. An example is: Copyright (c) 2005 AMX Corporation. All Rights Reserved. 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). - The second field is the Value. 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 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. An example is: com.amx.switcher.v1_0_0; with the specification version of 1.0.0. This section specifies the files (to be imported) that contain the packages and services the module requires. Add a JAR or ZIP file by pressing the Add button. Remove a JAR or ZIP file by placing a checkmark next to the entry and using the Remove button. Pressing the Add button displays a File Selection dialog that allows you to navigate to the file location. Once the file is selected, press the Open button to import the file. File dependencies added by the Caf Duet Module Wizard should not be removed.
Module-Vendor: Device-Specific/UserDefined Manifest Items:

Import Packages:

Export Packages:

File Dependencies:

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).

If you do not want the above dialog to show up every time you are in your development phase; you can disable it from within the Preference > Duet dialog, by unchecking the "Persist the Device Class Metadata during the process of packing the module" (see FIG. 8). 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.
3. Click Next to open the JAR Export wizard dialog (FIG. 21). This is the next step in
the JAR export process where you can define which resources are packed into an exported JAR file.
4. Select which available module resource files will be encrypted and/or packed for

export.

Make sure to select the package, expand the selection, and check-off all desired files
FIG. 21 Exporting a Module using the JAR Export dialog When packing a module using helper classes: - Expand the project from within the "Select the resources to export:" section shown above. - Select the package. - From the right of the dialog window, make sure the helper class filename has been checked.
Resources to export: provides a listing of selectable module resources. Within each of these resources is a series of files that can either be selected or deselected for packing. Files contained: this is the selectable listing of files contained within each resource. When a resource is highlighted/selected from the left Resources to export section, its contained files are shown within the right section of the dialog. Select a resource by placing a checkmark next to the resource name. Once that resource is selected, the right section of the dialog shows all contained files available for packing. Specify exactly which files you want to export within the JAR by placing or removing a checkmark in the box adjacent to each file. If encryption is available for a particular file, the Encryption column will display an encryption status for these files. If encryption is not available for a file, the Encryption button will be greyed-out.
Caf Duet v1.6 - Users Guide 31
Encryption button: this button enables you to modify the encryption status of a particular file. If the selected file currently has no encryption, the button reads Enable Encryption. If the selected file is currently encrypted, the button reads Disable Encryption. Only JAVA files can be encrypted. Only the Master can decrypt these files. They cant be decrypted by any other PC-based machine or application. Use the Ctrl button to select multiple files at one time.

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.

Only override a method if you do not want the default base-class behavior. If a base-class method is empty (i.e. has no implementation), it is advised not to call it from your source code since it might have an implementation and behavior in the future that is inconsistent with your code.
At the very least, the Switcher will need a switchInputToOutput()method to operate. There are three methods of this name, each with a different signature. It's a good idea to use all of them, to ensure cross-compatibility with other switchers. If you utilize all the methods, you will have a much better chance at being able to change switcher models without changing the main body of the application code.
11. Under the Module portion of the tree (FIG. 23), it's a good idea to choose
handleAdvancedEvent( ). HandleAdvancedEvent is called when the SNAPI router is not able to
interpret the channel, level, or command sent by the application code. Additionally, passthru( )is advisable for a similar reason. passthru( )is called to send a device-specific protocol string directly to the device. Therefore, passthru is formatted in the device-specific protocol to allow device functions that have not been supported by an advanced or basic function.
HandleAdvancedEvent is for functions that are implemented by the module,
but are not supported by SNAPI.
12. Click Finish to save your wizard configurations, set your build paths, and create your

project.

FIG. 23 Override/Implement Methods dialog
13. Click Yes to confirm the use of the Duet Perspective (project default). You can also
select not to receive this message in the future. It is within this perspective that a user can begin creating device specific code.
14. At this point, you should have a Package to explore. In the Package Explorer window
(FIG. 24), expand the package you created (upper-left) to reveal the various.jar files involved. All the device specific code resides in the com.<make>.<model>.<revision> entry. The MakeModel.java (or whatever you chose to rename it - our example uses AmxSwitcher.java) is your source code file. Open it now. For the remaining portion of these procedures, it is assumed this file is named AmxSwitcher.java.

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

Digital Satellite System: Supported-Bands Support-Discrete-Power Digital Video Recorder: Supported-Bands Support-Discrete-Power

Device Metadata (Cont.)

Devices: Disc Device: Property Name: Direct-Disc-Selection Num-Discs Support-Discrete-Power Disc-Device-Type Property Type: Default Value: Boolean Integer Boolean String false 1 false DVD
Selections include: DVD, CD, Laser Disc, Mini Disc, and Other Discs. Document Camera: HVAC: Support-Discrete-Power Num-Thermostats Support-HumidifyDehumidify Keypad: Num-Keypads Num-Button-Per-Keypad Keypad-Addressing-Scheme Boolean Integer Boolean Integer Integer String (Regular Expression) false 1 false 1 blank blank
Example: \\[?(\\d{1,3}[\\.:/]){2,4}+\\d{1,3}\\]?
Support-Input-From-Keypad Support-Output-To-Keypad Light: Num-Lights Light-Addressing-Scheme
Boolean Boolean Integer String (Regular Expression)

false false 1 blank

Num-Keypads Num-Button-Per-Keypad Support-Input-From-Keypad Support-Output-To-Keypad Monitor: Support-PIP Has-PIP-Tuner Support-Multiple-Screens Support-Discrete-Power Motor: Open-Text Close-Text Multi-Window: Pool Spa: N/A Support-Dual-Equipment Num-Pool-Auxilary-Relays
Integer Integer Boolean Boolean Boolean Boolean Boolean Boolean String String
0 blank false false false false false false Open Closed

Boolean Integer

false 0
Devices: Pre Amp Surround Sound Processor: Receiver: Property Name: Support-Discrete-Power Supported-Bands Support-Discrete-Power Security System: Num-Partitions Support-Points-Detail Sensor Device: Settop Box: N/A Supported-Bands Support-Discrete-Power Slide Projector: Switcher: Support-Discrete-Power Num-Inputs Num-Outputs Support-Breakaway Support-Gain Support-Volume Text Keypad: TV: N/A Supported-Bands Support-PIP Has-PIP-Tuner Support-Multiple-Screens Support-Discrete-Power Utility: VCR: N/A Supported-Bands Support-Discrete-Power Video Conferencer: IP-Dialing-Capable Phoneline-Dialing-Capable Num-Speed-Dial-Indexes Farend-Camera-ControlAvailable Farend-Source-Select-Available Support-Multipoint Support-Discrete-Power String Boolean Boolean Boolean Integer Boolean Boolean Boolean Boolean TV false false false 0 false false false false String Boolean Boolean Boolean Boolean TV false false false false Boolean Boolean String Boolean Boolean Integer Integer TV false false blank blank true false false Property Type: Default Value: Boolean String Boolean Integer Boolean false FM, AM false 1 false