[Greg McKaskle]

Thanks for the details.

Setting up the camera connection is not taxing on the CPU, but the camera and cRIO must both be booted up and share data over http before the first image comes back. Until this communication completes, it seems that the getImage() times out and returns an empty image. The LV implementation doesn't do this, but blocks instead. The difference in implementation matches the scheduling characteristics of the language.

Unless this is in its own thread, rather than loop until you get an image, I'd suggest you test the width to skip the processing, note that the vision isn't working yet, but otherwise allowing the code to do other things.

Does the code store every image for ftp? While this will obviously work, this is somewhat taxing on the cRIO and the flash. It is certainly good for debugging the vision code, but you don't want to fill up the disk/flash, and perhaps you don't need to store all of them.

Greg McKaskle