Functional Requirements

  • Flight Data
    • Flight stage
    • Full system health status
      • Operational
      • Minor error
      • Fatal error
  • Network Status
    • View Network Connection Status
      • Connected
      • Not Connected
    • View time since last network packet was received
      • Example 20ms
  • Peripheral Data
    • Note:
      • Health status will be broken down into:
        • Operational
        • Disconnected
        • Faulty
    • View Accelorometer Data
      • Health status
      • Activation state
      • x,y,z
    • View Gyroscope Data
      • Health status
      • Activation state
      • x,y,z
    • View Barometric Pressure Data
      • Health status
      • Activation state
      • altitude
    • View Magnetometer Data
      • Health status
      • Activation state
      • heading
    • View Ultrasonic Sensor Data
      • Health status
      • Activation state
      • distance in mm
  • Actuator Data
    • View Motor data x4
      • Health status
      • Power percentage
    • View servo data x4
      • Health status
      • Angle
  • System Data
    • System needs to be capable of uniquely identifying connection
    • System needs to be capable of verifying firmware version

Transferred Data

This contains information pertaining to what data is actually transmitted and received to and from the UAV over the wireless connection.


Estimated Total Unique Messages: 46

Received Data (from the UAV)

logging

  • debug
  • info
  • error
  • fatal

peripheral

managed by AACS > Sensor Control Interface

  • accelorometer:
    • x
    • y
    • z
    • status : operational, faulty, disconnected
    • activation state: activated, deactivated
  • gyroscope:
    • x
    • y
    • z
    • status : operational, faulty, disconnected
    • activation state: activated, deactivated
  • altimeter
    • altitude
    • status : operational, faulty, disconnected
    • activation state: activated, deactivated
  • magnetometer
    • heading
    • status : operational, faulty, disconnected
    • activation state: activated, deactivated
  • ultrasonic
    • distance
    • status : operational, faulty, disconnected
    • activation state: activated, deactivated

actuator

managed by AACS > Actuator Control Interface

  • motor 1
    • status : operational, faulty, disconnected
    • power percent
  • motor 2
    • status : operational, faulty, disconnected
    • power percent
  • motor 3
    • status : operational, faulty, disconnected
    • power percent
  • motor 4
    • status : operational, faulty, disconnected
    • power percent
  • servo 1
    • status : operational, faulty, disconnected
    • angle
  • servo 2
    • status : operational, faulty, disconnected
    • angle
  • servo 3
    • status : operational, faulty, disconnected
    • angle
  • servo 4
    • status : operational, faulty, disconnected
    • angle

flight data

managed by AACS > Master Control Interface

  • flight stage
  • overall system health
  • ready to enter launch stage
  • ready to enter target acquisition stage
  • ready to enter stealth surveillance stage
  • ready to enter vehicle extraction stage
  • ready to enter landing stage

Transmitted Data (to the UAV)

UI Design

C2 User Interface Design

Accelerometer X: 0.5553765 Y: 0.0127444 Z: -0.568222

Gyroscope X: 0.5553765 Y: 0.0127444 Z: -0.568222

Barometric Pressure altitude: 233.7555 ft

Ultrasonic distance: 205.25552 mm

Magnetometer heading: 45.557

Flight Status: Stage: Startup System Health: Operational

Peripheral Status: Accelerometer: Operational Gyroscope: Operational Barometric Pressure: Operational Ultrasonic: Faulty Magnetometer: Disconnected

Motor Status: Motor 1: Operational Motor 2: Operational Motor 3: Operational Motor 4: Operational

Servo Status: Servo X: Operational Servo Y: Operational Servo L: Disconnected Servo R: Disconnected

Motor 1 Power: 10%

Motor 3 Power: 11%

Motor 2 Power: 12%

Motor 4 Power: 10%

Servo X Angle: 90

Servo Y Angle: 95

Servo L Angle: N/A

Servo R Angle: N/A

command injection:

Logs: ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...

Accelerometer Graph (X, Y, Z)

Altitude Graph

Link to original

System Architecture

C2 System Architecture

C2 Proxy
C2 Web Interface

TCP Socket Handler

Needed

  • Starts a new thread for each connection
  • Every connection is treated like the same device
    • This is to handle situations where the UAV disconnects and reconnects
    • There should only ever be one UAV
  • Command Callback function
  • Send Command function
  • One static socket
    • This is overridden when a new connection is received
      • This way the application is always working with the current connection

Methods

  • socket_handler_init(receive_message_callback_function)
    • Starts up a new thread
  • socket_handler_send(String)

Variables

  • static : socket

WebSocket Handler

Command Manager

WebSocket Client

Command Handler

Control Panel

UAV TCP Client

Mission Planner

Link to original