-
Notifications
You must be signed in to change notification settings - Fork 88
FTC Dashboard Support #380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FTC Dashboard Support #380
Conversation
# Conflicts: # README.md
…e-RR into patch-rr-log # Conflicts: # README.md
Add separate app menu rather than putting extra options under help, hide edit menu on Windows & Linux
…5/AdvantageScope into patch-ftc-dashboard-working
# Conflicts: # src/shared/Preferences.ts
# Conflicts: # src/main/electron/main.ts
|
Okay, I think this is fully working now. Testing without an FTC robot might be a little difficult; I've been using https://github.com/jdhs-ftc/DashReplayView/ (my previous roadrunner log parser, that used ftc dashboard as a backend), and the upstream backend tests could be used too. |
|
I've added running detection as well. These could easily technically be added, but would require changes to AdvantageScope and might be out of scope based on other closed PRs. |
I think both of these are reasonable omissions given what AdvantageScope supports for existing formats. Looks like this PR is based on a slightly older version of the Road Runner format PR, but if you get it up-to-date it's probably close to being ready to merge (maybe with a few minor tweaks). |
…-working # Conflicts: # README.md # rollup.config.mjs # src/hub/dataSources/HistoricalDataSource.ts # src/hub/dataSources/roadrunnerlog/RRLOGDecoder.ts
This adds support for receiving telemetry, status, and config from FTC Dashboard running on an FTC robot. Communication is via JSON websockets.