I am not sure if these two things are related or not.
Our teleop program was working fine. Three motors run by three victors. Three solenoids run with joystick buttons activated by the first six solenoid outputs on the breakout.
About four days ago the motors stopped working for no apparent reason., the compressor started coming on as soon as the robot was turned on (the feeds from the pressure sensor into the digital in on the sidecar seemed to have no effect). Another team I noticed has had a similar problem.
However the solenoids kept working.
I guessed that the problem might be with the 2009 sidecar we are using (the solenoids bypass the sidecar). One team had mentioned that their 2009 sidecar had failed.
Yesterday we switched out the 2009 sidecar and put in the 2010 sidecar. We also took this opportunity to download and install the LABview update from 2.1 to 3.0.
Now the computer cannot "see" the cRIO. We are using our developer laptop. Not the class mate. The classmate stopped seeing the cRIO last week
• We tried using both the crossover cable as well as the standard ethernet cable.
• We checked and double checked all power connections.
• We tried several fully charged batteries to make sure battery power was correct
• We checked to see if the cRIO had been accidentally set to "safe mode"
• On the cRIO the small green LED marked "power" is on. The orange and green light that surround ethernet 1 input are on and do not flash. No other lights on the cRIO are on. I believe this is normal
Any ideas?
Thanks
As for the other problems I will check!