|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
cRIO v43 == fail
Hi everyone,
We've had some problems. We had some drive code on our old robot. After updating to the new firmware and recompiling/deploying the code, we have an issue. We are getting an error: >>>> ERROR: Allocating module that is out of range or not found: Digital Module 6 ...in InitPWM() in C:/WindRiver/workspace/WPILib/pwm.cpp at line 33 WPILib was compiled from SVN revision 2993 Looking at the source for WPILib, this call goes back to SensorBase::CheckDigitalModule(). So this call: nLoadOut::getModulePresence(nLoadOut::kModuleType_ Digital, 6 - 1) is returning false, but it should return true. I can confirm that we do have a digital sidecar in slot 6. The cRIO Imaging Tool also says that the module is OK. I can't find the source for getModulePresence either. Should I report this as a bug to WPILib? Since the source for getModulePresence doesn't appear to be in WPILib, it seems like it would be out of their control (at least, I can't find the definition with a find | xargs grep getModulePresence). I could try commenting the check out and see if that works... I have quadruple checked the module, and everything looks good. The imaging tool says the module is installed correctly. But the runtime check is failing. Why... all these silly updates- the last version that worked correctly for me was v28... anyway, if anyone has ideas, your help would be MUCH appreciated. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|