Problem with Disabled.vi

[thelegend]

Hi,
When I run the driver station to test out some code that I have written, I get the following error repeated multiple times in the Diagnostics section.

ERROR <Code> -44007 occurred at Disabled.vi>>Robot Main.vi
<time>00:09:21 01/01/1970
FRC: The RefNum you are trying to Get does not exist in this RefNum Registry.

I have taken a look in the Disabled.vi and there isn't much in there, so I don't know where to start. Here is a screen shot of my disabled.vi.

[Greg McKaskle]

I don't see an attached image. I believe the default Disabled doesn't retrieve any refnums, so it would definitely be useful to see what your code looks like.

Greg McKaskle

[thelegend]

Thanks for your reply Greg... Here is the rest of our code

Main:


Begin:


Teleop:

[Mark McLeod]

Sorry, your Begin picture is old, and your Teleop picture is of a more recent Begin.

Robot Main is protesting that Teleop's inputs have been changed and are no longer valid.

[Alan Anderson]

Whatever code is running on the cRIO, it's not what you posted in the pictures, because what you posted cannot run. I suspect you still have an old default Disabled.vi which tries to set "Left and Right Motors" to zero, but since you renamed the drive motors that's an invalid reference name.

You apparently deleted some minor things from Teleop.vi that look unimportant but are actually part of the framework. Robot Main won't run that way (note the grey broken "run" arrow in the toolbar).

[team3039]

I've had this problem before. It indicates that you created a project without the simulator but you're trying to run it on the computer. Right click on the little white window in the bottom left corner and choose RT CompactRio Target to deploy it to the cRio.

[Mark McLeod]

The loop inside Teleop is not good.
It will never end, because the value of controller Button 2 is only checked once when the loop begins, then is never checked again.

In general, Teleop should execute and leave as soon as possible. No loops waiting for other things to happen.
That's because Teleop is expected to process a command packet sent from the Driver Station every 20ms.

Your code will do what you want if you leave everything, but remove just the loop from around your code.
Teleop is actually inside a loop itself, so your code will get called over and over.

[Greg McKaskle]

As mentioned, the RobotMain VI is broken -- has a broken arrow. The one issue visible is because two parameters are connected, but the TeleOp function has been changed to no longer take the parameters. You can either put them back or you can delete the dashed wires on RobotMain.

Greg McKaskle