After rebooting RoboRIO, no robot code until restart code.

[jreneew2]

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.)

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.

[AustinSchuh]

There should be a core dump in /usr/local/frc/ (or somewhere close to there). cat /proc/sys/kernel/core_pattern to find the exact path. You should be able to scp that back to your development machine and use GDB to load the core file and figure out where it crashed.

[Jonathan L.]

Just to clarify, are you using a cRIO or a roboRIO? The subject says roboRIO but cRIO is in the error code.

I am not sure if this is related to your problem, but last year our team had a lot of trouble getting the roboRIO to stop crashing. We had a nav6 connected to the the roboRIO via the RS-232 port. Eventually we disconnected the nav6 and tried connecting, and running code again. Everything worked.

Try disconnecting the nav6 and see if your code crashes or not. If it does not crash, go to the roboRIO Webdashboard and uncheck "Enable Console Out" even though the recommended setting is checked. The option is shown in the attachment. Then try your code again with the nav6 connected.


We also noticed a bug in the nav6 (LabVIEW) code where the code would get stuck in an infinite running loop in the Begin VI if the nav6 was not connected.

[jreneew2]

We are using the roboRio. We were using the nav 6 and successfully pushing code. I think the reason is because of some linker errors to do with Opencv. I will have to do some more testing, but I've narrowed down the issue.

[ozrien]

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?

[m1tche11d]

Originally Posted by ozrien

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?

This worked for us. Can you explain why this works?

[jhersh]

Originally Posted by m1tche11d

This worked for us. Can you explain why this works?

Memory is getting corrupted by a bad parameter in the DS object in the HAL. There will hopefully be a release before long that will address the issue. Until then, the workaround should keep teams developing.

[fsilberberg]

Originally Posted by jhersh

Memory is getting corrupted by a bad parameter in the DS object in the HAL. There will hopefully be a release before long that will address the issue. Until then, the workaround should keep teams developing.

The release today should fix this problem.

[jreneew2]

Yep, the update today fixed it! Thank you!

[rod@3711]

where do I find the update?

[RufflesRidge]

Originally Posted by rod@3711

where do I find the update?

If you set up Eclipse using the online plugin install, simply connect to the internet and select Help->Check for updates. If you did the offline install, you will need to do the update manually. Here's the relevant text from ScreenSteps:

If updated plugins are released, you can either repeat this process ( you will get one additional Eclipse window telling you that the components are already installed and an upgrade will be performed instead of an install), or if online installation is an option, you can complete the online installation steps above, then get future updates using the Eclipse Automatic Updates (or the manual update check described below)