|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Labview Pwm/DIO ERROR -63195, need help
The FPGA portion sounds a bit like a red herring.
Ultimately, all IO goes through the FPGA using a standard bitfile that you don't have to touch. If the bitfile itself was the problem, you'd have a problem right from the start. It's also a problem that every team would have because it's part of the imaging process. You'll want to focus your attention on building out. If you start with the initial project, it includes a couple of PWM ports going to motors. If that doesn't error, you can try to add the next component on. If you're working with Command and Control, it's even easier to test in this modular mindset. Start with the drive subsystem and see if the error pops up. If it does, you know it's the most recent thing you added. Check the wiring. Check the hardware. Make sure it's responding. If it's not, you'd expect to see the error. Take a look at the lights on the motor controller when you enable. What do they tell you? |
|
#2
|
|||
|
|||
|
Re: Labview Pwm/DIO ERROR -63195, need help
Our team has had the same FPGA and device handling error show up in our driver station and prevent our code from running when we enable. This has been happening on different robots and computers, and even with blank projects, all in the past week. As far as we know, none of the hardware on the robots has changed.
Interestingly, error -63195 is always preceded at the beginning of runtime by error -63192, which says that the RIO resource name is invalid. We checked it with NI MAX, however, and the resource name seems to be fine. We suspect the problem is in the WPI libraries at the base of LabVIEW or on the robot and know that we didn't touch that code. Occasionally, rebooting the robot/roboRIO multiple times, clearing object cache, and removing code from the roboRIO has solved the problem, but none of these solution has been consistent--the problem still occurs intermittently. The latest method we tried was shelling into the roboRIO and removing the "frc" folder, which appears to hold the LabVIEW libraries. So far it seems to work, but we're not sure yet whether it's a permanent fix. |
|
#3
|
||||
|
||||
|
Re: Labview Pwm/DIO ERROR -63195, need help
We were having this error also, but we did a roborio complete format, and firmware load, and that seems to have fixed the issue.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|