Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

IMAQdx timestamp off-by-one

Solved!
Go to solution

Hi,

 

It sure looks like the camera is sending an incorrect timestamp to me... in that trace packet 613 looks to be the first image leader (that contains the 64-bit timestamp). If you compare it to packets 1619 & 2243 (the next two leaders) you'll see the first is much larger and then the next ones start counting in a normal fashion. You can put the filter in as "udp.srcport == 10010 && udp.length == 52" in that trace to see just the leaders. The timestamp around 0x36h.


Eric

 

 

Message 11 of 12
(822 Views)

@BlueCheese wrote:

 

It sure looks like the camera is sending an incorrect timestamp to me... in that trace packet 613 looks to be the first image leader (that contains the 64-bit timestamp). If you compare it to packets 1619 & 2243 (the next two leaders) you'll see the first is much larger and then the next ones start counting in a normal fashion. You can put the filter in as "udp.srcport == 10010 && udp.length == 52" in that trace to see just the leaders. The timestamp around 0x36h.

 

Thanks. After applying the filter, I can see what you describe.


BlueCheese wrote:

 

My suspicion is that this is a firmware issue on your Manta camera. Can you see if there is a firmware update you can install?

 


This was indeed the problem. Today I received a response from Allied, and they had a firmware update for my camera.

 

For others with an Allied Manta, the firmware with bad timestamps was version 00.01.44.00, according to Allied's "Sample Viewer" application. The firmware with correct timestamps is 00.01.44.04.

0 Kudos
Message 12 of 12
(814 Views)