1 / 1

Command and Control (C2) Team GOTChA Chart

Command and Control (C2) Team GOTChA Chart. G oals. T echnical Ch allenges. Provide an interface between Roboflag software and MVWT hardware Provide a non-Roboflag interface for user applications and the MVWT hardware. Not familiar with Roboflag arbiter software, MVWT I C2 software

jamar
Download Presentation

Command and Control (C2) Team GOTChA Chart

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Command and Control (C2) Team GOTChA Chart Goals Technical Challenges • Provide an interface between Roboflag software and MVWT hardware • Provide a non-Roboflag interface for user applications and the MVWT hardware • Not familiar with Roboflag arbiter software, MVWT I C2 software • Possible communication constraints from Vehicle Team • Don’t know format of positioning system • Complexity of C&C API, inexperience in writing APIs • Need fast enough software to work with 12-24 vehicles. Objectives • Maintain current interface code for MVWT I. (1.1, 6/27) • Modify code from MVWT I to work with MVWT II (1.2, 7/4) • Provide C&C API for user applications to handle up to 12 vehicles (MVWT lab) or 24 vehicles (roof), running at 10 Hz(2, *8/3) • Graphical support (data logging visualization) (3, *8/15) • A new simple generic GUI (3, *8/15) Approaches • Study and do a live run of the current Roboflag code and current testbed code. • Weekly meetings with both teams to determine proper interfaces. • Detailed block diagrams, work breakdowns, schedules for API, keep documentation in Doxygen.

More Related