GitXplorerGitXplorer
C

RoboRecon

public
0 stars
3 forks
1 issues

Commits

List of commits on branch master.
Verified
29dc4301c070ac1e538155b861cb42215c22ea6c

Merge pull request #17 from bbacskay/export_to_file_2

CCarolinaKinetic committed 7 years ago
Unverified
bed092302f85238381d665c3c234e2686a7882c6

Fixing scouting export file data content.

bbbacskay committed 7 years ago
Unverified
30e8d95a1f3a396024af270d01dc4e840a83696e

Merge branch 'bbacskay-master'

CCarolinaKinetic committed 7 years ago
Unverified
a8db8742661d8c39b0d40b93f38b89f17b0d75db

Merge branch 'master' of https://github.com/bbacskay/RoboRecon into bbacskay-master

CCarolinaKinetic committed 7 years ago
Unverified
a77bae0fa84bfcedc13db725344abcf5988a2743

Merge branch 'bbacskay-update_app_name'

bbbacskay committed 7 years ago
Verified
c37e5c5bbb86a743d28d50bd92a927be585bcdf0

Merge pull request #14 from bbacskay/export_to_file

CCarolinaKinetic committed 7 years ago

README

The README file for this repository.

RoboRecon

This is a mobile app developed by Team 3489 (Category 5) to gather scouting data for FIRST Robotics Competition.

Overview

RoboRecon is an app that runs on Android or iOS devices. This document refers to the devices as "tablets," though you may also be able to use large-screen phones, the app installed on Chromebooks with ChromeOS 53 or later installed, and possibly other devices.

The app is built on the Ionic technology stack, and uses a MEAN stack on a Raspberry Pi (RPi) as a centralized server to capture and collate data that was entered on the tablets. The tablets are connected to an 8-port network switch via microUSB-to-Ethernet cables, and the app that runs on the tablets connects to the RPi over the closed network. ("Closed network" refers to the fact that there is no Internet connection.)

The RPi hosts a MongoDB database and provides a REST API that the tablets interact with to push and pull data. A thumb drive is used to transport the data from the stands to the pit.

History

RoboRecon is the third iteration of the mobile app that started out as Cat5Scouting, and then was morphed into TheHindenburg. The first iteration used SQLite to store data on the six Android tablets that our scouting students used to capture data. That data was then exported to CSV files and imported into a spreadsheet for analysis. The second iteration, which was the first iteration that had students writing code for it, used Firebase to store data.

At the end of the 2017 FRC season, the codebase for TheHindenburg was released to a GitHub open source repository. Feel free to fork this repo if you'd like to try using Firebase as your datastore. Firebase worked well for us at regionals, but when we went to World's in Houston, we couldn't get a strong enough Internet connection and had to fall back to using paper scouting. (Ugh!)

Open source contributions

One difference between the past two years and this year is that we've open-sourced the application code, and are keeping the application code open source as we move forward for the 2018 season. If you'd like to participate, there are different ways you can do so, including:

  • Using the app without contributing code
  • Forking the repository and adding your own code for your own use
  • Forking the repository and contributing your code back to the code base for all to use

In addition to writing code and optionally contributing it to the code base, you can also:

  • Submit bug reports and feature requests on GitHub
  • Write or record video for tutorials for other teams to follow for how to set up the environment
  • Share the questions that you will set up your copy of the app to ask

Contact

To contact the Category 5 app development team to ask questions or provide feedback, there are several avenues: