Software Installation Notes from Toronto Quick Build

Today we did our Quick Build session in Toronto at Crescent School immediately following our remote Kick-Off at the Science Centre. Here are the notable observations I had from the installation of this year’s software tools. They are Java-centric as our team, and a large number of those attending wanted to use Java. They are also geared towards the Rookie experience, as that was the main audience of our Quick Build. They also assume you have a separate (non-Classmate) laptop being used for programming, and the Classmate used primarily as a Driver Station. We strongly recommend this setup to our Rookies. These are kind of abbreviated “Coles Notes” for anyone running a Quick Build, or who is experienced and wants to get up and running quickly. It also has some notes on the most common problems we ran in to.

Preparing the Classmate:

  • If your Classmate boots up with a working Windows installation out of the box, don’t bother reimaging it
  • There is no FRC software on the USB supplied image, so don’t expect to have a working development, tools or driver station after immediately re-imaging the Classmate - it’s basically only needed if you brick your Classmate, or it came without a working OS
  • Some Classmates came wiped with no working OS and had to be imaged
  • Some kits had image USB keys that were empty or had corrupted images - images can be downloaded here if you were one of these lucky teams with a wiped Classmate AND a bad USB:
    http://wpilib.screenstepslive.com/s/4485/m/24192/l/144974-imaging-your-classmate-veteran-rookie-image-download
  • If you need to re-image your Classmate because it came wiped, or the OS is not working, insert the USB while the computer is off, press F11 immediately after powering on, select “USB HDD”, and follow the instructions on-screen
  • Once you have a working Windows OS on the Classmate, you still need to install the FRC Tools and Driver Station (aka FRC 2015 Update Suite) which can be found here:
    http://www.ni.com/download/first-robotics-software-2015/5112/en/
  • Reboot the Classmate
  • This should be enough to get your Classmate working as a Driver Station, and will also do some basic tasks like: Image your RoboRIO and Deploy Java Runtime to the RoboRIO (if you will be programming in Java)
  • This won’t get you any actual development tools yet - if you want them read the next section and do them to the Classmate - I don’t recommend you use the Classmate for actual development, but I do recommend you install the development tools in case of an emergency - the Classmate CAN act as a programming computer too, but I highly recommend you don’t use it as your primary programming computer - Keep the Classmate as a pure Driver Station-only device as much as possible
  • At this stage you will want to run the Driver Station application, click through the tabs to familiarize yourself with the different screens
  • Set your Team Number on the settings page
  • Connect the Logitech joystick and XBox 360 controller and make sure they show up on the USB tab - verify all joysticks and buttons work by watching the indicators change

Preparing your Development Computer (Java-centric):

Preparing the Radio:

  • Power up your radio and plug an ethernet cable in from your computer to the radio
  • Be sure the ethernet network connection on the computer comes up before moving on - on Windows you should wait till the network icon in the bottom right stops spinning the blue circle
  • Disable your wireless network adapter so it doesn’t interfere
  • Run the Bridge Configuration Utility here:
    C:\Program Files (x86)\National Instruments\LabVIEW 2014\project\Bridge Configuration Utility\FRC Bridge Configuration Utility.exe
  • Enter your team # and put in a WPA2 key at least 8 characters in length
  • Once complete, unplug the ethernet cable, power cycle the radio and verify that the radio is broadcasting a new SSID named after the team #
  • If you have issues connecting to the radio in the configuration utility, try changing your computer’s IP to 192.168.0.100 subnet 255.255.255.0 and try again
  • If that fails, try changing your computer’s IP to 10.xx.yy.100 subnet 255.0.0.0 where xx and yy are the digits of your team number xxyy and try again
  • Re-enable the wireless network adapter on your computer and disconnect the ethernet cable
  • Connect to the new team # wireless network, and verify your WPA2 key is correct, and you can join the network
  • Change your computer’s IP to 10.xx.yy.100 and ping the radio at 10.xx.yy.1 to ensure everything is working

