[apalrd]

1. What are you trying to do with your Dashboard where you filled the 900byte packet?

2.Why isn't 25hz fast enough if you do manage to fill the packet and use two?

I ran a dashboard this year that used the Dashboard packet, and I filled it with:

1 uint8 kick distance
2 doubles gyro data
camera image (separate from DB packet)
1 uint8 chassis mode enum
3 booleans for suckifier system
2 doubles for kicker (recoil position and pot position)
1 uint8 kicker mode enum
3 doubles for arm (setpoint, shoulder pot, chassis string pot)
1 uint8 arm mode
2 booleans for arm (shift state and swap sensor state)
2 doubles for drivetrain speed (ft/sec actual, ft/sec highest since boot)
1 uint robot mode (I think its 16 bit since thats LV default for enums)

And then I wrote a LabVIEW dashboard to arrange all of the data. I ran out of room to show it all,so I created a system of 6 tabs ("Prematch","Autonomous","Teleop","Pit-Debug Kicker","Pit-Debug Arm","Pit-Debug Drivetrain"), 3 of which automatically switched. If in pre-match, auto. or teleop, it would automatically switch tabs based on auto/teleop or disabled state. If in the pit tabs, it would stay. Really helpful, provided a ton of data, and allowed us to look at sensor variables without deploying code - helpful to see if problems are in hardware or software.

I did not fill up one packet.

So 900 bytes is a LOT of data.