|
Problems with VI after integrating into robot project.
We have a vi that generates values for our elevator. It uses two copies of a sub-vi, which calculates a motion profile. It ran great yesterday, so we decided to plop it into our robot code.
In testing today, things just didn't run right. No problem, we thought, we'll just tweak it some more off the robot to see what wasn't going well. That's when we hit a problem.
Now, when we try to run the elevator vi by itself, it fails with allusions to running out of memory, and points to an array initialization in one of the sub-vi. We tried deploying the code to the robot, which doesn't throw any errors, but nothing happens. For some reason, we can't run the vi by itself anymore. Now, no matter what, we cannot get the vi to compile to run on the PC. It only does math, and doesn't control any motors directly.
We are able to run the sub-vi in other vi's, without issue. The problem seems to be localized to running the sub-vi under our elevator vi.
We're stumped. Could it be the FRC update (which we installed this morning)? It worked perfectly yesterday, and we did not change anything in it. I'll include a screen shot of the error later. Our school blocks chief delphi, and I'm writing this from a mobile device.
|