Preparing the RoboRIO:

  • Disable your wireless network so it doesn’t interfere
  • Connect an ethernet cable directly from the RoboRIO to your computer
  • Change your computer’s IP back to automatic (DHCP) it should get a 169.254.?.? address after some time
  • Run the RoboRIO Imaging Tool here:
    C:\Program Files (x86)\National Instruments\LabVIEW 2014\project\roboRIO Tool\roboRIO_ImagingTool.exe
  • Scan to try and detect the RoboRIO
  • If it can’t find it, try connecting both the RoboRIO and the computer to the radio using an ethernet cable for each (do not use wireless!)
  • If you still can’t find it, try changing the computer’s IP address to 10.xx.yy.100 subnet 255.0.0.0 and try the above steps again
  • If you still can’t find it, try a different computer - like the Classmate and repeat the steps above from the beginning - we had a few finicky non-Classmates have difficulty finding the RoboRIO
  • Once the RoboRIO is found, enter the team number, click format, select the only image file in the box below and start reimaging
  • The process takes some time about 5-10 minutes, I would estimate
  • If it finishes almost instantaneously, you forgot to click “format” and select an image
  • After the imaging is complete you now need to load the Java Runtime on to the RoboRIO (for those programming in Java)
  • Re-enable your wireless (so that you have internet access), but keep your computer connected to the RoboRio via an ethernet cable
  • Run the Java Runtime installer script here:
    C:\Users&lt;YourUsername>\wpilib ools\java-installer.jar - where <YourUsername> is the username you logged into your computer with
  • This script requires an internet connection to download the Java runtime the first time you run it
  • Complete the installation of Java runtime - I estimate it should take 5-10 minutes to complete - we had a few teams have their computers/RoboRIOs stall during this step when they tried to do it wirelessly
  • Power cycle the RoboRIO and radio
  • Unplug your computer’s ethernet from everything
  • Plug the RoboRIO ethernet cable into the radio
  • Connect to your team # SSID wirelessly
  • If all went well you should be able to ping the RoboRIO at 10.xx.yy.20 - note the IP change for the RoboRIO! Yes it is “.20”

Test the Classmate Driver Station

  • On the Classmate, join the team # wireless network
  • Run the Driver Station application
  • Double check that the Team Number is correctly entered in the setup tab
  • If all is working well, you should see the Communication light turn green, and Joysticks will turn green if you have any connected
  • The Robot Code light should still be red until you actually send your first program to the RoboRIO

Test your Programming Computer

  • Connect to the team# wireless network
  • Change the computer’s IP address to 10.xx.yy.100 subnet 255.0.0.0
  • Open Eclipse
  • Create a new robot project: File->New->Other, WPILib Robot Java Development->Robot Java Project->Iterative
  • Name the project whatever you wish
  • Right Click the project name in the “Project Explorer” window on the left -> Run As -> WPILib Java Deploy
  • At some point you will be asked for your team # - ensure you enter it correctly as it dictates what IP address it will look for the RoboRIO at
  • If you need to check the team #, it is in Windows -> Preferences -> WPILib Preferences
  • WPILib Java Deploy will automatically build your code, connect to the RoboRIO, send it and run it - this happens MUCH faster than the old control system so check the console log at the bottom of the screen carefully!
  • If you still have your Driver Station running (on your Classmate or elsewhere), you should see the Robot Code light turn green if the deploy was successful

I know this is rehashing some of what the Screensteps have, but I found it a lot more convenient just having the salient steps and potential problems all in one place.

Cheers and good luck everyone!

I’m trying to install Java on the roboRIO right now and it froze on “Deploying JRE to roboRIO.” What should I do?

Are you connected directly to the RoboRIO? What kind of computer are you using? What’s the IP address of the computer?

I’m connected to the roboRIO via USB. I’m using an MSI notebook. The IP of the computer is 192.168.1.126 (if that’s the IP you’re asking for).

Try disconnecting your computer from all other networks (wired and wireless) leaving just the USB connection. You may need to restart the JRE installer, but you should be able to point it at the already downloaded file so you won’t need an internet connection to re-download.

Power cycling the roboRIO seems to have done the trick.

There should be a log folder in the installer folder, with a log file in it. Should be “C:\Users&lt;YourUsername>\wpilib ools\logs\javainstaller.log”. Could you please post that file?

