Updated C-Rio and Labview now code doesnt do ANYTHING

[whcirobotics]

Hi CD,
We just updated our labview to v3.2, and CRiO Image to v28. Before we updated the labview and the C-Rio the code worked fine, it drove and everything worked. But right now, today on the final day of the build season, we decided to pack it in and decided on updating it and ........ Now it does not work AT ALL! It does not read the joystick command, the compressor does not turn on. And we have a bit less than 7 hours to get it working and get it tested. I dont know what the update did to the software but it screwed us up BIG TIME. Please help us.

Thanks

[billbo911]

Hi CD,
We just updated our labview to v3.2, and CRiO Image to v28. Before we updated the labview and the C-Rio the code worked fine, it drove and everything worked. But right now, today on the final day of the build season, we decided to pack it in and decided on updating it and ........ Now it does not work AT ALL! It does not read the joystick command, the compressor does not turn on. And we have a bit less than 7 hours to get it working and get it tested. I dont know what the update did to the software but it screwed us up BIG TIME. Please help us.

Thanks

When you install the 3.2 LV update and then flash the cRio, you need to "Build" your code again and then do a "Run as Startup".

[whcirobotics]

I did build and Run as startup, but it does nothing still. NOTHING. The motors dont even get any inputs, the lights on them are flashing.

[Alan Anderson]

I hate to be "that guy", but did you remember to ENABLE the robot from the Driver Station?

Does the Driver Station show green lights for Communication and Robot Code? What does it say at the bottom left of the screen?

[whcirobotics]

Yes i Enabled the robot, At the bottom left of the screen it says "Teleop Enabled".

[Alan Anderson]

The Driver Station also reports the revision numbers for the cRIO image and for the Driver Station software itself. What are they?

[Blackphantom91]

There could be a conflict in code with this version that was just recently added. See if you can add a basic drive code to your system. We had to build our code completely over again just because we think their was compatibility issues with the new updates T_T. Its worth a try also you could go backwards to an old image but you have to go back to 28 when competition starts back up.

[DavidGitz]

So far it looks like the following have been deemed at least as (probably) not the problem:
-Communications: You were able to enable Teleop, which means that the Communications and Robot Code both show up on the DS.
-Independent of your Joysticks, as the Compressor is not starting.

What I would do:
-Make sure the DSC is connected: 37-pin cable on both ends, Digital Module. 12V,6V, 5V LED's should be on.
-Try running the Default Framework. If you can get Teleop Enabled and your Speed Controller's stop blinking (I don't know which ones are in the Default Framework, you will need to check that and make sure that they are Jaguar/Victor as appropriate) you should be good with your electrical connections, at least with those devices. More importantly that will show that your cRIO firmware image and DS Update are good.