Quote:
Originally Posted by TuxCoding
Yeah, we are trying to do that this year, since we switched our robot code from Labview to Java. We keep running into "Table Key not found" errors (basically not finding the values on the Dashboard and saying "Output not updated often enough"). I tried both Networktables and SmartDashboard, and was wondering how you set up the VI and .java file?
|
The "Output not updated often enough" message is from the motor safety stuff, most likely from a RobotDrive object you created in your code. The idea is that if the RobotDrive outputs aren't updated often (every 100ms by default) it assumes that the program crashed and stops the PWM output to the motors. You can either make sure to keep updating motor values in any loops you have or disable the motor safety with:
Code:
yourRobotDriveObject.setSafetyEnabled(false);
To address the "Table key not found" error, you can see what values are in NetworkTables using the OutlineViewer.jar program. Just run it on your driver station computer and it will show you all the keys and values in NetworkTables. Then you can verify that the key is being written. For the SmartDashboard supplied with C++ and Java the keys need to be in a subtable called "SmartDashboad". I'm not sure about the LabVIEW dashboard, but will find out and add it to this post a little later today.