pwu.380

I ended up calling NI and they suggested to use a producer/consumer structure, but my script isn't working out and I'm don't know it it's some kind of syntax error or if my entire structure is faulty. Anyone care to take a look at it?

QUOTE (crelf @ Feb 4 2009, 06:02 PM)

A couple of quick questions: is there anything in the error cluster that's coming out of the IMAQ VIs? You haven't wired your error clusters, so you might be missing an error or warning. Also, what's the bus you're using for image acquisition? Is it a gigE, FireWire camera, or are you using a NI image acquisition card with a different standard?

I just wired the errors, and there's nothing.

The camera is going to a frame grabber card from NI. It's an analog input to the card and from there should be a PCI bus to the motherboard.

Well, as sudden as it started working, it stopped again. Now it's grabbing at a sluggish 5 fps. I have no idea what happened because I didn't change the code at all between today and yesterday. As far as buffers are concerned, that wouldn't be sustainable for indeterminately long image captures right? Because eventually you'll run out of memory to store the images in. Unless there's some kind of speed gain to be made in bulk processing of images.

Also, I'm pretty sure the camera is capable of acquiring full res pictures at full speed, because I can display them at the full frame rate if I remove the saving process.

So, any suggestions?

QUOTE (normandinf @ Feb 3 2009, 09:29 PM)

I got to write to disk at maximum speed of my camera (26fps) with your code with only a small change:

Wire a TRUE constant to the IMAQ Grab Acquire.vi's IMMEDIATE? input. It's false by default.

http://lavag.org/old_files/monthly_02_2009/post-10515-1233692772.png' target="_blank">

That worked really well, I'm incredulous.

Any explanation as to why this happens or is it one of those "just because" kind of things?

In any case, I appreciate your help.

Lets say it's fairly minimalist.

Also, I'm getting nearly the full frame rate when I halve the acquired image dimensions (so a quarter the size). But I still don't think write speed is the issue, the hd should be capable of writing at 40mb/s.

First, I'm pretty new to LabView and any sort of declarative programming in general. My profile is actually lying, because there was no option in the drop down menu for started in 2009.

I have a camera that runs at 15 fps and when I'm just grabbing the images to display it runs just fine, but when I put a function to save the frames in the same loop, the frame rate drops dramatically. It becomes something closer to 5 fps. Now I'm stuck, the individual pictures are about 1.5mb so I don't think I'm being bottlenecked by hard drive write speed. I don't know where to go from here, 15 fps isn't that fast in the first place, so it shouldn't be an unreasonable demand.

Also, the low level grab examples from LabView don't work. I get a camera not detected error, but it shows up in MAX and works for high level grabs.