Web interface

[x86_4819]

Another benefit web interfaces have is their ability to run remotely on almost any device. The webdash I built last season (mentioned by OP) was designed to be run on a roborio and provide convenient debugging information. If our robot started acting funny while someone else was driving I could just pop on the dashboard from my phone to read the logs, check/modify networktables data, or download a complete logfile from the current run to view later. This dashboard was eventually installed and set to run on startup on each of our controllers, and is my first place to check for any robot problem.

Gameplay dashboards are different. Running it on the robot seems to have more drawbacks than benefits, since you can't run pre-match configuration without it. By the way (this goes to virtuald and any who ran web-based gameplay dashboards) how did you manage your webserver so that non-programmers could easily access it?

[JesseK]

Originally Posted by x86_4819

By the way (this goes to virtuald and any who ran web-based gameplay dashboards) how did you manage your webserver so that non-programmers could easily access it?

The intent is via web calls - start a browser, point to a URL. We plan to have a 'raw data' page which gives an auto-refreshing view of 'all' data in a simple table format.

If non-programmers want more than that, I'm sure we could hook something like Tableau up to the MongoDB backend.

[virtuald]

I made a shortcut on the desktop of our driver station machine that would start chrome with the correct resolution and the correct page.