I didn’t see where the roboRIO firmware was installed in your instructions. It should be installed per R45 and https://wpilib.screenstepslive.com/s/4485/m/13503/l/273817-updating-your-roborio-firmware

Also, imaging is strongly recommended over USB rather then ethernet per https://wpilib.screenstepslive.com/s/4485/m/13503/l/144984-imaging-your-roborio. This would also solve the IP address troubleshooting you went through.

Hi, trying to Upgrade Firmware on the roborio and I am finding that the NI firmware isnt on the disk. After installing NI from the 2015 disk, in program files there is no Firmware in Shared and in program (x86) there is a folder CVS, not \cRIO and CVS contains 76CE and 77AA not 76F2

I cant seem to find the firmware update anywhere. Is there maybe a link for this at NI?

Thanks!

I was using USB. For some reason the roboRIO just needed to be restarted even though I had recently restarted it already. As far as the log file goes it looks like it was just having trouble manipulating the roboRIO.

It would be helpful for me if you could post the log file, so I can see the error condition it got in and hopefully fix it so that the installer at least gives a more useful error than just freezing.

Did you install the FRC 2015 Update Suite?

Thank you very much, this is very helpful.

This appears to be the log for my second attempt, where it also froze.

04/Jan/2015 15:59:30,344- ConnectRoboRioController: Connecting to roborio-3266.local
04/Jan/2015 15:59:30,345- ConnectRoboRioController: Checking for mDNS connection to the roboRio
04/Jan/2015 15:59:33,626- ConnectRoboRioController: Found mDNS connection
04/Jan/2015 15:59:33,626- ConnectRoboRioController: Connected to the roboRio at roborio-3266.local
04/Jan/2015 15:59:33,678- DeployController: Removed the old tgz file
04/Jan/2015 15:59:33,678- DeployController: Starting zip
04/Jan/2015 15:59:33,685- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE, putting tar entry is JRE
04/Jan/2015 15:59:33,686- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\bin, putting tar entry is JRE/bin
04/Jan/2015 15:59:33,687- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\bin\java, putting tar entry is JRE/bin/java
04/Jan/2015 15:59:33,689- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\bin\keytool, putting tar entry is JRE/bin/keytool
04/Jan/2015 15:59:33,690- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\bin\rmid, putting tar entry is JRE/bin/rmid
04/Jan/2015 15:59:33,691- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\bin\rmiregistry, putting tar entry is JRE/bin/rmiregistry
04/Jan/2015 15:59:33,693- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\bom, putting tar entry is JRE/bom
04/Jan/2015 15:59:33,694- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib, putting tar entry is JRE/lib
04/Jan/2015 15:59:33,695- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm, putting tar entry is JRE/lib/arm
04/Jan/2015 15:59:33,695- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\client, putting tar entry is JRE/lib/arm/client
04/Jan/2015 15:59:33,696- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\client\libjsig.so, putting tar entry is JRE/lib/arm/client/libjsig.so
04/Jan/2015 15:59:33,697- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\client\libjvm.so, putting tar entry is JRE/lib/arm/client/libjvm.so
04/Jan/2015 15:59:33,890- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\client\Xusage.txt, putting tar entry is JRE/lib/arm/client/Xusage.txt
04/Jan/2015 15:59:33,891- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\jli, putting tar entry is JRE/lib/arm/jli
04/Jan/2015 15:59:33,891- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\jli\libjli.so, putting tar entry is JRE/lib/arm/jli/libjli.so
04/Jan/2015 15:59:33,894- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\jvm.cfg, putting tar entry is JRE/lib/arm/jvm.cfg
04/Jan/2015 15:59:33,895- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libdt_socket.so, putting tar entry is JRE/lib/arm/libdt_socket.so
04/Jan/2015 15:59:33,895- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libhprof.so, putting tar entry is JRE/lib/arm/libhprof.so
04/Jan/2015 15:59:33,900- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libjava.so, putting tar entry is JRE/lib/arm/libjava.so
04/Jan/2015 15:59:33,906- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libjava_crw_demo.so, putting tar entry is JRE/lib/arm/libjava_crw_demo.so
04/Jan/2015 15:59:33,907- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libjdwp.so, putting tar entry is JRE/lib/arm/libjdwp.so
04/Jan/2015 15:59:33,915- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libjsig.so, putting tar entry is JRE/lib/arm/libjsig.so
04/Jan/2015 15:59:33,915- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libnet.so, putting tar entry is JRE/lib/arm/libnet.so
04/Jan/2015 15:59:33,918- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libnio.so, putting tar entry is JRE/lib/arm/libnio.so
04/Jan/2015 15:59:33,920- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libnpt.so, putting tar entry is JRE/lib/arm/libnpt.so
04/Jan/2015 15:59:33,921- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libverify.so, putting tar entry is JRE/lib/arm/libverify.so
04/Jan/2015 15:59:33,923- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\arm\libzip.so, putting tar entry is JRE/lib/arm/libzip.so
04/Jan/2015 15:59:33,927- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\calendars.properties, putting tar entry is JRE/lib/calendars.properties
04/Jan/2015 15:59:33,927- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\classlist, putting tar entry is JRE/lib/classlist
04/Jan/2015 15:59:33,930- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\content-types.properties, putting tar entry is JRE/lib/content-types.properties
04/Jan/2015 15:59:33,930- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\currency.data, putting tar entry is JRE/lib/currency.data
04/Jan/2015 15:59:33,931- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\ext, putting tar entry is JRE/lib/ext
04/Jan/2015 15:59:33,931- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\ext\meta-index, putting tar entry is JRE/lib/ext/meta-index
04/Jan/2015 15:59:33,931- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\ext\sunjce_provider.jar, putting tar entry is JRE/lib/ext/sunjce_provider.jar
04/Jan/2015 15:59:33,941- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\hijrah-config-umalqura.properties, putting tar entry is JRE/lib/hijrah-config-umalqura.properties
04/Jan/2015 15:59:33,942- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\jce.jar, putting tar entry is JRE/lib/jce.jar
04/Jan/2015 15:59:33,945- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\jsse.jar, putting tar entry is JRE/lib/jsse.jar
04/Jan/2015 15:59:33,956- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\jvm.hprof.txt, putting tar entry is JRE/lib/jvm.hprof.txt
04/Jan/2015 15:59:33,957- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\logging.properties, putting tar entry is JRE/lib/logging.properties
04/Jan/2015 15:59:33,957- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\meta-index, putting tar entry is JRE/lib/meta-index
04/Jan/2015 15:59:33,957- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib
et.properties, putting tar entry is JRE/lib/net.properties
04/Jan/2015 15:59:33,958- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\resources.jar, putting tar entry is JRE/lib/resources.jar
04/Jan/2015 15:59:33,974- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\rt.jar, putting tar entry is JRE/lib/rt.jar
04/Jan/2015 15:59:34,399- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\security, putting tar entry is JRE/lib/security
04/Jan/2015 15:59:34,399- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\security\blacklist, putting tar entry is JRE/lib/security/blacklist
04/Jan/2015 15:59:34,399- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\security\cacerts, putting tar entry is JRE/lib/security/cacerts
04/Jan/2015 15:59:34,402- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\security\java.policy, putting tar entry is JRE/lib/security/java.policy
04/Jan/2015 15:59:34,402- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\security\java.security, putting tar entry is JRE/lib/security/java.security
04/Jan/2015 15:59:34,403- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\security\local_policy.jar, putting tar entry is JRE/lib/security/local_policy.jar
04/Jan/2015 15:59:34,404- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\security	rusted.libraries, putting tar entry is JRE/lib/security/trusted.libraries
04/Jan/2015 15:59:34,404- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib\security\US_export_policy.jar, putting tar entry is JRE/lib/security/US_export_policy.jar
04/Jan/2015 15:59:34,404- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\lib	zdb.dat, putting tar entry is JRE/lib/tzdb.dat
04/Jan/2015 15:59:34,408- DeployController: Processing file C:\Users\Spencer\wpilib	ools\JRE\release, putting tar entry is JRE/release
04/Jan/2015 15:59:35,048- DeployController: Size command is C0644 15273720 JRE.tar.gz

