Michael Cheung
Austin Joe
Mike van Abbema

Dr. Eric Manning


Control Unit (CU)

This unit runs a real-time OS (MicroC/OS-II) and programs the control and operations of any network application requiring real-time control. Status would be streamed out asynchronously on a hard-wired TCP/IP connection using XML/SOAP to the Awareness Unit. The CU would consist of a 386-microprocessor board.

  • Hardware includes a 386-based microcontroller
  • MicroC/OS-II real-time kernel (or VxWorks)
  • Multiple (minimum 2) independent units

Awareness Unit (AU)

This unit receives streaming telemetry data from a CU. From this data, the AU communicates with other AUs to determine if any critical errors are imminent and require immediate action. If an error is determined to be pending, the AU would send interrupts to adjust the CUís program to avoid conflicts, then command the normal operation of the CU once the conflict is resolved.

  • Hardware used is a basic P3-500 MHz system with wired and wireless network cards
  • Running Windows XP Professional SP1
  • Receives telemetry from CUs
  • Able to monitor status and send control signals to CU
  • C/C++, TCP/IP connectivity
  • Wireless TCP/IP connectivity:
    • Receives updates from other AUs
    • Java Applet / J2EE (servlet) connectivity
  • On conflicts between CUs, sends interrupts to CU

The AU would also send streaming, asynchronous status data to a monitoring station over a wireless TCP/IP connection using XML/SOAP and would be able to accept commands from the monitoring station. The AU would be programmed in C++ or other programming languages and use a basic computer system with wired and wireless network cards. Each AU would be connected to a single CU, forming an AU-CU pair.

Monitoring Station (MS)

The monitoring station would be a web-browser-based J2EE application (using Java servlets or applet connectivity) and receive data over a wireless TCP/IP connection from either a single or multiple AUs. This data would be presented graphically to the user and relevant information would be saved into a historical database. The MS would be able to send commands to AUs to direct operations of CUs.

  • Receives status of CUs via AUs
  • Able to control a CU (status, start, stop, reset commands)
  • Uses web browser/Java applet as interface (currently)
  • J2EE connectivity (servlets, JDBC)
  • Collects data from AU and stores relevant information to database for historical analysis

Updated: July 27, 2004