custom dashboard and priority user data

[jamescardona]

I am building a custom dashboard in labview and got everything working. Unfortunately the DOs (GPIO State) are wired off the low priority user data line, so then I do not see my sensor updates on the classmate for about 2 seconds. I would like to switch a few sensors to the (currently disabled) high priority user data line to have prompt and usable inidcation. Can anyone tell me how to do that?

[jhersh]

You should remove any lines that you don't care about. Then the data will be more likely to fit even if it is low priority.

If you want to move it to high priority, just create another typedef to represent the high priority data that has which ever variables you want in it, then pack it the same way on the robot and unpack it the same way on the dashboard.

-Joe

[Alan Anderson]

Is it the data priority that's making updates so slow? Or is it the fact that the DIO reading code on the robot itself is only performed every couple of seconds? Look at how and when the default Dashboard data is put together.

[Greg McKaskle]

The priority of the data only comes into play when the ~1kB status packet fills up. At that point low priority data loses out to high priority data for a slot in the packet. Honestly, I'd rather those terms not be used, or even better, the robot should another port to send back all the dashboard data you like.

Anyway, the speed is limited to 50Hz because it is being attached to the next status packet. If your data is being sent more slowly than that, it is because the robot isn't attaching the data very quickly.

You may want to modify the build dashboard code in the robot template to do what you like.

Greg McKaskle