04/Jan/2015 15:59:35,094- DeployController: Return code is 0
04/Jan/2015 15:59:37,043- DeployController: Return code is 0
04/Jan/2015 15:59:37,047- DeployController: Attempting to remove old JRE
04/Jan/2015 15:59:37,049- DeployController: Running command rm -r /usr/local/frc/JRE
04/Jan/2015 15:59:37,170- DeployController: Error with command rm -r /usr/local/frc/JRE
04/Jan/2015 15:59:37,170- DeployController: No JRE folder removed
04/Jan/2015 15:59:37,170- DeployController: Extracting the JRE
04/Jan/2015 15:59:37,171- DeployController: Running command tar -xzf /home/admin/JRE.tar.gz -C /home/admin/
04/Jan/2015 15:59:38,378- DeployController: Error with command tar -xzf /home/admin/JRE.tar.gz -C /home/admin/
04/Jan/2015 15:59:38,378- DeployController: Failure to send JRE to the roboRio
java.io.IOException: Error when extracting the tar gz: exit code 2
	at edu.wpi.first.wpilib.javainstaller.Controllers.DeployController.executeCommand(DeployController.java:289) ~[java-installer.jar:?]
	at edu.wpi.first.wpilib.javainstaller.Controllers.DeployController.setupJRE(DeployController.java:205) ~[java-installer.jar:?]
	at edu.wpi.first.wpilib.javainstaller.Controllers.DeployController.lambda$initialize$10(DeployController.java:87) [java-installer.jar:?]
	at edu.wpi.first.wpilib.javainstaller.Controllers.DeployController$$Lambda$160/150205267.run(Unknown Source) [java-installer.jar:?]
	at java.lang.Thread.run(Unknown Source) ?:1.8.0_25]
