Vision: IMAQ Area Filter crashes cRIO

[Greg McKaskle]

never ever ...

All CPUs are limited. If you get a bigger camera or a faster camera, you will overwhelm even a XEON monster with the data that it can produce. The cRIO is perfectly capable of processing images for this year's challenge, provided you use it appropriately.

A cRIO shouldn't crash doing image processing, and I'll hook mine up to see if I can reproduce it. You may want to verify that you have this year's cRIO image installed, and if you don't mind a few more experiments, can you change the two Boolean true's to false to see if one of those is responsible for it?

Greg McKaskle

[team3039]

We experienced tons of lag with cRio Vision Processing. I've successfully implemented the vision tracking code on the dashboard, and we get much cleaner readings and smoother tracking.

[Greg McKaskle]

My point is not that cRIO is right and dashboard PC is wrong or vice-versa. The two are actually quite similar in how they work.

The key is to identify the strong and weak aspects of an approach. If you combine this with the ability to list alternate approaches, and you have powerful tools that will allow you to innovate and discover new and novel designs that are effective at solving a problem.

So, to play this game a bit. What would "ton of lag" mean? Do you have an idea what is causing the lag?

Greg McKaskle