Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

GigE Vision All-In packet

Solved!
Go to solution

Hello,

 

I am searching for a solution for a simple problem. I designed linescan camera, GVCP works, camera streams UDP packets on request from NI Max, but these packets are not recognized as data and Timeout Error 0xBFF6901B comes. Attached I send my All-In UDP packet. The same happens on my laptop and NI Industrial Controller with Intel network interface. Firewall is always off. On which parameters NI Max decides, that current packet is data packet? UDP Port?

 

I set the value to 1 in my camera's XML file and my camera should support All-In transfers. Should I have set it elsewhere too?

 

What else should I check? 

 

Regards,

Linus

0 Kudos
Message 1 of 8
(4,809 Views)
Solution
Accepted by topic author linru

Hi Linus,

 

This feature is new to GigE Vision 2.0 and not yet supported by IMAQdx. Per the spec, this mode is optional on both sides and the application software is required to enable it (SCCFGx) before the camera is allowed to use this mode. Since IMAQdx never enables it, the camera is required to use standard packet transmission.

 

Eric

Message 2 of 8
(4,793 Views)

Thank you very much for fast response. I was wondering, why NI Max does not access 0x0D24 SCCFG0 register and does not try enable All-In mode. Looks like, that there is no bug at all in my design 🙂 So now I should use the system with 3 packets (Leader, Payload and Trailer) per line (camera is linescan, so there is no "frames")? 

 

Regards,

Linus

0 Kudos
Message 3 of 8
(4,787 Views)

Linus,

 

With GigE Vision, the concept of "frames" when applied to linescan is that they are virtual but still exist. You still need to follow the GigE Vision spec and provide required features such as "Height" that allow the software to configure and view how many lines there are in each virtual frame. Typically most linescan cameras let many thousands of lines be configured into a single virtual "frame". For each frame only one leader/trailer is used.

 

Sending each line as an individual frame is strongly discouraged in most software because the per-frame overhead in acquisition and processing is typically significant (and most algorithms require combining multiple lines anyway). You'll get far better results in IMAQdx and Vision Development Module if you send the data as larger frames than single lines.

 

Eric

Message 4 of 8
(4,785 Views)

BlueCheese, thank you. The advice about multiple lines in a frame was very useful. The client is willing to have configurable frame size up to 512 lines.

 

Though I have problems transmitting single line. I attached my data leader, payload and trailer packets. I still have the same Timeout 0xBFF6901B error. First idea: my UDP source port is wrong. Is port 20202 reserved for anything else? Windows firewall is off, I am using a notebook without Intel NIC. Second idea: jumbo frame for payload packet is not supported? But I see it in Wireshark. Third idea: should block_id be reseted each time I press Snap button in NI Max? My line should be 5076 bytes/pixels wide.

 

I have set Extended ID field to zero, also block_id64 and packet_id32 fields should disappear. Payload type is uncompressed image data 0x0001. What am I doing wrong?

 

Regards,

Linus

0 Kudos
Message 5 of 8
(4,743 Views)

Hi Linus,

 

Have you tried running against the official AIA GigE Vision validation suite? This is required to release a product using the GigE Vision name and specification anyway. It should help validate that your implementation is correct. You should also check each one of the listed requirements in the specification to ensure your device is complying.

 

Eric

0 Kudos
Message 6 of 8
(4,737 Views)

I'll bug my manager to contact the AIA and get the budget for GigE Vision validation. What does this suite exactly do? Does it give any advice how to fix the incompatibility errors?

 

Linus 

0 Kudos
Message 7 of 8
(4,734 Views)

It should point you to the requirements it finds failing and then you can determine why your device is not meeting that requirement.


Eric

0 Kudos
Message 8 of 8
(4,732 Views)