Standards: GenDC
@imveurope
www.imveurope.com
Forum steering committee, and all the TL committees. Tese TL committees agreed to work on supporting a common TL- agnostic, futureproof data format that would be shared and maintained in a common GenICam forum. Extensive work was done by a workgroup composed of the GenICam chairs, TL chairs and other interested parties to make GenDC a reality. Te GenDC specification was finalised and released in December last year.
Typical GenDC data container layout for a 3D image
receiver devices supporting multiple TLs would also need to develop and maintain a different solution for each TL. GenDC thereby eliminates duplication of work and possible discrepancies by defining a standard, general and shared data-description format for those new use cases. Te fact that GenDC is developed and maintained in a common workgroup greatly simplifies the standardisation efforts, and reduces the time and effort needed to provide support for a new imaging payload type.
GenDC in detail GenDC is an imaging data-container representation that supports the description of almost any type of imaging data. It decouples the data container format – the ‘what’ to transmit – from the TL data transmission – the ‘how’ to transmit. Te TL is thus only responsible for the transmission and reception of an opaque GenDC payload. Transmitter and receiver devices for
different TLs can share the same GenDC data encoder and decoder, meaning that a new camera or frame grabber for a different TL is easily supported by simply changing the transmission or reception physical front end. Subsequently, the same general GenDC data-descriptor format is used for all payload types, from camera to computer as well as within and outside application soſtware, i.e. in memory or file.
GenDC can describe simple or complex
payloads with a unified data-descriptor structure that includes: 1D, 2D, or 3D images, for example monochrome, packed or planar colour, or 3D range; compressed buffers, such as JPEG, JPEG 2000, and H.264; multi- view or multi-spectral, such as stereo, visible and infrared, or hyperspectral data; image sequences, including multi-frame bursts; processing results such as histogram or blob analysis; metadata such as general data information, GenICam chunk, or XML; and mixed content, for example 2D image plus metadata plus processing result. GenDC is supported by existing or future vision TLs as an opaque new generic payload type, or as raw data. Respective TL committees can define specific mechanisms and rules to guarantee minimal data- transport overhead and easy interpretation of the data container on reception.
GenDC history First presented at the Kyoto International Vision Standards Meeting (IVSM) in the spring of 2016, the GenDC concept was received with enthusiasm and obtained the backing of the G3 group, its Future Standard
34 Imaging and Machine Vision Europe • Yearbook 2019/2020
GenDC eliminates duplication of work and possible discrepancies by defining a standard, general and shared data-description format
Summary Te GenDC module defines a generic and flexible imaging data container representation. Its basic principle is to create a layer that decouples what to transport (the data container description) from how to transport it (the data transmission method) using a particular media. GenDC – being TL neutral – standardises the format of the data buffers transmitted and received by various present and future TL standards. Also, since it is defined and maintained by a single workgroup composed of representatives from GenICam and each TL, the TL committees are now able to focus solely on providing efficient and reliable real-time data transmission over a particular physical media. TL standards specifications are thus no longer affected by changes to data representation or by new payload types, which can now be added without requiring updates. Moreover, since the GenDC specification defines a self-described data format, it is also a standard
way to represent almost any imaging-related information in many different contexts beyond the data exchange between a transmitter and a receiver. Tis includes, for example, data containers stored in host memory or in a file. Finally, with all the above features,
GenDC completes the GenICam offering of TL-independent modules to control and exchange data between imaging devices, including GenAPI, SFNC, GenCP, GenTL, and now GenDC. O
The GenDC 1.0.0 specification can be found on EMVA web site at:
www.emva.org/wp-content/uploads/ GenICam_GenDC_1.0.pdf
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
