Goals

• Develop Hardware/Software that can be integrated into data communications products to allow configuration, monitoring and troubleshooting of these products via a IR link to a PDA device.
• The HW/SW for this interface should be developed on a microcontroller development board. The microcontroller system will be used to simulate the typical processing engine found on data communications products that the IR interface will connect to.
• Deliverables for the project: (1) The "Prototype" - A working piece of hardware that houses the IR interface as well as the prototype microcontroller system. Also, all software needed to run the embedded system and IR interface. (2) PDA Software - Software application that runs on PDA device(s), (3) Documentation for all HW/SW that will allow customer(s) to integrate this functionality into embedded data communications products. Customers are meant to be design engineers working on data communications products.

General Requirements

• Standards should be following where possible rather than developing proprietary protocols and schemes.
• If possible, object-oriented software development in C++ should be used.

Detailed Requirements

1. PDA Software Application

1.1. Should be easily portable across multiple PDA platforms. Where possible use standards to make this possible. Top priority would be the PALM PDAs.

1.2. Provide the ability to bring up a command line prompt on the PDA, much like is typically done through a direct serial connection.

1.3. For demonstration purposes, the command prompt should support several commands that control the prototype system (for example, turn on LEDs, dump memory, etc.)

1.4. Provide the ability to "beam" a text file from the PDA to the prototype system. The prototype system should store this file in memory. A command should be made available through the CLI interface to dump this file to the PDA display. If possible, any standard methods of file transfer over the IR link found in current PDAs should be used rather than developing a proprietary scheme. This requirement is meant to provide the capability of transferring a configuration script file to a data communication device over an IR link.

1.5. Also, provide the ability to beam a file from the prototype system into the PDA.

1.6. Ethernet Configuration Application: An application should be developed for the PDA that simulates the configuration of IP address, subnet mask and default gateway for an Ethernet port. This application should present to the user a "GUI" type interface on the PDA and send CLI type commands to the prototype system to simulate configuration of an Ethernet port (just simulated, doesn't have to exist on prototype). Background - typically, the primary management interfaces for most current data communications equipment are telnet and HTTP, both of which require a configured IP connection to gain access to the device. Typically, a customer will first have to connect a laptop to the device with RS-232, bring up a terminal program, then configure the ethernet parameters before plugging the device into his LAN and completing the configuration via telnet or a web-browser interface. It would be much easier for the customer to simply point his PDA at the device and easily configure this basic parameters so that he could complete the remaining configuration via the primary interfaces.

2. Prototype System

2.1. Must provide a IR interface subsystem that can be easily interface to any microcontroller/microprocessor system.

2.2. HW cost for the IR interface should be minimized as much as possible.

2.3. Range - IR interface must operate at an acceptable distance from the PDA. A goal of three-feet should be used, with one-foot being the minimal acceptable distance.

2.4. Beam Angle - Many devices may be rack-mounted and housed 6 feet off the ground or 3 feet off the ground. It is desired that the user be able to point the PDA at the IR interface of the prototype from as large a range of angles as possible.

2.5. Addressing - The system must provide the ability to independently connect a PDA to either of two IR interfaces located in close proximity. This simulates the case of multiple units being very close together.

2.6. Processor System - Any processor system may be used that adequately simulates those typically found in data communications devices. It would be desirable for the system to be capable of eventually running an IP stack, which could be needed for future design team projects.

2.7. Indicators - The prototype should provide some set of indicators (LEDs, seven-segment displays, etc.) that can be used to verify execution of commands from the PDA.

2.8. Inputs - push buttons etc., should also be provided to simulate autonomous events that could be reported to the PDA.

2.9. Security - access of any kind must be authenticated via a login.