Thanks for the advice...
That problem was easily resolved....
..... but now we have a new problem
Our team-coded classes are failing to initalize some components.
Each time these components are called, The cRIO freaks out and
reboots it self. So please, just a few more questions:
How "Bug-less-ly" can you initalize a WPILib C++ object via.......
Object i.e: Victor myVictor(...)
vs.
Pointer i.e: DigitalInput* myDI = new DigitalInput(...)
What are all the possible program exceptions to look
for that relates only when initalizing the object?
If we were to put them in a custom C++ class that
our main robot will use, of which that custom class will hold all
of the required group of electronic objects of the special component
on the robot that custom class is made for; What would be a nice,
error/exception free example for this? (Sorry if you see this as a run-on)
Our team has the recent updates for Windriver, the cRIO, and the
Driver Station. So we don't think those shouldn't be the problem.
Please, help us.....
Thank you all in advance,
And thank you everyone else who helped us on this topic so far.....