Build Error: Image of roboRIO does not match plugin

Technical Java
1

I am trying to deploy some Java code to the roboRIO, but I am getting this error. Here is the console log, starting with the “dependencies” section. Everything before this is perfectly normal.

dependencies:
[hostinfo] Error retrieving remote host information for host:roboRIO-6705-FRC.lan.

BUILD FAILED
C:UsersWildCat5ewpilibjavacurrentantbuild.xml:330: Assertion failed boolean test.
Image of roboRIO does not match plugin.
Allowed image year: 2017 version: 8.
Actual image year: ImageRegExFail version ImageRegExFail.
RoboRIO needs to be re-imaged or plugins updated.

I have checked the roboRIO’s hardware configuration page (at its IP address), and the roboRIO’s current image is “FRC_roboRIO_2017_v8” which appears to be correct.

I have also checked for updates to the plugins in Eclipse multiple times, but they are up to date as of 1/26/17 (version 2017.2.1).

I have no idea what could be wrong. I have tried re-imaging the roboRIO, re-downloading Java to the roboRIO, delteing the WPILib directory, and restarting Eclipse. I don’t know what to try next.

Thanks for your help.

2

Please attach your sysprops.xml file.

3

Can you ping the roboRIO at roboRIO-6705-FRC.local using the cmd or terminal window?

Also, what OS are you running on your laptop.

And are you connecting with an ethernet cable, wifi, or USB? If not USB, can you also try that?

4

I will try to ping the robot tomorrow when I can access the computer we are using. That computer is running Windows 10.

I am connecting via a USB cable (USB-A to USB-B).

Where would I find the sysprops.xml file? In the WPIlib folder?

Thanks for the help.

5

Yes, we had the same problem but the resolution was to image it with a USB cable. The first time we used ethernet which seems to be the cause of our issue.

6

It would have been in the root of the eclipse project folder. However, I just realized that with the 2017.2.1 release, it is no longer used.

7

I pinged the roboRIO and got this response:

Pinging roboRIO-6705-FRC.local [fe80::280:2fff:fe25:7393%4] with 32 bytes of data:
Reply from fe80::280:2fff:fe25:7393%4: time=14ms
Reply from fe80::280:2fff:fe25:7393%4: time=1ms
Reply from fe80::280:2fff:fe25:7393%4: time<1ms
Reply from fe80::280:2fff:fe25:7393%4: time<1ms

Ping statistics for fe80::280:2fff:fe25:7393%4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 14ms, Average = 3ms

8

Ok. Then what should I try next?

9

Thread 5 from this thread suggest that ethernet-vs-USB can make a difference, or else that just re-re-image itself might be worth the time.

One other thing I’ve just noticed is that your ping-response, eg …from fe80::280:2fff:fe25:7393%4: time=14ms… is an IPv6 address, in general you should change your network(adapter) properties to be IPv4 and NOT IPv6.

10

We have tried re-imaging the roboRIO probably 10 times, and re-downloading the JRE a few times. What I’m trying now it to delete the entire 2017 FRC update suite and re download it. I will look into using Ethernet instead of USB and changing the network adapter properties.

Thanks

11

I have had exactly the same problem (we always use the USB cable to do the imagine and the Java download). The funny thing it was working fine, I left the driver station with the build team for a night, and when I got back the next day it was broken. I have reimaged and reinstalled Java several times, deleted and reinstalled the WPILib plugin for Eclipse, and can’t get it to go away (even using a different laptop that had also been working at the start). We finally commented out the check in the build file (there was a thread here from last year I think), as I know that I am running the 2017 version. If you figure it out, please make sure to post the answer :slight_smile: None of the laptops have been connected to a 2016 RoboRIO at this point, so it’s hard to see how something could have gotten munged in the settings anywhere.

12

WHere do I comment out the check in the build file? In the project’s build.xml, I don’t see any “check.” Can you help me find it?

13

The path of the file (replacing {user} with your username) is: C:\Users{user}\wpilib\java\current\ant

The file is build.xml

The comment out part is an assert at about 278 - just use XML comments to comment out the whole thing like below.

We really shouldn’t have to be doing this, and if you re-install the WPILib stuff at any point it will wipe this out, but it will get you past the immediate blockage (as long as you are sure you have the right version on the RIO which can be verified by the NI dashboard webpage - Image Version should be FRC_roboRIO_2017_v8).

<!-- <assert message=“Image of roboRIO does not match plugin. ${line.separator}Allowed image year: ${roboRIOAllowedYear} version: ${roboRIOAllowedImages}. ${line.separator}Actual image year: ${roboRIOImageYear} version ${roboRIOImage}. ${line.separator}RoboRIO needs to be re-imaged or plugins updated.”>
<bool>
<and>
<contains string="${roboRIOAllowedImages}" substring="${roboRIOImage}"/>
<contains string="${roboRIOAllowedYear}" substring="${roboRIOImageYear}"/>
</and>
</bool>
</assert>
<echo>roboRIO image version validated</echo> -->

14

Thanks. I will be sure to try that and see if it works.