View Single Post
  #11   Spotlight this post!  
Unread 14-01-2016, 21:00
Happy Birthday! rod@3711 rod@3711 is offline
Registered User
AKA: rod nelson
FRC #3711 (Iron Mustangs)
Team Role: Mentor
 
Join Date: May 2014
Rookie Year: 2014
Location: Trout Lake, WA
Posts: 64
rod@3711 is an unknown quantity at this point
Re: No robot code on roboRIO

Quote:
Originally Posted by m1tche11d View Post
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\bu ild.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.
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.
Reply With Quote