01-09-2014 01:25 PM
Same problem is still happening...
The reboot didnt work.
Do you think this may be the indicators values I am trying to get ? I mean the lost image count, the total images transfered or the frame rate? I actually think no, since yesterday the VI was working properly with the indicator frame rate.
Well, if things dont fix ill have to use the VI you showed in the very beggining.
Thanks,
01-09-2014 01:55 PM
looks like i did it somehow...
I went to the VI and there was a case struct unwired there, not sure why but thats the reason.
What I did for a test was just wire a true state there (the same as remoing the case struct) and made it work, but i am sure thats not the right thing to do....
Well, what should i so, Ill be attatching an image of the vision acquisition VI and if u can answer, I appreciate.
Something else Id like to ask is, the VI was setup to acquire at 11 FPS but its indicating 9 FPS when I run and also, only looks like its getting all the images saved and running at the FPS I specify. I dont want to be hostage of this type of programming, I mean, I want to save a video and run it at same speed it was acquired, to avoid running time being different to the saved time, do you understand me?
I just think that manual adjusts are not the best to do...
Anyways, help for your time here and thank you in advance
😄
Att,
10-25-2024 12:10 AM
as a greener, i consider about if the IMAQ create.vi will clear its buffer after being read, or continuously cache photos until the memory is full.