70 likes | 149 Views
Team 22. Project-Virtual Whiteboard. Concept & Motivation. Whiteboard is convenient, but you can’t carry it around. Writing/Drawing on a software is also very cool, but its hard to draw with mouse. Why not combine them?
E N D
Team 22 Project-Virtual Whiteboard
Concept & Motivation • Whiteboard is convenient, but you can’t carry it around. Writing/Drawing on a software is also very cool, but its hard to draw with mouse. • Why not combine them? • We have the idea of creating a virtual whiteboard. A whiteboard that you can project and write. The overall goal is to create some virtual whiteboards and let them act like clients and then have a central server end to collect all boards information and output together. Then users will have the same whiteboard they are working on.
Competitive Analysis • Conventional Whiteboard. Portability is a big problem, people can't carry a conventional whiteboard around easily. • Wii's virtual drawing board.It uses IR sensor to track the controller. You can only have a limited number of users using it, probably 4. It can't support more than that. Also you kind point the controller towards the screen rather than “writing”. • "Write" on a software on you pc. It's hard to write/draw with a mouse! Even if you have a separate hardware acts like touchpad+pen, you can only draw in front of your computer, which don’t feel like drawing on the board. • Web whiteboard Same problem with drawing on pc.
Requirements • The camera should be able to track the LED light source (acts like your marker) and render the “picture” to track of the LED light source. • The server board should be able to convert all the track histories from each client to a output picture. • Output through projector.
Technical Specifications • Hardware: • LED pen (build on our own, act like a marker) CLIENT END • Android phone (for image capturing and some image processing) CLIENT END • BeagleBoard-xM (for combining clients’ information) SERVER END • Projector/screen (display output) • Software: • Android SDK (Phones/Clients) • Ubuntu/C (BeagleBoard-xM) • USB Driver (version 1) • Wi-Fi Driver (version 2) • Protocols: • USB (localized version, version 1) • Wi-Fi (advanced version, version 2) • VGA/DVI video output (from BeagleBoard to projector)
Architecture Phone (capturing & processing images) Phone (capturing & processing images) Light Light LED Pen (light source) LED Pen (light source) Client End 1 Client End 2 …... Projector Server End USB/Wi-Fi BeagleBoard (Construct output) …... VGA/DVI
Risk & mitigation plan • The communication between phone and board may fail, which then the server-client communication won’t be able to establish. • do USB connection rather than Wi-Fi • The lag between when user write to when the strokes are displayed may be too long and make the experience not good. • Redistribute the workload on phones and boards, to utilize the processing power better. • The phone tracker may not be able to pick up LED information correctly. • Make a better LED light source or other way to track the “marker”. • Concurrency problem when combining multiple clients’ information into one output. • Support one user rather than multiple.