DriverStation Error -44006

[umangv620]

I updated Driver Station, LabView and the cRIO to the latest versions.
I am getting this error for some reason:
ERROR <Code> -44006 occurred at DriverStationEnhanced IO.lvlib:Access Raw Cypress outputs.vi>>DriverStation.lvlib:Start Communication.vi>>Robot Main.vi

Since we never tampered with the DriverStation Communication code, I suspect this is the default code, and other teams might be getting this too. Is there any fix for this?

[Gamer930]

We have the same error message that comes up about 12 times a second. . . .

Does your PWM Outputs work when you get that error message?!?!? Its like the entire digital sidecar isn't getting a signal even tho it is getting power and the 3 Green LEDs are on.

I contacted NI this afternoon to one of the Applications Engineers. She is contacting the NI Research and Development Engineers and determine what fixes were made that could cause that error message to form.

Please post if you figure out a fix and I will do the same if I hear from NI or find a fix

[umangv620]

Originally Posted by Gamer930

We have the same error message that comes up about 12 times a second. . . .

Does your PWM Outputs work when you get that error message?!?!? Its like the entire digital sidecar isn't getting a signal even tho it is getting power and the 3 Green LEDs are on.

I contacted NI this afternoon to one of the Applications Engineers. She is contacting the NI Research and Development Engineers and determine what fixes were made that could cause that error message to form.

Please post if you figure out a fix and I will do the same if I hear from NI or find a fix

We are getting a signal to the digital sidecar, because I remember moving our camera servo up and down, which is connected to PWM 5 on the digital sidecar.

[Joe Ross]

Are you using the cypress I/O module in enhanced mode?

[umangv620]

Originally Posted by Joe Ross

Are you using the cypress I/O module in enhanced mode?

umm...how do I check?

[Gamer930]

Not trying to take over the thread but we have it Configured as Compatible and get that error

[Edit] the cypress board at least for us isn't even plugged in with USB[/edit]

[ebmonon36]

Is anyone with this error experiencing lag in the drive commands? We are experiencing about a half second to one second delay and are wondering if this could be the source.

Eric

[umangv620]

We were experiencing this lag. I think we got rid of it later on, but I think it was cause we had Tank drive and Arcade drive running on the same motors. we fixed this, and suddenly the controls were much more responsive.

[Andy Bradley]

We are having the exact same problem. After the updates, we get the following error anywhere from 4 to 7 times a second:
ERROR <Code> -44006 occurred at DriverStationEnhanced IO.lvlib:Access Raw Cypress outputs.vi>>DriverStation.lvlib:Start Communication.vi>>Robot Main.vi

The can bus is dropping in and out, and I suspect the spamming error messages may be a contributing factor. Any luck solving this one?

ETA: The errors can be found by selecting the diagnostics tab on the driver station screen, and then clicking the "View Log File..." button. We aren't using the cypress board at all, but will try to configure/connect it to see if the errors stop.

[Mark McLeod]

Originally Posted by Andy Bradley

ERROR <Code> -44006 occurred at DriverStationEnhanced IO.lvlib:Access Raw Cypress outputs.vi>>DriverStation.lvlib:Start Communication.vi>>Robot Main.vi

See if this helps:

On the Driver Station I/O tab select "Configure..." (lower left of window), then on the pop-up choose Enhanced and click OK.

[Andy Bradley]

Tried that. Also tried configuring the different IO points as inputs/outputs etc. Also tried uninstalling the driver station and reinstalling it with/without the cypress components - all to no avail. The only thing I haven't done yet (even though I said I would earlier) is actually install the cypress module. I'll keep trying, but please post any new info if you find it. Thanks.

[Gamer930]

Ok. . . We tried drastic measures and did a suggestion that NI Suggested. . . We did a full CRio Cleaning as they call it.
http://digital.ni.com/public.nsf/all...257673007935A1

We found nothing in the CRio but it started to work after. . . No clue what the actual problem was. . .

MAKE SURE YOU ARE VERY CAREFUL AND USE AN ESD STRAP OR MAT

Only thing I can think of is if the board inside the CRio is grounded to the case and shifted from impact??

[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.