Code not showinig on RoboRio

Technical
1

When I deploy, everything builds and deploys totally fine as shown in the logs below, but when I open the driver station, it says that there is no robot code.

Executing task: gradlew deploy -PteamNumber=5000 --offline -Dorg.gradle.java.home=“C:\Users\Public\wpilib\2022\jdk” <

Starting a Gradle Daemon, 4 incompatible and 1 stopped Daemons could not be reused, use --status for details
Driver Station reported IP: 10.50.0.2

Task :discoverroborio
Discovering Target roborio
Using [email protected]:22 for target roborio

Task :deployprogramKillroborioroborio
-C-> sed -i -e ‘s/“exec /”/’ /usr/local/frc/bin/frcRunRobot.sh @ /home/lvuser
-[-1]
-C-> . /etc/profile.d/natinst-path.sh; /usr/local/frc/bin/frcKillRobot.sh -t 2> /dev/null @ /home/lvuser
-C-> sed -i -e ‘s/^StartupDLLs/;StartupDLLs/’ /etc/natinst/share/ni-rt.ini @ /home/lvuser
-[-1]

Task :deployrobotCommandfrcJavaroborio
-C-> echo '/usr/local/frc/JRE/bin/java -XX:+UseConcMarkSweepGC -XX:+AlwaysPreTouch -Djava.lang.invoke.stringConcat=BC_SB -Djava.library.path=/usr/local/frc/third-party/lib -jar “/home/lvuser/PneumaticsTestAgain.jar” ’ > /home/lvuser/robotCommand @ /home/lvuser
-[-1]
-C-> chmod +x /home/lvuser/robotCommand; chown lvuser /home/lvuser/robotCommand @ /home/lvuser

Task :deployfrcStaticFileDeployroborio
-C-> mkdir -p @ /home/lvuser/deploy
-[-1]
1 file(s) are up-to-date and were not deployed

Task :deployjrefrcJavaroborio
-C-> if [[ -f “/usr/local/frc/JRE/bin/java” ]]; then echo OK; else echo MISSING; fi @ /tmp
-[-1]-> OK

-C-> opkg list-installed | grep openjdk @ /tmp
  -[0]-> frc2021-openjdk-11-jre - 11.0.9u11-1 - FRC OpenJDK Java Runtime Environment

Searching for JRE 11.0.9u11-1
Found JRE frc2021-openjdk-11-jre - 11.0.9u11-1 - FRC OpenJDK Java Runtime Environment
JRE Is Correct Version
Artifact skipped

Task :deployfrcJavaroborio
1 file(s) are up-to-date and were not deployed
-C-> chmod +x “/home/lvuser/PneumaticsTestAgain.jar”; chown lvuser “/home/lvuser/PneumaticsTestAgain.jar” @ /home/lvuser

Task :deploynativeZipsfrcJavaroborio
25 file(s) are up-to-date and were not deployed
-C-> chmod -R 777 “/usr/local/frc/third-party/lib” || true; chown -R lvuser:ni “/usr/local/frc/third-party/lib” @ /usr/local/frc/third-party/li
-C-> ldconfig @ /usr/local/frc/third-party/lib
-[-1]

Task :deployprogramStartfrcJavaroborio
-C-> sync @ /home/lvuser
-[-1]
-C-> . /etc/profile.d/natinst-path.sh; /usr/local/frc/bin/frcKillRobot.sh -t -r 2> /dev/null @ /home/lvuser

BUILD SUCCESSFUL in 19s
13 actionable tasks: 11 executed, 2 up-to-date

Terminal will be reused by tasks, press any key to close it.

2

It appears that the deploy succeeded. Try re-imaging the Rio.

3

There’s a few different potential causes for this:

  • Are you seeing anything in the DS console log (hit the gear icon to view the full console window)? Your code may be crashing at startup
  • In rare instances in 2022, the filesystem can get corrupted in such a way that the code won’t actually get started. This is typically caused by powering off the Rio during a deploy. Reimaging will fix this case.
4

Did you set your team number on driver station? I had the same issue when I used a computer with everything newly installed.

5

Can you post a picture of your Driver Station Diagnostics Tab? Also check out what the roboRIO web dashboard says. For example, you can double-check the team number on the roboRIO.

If the roboRIO has the wrong team number, use the roboRIO Imaging Tool to fix it. Don’t reformat, just use “Edit Startup Settings”. (You’ll encounter this problem if your roboRIO is new, or if you’ve entered two robots at an off-season competition.)

6

Since the code deployed, then 999 times out of a 1000 this happened. Bad code didn’t successfully execute and complete robotInit()

Null Pointer exception is the most popular error my team sees but there are plenty of other ways to go wrong. The console or riolog will show OP’s exact error and line number.

1 Like
7

Thanks for these suggestions!

Currently we are meeting on Tuesdays; will try them out them!

8

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.