04/Jan/2015 16:04:17,039- MainApp: Exiting installer from popup

I have been trying to install java on the roboRIO, but I am unable to locate the installer. I have tried finding it on 3 computers, all of which are fully updated with the 2015 suite. I cannot ind the wpilib folder in the home directory. Any help is greatly apprecated.

:eek:

Are you sure that you’ve installed the eclipse plugins? Make sure that you open eclipse after installing the plugins, that’s what creates the wpilib folder. See these instructions. http://wpilib.screenstepslive.com/s/4485/m/13809/l/145002-installing-eclipse-c-java

This appears to be the log for my second attempt, where it also froze.

As for this error, I’ve never seen that error before. The fact that tar gave an error 2 likely means that the JRE tar was copied unsuccessfully to the roboRio and the .tar.gz was corrupted in some way. I’ll see if I can reproduce the issue.

I"m having trouble installing java on the roborio. I freeze at downloading jre to roborio.
I am connected via USB
I have updated firmware using same connection
Windows 8
Here is the latest logs:
11/Jan/2015 11:30:06,841- CreateJreController: Staring JRE Creation
11/Jan/2015 11:30:06,841- CreateJreController: Creator location: C:\Users\Team 4277\wpilib ools\ejdk1.8.0_06\lib\JRECreate.jar
11/Jan/2015 11:30:06,841- CreateJreController: Command: [java, -jar, C:\Users\Team 4277\wpilib ools\ejdk1.8.0_06\lib\JRECreate.jar, --dest, JRE, --profile, compact2, --vm, client, --keep-debug-info, --debug]
11/Jan/2015 11:30:15,179- CreateJreController: Successfully Created JRE!
11/Jan/2015 11:30:24,987- ConnectRoboRioController: Connecting to roborio-4277.local
11/Jan/2015 11:30:24,990- ConnectRoboRioController: Checking for mDNS connection to the roboRio
11/Jan/2015 11:30:28,435- ConnectRoboRioController: Found mDNS connection
11/Jan/2015 11:30:28,436- ConnectRoboRioController: Connected to the roboRio at roborio-4277.local
11/Jan/2015 11:30:28,672- DeployController: Removed the old tgz file
11/Jan/2015 11:30:28,673- DeployController: Starting zip
11/Jan/2015 11:30:28,700- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE, putting tar entry is JRE
11/Jan/2015 11:30:28,702- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\bin, putting tar entry is JRE/bin
11/Jan/2015 11:30:28,703- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\bin\java, putting tar entry is JRE/bin/java
11/Jan/2015 11:30:28,706- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\bin\keytool, putting tar entry is JRE/bin/keytool
11/Jan/2015 11:30:28,708- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\bin\rmid, putting tar entry is JRE/bin/rmid
11/Jan/2015 11:30:28,715- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\bin\rmiregistry, putting tar entry is JRE/bin/rmiregistry
11/Jan/2015 11:30:28,717- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\bom, putting tar entry is JRE/bom
11/Jan/2015 11:30:28,720- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib, putting tar entry is JRE/lib
11/Jan/2015 11:30:28,722- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm, putting tar entry is JRE/lib/arm
11/Jan/2015 11:30:28,723- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\client, putting tar entry is JRE/lib/arm/client
11/Jan/2015 11:30:28,725- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\client\libjsig.so, putting tar entry is JRE/lib/arm/client/libjsig.so
11/Jan/2015 11:30:28,728- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\client\libjvm.so, putting tar entry is JRE/lib/arm/client/libjvm.so
11/Jan/2015 11:30:29,292- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\client\Xusage.txt, putting tar entry is JRE/lib/arm/client/Xusage.txt
11/Jan/2015 11:30:29,293- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\jli, putting tar entry is JRE/lib/arm/jli
11/Jan/2015 11:30:29,297- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\jli\libjli.so, putting tar entry is JRE/lib/arm/jli/libjli.so
11/Jan/2015 11:30:29,307- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\jvm.cfg, putting tar entry is JRE/lib/arm/jvm.cfg
11/Jan/2015 11:30:29,309- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libdt_socket.so, putting tar entry is JRE/lib/arm/libdt_socket.so
11/Jan/2015 11:30:29,313- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libhprof.so, putting tar entry is JRE/lib/arm/libhprof.so
11/Jan/2015 11:30:29,330- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libjava.so, putting tar entry is JRE/lib/arm/libjava.so
11/Jan/2015 11:30:29,348- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libjava_crw_demo.so, putting tar entry is JRE/lib/arm/libjava_crw_demo.so
11/Jan/2015 11:30:29,354- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libjdwp.so, putting tar entry is JRE/lib/arm/libjdwp.so
11/Jan/2015 11:30:29,392- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libjsig.so, putting tar entry is JRE/lib/arm/libjsig.so
11/Jan/2015 11:30:29,396- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libnet.so, putting tar entry is JRE/lib/arm/libnet.so
11/Jan/2015 11:30:29,406- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libnio.so, putting tar entry is JRE/lib/arm/libnio.so
11/Jan/2015 11:30:29,415- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libnpt.so, putting tar entry is JRE/lib/arm/libnpt.so
11/Jan/2015 11:30:29,418- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libverify.so, putting tar entry is JRE/lib/arm/libverify.so
11/Jan/2015 11:30:29,423- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\arm\libzip.so, putting tar entry is JRE/lib/arm/libzip.so
11/Jan/2015 11:30:29,435- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\calendars.properties, putting tar entry is JRE/lib/calendars.properties
11/Jan/2015 11:30:29,436- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\classlist, putting tar entry is JRE/lib/classlist
11/Jan/2015 11:30:29,447- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\content-types.properties, putting tar entry is JRE/lib/content-types.properties
11/Jan/2015 11:30:29,449- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\currency.data, putting tar entry is JRE/lib/currency.data
11/Jan/2015 11:30:29,451- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\ext, putting tar entry is JRE/lib/ext
11/Jan/2015 11:30:29,452- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\ext\meta-index, putting tar entry is JRE/lib/ext/meta-index
11/Jan/2015 11:30:29,454- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\ext\sunjce_provider.jar, putting tar entry is JRE/lib/ext/sunjce_provider.jar
11/Jan/2015 11:30:29,485- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\hijrah-config-umalqura.properties, putting tar entry is JRE/lib/hijrah-config-umalqura.properties
11/Jan/2015 11:30:29,487- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\jce.jar, putting tar entry is JRE/lib/jce.jar
11/Jan/2015 11:30:29,501- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\jsse.jar, putting tar entry is JRE/lib/jsse.jar
11/Jan/2015 11:30:29,535- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\jvm.hprof.txt, putting tar entry is JRE/lib/jvm.hprof.txt
11/Jan/2015 11:30:29,537- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\logging.properties, putting tar entry is JRE/lib/logging.properties
11/Jan/2015 11:30:29,538- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\meta-index, putting tar entry is JRE/lib/meta-index
11/Jan/2015 11:30:29,540- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib
et.properties, putting tar entry is JRE/lib/net.properties
11/Jan/2015 11:30:29,542- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\resources.jar, putting tar entry is JRE/lib/resources.jar
11/Jan/2015 11:30:29,597- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\rt.jar, putting tar entry is JRE/lib/rt.jar
11/Jan/2015 11:30:31,158- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\security, putting tar entry is JRE/lib/security
11/Jan/2015 11:30:31,163- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\security\blacklist, putting tar entry is JRE/lib/security/blacklist
11/Jan/2015 11:30:31,165- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\security\cacerts, putting tar entry is JRE/lib/security/cacerts
11/Jan/2015 11:30:31,175- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\security\java.policy, putting tar entry is JRE/lib/security/java.policy
11/Jan/2015 11:30:31,179- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\security\java.security, putting tar entry is JRE/lib/security/java.security
11/Jan/2015 11:30:31,183- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\security\local_policy.jar, putting tar entry is JRE/lib/security/local_policy.jar
11/Jan/2015 11:30:31,185- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\security rusted.libraries, putting tar entry is JRE/lib/security/trusted.libraries
11/Jan/2015 11:30:31,186- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib\security\US_export_policy.jar, putting tar entry is JRE/lib/security/US_export_policy.jar
11/Jan/2015 11:30:31,188- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\lib zdb.dat, putting tar entry is JRE/lib/tzdb.dat
11/Jan/2015 11:30:31,202- DeployController: Processing file C:\Users\Team 4277\wpilib ools\JRE\release, putting tar entry is JRE/release
11/Jan/2015 11:30:32,283- DeployController: Failure to send JRE to the roboRio
com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused: connect
at com.jcraft.jsch.Util.createSocket(Util.java:349) ~[java-installer.jar:?]
at com.jcraft.jsch.Session.connect(Session.java:215) ~[java-installer.jar:?]
at com.jcraft.jsch.Session.connect(Session.java:183) ~[java-installer.jar:?]
at edu.wpi.first.wpilib.javainstaller.Controllers.DeployController.lambda$initialize$10(DeployController.java:85) [java-installer.jar:?]
at edu.wpi.first.wpilib.javainstaller.Controllers.DeployController$$Lambda$160/1605457580.run(Unknown Source) [java-installer.jar:?]
at java.lang.Thread.run(Unknown Source) ?:1.8.0_25]
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method) ~?:1.8.0_25]
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) ~?:1.8.0_25]
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~?:1.8.0_25]
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) ~?:1.8.0_25]
at java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~?:1.8.0_25]
at java.net.PlainSocketImpl.connect(Unknown Source) ~?:1.8.0_25]
at java.net.SocksSocketImpl.connect(Unknown Source) ~?:1.8.0_25]
at java.net.Socket.connect(Unknown Source) ~?:1.8.0_25]
at java.net.Socket.connect(Unknown Source) ~?:1.8.0_25]
at java.net.Socket.<init>(Unknown Source) ~?:1.8.0_25]
at java.net.Socket.<init>(Unknown Source) ~?:1.8.0_25]
at com.jcraft.jsch.Util.createSocket(Util.java:343) ~[java-installer.jar:?]
… 5 more

Any help would be greatly appreciated.

I couldn’t find the installer at first. It turns out that the National Instruments stuff in in both the Programs Files and the Program Files (x86). The java installer is in the Program Files (x86)

You said you updated the firmware, but does that include imaging roboRIO with the imaging tool? The connection refused error you’re getting should only occur when the roboRIO doesn’t have the v23 image on it.

I did both the firmware and then image v23.zip
I have tried both usb and ethernet connection also