cRIO Possibly Bad

[346Programer]

Okay so last weekend we were trying to hook up the ultrasonic sensor; however, we switched some wires and created smoke. Long story short, we fried a bumper that was attached to the cRIO module. We are trying to find out if the cRIO is bad as a result. So we started to download code and this is the output:

init:
init:
Deleting directory C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\build
Deleting directory C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\suite
Deleting directory C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\j2meclasses
clean:
Created dir: C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\build
Compiling 9 source files to C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\build
compile:
Created dir: C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\j2meclasses
preverify:
Created dir: C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\suite
Building jar: C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\suite\ButlerRobot_1.0.0.jar
jar-app:
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]
Romizer processed 107 classes and generated 4 files.
Expanding: C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\suite\ButlerRobot_1.0.0.jar into C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\suite
Moving 1 file to C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\suite
Moving 1 file to C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\suite
Moving 1 file to C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\suite
Deleting: C:\Users\Adam\Documents\NetBeansProjects\ButlerRob ot\image.suite.api
Host OS: Windows 7 6.1, 6.1
Host JVM: Java HotSpot(TM) Client VM 17.0-b17
Target IP: 10.3.46.2
Network interfaces on host:
Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller: address: 10.3.46.12 netmask: 255.255.255.0 <--- on robot's subnet
Connecting FTP @10.3.46.2
upgrade:
Sending local file image.suite
flashapp:
deploy:
init:
[cRIO] [OTA Server] ********* REBOOTING cRIO *********
[cRIO]
Waiting for cRIO to reboot (1s)
Waiting for cRIO to reboot (2s)
Waiting for cRIO to reboot (3s)
Waiting for cRIO to reboot (4s)
Waiting for cRIO to reboot (5s)
Waiting for cRIO to reboot (6s)
Waiting for cRIO to reboot (7s)
Waiting for cRIO to reboot (8s)
Waiting for cRIO to reboot (9s)
Waiting for cRIO to reboot (10s)
Waiting for cRIO to reboot (11s)
[cRIO]
[cRIO] -> * Loading debug.o: debug
[cRIO] Debugging is up, target server mounted at /tsfs
[cRIO]
[cRIO]
[cRIO] VxWorks
[cRIO]
[cRIO] Copyright 1984-2006 Wind River Systems, Inc.
[cRIO]
[cRIO] CPU: MPC5200 -- Wind River Lite5200 BSP.
[cRIO] Runtime Name: VxWorks
[cRIO] Runtime Version: 6.3
[cRIO] BSP version: 2.0/10
[cRIO] Created: May 27 2011, 11:02:24
[cRIO] ED&R Policy Mode: Deployed
[cRIO] WDB Comm Type: WDB_COMM_END
[cRIO] WDB: Ready.
[cRIO]
[cRIO] * Loading nisysrpc.out: nisysrpc
[cRIO] * Loading NiRioRpc.out: NiRioRpc
[cRIO] * Loading nivissvc.out: nivissvc
[cRIO] * Loading nivision.out: nivision
[cRIO] NI-RIO Server 4.0.0b8 started successfully.
[cRIO] task 0xe2ec88 (NiRioRpc) deleted: errno=0 (0) status=0 (0)
[cRIO] * Loading visa32.out: visa32
[cRIO] * Loading niserial.out: niserial
[cRIO] * Loading NiFpgaLv.out: NiFpgaLv
[cRIO] * Loading FRC_FPGA.out: FRC_FPGA
[cRIO] * Loading FRC_NetworkCommunication.out: FRC_NetworkCommunication
[cRIO] FRC_NetworkCommunication was compiled from SVN revision 2923
[cRIO] FPGA Hardware GUID: 0xA14C11BDE4BB64AEF6A86FC52A294CD9
[cRIO] FPGA Software GUID: 0xA14C11BDE4BB64AEF6A86FC52A294CD9
[cRIO] FPGA Hardware Version: 2012
[cRIO] FPGA Software Version: 2012
[cRIO] FPGA Hardware Revision: 1.6.4
[cRIO] FPGA Software Revision: 1.6.4
[cRIO] * Loading FRC_JavaVM.out: FRC_JavaVM
[cRIO]
[cRIO]
[cRIO] [OTA Server] Version: 2012 FRC, Jan 5 2012, 17:20:48
[cRIO]
[cRIO]
[cRIO] Welcome to LabVIEW Real-Time 11.0rc14
[cRIO] task 0xddb110 (sysapi-rpc) deleted: errno=0 (0) status=0 (0)
[cRIO]
[cRIO] [Squawk VM] Version: 2011 FRC, Nov 5 2011, 14:34:13
[cRIO] FPGA Hardware GUID: 0xa14c11bde4bb64aef6a86fc52a294cd9
[cRIO] FPGA Software GUID: 0xa14c11bde4bb64aef6a86fc52a294cd9
[cRIO] DIO LoopTiming: 260, expecting: 261
[cRIO] DIO LoopTiming: 260, expecting: 261

Before the above incident, the robot drove perfectly. Now, it stops at this line. Is there something wrong with the cRIO?

[Kevin Sevcik]

It seems highly unlikely that you could fry the entire cRIO by mis-wiring an ultrasonic. Not impossible, but unlikely. More likely is that you fried the bumper, digital sidecar, analog module, and/or DIO module. I would swap out as many of those items as you have spares of, download a default program that you absolutely know will work, and then see where you are. If things start working again, swap in the suspect parts one by one and see when/if things break.