View Single Post
  #2   Spotlight this post!  
Unread 27-01-2012, 10:28
derekwhite's Avatar
derekwhite derekwhite is offline
Java Virtual Machine Hacker
no team (FIRST@Oracle)
Team Role: Programmer
 
Join Date: May 2009
Rookie Year: 2009
Location: Burlington, MA
Posts: 127
derekwhite is on a distinguished road
Re: Output not updated often enough error

the "Output not updated often enough error" message is a secondary problem. That message will print when your robot apps stops working for any reason.

The Key is in the stack trace:
java.lang.NullPointerException
[cRIO] at edu.wpi.first.wpilibj.templates.RobotTemplate.tele opPeriodic(RobotTemplate.java:43)

So at line 43 of RobotTemplate.java the app tried to do something with a pointer that was null. Like call a method or reference a field.

In your code the suspect pointer is "robot". Which you'd think was initialized in robotInit(), but that is actually a local variable that is hiding the field "robot". So the field is still null.

The NetBeans editor may have given you a yellow warning on that line. It can sometimes nag too much, but you should always look at the warning by hovering the mouse over the yellow triangle.
Reply With Quote