Click to close
Click to close
When the authors of this website first started programming for FRC, we would get the 'Robot Drive Not Running Fast Enough' error frequently. After speaking with several teams at regionals, we came up with a solution. The following optimization has been used by the teams that we are alumni of and mentors of, and none of the teams have had that error since.
Begin by opening the devices in Begin.vi, notice that we even skip setting the refnum, and just bundle everything.
Now, place an indicator on the front panel, here is another place where the TypeDef can be extremely useful, so we'll take a moment to set one up, notice that we also take this opportunity to rename each element in the cluster to something meaningful (drive joystick, rather than JoystickDevRef)
We can use these names in the Begin.vi block diagram as well - by switching the bundle for a bundle by name - this also bears other advantages like what is demonstrated in the TypeDef tutorial
For now, we copy the indicator from Begin, to Teleop and paste it on the front panel (and switch it to a control).
We can connect both the control and the indicator to the terminal block, and connect the two in main.vi
Inside Teleop we can unbundle the DevRefs and use them.
This wire allows us to skip the getDevRef for every device every time through the loop. Giving us the performance boost we were after.
Notice that the wire in main will not break thanks to the typedef.
This minor change to the architecture can permit Teleop to complete just a little faster, which can remove the error message, and using a typedef, can save a lot of time during development too.