View Single Post
  #1   Spotlight this post!  
Unread 01-12-2016, 07:40 PM
jreneew2's Avatar
jreneew2 jreneew2 is offline
Alumni of Team 2053 Tigertronics
AKA: Drew Williams
FRC #2053 (TigerTronics)
Team Role: Programmer
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Vestal, NY
Posts: 189
jreneew2 has a spectacular aura aboutjreneew2 has a spectacular aura aboutjreneew2 has a spectacular aura about
After rebooting RoboRIO, no robot code until restart code.

This seems like a strange issue but,

When ever I boot up the robot and connect to it, the driver station says that that teleop is disabled for a second then crashes and says "no robot code". However, if I restart the robot code I can enable teleop with no problems and drive around.

I have updated everything to 2016 code and have a nav6 running on the roboRIO over USB using the navX library because the nav6 code is not ported yet.

Here is the console log (very minimal no obvious errors.)
Code:
Warning  44002  Ping Results:  link-GOOD,  DS radio(.4)-bad,  robot radio(.1)-bad,  cRIO(.2)-bad,  FMS-bad FRC:  Driver Station ping status has changed.  Driver Station 
Warning  44002  Ping Results:  link-GOOD,  DS radio(.4)-bad,  robot radio(.1)-bad,  cRIO(.2)-GOOD,  FMS-bad FRC:  Driver Station ping status has changed.  Driver Station 
 ➔ Launching «'/home/lvuser/FRCUserProgram'» 
Warning  44003  FRC:  No robot code is currently running.  Driver Station 
 AHRS Constructor! 
 [HAL] Starting task FRC_navX-MXP_IO... 
 Robot init! 
 [HAL] Starting task FRC_DriverStation... 
 driveBaseSub constructor! 
 NT: server: client CONNECTED: 172.22.11.1 port 57018 
 FWC Constructor!
I've never seen this happen? Any suggestions?

Thanks.
Reply With Quote