Error -63195 on DIO and Analog Opens

[MikeF1617]

Recently, my team removed the pneumatics system (PCM and all) from our robot due to weight issues, and since then boot-up code and deployed code results in these errors being outputted to the driver station:

ERROR  -63195 occurred at Read/Write Control in FPGA_DIOReadOutputEnable.vi->WPI_DigitalModuleDIOAllocator.vi->WPI_DigitalInputOpen.vi->Begin.vi->Robot Main.vi
NI-RIO:  (Hex 0xFFFF0925) The handle for device communication is invalid or has been closed. Restart the application.

ERROR  -44070 occurred at FPGA_AIReadAccumulatorOutput.vi>>WPI_AccumulatorGetOutput.vi>>WPI_GyroGetAngle.vi>>BuildCustomDashBoardData.vi>>main_ctrl.vi>>Robot Main.vi
FRC:  The <b>Analog Channel</b> for the accumulator is invalid.

ERROR  -63195 occurred at Read/Write Control in FPGA_AIAverageBits.vi->WPI_AnalogModuleOpen.vi->WPI_AnalogChannelOpen.vi->Begin.vi->Robot Main.vi
NI-RIO:  (Hex 0xFFFF0925) The handle for device communication is invalid or has been closed. Restart the application.

ERROR  -63195 occurred at Read/Write Control in FPGA_DIOReadLoopTiming.vi->WPI_DigitalModuleOpen.vi->WPI_MotorControlOpen&ConfigurePWM.vi->WPI_MotorControlOpen Talon.vi->Begin.vi->Robot Main.vi
NI-RIO:  (Hex 0xFFFF0925) The handle for device communication is invalid or has been closed. Restart the application.

I tried re-flashing the roboRIO, but that did nothing to solve the problem. I checked and all pneumatics code is removed (it had been producing other issues related to CAN due to lack of PCM). I then tried reverting to older revisions of the code and was able to find a version without the errors, but the revision is old and would be very inconvenient to use and bring back to the current version, and I worry that the errors would not be resolved. I did not see any major differences in the code that could cause this, and the only change to begin.vi (which is where all the errors were occurring as shown in the errors above) was that a Talon was inverted, which I un-did just to be safe, but that did not help. The old begin.vi and current begin.vi are attached (the newer one has an added I2C open, but that was added after the errors were found, not before).

What is extra peculiar is that if I ran the old code, stopped it, than ran the new code, everything works.

We also had functioning code on our bagged robot and after un-bagging it, we removed the pneumatics. On the robot's boot with the start-up code, it had these same errors, in addition to penumatics errors. I put the most up-to-date code onto the robot and the errors remained, excluding those relating to pneumatics. I set the new code as start-up and re-booted the robot, but that still did not fix the problem. I tried running the code off of my laptop, but that also did not fix it.

This NI help page that I found also did not fix the problem.

We have the most up-to-date FRC update (2015.1.0). We also re-connected the PCM but that did not fix the problem. So I can't blame the pneumatics, but it is very coincidental, and maybe it has something to do with it.

This post is about the same error, but in our case we have it for all analog and digital input/output, which is problematic, and I am not sure how to fix this issue based off of the information from that post. It appears to identify the problem as the functions in begin being run before an FPGA reference is attained by the code, but I am not sure how to solve this. I assume it would be possible to go deep into the WPI code and copy out the function that returns the FPGA reference and if it is not valid, loop in begin until it is, but that seems sketchy and it shouldn't be needed.

Is there an easier solution to fixing this other than re-writing our code from the last working copy or by checking if an FPGA reference is present before opening our devices?

Thanks,
Michael