We are a rookie team, and out group has been attempting to get both Java and LabView code onto the robot. We’ve done many suggestions found on the forums and followed the step-by-step instruction guide for both.
For each of these, we used the correct imaging for each code and set it up for our team IP (I.E., 10.47.01.02 for the robot, 10.47.01.05 for our netbook).
{while trying Java}
I’ve taken down every single firewall I can find, opened every port, and wrote a new “rule” for outgoing data as found in a forum post. This did not work. I uninstalled and reinstalled Netbeans modules, as recommended in the forums. We performed updates and re-updates. With our Driver Station, we have greenlights for Communication and Joysticks. When we tried to run the Java, as outline in the FRC step-by-step instruction guide, we had an error code which, at the top, essentially said there was a communication problem.
{while trying LabView}
Deployed every way it said to in the instructions, all the other settings are the same, and no dice.
Does anyone else have this issue or know of a way to fix it? I’ve spent 4 hours and my friend has spent 8 trying to get this thing to get onto the robot.
On the driver station, there is still a red indicator light next to “robot code”, and if we try to enable the robot, it flashes “no robot code”. When we tried to “Run Main Project” on Java, it would compile for about 45 seconds until it gave a block of red text (currently, my associate is trying different things with LabView, so I can’t recreate the block of text exactly. However, according to the little messages in Netbeans as the code compiled, it got to where it was trying to connect to the robot and failed.
When Labview is run, it says “successfully deployed” but nothing happens.
Edit (Labview): “The realtime application has not been built. You must build the application before deploying.” “FRC robot bootup deployment unable to resolve from current dialogue”.
Update: We got the robot code light lit on the Driver Station, using LabView but there is no movement. We’re currently looking for the joystick input on LabView. Chriz4gx’s thread has a solution that worked for us.
If you haven’t made too many changes to the default LabVIEW project, it’ll be showing you the X, Y, and “throttle” axes of Joystick 1 on the Dashboard screen. It’ll also show the commanded values on the motors defined as your left and right drive.