Our cRIO from last year wont take new code. We keep getting told that the software for labview needs to update on the cRIO side. We can’t figure out how to do this, but we CAN use last year’s code for the practice bot.
Did you reformat that cRIO to the new image for this year?
Start at http://www.usfirst.org/roboticsprograms/frc/control-system and follow the links to find your way to Imaging your cRIO.
We figured out the problem with the Crio and ran into a different problem. We are getting power to our Victor 888’s but they don’t get the signal to power the motors. We are using code that has been proven on our actual robot so it can’t be a code problem. We have no idea what the problem could be. I don’t know if it’s possible for anybody to help given the information I’ve provided but anything at all would be greatly appreciated. Let me know if there is any more information I can provide. We worked on this problem (along with the Crio problem) for 10 hours today. For the record I’m not the electrical or programming guy so I may be a little slow with terminology.
I suggest re-formatting the cRIO to the 2014 format (assuming you’ve done so already). If problem persists, check PD board, then PWM connections. I believe the Victor 888 has a “B” on the PWM port, B to Black (bad way to put it, because B could stand for a lot of things, should’ve marked it “-”, “S”, and “+” but whatever), and then make sure it is also in the right orientation on the sidecar.
If problem persists, try running the motor directly off the battery itself.