View Single Post
  #13   Spotlight this post!  
Unread Yesterday, 22:57
HSi HSi is offline
Registered User
FRC #1712 (Dawgma)
Team Role: Programmer
 
Join Date: Jan 2016
Rookie Year: 2014
Location: Ardmore
Posts: 7
HSi is an unknown quantity at this point
Re: Labview Pwm/DIO ERROR -63195, need help

Quote:
This error has now returned, we tried to diagnose, loading the default project with multiple laptops, and multiple roborio's. We have diagnosed that it is a single rio, (we have 4) that this error follows.

Any ideas?
My team is using the NavX and we also had the problem. First, I suggest you make sure that your NavX libraries are located where the NavX software installer placed them. Regarding the problem as a whole, we believe we have found a way to evade the problem without removing the NavX from our code and robot. To summarize, our solution was to build a blank robot project down to the roboRIO (i.e. so the code runs at startup) and then build our actual robot project down. Here's some of the troubleshooting and reasoning behind it (though I admit this might not explain why only one roboRIO is having the errors):

We first noticed that the errors appear on the robot depending on what was deployed or built at startup. If a blank/standard project was the first project deployed after the robot was turned on or after the roboRIO was reset, every subsequent project deployed to the robot caused no errors. If the first deployment caused the -63192 and -63195 errors, then every project after also has the errors.

Hence, we built down a blank project onto the roboRIO, and every deployment was fine. We then built down our actual project just to see whether the act of building down could resolve the issue, and the errors stopped appearing as well. This seemed to solve the problem for both of our roboRIOs.

I'll put out a warning that the errors have occasionally appeared a few times during deployment of work-in-progress robot code, but they stop before the end of deployment and don't inhibit the functioning of the robot like before.

I would offer an explanation for this solution/"evasion technique", but unfortunately I don't completely understand it either, especially with the new information about the NavX communication loop causing the errors. Maybe our errors have two different sources. It would be great if someone could shed light on this.
Reply With Quote