IDS Software Suite 4.95

The IDS Camera Manager has been revised completely and is based on the same source code for both Windows and Linux. This means that the same functions can be offered under Windows and Linux, e.g.

•Camera information

•Additional functions like boot boost, multicast or trusted pairing

•Configuration of the GigE cameras optionally with persistent IP address, automatic IP address or via DHCP

Due to the revision of the user interface, some areas have been restructured. Therefore, the IDS Camera Manager is only available with German and English user interface in this version. Further languages will be added with the upcoming version.

IDS Camera Manager

Porting of further applications:

•The sample application uEye Demo was previously only available on Linux. uEye Demo is now also available on Windows including the source code.

•The uEye Hotpixel Editor is now also available under Linux. With the uEye Hotpixel Editor you can edit the list of sensor hotpixels stored in the camera.

uEye Demo

uEye Hotpixel Editor

In addition to a persistent IP address or an IP address from the IP address range for automatic IP configuration, you can also activate to obtain an IP address via a DHCP server. For this purpose, the is_IpConfig() function has been extended in addition to the IDS Camera Manager.

Manual ETH configuration

is_IpConfig()

The new function is_ImageQueue() joins all queue functions. With this, the following uEye functions are now obsolete:

•is_ExitImageQueue()

•is_InitImageQueue()

•is_WaitForNextImage()

is_ImageQueue()

The is_CaptureConfiguration() function is used to define the settings of the internal image memory queue. You can configure the queue size (in MB) and the number of image memories.

is_CaptureConfiguration()

With version 4.95 there is a breaking change in the uEye .NET interface. In the previous versions there was only one uEye .NET Library, with version 4.95 the uEye .NET interface is split into two new libraries. This change makes the uEye .NET interface compatible with .NET Standard 2.0.

The header file uEye.h has been renamed to ueye.h in the same way under Windows and Linux.

Programming notes

Extensive improvements under Linux: for example, dynamic loading of the API is also possible or the use of the same debayering algorithms as under Windows.

The different parameter names for Mem and MemId have been unified to cMem and nMemId. The name is supplemented with the "p" prefix for the number of pointers. When using the uEye Python interface PyuEye in combination with "Named/Keyword arguments", the program code may have to be adjusted here.

is_AddToSequence()

is_AllocImageMem()

is_CopyImageMem()

is_CopyImageMemLines()

is_FreeImageMem()

is_GetActiveImageMem()

is_GetImageHistogram()

is_GetImageInfo()

is_InquireImageMem()

is_LockSeqBuf()

is_RenderBitmap()

is_SetAllocatedImageMem()

is_SetImageMem()

is_UnlockSeqBuf()

A new command has been added to the is_Configuration() function. This allows you to update the IP address of the network adapter that has been cached by the driver.

is_Configuration()

For is_Event() a new event was introduced: IS_SET_EVENT_FRAME_SKIPPED. The event is signaled when a frame has been skipped.

is_Event()

In the is_CaptureStatus() function the IS_CAP_STATUS_TRANSFER_FAILED status was introduced as replacement of the IS_CAP_STATUS_USB_TRANSFER_FAILED status. The IS_CAP_STATUS_USB_TRANSFER_FAILED status is obsolete and should no longer be used.

is_CaptureStatus()

The is_SetStarterFirmware() function is obsolete and is replaced by the IS_ALLOW_STARTER_FW_UPLOAD parameter in the is_InitCamera() function.

is_InitCamera()

UI-359x: When activating subsampling, the sensor-internal anti-blooming function is automatically switched on.

UI-359x

The number of image memories that the driver preloads in the USB subsystem has been increased. Note especially for embedded systems that this increases the memory requirements.

The behavior of the flash pin (pin 8) of the uEye LE USB 3.1 Gen 1 has been revised. After booting, the pin now outputs a HIGH level. This corresponds to the behavior of the flash pin as in the USB 3 uEye LE camera family.

uEye LE USB 3.1 Gen 1

The USB 2 firmware files have been moved to the hard disk corresponding to the USB 3 firmware files.