search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Standards: GenDC


@imveurope


www.imveurope.com


Decoupling what to transport fromhow to transport it


Stéphane Maurice, GenICam vice chair and director of soſtware development at Matrox Imaging, describes the benefits of GenDC, the latest member of the GenICam standard family


S


tanding for generic data container, GenDC defines a transport media- independent data description that


allows devices to send or receive almost any form of imaging data to and from a host system, using a uniform and standard data description. GenDC completes the GenICam (generic interface for cameras) family of modules that control and exchange data between imaging de vices. GenDC defines a generic and self-


described imaging data container that is independent of the way it is transported or stored. It also defines standard mechanisms shared by the various transport layer (TL) protocols in camera interface standards – such as GigE Vision, USB3 Vision, CoaXPress, and others – to transport it. As a result, a TL needs only to define how to transport the data container, without needing to know the content or format of the data container. Tis separation allows the addition of data types to the GenDC standard without requiring modifications to individual TL specifications. All TL protocols implemented by common machine vision camera interface standards will support GenDC; each of them already has a proposal on how to handle it. A quick and general adoption of GenDC is therefore expected. Tis can be attributed in good part to the common standardisation efforts in the machine vision industry around the globe.


Why GenDC? Similar to other machine vision standardisation projects, the main objectives of GenDC are to avoid work duplication, simplify common tasks, and establish a common definition between various


GenDC modular model decoupling data encoding or decoding from its transmission


manufacturers. All types of cameras and devices can use GenDC as an opaque and portable data blob – a chunk of binary data – that describes the images or data to transport or process. Tis makes porting an imaging device from one transport medium to another a very simple task, as the data description and encoding is always the same and can be done in a shared section separate from the transmission protocol implementation. Accordingly, on the reception side, the common data description format of GenDC decouples the data reception from the data interpretation, making the design of a receiver modular, simple and uniform. Today, most TLs – which are part of the existing camera interface standards – support


32 Imaging and Machine Vision Europe • Yearbook 2019/2020


only basic 2D images, monochrome and packed colour. However, these TLs are all looking to support new, more complex data payload types such as planar colour images, compressed data, 3D data, multi-spectral images, metadata and processing results. Up until now, for every new payload type, each TL standard technical committee independently had to address the way those new payloads are to be formatted and transmitted. Moreover, these technical committees have had to release new versions of their respective TL specification to accommodate those new payload types. It could take several years to have a particular new payload type supported across all the TLs. Manufacturers of transmitter and


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52