cRIO lag after 2012 image installed

[ehlochbr]

Hi everyone,

We re-imaged our cRIO last night and tested some code afterwards. We had MAJOR lag and we can't figure out why. We would push a button on our controller and the robot wouldn't respond for at least a second. We're not sure what's wrong. Anyone have any ideas?

FYI - we're using Labview...

Thanks in advance!!!

[RufflesRidge]

If you click on the Diagnostics tab of the Driver Station are you seeing any error messages in the box there? Having a large number of unhandled errors can significantly slow down the operation of a LabVIEW program.

Forgetting to reorder one or more modules to match the new order would be a good way to get a whole bunch of errors that would probably give you that symptom.

[ehlochbr]

I'll check that. We did move the modules so that their location matches the new order of the latest cRIO image.

[Joe Ross]

Assuming you openend last year's project, check all of your module assingments in begin.vi. In some cases, they may no longer be valid.

I second checking the diagnostics tab.

[ehlochbr]

When we installed labview 2011, it automatically changed our digital module assignments in the code for us (which surprised us). So there was no code that needed to be changed to reflect the new digital module location.

If the code needed to be changed then nothing would have worked but stuff did work, it just worked long after we pushed the button.

This is a lot of help. I really appreciate the responses! Keep them coming!

[Greg McKaskle]

If you have no errors on the diagnostics tab, the next item I'd look at is the Charts tab of the DS. You should see CPU, memory, and other useful robot elements charted and logged there. Can you run the robot through different modes to see if it is just tele, or just auto, or always pegging the CPU?

The step after this would be for me to profile it using the CPU profiler built into LV. It is important to open and start the profiler before you begin running your code, then run the code for say 10 seconds, then stop the code, and only then stop the profiler. The profiler will only record functions that started and stopped in a profile session, so opening it too late or stopping it too soon can confuse you if you aren't very aware of how the code is being invoked.

Greg McKaskle