PROJECT STATUS UPDATE

R10003 - WIRELESS OPEN-SOURCE/OPEN-ARCHITECTURE COMMAND AND CONTROL

SYSTEM (WOCCS)

Eric Hettler

Manuel Paris

Ryan Miller

Christian Moreno

James Reepmeyer

ME

2

Agenda Mission Statement Prior Projects Current and Planned Projects Stakeholder needs Objectives and Functions Needs Summary Proposed Projects Revised project proposals Schedule

3

Mission Statement Product Description /Project Overview

We will develop a new command and control system that will introduce a reliable, intuitive, modular and secure system to benefit MSD teams and teach valuable skills and technology relevant to the needs of the Harris Corporation.

Primary Goals Produce project readiness packages for 4 to 6 MSD teams Define new WOCCS project family

Stakeholders Harris Corporation MSD Teams MSD Customers RIT Educational Community

4

Past Senior Design Teams P08027 – Wireless Assistive Control System P06501 – Zigbee Technology P08201 – RP-10 P09232 – Airframe B

Common ThemesLimitations with feedbackUse of unproven and untested systemsDistance and range scalingCOTS capabilities

5

Planned Projects

P10231 – Versatile Adaptive ControllerLead by Joe Pinzone

P10236 – RF TelemetryLead by Chris Barrett

6

Project Family WOCCS represents a new MSD family

Builds off of prior C&C systemIntended to provide a common C&C

software/hardware interfaceWide applicability across MSD programWill result in 4+ MSD projects spanning 1-2

years

ChallengesLittle prior student development – unknown scale

and scopeNo other related project families to reference

7

Stakeholder Needs – Affinity Diagram

MSD Students• Easy and

accessible interface

• Modularity• Multiple

data channels

• Long range• Low power• Reliability• Inexpensive

Harris Corp• Teach

common RF technologies

• Promote Harris presence in MSD program

• Visibility to RIT community

MSD Customers• Value-added

system• Ease of use• Ease of

integration• Little to no

additional cost

• Reliability

RIT Ed Community• High visibility• Intuitive –

Easy to use, easy to teach

• Broad applicability

• Inexpensive

8

Stakeholder Interview - Harris

• Want students interested in RF Technologies• Will not be the end-user of the WOCCS• Budget not a major concern• Key-points in the project for Harris :

• RF Technologies• Vibrations• Materials• Sensors• Energy Efficiency• Programming

9

Develop a modular wireless

C&C system

Wireless Command

Few channels, high bandwidth

Many channels, low bandwidth

Wireless Feedback

Sensor data

Streaming real-time video

Use on a variety of vehicles

Open source

Scalability

Long battery life

Small footprint

Sufficient range

Reliability

Battery life

Range

Minimal data loss

Biomed applications

User-friendly interface

Shorter range

Lightweight (to be carried by a user)

Feedback-intensive

Secure

Objectives Wireless Command

Few Channels, High BandwidthMany Channels, Low Bandwidth

Wireless FeedbackSensor Data vs Real-time Video

ReliabilityBattery LifeRangeMinimal Data Loss

Applications

Use on variety of vehiclesLong battery-lifeOpen SourceSufficient rangeSecurity

In BiomedLightweightFeedback intensiveUser friendly interfaceSecurity

12

Needs SummaryNeed Rank

(DPM)Rank

(Harris)Measure Example

Modularity 2 6 Number of Channels 8-10

Security 8 3 Encryption Standard WEP

Ease of Interface 3 3 Documentation and Licensing

GPL?

Reliability 1 1 Range w/o connection problems

1 km

Inexpensive 7 7 USD Did not specify

Energy Efficiency 6 8 Runtime in hours

Small Size 4 5 Packaging Volume and Weight

Fit on Airframe A

Data Transmissionrate

5 2 Channel Bandwidth (kbps)

250

15

Initial Proposed Projects (1) Wireless link design

Data link developmentSpecify interfaceSignal processingFind scalable hardware for both base

end and device endStaffing: IE, EE, and CE

○ Background focus in signal processing and coding

16

Initial Proposed Projects (2) Software (Base end)

Reduce signal processing softwareDevelop signal routing and

encode/decodeCombine signal processing/routing

software and unify codeProvide scalable software to work with x

number of channels at y bandwidthStaffing: SE, CE, EE

17

Initial Proposed Projects (3) User Interface

Develop human interface to the softwareUse aircraft controller as test case

○ Represents a worst-case scenario of data channels and bandwidth requirements

○ Develop vehicle controller and feedback/sensor display

Staffing: ISE, ID, SE, and CE

18

Initial Proposed Projects (4) On-board hardware optimization

Shrink/reduce/optimize/package radio send/receive hardware from team (1) for use on real-world devices

Reduce sizeReduce power consumptionProvide and/or enhance radio power supplyStaffing: EE (power system), CE (hardware and

interface), and ME (structural and thermal)

19

Initial Proposed Projects (5) (Robotics) Integration

Integrate work from 4 previous teamsRun a robotics project from start to finish

using hardware and software completed to-date

Provide feedback for future optimization Document all successes and failuresStaffing: ISE, ME (Robotics), EE or CE

(hardware integration)

20

Initial Proposed Projects (6) (Biomed) Integration

Integrate work from 4 previous teamsRun a biomedical project from start to

finish using hardware and software completed to-date

Provide feedback for future optimization Document all successes and failuresStaffing: ISE (ergonomics), ME

(Biomed), EE or CE (hardware integration)

21

Results of Research Dr. Kolodziej – Airframe A/B/C RP family of robots Harris

wants COTS parts (No IP issues)Harris’ goal is developing student interest

in RF technologies, not any specific final product

Biomed application P10231 and P10236 are now attached to

the Harris document

22

Suggested Projects: InterfaceSummary: Replacement for intended Project 1 Retains some scope from original project:

Data link development COTS Hardware survey

However, adds new scope: Survey previous interfaces used by MSD teams Identify specific points of failure within interfaces Specify the wireless interface to be used

Team Structure: 3 EE 2 SE 1 SE (Team lead?)

23

Suggested Projects: API Development

Summary: Replacement for intended Project 2 Retains some scope from original project:

Develop signal routing and encode/decode Provide scalable software

However, adds new scope: API development to specify:

○ Data structures○ Analog/Digital/both signal input types?

Could result in two closely linked teams One for base end One for device end

Team Structure: 3 SE 2 CE

24

Suggested Projects: Hardware SelectionSummary: Replacement for intended Project 3 and Project 4 Select actual hardware for final product use Shrink and Optimize hardware and packaging to fit on real-

world devices Reduce size Reduce power consumption Provide and/or enhance radio power supply

Optimize software code Test! Team structure:

2 EE 2 CE 2 SE

25

Schedule

Week 6Re-Identify End UsersRe-Define project goals

Week 7Re-evaluate project plansConduct follow-up interviews with all

stakeholders

26

Schedule

Week 8Define individual projects

Week 9Refine project goals and staffing

requirements Week 10

Project Readiness packageMarketing Video

27

Conclusion

We are designing 4 different cards2 very different applications

There is more background for this project than we realized

Need to develop more concrete set project goals and deliverables

Clarify customers (end-users)

28

Thanks

Dr. Kolodzeij - ME Dr. Hensel - ME Dr. Slack - EE Dr. Vallino - SE Mr. McCusker - Harris

PROJECT STATUS UPDATE

R10003 - WIRELESS OPEN-SOURCE/OPEN-ARCHITECTURE COMMAND AND CONTROL

SYSTEM (WOCCS)

Eric Hettler

Manuel Paris

Ryan Miller

Christian Moreno

James Reepmeyer

ME