Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

TimeStamp

Hi,

I am using a Jai camera and would like to know the exact time at which frames have been acquired.

Using IMAQdxTimestampLow I get some numbers for the difference in times between frames, which I cannot correlate to the FPS.

Anyone ?
Thanks.

0 Kudos
Message 1 of 24
(4,208 Views)

And the block diagram....

0 Kudos
Message 2 of 24
(4,206 Views)

Hi ratus,

 

have you looked at this example?

http://decibel.ni.com/content/docs/DOC-4531

 

Regards,

Joseph Tagg

0 Kudos
Message 3 of 24
(4,179 Views)

Thanks for the reply.
Actually, the GetMetaData.vi I am using is similar to this example.

Best

0 Kudos
Message 4 of 24
(4,176 Views)

It is similar, but you need to make sure you combine both parts of the timestamp.

0 Kudos
Message 5 of 24
(4,172 Views)

Just have done it and it gives the same results.

Download All
0 Kudos
Message 6 of 24
(4,168 Views)

Ok.

What is the loop cycle time? Does that correspond to the FPS?

0 Kudos
Message 7 of 24
(4,160 Views)

As I acquire the next buffer, I think the loop cycle does not matter that much with this buffer acquisition (buffer length 1000) ?

So I guess I really acquire @ 200 fps which is also the specification of the card.
W.

 

0 Kudos
Message 8 of 24
(4,156 Views)

I looked back at the example I sent more carefully and there is the following note:

 

Caveats and Additional Notes

You will notice that I have divided the U64 by 10^7 before converting to timestamp.  This is because timestamp takes an input of seconds (it represents the number of seconds that have passed since Midnight, Jan 1, 1904), and the U64 contains values in 100s of microseconds (or tenths of milliseconds).  This may vary a little bit for different cameras, so if you are not getting an accurate timestamp, check to see what the quotient is.  You may need to adjust the constant for your camera.

 

As you can see, the actual value returned by the timestamp should be determined by the camera. Check there to make sure that it is being interpreted correctly. It seems that your program gives a x-y of 1s if the U64 is really returning tenths of milliseconds.

0 Kudos
Message 9 of 24
(4,137 Views)

Well, I would have to divide by 2.08000E+6 to get a time interval between frames of 5 ms....
Not sure it corresponds to something.

0 Kudos
Message 10 of 24
(4,132 Views)