Quote:
Originally Posted by Tom Bottiglieri
We built our robot dashboard using websockets served out by Java ( https://github.com/Team254/FRC-2015/...54/frc2015/web)
It worked well in the lab, but it failed to connect a few times on the field. I was never able to debug why this failed, and we were seemingly using approved ports. Anyway, good luck! |
Interesting, did you try multiple ports or stick with 5800? I wonder if this is an FMS problem or an issue with Jetty.
Quote:
Originally Posted by Ari423
Just wondering, what is the advantage of using a web interface over a Java, LabVIEW, or C++ (or other) NetworkTables dashboard? I have heard of a few teams using a web interface but I have never heard a good reason why.
|
You have complete control over how you customize and deliver information and control of the robot, using technologies that are installed and work on nearly every device. You can also do some clean visualization with very little code (for example, graphing values with Epoch
https://fastly.github.io/epoch/real-time/). You could use it to easily fetch & view log files, control the robot from a phone or tablet, visualize 3d data, adjust autonomous routines, etc.