Wireless OpenSourceOpenArchitecture Command Control System WOCCS Group Members

Wireless Open-Source/Open-Architecture Command Control System (WOCCS) • Group Members: – – – Eric Hettler Manuel Paris Ryan Miller Christian Moreno James Reepmeyer EDGE™

Problem • Wireless Open-Source/Open-Architecture Command Control System (WOCCS) • Used to control and communicate with remotely controlled vehicles and devices • Communicate data over multiple channels in both directions § Send data to device for control § Receive data from device for feedback and data collection • Fully modular • Common interface EDGE™

Module Breakdown EDGE™

Stakeholders - Harris Corporation • Providing funding and guidance • Not the end user • Work with the government on many projects that require security clearance • Cannot allow senior design teams to work on these projects • Designed this project to get students interested and involved with Harris and RF communication • Create a pool of newly graduated engineers to recruit from EDGE™

Stakeholders – MSD Teams • End user • Many senior design projects in the past required wireless communication • This was a failure point in some cases • Rarely had time to develop the wireless communication and just bought off the shelf systems • This new system will be modular enough to meet the needs of any senior design team that needs to use it EDGE™

Historical Project – P 08027 • • Bio Track, Wireless Assistive Control System (WACS) 6 Engineers, Faculty Adviser: Dr. Edward Brown Goal: Human movement interface to control RC car Used COTS components – Bio. Radio 150 • 12 available data channels • 4 total channels used – Labview • Input filtering • Signal processing • Wireless data output – Custom RF hardware and microprocessor for RC car • Communicated at 434 MHz and 325 MHz bands • Total project costs: ~$411 – RF component costs: ~$100 – No software costs- Labview student version? EDGE™

WACS Results • Successes – Wireless vehicle control with muscle movement input • User simulates vehicle driving motions • Output from Labview is sent wirelessly to RC car • Received data converted to directional signals • Problems – – Syncing error between Labview and Bio. Radio Latency-induced device shutdown (work-around used) Bio. Radio channel crosstalk (work-around used) No feedback method for user • Time-constraint based? Extra data channels existed to convey feedback – User tethered to PC area EDGE™

P 06501: About Zigbee Technology ü 2005 ü 5 Engineers : 2 CE, 3 EE ü Sponsors : Sensorcon, PCB Express ü Advisor : Dr Hu, Dr Reddy Problem : Crossbow Technology provides wireless sensor motes but cost deters the creation of large networks Requirements : Sending commands to the network, receiving messages from the connected mote and display the real time network topology Solution : Create low cost Zig. Bee Data Forwarding Unit (DFU) hardware and software prototype EDGE™

P 06501 : About Zigbee Technology Why : üLow-power üLow-cost üUse of standard (Protocols and Hardware) Results : ü 3 concepts have been studied, only one until the end ü Life-time calculations : more than 4 years ü The final project works Lessons Learned : ü Open-Source, Open-Architecture ü Find different solutions for the same problem ü Low-power implies sleeping devices : how to transmit data to sleeping devices ü Most important : separate each part of the project in sub-projects, hence the need of good modularity (interface device/device) Conclusion : This project relates with our project, the low-power is very useful. The only problem is the range, which is 30 ft outdoor. Is it possible to go further with this technology? EDGE™

Historical Project – P 08201 • • • Vehicle Systems Technology Track, 10 Kg Payload Modular Robot 8 Engineers: 1 IE, 3 EE, 2 ME, 2 CE Faculty Advisor: Dr. Wayne Walter Goal: Construct a land-based robotic platform. In this project, the platform was wirelessly controlled. Used COTS components – Crossbow Telos. B Mote • IEEE 802. 15. 4 compliant, 250 kbps data transfer rate, 30 m range • USB port for programming and/or communication – Crossbow MICAz module • 2. 4 Ghz Transceiver • IEEE 802. 15. 4 compliant, 250 kbps data transfer rate, 30 m range • USB port for programming and/or communication – Freescale CSM 12 D Microcontroller • Six PWM channels, Two for drive motors, Four for steering motors • Twelve digital inputs • Eight encoders – Java and nes. C • Total project costs: ~$2500 – Wireless components rather inexpensive EDGE™

Results • Successes – Wireless vehicle control • Successful wireless control • Each motor module could be controlled individually • Long battery life • Ways to Improve – – Display when robot is out of range Add functionality to obtain feedback from robot Add PID control to maintain speed during manual operation Add PID control to maintain position used under autonomous navigation EDGE™

P 09232 – Airframe B • Airframe B – Needed aircraft controls • Spent in excess of $200 (1/10 project cost) on radio controller alone – No down feed for on board camera or telemetry packages • Success – Radio worked for flight – In this application the off the shelf controller worked – No video down feed was utilized EDGE™

Other UAV Projects • • • P 09233: Airframe Measurements P 09234: Aircraft Controls P 09235: Aircraft Payload Interface P 10236: Versatile Adaptive Controller Project number unknown: Aircraft Control Link EDGE™

Common Problems • • Limitations Feedback Use of unproven and untested systems Distance and Range do not scale very well When using COTS, capability never exactly matches needs EDGE™

To Conclude What we are confused about : ü Our knowledge set does not align with the project Possible direction for the future : ü Determine our scope ü Conduct several interviews EDGE™

Questions? EDGE™