[gamegeek1995]

Some of this is copy-pasted from my last thread, but it's still relevant to this problem.

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} [currently trying labview exclusively]
Deployed every way it said to in the instructions, all the other settings are the same, and no dice.

All lights are green on the driverstation, but every time we build, "run as startup", or deploy any part of the code (or all of it), we get the same "Unable to connect to real time target" response.

We thought yesterday, when we got all green lights, that we'd fixed the issue. However, the only difference between Java and LabView is this false positive. Any suggestions?