[Tom Line]

P.S. - we DID finally figure this out. Here's the skinny since I know a number of teams have asked for it:

NI has disabled the Imaq write because the CRIO team stated that the on board flash storage has a limited number of writes before failure (as do all solid state memory drives utilizing flash memory that are currently in use).

In their testing they saw failure after extended (and I mean extended extended extended extended) use. I'm not sharing the exact numbers because that's probably protected / private info. In normal use I'd be shocked if a team hit the limit in many years of Crio use.

Now - getting it to work is not easy because you have to know how some of .vi's function. But now that we know how to make it work, implementation is easy. You can find the write code in our posted labview code, but also note two things: #1 you have to modify the camera get image .vi by adding an output to it. This output should be wired to the string that is being passed into the .jpeg decode vi (all internal to the get image vi). That is your vision data.

Next, when you feed that into the string input on the text write vi from the file i/o palette, you have to right click on the write vi and turn off the check mark next to "EOL", or you will get corrupted images.

Good Luck!