22 Using Sample Applications

Running the DataCollectionDemo

The DataCollectionDemo demonstrates the following functionality:

• Multiple virtual machines (MVM)

• Inter-IMlet communication using local datagrams

• Device I/O API pulse counter

• Device I/O API serial peripheral interface

• Logging API

In the DataCollectionDemo, several data collector IMlets read data from peripheral devices using the Device I/O API and send the data to a data processor.

For more information about the setup and behavior of the DataCollectionDemo, see the readme.txt file, under apps\DataCollectionDemo in the Java ME SDK installation directory.

For more information about the Qualcomm IoE platform, see Oracle Java ME Embedded Getting Started Guide for the Reference Platform (Qualcomm IoE).

Running the GPIODemo

The GPIODemo can run on an emulator. The implementations are different, because the emulator uses the External Events Generator, and the external device supports direct interaction.

To run GPIODemo on the emulator:

1. Run GPIODemo on the EmbeddedDevice1 emulator.

2. Click the GPIO Pins tab. This view approximates the device actions.

3. Open the Tools menu and select External Events Generator. Open the GPIO tab.

4. Click BUTTON 1 in the External Events Generator to toggle the state of the pin named BUTTON 1 in the EmbeddedDevice1 emulator. If the button value in the External Events Generator is changed to High, then the button value in the EmbeddedDevice1 emulator is also changed to High.

Running the I2CDemo

The I2CDemo is designed to work with Oracle Java ME SDK 8. It has no user interaction.

To run I2CDemo on the emulator:

1. Run I2CDemo on the EmbeddedDevice1 emulator.

2. Click the I2C tab.

3. Run I2CDemo.jad located under apps\I2CDemo in the Java ME SDK installation directory.

4. The I2CDemo acquires a slave named I2C_Joystick, writes data to the slave, and retrieves it. The I2CDemo is successful if the Sent Data and Received Data match.

Running the NetworkDemo

You can configure the NetworkDemo as a server or as a client by editing the application descriptor. You start two instances of NetworkDemo; the first one acts as a server and the second one acts as a client. The client instance attempts to connect to the server instance and if the connection is successful they exchange a message.

To run NetworkDemo on the emulator:

1. Create two instance projects of the NetworkDemo sample project.

2. Right-click the first project and select Properties.

3. In the Platform category, select the device EmbeddedDevice1. In the Application Descriptor category, set the value of the following property:

   Oracle-Demo-Network-Mode:Server
   

4. Click OK.

5. Start the first project. It opens on the emulator EmbeddedDevice1 and waits for a connection.

6. Right-click the second project and select Properties.

7. In the Platform category, select the device EmbeddedDevice2. In the Application Descriptor category, set the value of the following property:

    Oracle-Demo-Network-Mode:Client
   

8. Click OK.

9. Start the second project. It opens on the emulator EmbeddedDevice2.

10. The client attempts to connect to the server. If successful, the following is displayed in the output for the first project (the server):

    Waiting for connection on port 5000
    Connection accepted
    Message received - Client messages
    

    The following is displayed in the output of the second project (the client):

    Connected to server localhost on port 5000
    Message received - Server string
    

Running the PDAPDemo

To run PDAPDemo on the emulator:

1. Create test files and directories inside the emulator's file system. The file system is located in the Java ME SDK configuration directory. For example, for EmbeddedDevice1, the file system is located under userdir\javame-sdk\8.0\work\EmbeddedDevice1\appdb\filesystem\root1

2. Open the project in NetBeans IDE 8.0, right-click the project and select Properties.

3. In the Platform category, select the device EmbeddedDevice1 and click OK.

4. In the Device Selector window, right-click an EmbeddedDevice1 emulator, select Run Project and then PDAPDemo.

5. Start the project.

6. On the EmbeddedDevice1 emulator, open the Tools menu and select Manage File System to see a list of mounted file systems.

7. Open a terminal emulator and create a Telnet connection to localhost on port 5001.

   
   

   Note: The Telnet negotiation mode must be set to Passive. The negotiation mode can be set inside a Telnet client application (for example, PuTTY), by selecting Category, then Connection, then Telnet, and then Passive.

   
   

8. A command line opens where you can browse the emulator's file system. You can use the following commands:

   • cd: Change directory

   • ls: List information about the files for the current directory

   • new: Create a file or directory

   • prop: Show properties of a file

   • rm: Remove a file

   • view: View a file's content

Running the LightTrackDemo

The LightTrackerDemo is specifically aimed at demonstrating functionality on an embedded device.

In the LightTrackerDemo, a certain number of LEDs are turned on and turned off on the board, in a sequence that you can control. It makes use of the Device I/O API and the GPIO port to demonstrate its functionality. It requires connection of an ADC channel to an on-board potentiometer.

For more information about the setup and behavior of the Light Tracker demo, see the readme.txt file located under apps\LightTrackDemo in the Java ME SDK installation directory.

Running the SystemControllerDemo

The SystemControllerDemo is specifically aimed at showing off functionality on an embedded device, such as the Qualcomm IoE reference platform.

The purpose of the SystemControllerDemo is to control the life cycle of IMlets on the reference platform. It makes use of the following functionalities:

• Multitasking Virtual Machine (MVM)

• IMlet auto-start

• Application Management System (AMS) API

• Logging API

• General Purpose Input/Output (GPIO)

• Watchdog timer

For more information about the setup and behavior of the System Controller demo, see the readme.txt file located under apps\SystemControllerDemo in the Java ME SDK installation directory.

For more information about the Qualcomm IoE platform, see Oracle Java ME Embedded Getting Started Guide for the Reference Platform (Qualcomm IoE).