No robot code on roboRIO

Technical C/C++
1

Our team is trying to deploy an example C++ program to the roboRIO, as per the instructions in the “Getting Started With the 2016 Control System” document, and are running into an error with actually getting the code onto the roboRIO.

When we deploy code to the roboRIO, our debug log has the following output:

Buildfile: C:\Users\DriveStation\workspace\getting_started\build.xml
Trying to override old definition of task classloader
get-target-ip:
[echo] Trying Target: roboRIO-1997-FRC.local
[echo] roboRIO found via mDNS
dependencies:
[echo] roboRIO image version validated
deploy:
[sshexec] Connecting to roboRIO-1997-FRC.local:22
[sshexec] cmd : rm -f /home/lvuser/FRCUserProgram
[echo] [athena-deploy] Copying code over.
[scp] Connecting to roboRIO-1997-FRC.local:22
[scp] done.
[sshexec] Connecting to roboRIO-1997-FRC.local:22
[sshexec] cmd : killall -q netconsole-host || :
[scp] Connecting to roboRIO-1997-FRC.local:22
[scp] done.
[echo] [athena-deploy] Starting program.
[sshexec] Connecting to roboRIO-1997-FRC.local:22
[sshexec] cmd : . /etc/profile.d/natinst-path.sh; chmod a+x /home/lvuser/FRCUserProgram; /usr/local/frc/bin/frcKillRobot.sh -t -r;
[sshexec] Connecting to roboRIO-1997-FRC.local:22
[sshexec] cmd : sync
BUILD SUCCESSFUL
Total time: 10 seconds

Everything appears to be successful, however the roboRIO comm light is red (indicating no code) and the driver station still shows no robot code.

2

There’s no error in the log… the part where it says “Build Successful” means it succeeded.

3

I understand that. However, the driver station is telling us that there is no robot code on the roboRIO in spite of the successful build log. No matter how many times we reboot the roboRIO or restart the code, it still is telling us (after a successful build log) that the robot has no code on it.

4

We ran into the same error.

Are you using the simple robot template? If you are, try adding this code:

void Disabled()
{
while(IsDisabled()){}
}

and this:

void RobotInit()
{

}

it appears that these need to be overriden, or the robot will kill the process directly after you deploy it.

5

No dice, same situation. The build log did change slighty (Also, I added the colors it prints in so it would be easier to read:

Buildfile: C:\Users\DriveStation\workspace\getting_started\build.xml
Trying to override old definition of task classloader
get-target-ip:
[echo] Trying Target: roboRIO-1997-FRC.local
[echo] roboRIO found via mDNS
dependencies:
[echo] roboRIO image version validated
deploy:
[sshexec] Connecting to roboRIO-1997-FRC.local:22
[sshexec] cmd : rm -f /home/lvuser/FRCUserProgram
[echo] [athena-deploy] Copying code over.
[scp] Connecting to roboRIO-1997-FRC.local:22
[scp] done.
[sshexec] Connecting to roboRIO-1997-FRC.local:22
[sshexec] cmd : killall -q netconsole-host || :
[scp] Connecting to roboRIO-1997-FRC.local:22
[scp] done.
[echo] [athena-deploy] Starting program.
[sshexec] Connecting to roboRIO-1997-FRC.local:22
[sshexec] cmd : . /etc/profile.d/natinst-path.sh; chmod a+x /home/lvuser/FRCUserProgram; /usr/local/frc/bin/frcKillRobot.sh -t -r;
[sshexec] killall: lvrt: no process killed
[sshexec] Remote command failed with exit status 1
[sshexec] Connecting to roboRIO-1997-FRC.local:22
[sshexec] cmd : sync
BUILD SUCCESSFUL
Total time: 10 seconds

We only got this specific log once, when I redeploy the code we get the same log as in the original post.

To me, it seems that the two colored lines near the bottom are telling me that the code deploy is cancelling for some reason, but I can’t tell why it’s doing so.

6

Minor detail: the folder for our project has a small red x over it. I don’t know if this is indicative of a larger problem or not.

7

And just to verify, this roboRIO has had its firmware updated (https://wpilib.screenstepslive.com/s/4485/m/13503/l/273817-updating-your-roborio-firmware) and has been imaged (https://wpilib.screenstepslive.com/s/4485/m/13503/l/144984-imaging-your-roborio), right?

(Taking guesses–I myself am new to this control system! :smiley: )

8

This thread looks similar.

9

I am having the same issue when trying to run the example mecanum program or arcade program. The Comm Light goes green for 1/2 second then red. I connected a usb camera to roborio, then tried the Simple Vision example and it ran as expected. Do not know the issue with drive programs.

10

FYI: This helped us… We are running again. Thanks.

11

Can you try the following…
[1] Make sure a gamepad is connected and wired to slot 5 (the last spot) in the driver station. Change your source to use that slot, or just use an extra joystick/gamepad to ensure that slot is not empty. Either is fine.
[2] Then restart your project using the restart-robot-code, or redeploying.

Does that remove the crash symptom?