search

WaltonRobotics / OutreachBots

Code developed for the initial chassis with the 2015 FRC Control System
0 stars 0 forks source link

Dashboard Overload #5

Open TheBassett opened 9 years ago

TheBassett commented 9 years ago

This shouldn't be a problem under normal circumstances, but it's worth mentioning - smart dashboard may be being updated a lot.

If the "Show Inputs" class is running, then SDB is updating all values when the scheduler is calling its execute (probably comparable to time of "teleop periodic"). I forget the structure of SDB but I know it does record many values in it's network tables - if these values are updated too much w/o being cleared there may be a problem. I think SDB stores the values on the network as well.

Again, the data being transferred/stored is minuscule, however, if it is updated every 20ms during a match on a network with camera tracking there might start to be problems.

timstanistreet commented 9 years ago

Thanks Alex -- good point, we should be careful on bandwidth usage. This code is for a test chassis so regular updates here are probably not too bad!

On Thu, Jan 15, 2015 at 4:05 PM, TheBassett notifications@github.com wrote:

This shouldn't be a problem under normal circumstances, but it's worth mentioning - smart dashboard may be being updated a lot.

If the "Show Inputs" class is running, then SDB is updating all values when the scheduler is calling its execute (probably comparable to time of "teleop periodic"). I forget the structure of SDB but I know it does record many values in it's network tables - if these values are updated too much w/o being cleared there may be a problem. I think SDB stores the values on the network as well.

Again, the data being transferred/stored is minuscule, however, if it is updated every 20ms during a match on a network with camera tracking there might start to be problems.

— Reply to this email directly or view it on GitHub https://github.com/WaltonRobotics/TestBot/issues/5.

destrucules commented 9 years ago

Hey Alex What are your thoughts on limiting the amount we update SmartDashboard without compromising on accuracy? I have ideas of my own, but given that you've pointed out the problem I imagine you have some experience or prior notions about what should be done to fix it. Thanks for pointing it out!

PS: I know FRC code is cool, but you do have a life! As much as we love your help and consideration, we don't want to burden you!

PPS: GitHub is awesome

On Thu, Jan 15, 2015 at 4:27 PM, Tim Stanistreet notifications@github.com wrote:

Thanks Alex -- good point, we should be careful on bandwidth usage. This code is for a test chassis so regular updates here are probably not too bad!

On Thu, Jan 15, 2015 at 4:05 PM, TheBassett notifications@github.com wrote:

This shouldn't be a problem under normal circumstances, but it's worth mentioning - smart dashboard may be being updated a lot.

If the "Show Inputs" class is running, then SDB is updating all values when the scheduler is calling its execute (probably comparable to time of "teleop periodic"). I forget the structure of SDB but I know it does record many values in it's network tables - if these values are updated too much w/o being cleared there may be a problem. I think SDB stores the values on the network as well.

Again, the data being transferred/stored is minuscule, however, if it is updated every 20ms during a match on a network with camera tracking there might start to be problems.

— Reply to this email directly or view it on GitHub https://github.com/WaltonRobotics/TestBot/issues/5.

— Reply to this email directly or view it on GitHub https://github.com/WaltonRobotics/TestBot/issues/5#issuecomment-70164980 .