cRIO Connection Failure

[wolfspell12]

We're having some problems deploying code to the cRIO. Other people have had this problem before by the looks of some googling, but I think we tried all the traditional fixes, such as disabling firewalls, checking IP address, and went as far as uninstalling our antivirus in attempt to fix the connection issue. The cRIO port is lit green, as it should be when tethered to the cRIO. Any help would be greatly appreciated. The following is the error message we get whenever clicking the run button in NetBeans.

ant -f C:\\Users\\gcgh\\Documents\\NetBeansProjects\\Robo tTemplate deploy run
clean:
Deleting directory C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build
Created dir: C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build
Created dir: C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\classes
[crio-compile] ./src, C:/Users/gcgh/sunspotfrcsdk\lib\wpilibj.jar;C:/Users/gcgh/sunspotfrcsdk\lib\networktables-crio.jar, C:/Users/gcgh/sunspotfrcsdk\lib\squawk.jar -> ./build/classes
Compiling 1 source file to C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\classes
compile:
preverify:
Created dir: C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\preverify
Created dir: C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\preverify.raw.util
[crio-preverify] ./build/classes, , C:/Users/gcgh/sunspotfrcsdk\lib\wpilibj.jar;C:/Users/gcgh/sunspotfrcsdk\lib\networktables-crio.jar, C:/Users/gcgh/sunspotfrcsdk\lib\squawk.jar -> ./build/preverify
Expanding: C:\Users\gcgh\sunspotfrcsdk\lib\wpilibj.jar into C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\preverify
Expanding: C:\Users\gcgh\sunspotfrcsdk\lib\networktables-crio.jar into C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\preverify
jar:
[crio-jar] ./build/preverify, ./resources -> ./build/app.jar
Building jar: C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\app.jar
suite:
Created dir: C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\suite
[crio-suite] ./build/app.jar -> ./build/suite/image
CompilerOracle: exclude com/sun/squawk/Method.getParameterTypes
CompilerOracle: exclude com/sun/squawk/SymbolParser.getSignatureTypeAt
CompilerOracle: exclude com/sun/squawk/SymbolParser.stripMethods
[translating suite image [closed: false, parent: squawk] ...]
### Excluding compile: com.sun.squawk.Method::getParameterTypes
### Excluding compile: com.sun.squawk.SymbolParser::getSignatureTypeAt
[Including resource: META-INF/MANIFEST.MF]
[Including resource: META-INF/maven/edu.wpi.first.wpilib.networktables.java/NetworkTablesAzalea/pom.properties]
[Including resource: META-INF/maven/edu.wpi.first.wpilib.networktables.java/NetworkTablesAzalea/pom.xml]
Romizer processed 388 classes and generated 4 files.
Expanding: C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\app.jar into C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\suite
Moving 1 file to C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\suite
Moving 1 file to C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\suite
Moving 1 file to C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\build\suite
Deleting: C:\Users\gcgh\Documents\NetBeansProjects\RobotTemp late\image.suite.api
deploy:
[crio-configure] Configuration files not included in this version of the sdk
[crio-configure] Checking that crio is configured for Java
Host OS: Windows 7 6.1, 6.1
Host JVM: Java HotSpot(TM) Client VM 24.45-b08
Target IP: 10.32.44.2
Network interfaces on host:
Intel(R) PRO/1000 PL Network Connection: address: 10.32.44.100 netmask: 255.255.255.0 <--- on robot's subnet
Connecting FTP @10.32.44.2
C:\Users\gcgh\sunspotfrcsdk\build.xml:79: The following error occurred while executing this line:
C:\Users\gcgh\sunspotfrcsdk\ant\configure.xml:41:
java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Du alStackPlainSocketImpl.java:79)
at java.net.AbstractPlainSocketImpl.doConnect(Abstrac tPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress( AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractP lainSocketImpl.java:182)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:392)
at java.net.Socket.connect(Socket.java:579)
at org.apache.commons.net.SocketClient.connect(Socket Client.java:182)
at org.apache.commons.net.SocketClient.connect(Socket Client.java:203)
at org.apache.commons.net.SocketClient.connect(Socket Client.java:296)
at com.sun.spot.sdk.tool.ftp.JakartaFtpWrapper.connec tAndLogin(Unknown Source)
at com.sun.spot.sdk.tool.ftp.UpgradeTask.execute(Unkn own Source)
at org.apache.tools.ant.UnknownElement.execute(Unknow nElement.java:292)
at sun.reflect.GeneratedMethodAccessor70.invoke(Unkno wn Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execut e(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(S equential.java:68)
at net.sf.antcontrib.logic.Switch$Case.execute(Switch .java:171)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execut e(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at net.sf.antcontrib.logic.Switch.execute(Switch.java :138)
at org.apache.tools.ant.UnknownElement.execute(Unknow nElement.java:292)
at sun.reflect.GeneratedMethodAccessor70.invoke(Unkno wn Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execut e(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(S equential.java:68)
at org.apache.tools.ant.UnknownElement.execute(Unknow nElement.java:292)
at sun.reflect.GeneratedMethodAccessor70.invoke(Unkno wn Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execut e(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.MacroInstance.execut e(MacroInstance.java:396)
at org.apache.tools.ant.UnknownElement.execute(Unknow nElement.java:292)
at sun.reflect.GeneratedMethodAccessor70.invoke(Unkno wn Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execut e(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:43 5)
at org.apache.tools.ant.Target.performTasks(Target.ja va:456)
at org.apache.tools.ant.Project.executeSortedTargets( Project.java:1393)
at org.apache.tools.ant.Project.executeTarget(Project .java:1364)
at org.apache.tools.ant.helper.DefaultExecutor.execut eTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Projec t.java:1248)
at org.apache.tools.ant.module.bridge.impl.BridgeImpl .run(BridgeImpl.java:283)
at org.apache.tools.ant.module.run.TargetExecutor.run (TargetExecutor.java:541)
at org.netbeans.core.execution.RunClassThread.run(Run ClassThread.java:153)
BUILD FAILED (total time: 31 seconds)

[wolfspell12]

More details, from an attempt to ping the robot with command prompt.
C:\Users\gcgh>ping 10.32.44.2
Pinging 10.32.44.2 with 32 bytes of data:
Reply from 10.105.255.249: TTL expired in transit.
Reply from 10.105.255.249: TTL expired in transit.
Reply from 10.105.255.249: TTL expired in transit.
Reply from 10.105.255.249: TTL expired in transit.

Ping Statistics for 10.32.44.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss).

[Krotn]

We've seen the same exception before as well. Generally when it's happened to me it's that NetBeans is configured for the wrong team number, the firewall is blocking the connection, there's a problem with the ip settings on the development computer.

It looks like NetBeans is set up right and you said that you tried disabling the firewall (maybe double check that you turned it off on both public and private networks). You could also let the driver station set up your ip for you by hitting the "Choose NIC" button under setup. Also, did you image your cRIO, was there an error during that possibly?

[wolfspell12]

We tried the IP fixes suggested and it's not working. We tried to re-image and the tool wouldn't even pick up the existence of the module. Something may also be wrong with safe mode-that kind of reboot won't fix it. One of our mentors is convinced the cRIO is corrupted and says we need to remove the software from it entirely. If that is indeed the case, then how do we fix it?

[Joe Ross]

More details, from an attempt to ping the robot with command prompt.
C:\Users\gcgh>ping 10.32.44.2
Pinging 10.32.44.2 with 32 bytes of data:
Reply from 10.105.255.249: TTL expired in transit.


Why is 10.105.255.249 replying? Something is very much wrong with the network setup.

[Mark McLeod]

Did you Disable the laptop's wireless NIC and all other NICs leaving the Ethernet port the only Enabled one?
If the wireless NIC is active the tool may get confused and try to use that instead of the wired Ethernet port. It's possible the wireless is connecting to a school router running a 10. network.

[eddie12390]

More details, from an attempt to ping the robot with command prompt.
C:\Users\gcgh>ping 10.32.44.2
Pinging 10.32.44.2 with 32 bytes of data:
Reply from 10.105.255.249: TTL expired in transit.
Reply from 10.105.255.249: TTL expired in transit.
Reply from 10.105.255.249: TTL expired in transit.
Reply from 10.105.255.249: TTL expired in transit.

Ping Statistics for 10.32.44.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss).



Can you post the information from

tracert 10.32.44.2

[wolfspell12]

Disconnected from wi-fi, no different. The cRIO imaging tool is not detecting any modules, despite the fact that there are three installed(This is an older style which has room for 8 modules if that matters.)

C:\Users\gcgh>tracert 10.32.44.2
Tracing route to 10.32.44.2 over a maximum of 30 hops
1 gcgh02 [10.32.44.6] reports: Destination host unreachable.
Trace complete.
C:\Users\gcgh>

Edit: also pinged again with wi-fi disconnected. Command prompt said pinging 10.32.44.2 but got a reply fro 10.32.44.6. (The computers IP) Sent 4 packets but lost none.

[eddie12390]

Disconnected from wi-fi, no different. The cRIO imaging tool is not detecting any modules, despite the fact that there are three installed(This is an older style which has room for 8 modules if that matters.)

C:\Users\gcgh>tracert 10.32.44.2
Tracing route to 10.32.44.2 over a maximum of 30 hops
1 gcgh02 [10.32.44.6] reports: Destination host unreachable.
Trace complete.
C:\Users\gcgh>

Edit: also pinged again with wi-fi disconnected.

Try to IP Reset the cRIO and then re-image it.

[garyk]

We tried the IP fixes suggested and it's not working. We tried to re-image and the tool wouldn't even pick up the existence of the module. Something may also be wrong with safe mode-that kind of reboot won't fix it. One of our mentors is convinced the cRIO is corrupted and says we need to remove the software from it entirely. If that is indeed the case, then how do we fix it?

Has it ever worked?

Try connecting your computer directly to the cRIO with a crossover (orange) lan cable, plugged into the cRIO's LAN port, so there's no switch/bridge in the data path. As was mentioned before, disable WiFi on your computer (not just disconnect any connection, go to Control Panel => Networking and disable WiFi). Your computer's LAN IP address should be 10.32.44.5. Then run the NI imaging tool and let us know what happens.

If you did find a solution please post so others with the same problem benefit! Thanks!

[wolfspell12]

We switched pc's and we were able to reboot the cRIO in safe mode, and reformat it from there. We called National Instruments support number (check their website if you need it.) and they walked us through debugging. They wound up having us change a few things within cRIO FTP server. After that we were still having problems with getting the cRIO to respond. It turned out there was a problem with the digital sidecar because one of the ports went bad. We moved a PWM cable, then both sides of tank drive started to respond :D.

Thank you all for the help!