So after 3 days of issues regarding deploying our build code to the roboRio, I’m getting kind of frustrated with the repeated build errors we were receiving.
Originally, we started getting a permission error regarding deploying code to the roboRio that was shown like this in eclipse:
We’ve assumed this was regarding a permission error & tried editing the roboRio through its web address page, putting a pass on admin.
Buildfile: C:\Users\Robotics Team 4012\workspace\Tank\Tank\build.xml
Trying to override old definition of task classloader
[echo] Trying Target: roboRIO-4012-FRC.local
[echo] roboRIO found via mDNS
[echo] roboRIO image version validated
[sshexec] Connecting to roboRIO-4012-FRC.local:22
[sshexec] cmd : rm -f /home/lvuser/FRCUserProgram
[sshexec] Could not chdir to home directory /home/lvuser: Permission denied
[sshexec] rm: can’t stat ‘/home/lvuser/FRCUserProgram’: Permission denied
[sshexec] Remote command failed with exit status 1
[echo] [athena-deploy] Copying code over.
[scp] Connecting to roboRIO-4012-FRC.local:22
C:\Users\Robotics Team 4012\wpilib\cpp\current\ant\build.xml:67: com.jcraft.jsch.JSchException: Could not send ‘C:\Users\Robotics Team 4012\workspace\Tank\Tank\Debug\FRCUserProgram’ to ‘/home/lvuser’ - 3: Permission denied
After a while of receiving this same error and verifying that our eclipse was setup correctly & the robot was imaged to 2016 we changed computers.
And now we receive a new error:
C:\Users\Robotics\wpilib\cpp\current\ant\build.xml:45: Assertion failed boolean test.
roboRIO not found, please check that the roboRIO is connected, imaged and that the team number is set properly in Eclipse
At this point we are not too sure what the problem is and are considering calling National Instruments, any help?
Permission denied suggests to me that /home/lvuser is no longer readable by the lvuser user (not sure what would have changed that, but that’s what I would guess). I would suggest either ssh’ing into the RIO as admin and verifying the permissions on that folder, or simply reimaging the RIO if you want a simple solution.
As to the second issue, are you sure that your computer is connected to the RIO? Can you ping roborio-team-frc.local? The particular assertion that you’re running into there are the tests to make sure that your computer can actually talk to the RIO.
Folder permissions are just an operating system thing, you can use ls and its various flags to what permissions are set, and chmod to change them. I would suggest simply reimaging the RIO, it’s likely to be easier.
We’ve tried reimaging it several times, no luck. Perhaps you could tell us how to use ssh more effective, as I’m not expierenced with it at all. We’ve also put a pass on admin, perhaps we need to edit the build.properties?
SSH is simply a method opening a shell on a remote computer. Giving you a tutorial on how to use a Linux shell is a little beyond the scope of typing on my phone, but what is the output of a “ls -la /home” (don’t include the quotes)?
The build.properties shouldn’t need to be modified, unless you’ve changed the package of your program. It just tells the robot what class to run.
That error you quoted is simply that the computer couldn’t talk to the RIO. Deleting the wpilib folder should not have made a difference, it’s likely some other networking issue resolved itself while you were restoring that folder.
OP, will your programmer be coming in today to work, or do you still need help?
Not posting a solution but if you need to test code while a solution for this problem is found, you can upload the FRCUserProgram in your Robot’s Debug folder as admin into the /home/lvuser folder. Then if you ssh or putty into the roboRio as admin again you can manually execute the program as follows: