Error 44007, not sure how to check refnum

Does anyone have a link or tutorial on how to do this?

We have tried using a blank FRC robot project, we still get this error. We have reimaged the roborio and reinstalled labview.

I have searched for how to check the refnum (like most posts referencing this issue have suggested) and have been unsuccessful in finding clear directions. We are a second year team and the person who did the programming is not participating this year, so we have very limited programming skills. Any help is appreciated.

That error means you have mis-typed the name of one of your devices that was Open’ed in Begin.vi, or have renamed a default name, but missed renaming it everywhere it is being used.

The names have to be exact everywhere they are used (e.g., Teleop or Autonomous)- no extra spaces, exact same capitalization, no misspellings.

One way to be sure they are the same is to copy the ones in Begin and paste them everywhere else they are used (no retyping and possible errors).

None of the names have been touched, it’s a completely new FRC robot project. I tried copying and pasting, just in case, and I’m still getting the same error.

The error specifically says in periodic tasks.vi and in teleop.vi. In periodic tasks, there are only the joystick and motor refnums and they are exactly what they are supposed to be.

I’m at a loss.

You could post a zip of the project and we could see if we get the same error running it.
The error origin can be tracked down through a Debug session.

I don’t get a Refnum error running a default project here, so there’s something that’s different.

Try deleting the code in periodic tasks, autonomous, and teleop and see if you can deploy.

I thought that the error codes would generally have the name that was being looked for. Then you could search for it and for Opens of I/O of the expected type and determine what was either deleted or misspelled.
Greg McKaskle

Thanks for the replies. We are still getting the error, but the robot is moving now, so we’ll worry about it another day. We ended up having to change the usb assignment for the joystick for it to run.