DriverStation Error -44006

[Greg McKaskle]

Cleaning the cRIO and installing gaskets is a fine idea, but if there is a short, you'll get a blown fuse or worse. You will not simply receive an error about the Cypress I/O trying to read enhanced I/O, but not having enhanced I/O enabled.

Greg McKaskle

[Ziaholic]

I'm having this exact error, many times a second, and I'm not even using the Cypress board.

How do we eliminate any/all references to the Cypress if we don't need them? I'm guessing that this error spamming might be related to some of the system watchdog errors we're getting.

[Ziaholic]

I got some advice yesterday from Doug Norman (from NI) who was in high-demand this weekend at the Arizona Regionals. Mucho Mucho Kudo's to him and his first-hand knowledge of the inner workings of the cRIO.

From what I learned from him, this error is unavoidable at the moment. but you can lessen the impact of it by turning off the internal cRIO error logging.

Here's how you do it:

1) With your project window selected, hit Ctrl-F (find)
2) in the search window type "error" and press Find (or hit Enter)
3) for my results, the 5th one from the top is ErrorsGlobal.vi ... select it and hit "Go To"
4) open up your Begin.VI block diagram and drag-drop the ErrorsGlobal.VI into it ... it appears as a global variable [log errors to file?]
5) wire up a constant to the input and set it to false

Keep in mind that now that "view error messages" button on the DriverStation will no longer result in anything anymore ... that is, until you alter that boolean constant in your Begin.VI.

I still had a few occasional system watchdogs after doing this, but not as many. It's not a perfect fix. The error is still ocurring, it just doesn't "hurt" as much. ... and it's as good as they've got for now.

[Alyssa Reiman]

We were trying what you said, since we had that error too. But we couldn't find errorGlobal.Vi, but we couldn't find it in our code. Any suggestions?

[Danny Diaz]

Originally Posted by Greg McKaskle

You will not simply receive an error about the Cypress I/O trying to read enhanced I/O, but not having enhanced I/O enabled.

Gahhh! This plagued us for the last two weeks - I was about to throw the entire control system under a bus until I got curious and said, "What's the difference between 'Compatibility I/O' and 'Enhanced I/O' and when I started using the compatibility I/O we started reading the information correctly. Next version, any way to get an error from the Enhanced I/O error terminal if you've got the stinking Driver Station set up in Compatibility I/O mode?

-Danny

[Greg McKaskle]

I'm not set up to test very well, but the VIs for Get Digital do seem to return an error if they haven't received any enhanced data. It may need more details to reproduce the issue.

Greg McKaskle

[Acarid]

We are getting this as well.

After implementing Mark's solution the robot will now run, but occasionally we do still see the error in the logs.