Driverstation referencing

[Alan Anderson]

Originally Posted by CooneyTech

On the left is teleop on the right is the dashboard reference.

I see them in the other order, but no matter.

Where are those wires heading upward in the dashboard code going, and what are they connected to? Is that part of the code inside a loop?

[CooneyTech]

Originally Posted by Alan Anderson

I see them in the other order, but no matter.

Where are those wires heading upward in the dashboard code going, and what are they connected to? Is that part of the code inside a loop?

It was a different test I did I was bundling them then trying to send them that way to. I have sense removed it and just did each one individually.

[CooneyTech]

Attached I have the driver station code and the code for Teleop where i reference it.

[Alan Anderson]

Originally Posted by CooneyTech

Attached I have the driver station code and the code for Teleop where i reference it.

It looks like your Dashboard code does a SmartDashboard write for those values once when the program begins, then never does it again. If you want to use the SD Write functions, you'll need to put them in a loop that runs as long as the values are required.

But you don't need to use the SD functions with the LabVIEW Dashboard. An indicator or control on the Operations tab is automatically a SmartDashboard variable all by itself, and Greg showed you how to make things on other tabs work as well.

[CooneyTech]

If its a SD by its self how exactly do I reference it? And for a loop would a while loop work ok?

[Alan Anderson]

Originally Posted by CooneyTech

If its a SD by its self how exactly do I reference it? And for a loop would a while loop work ok?

Most of the time, you would "reference" a SmartDashboard variable simply by looking at it on the Dashboard's front panel, or by clicking on it, or by typing a number in it.

A While loop is perfect. Just make sure to include a short delay (50 ms or so) to keep it from monopolizing the CPU.