Oh yeah, we're doing the same thing - we are pulling over 4 10-bit numbers using 5 user bytes, and then using the 6th user byte as a "code" indicator of what values we're pulling over so we can multiplex even more - you send 4 numbers with one code, send 4 more with another code, and so on, and before you know it you have all the information you need updating about 10 times per second! (just be careful, not all user bytes come over at the same rate since some user bytes are included in multiple packets).
The COOLEST thing EVER, that I REALLY wish everyone would look into, is the 3D Picture Control. Team 418 is going to have a 3D picture control on our Dashboard showing us a 3D representation of our robot arm based on the information we get back from the robot, so we can quickly and easily see where the arm is and how it's positioned at any time (even if the robot arm is occluded by the rack and other robots/objects). We'd love to integrate a field model in our 3D picture control so we can even see where we are in relation to the field and the rack and everything, but with only one person doing LabVIEW programming on the team (not me, I don't do anything, I make them do everything) it is waaaaay too much for them to bite off. However, if we had the manpower, it would be an extremely awesome way to get in some more driver practice time if you also simulated the Robot in LabVIEW at the same time...
Maybe if I can get a few projects off my back I'll have some time to do a small demo to show everyone the potential of just how useful these tools and LabVIEW really can be!
-Danny