Notices Overview
This topic summarizes all the notices applicable to MultiCam. For clarity, notices are grouped and sorted by:
| □ | Operating system (OS): Windows, Linux |
| □ | Processor architecture (PA): x86-64 (64-bit), x86 (32-bit) |
| □ | Product series (series): Grablink, Domino, Picolo |
Global notices (all OS, all PA, all series)
Power Saving Modes
Power saving modes of the operating systems (StandBy, Sleep, Suspend...) are not supported.
Image Buffer Allocation
Despite the support of 64-bit OS, the physical memory addressable by a frame grabber is determined by the hardware capabilities. Refer to DMA Addressing Capability for a list a products supporting 64-bit DMA transfers.
For boards having only a 32-bit physical addressing capability, it is mandatory to allocate the image buffer into the lowest 4 GB of the physical memory. For systems having more than 4 GB of physical memory, it is mandatory to use the automatic memory allocation mode of MultiCam.
For more information, refer to Memory Allocation
Notices for Grablink (all OS, all PA)
4-lane PCI Express Grablink cards support only the x4 link width
Refer to PCI Express Compatibility Issue for more information.
Operating latest generation of Grablink boards with a Camera Link clock rate lower than 30 MHz
Refer to Low Camera Link Clock Rate for more information.
Restrictions on allowed values for the Camera and CamConfig parameters
Refer to Camera and CamConfig Parameters for more information.
Configuration switches on latest generation of Grablink products
Refer toConfiguration Switches for more information.
PoCL_Mode control is only effective when the MultiCam channel is in the Ready state.
Refer to PoCL Mode Control for more information.
Notices for Picolo (all OS, all PA)
PCI and PCI Express bus requirements for Picolo cards based on the Conexant Fusion 878a
Refer to PCI and PCI Express Compatibility Note for more information.
Notices for Windows (all PA, all series)
MultiCam Service must be started before opening the driver
On Windows operating systems, MultiCam relies on a service named "MultiCam Service". This service is automatically started when the computer boots. Software should only access MultiCam when this service is started. McOpenDriver will return MC_SERVICE_ERROR if the MultiCam service is not started when called.
Windows Security warning when VeriSign Universal Root CA is missing
Refer to Driver Installation on Windows for more information.
Renewal of the "Code Signing For Microsoft Authenticode" certificate
Refer to Driver Installation on Windows 7 for more information.
The UEFI Secure Boot feature must be disabled on Windows Server 2016
Refer to Driver Installation on Windows Server 2016 for more information.
Unsupported Windows Fast Startup feature
Refer to Turning-off Windows Fast Startupfor more information.
Maximum buffer size is 4 GB
Refer to Buffer Size Limits for more information.
Notices for Windows 32-bit (all series)
Physical Address Extension
When PAE —Physical Address Extension— is activated, it is mandatory to use the automatic memory allocation mode of MultiCam.
Developing 64-bit applications
Both the 32-bit and 64-bit versions of MultiCam.lib import libraries are installed when the import libraries installation option is checked.
The development of 64-bit applications with MultiCam is also possible on a 32-bit Windows installation, providing that the x86-64 development tools are properly installed.
Notices for Linux 64-bit (all series)
Memory allocation
It is allowed to allocate memory anywhere in the available physical memory addressing space.
When memory is allocated beyond the lowest 4 GB of the physical memory addressing space, the OS performs automatically a buffer copy.
For systems with more than 2GB of RAM
The kernel reserves swiotlb memory for DMA transfers with devices that do not support 64-bit addressing.
Usually, the default is 64MB for the whole system. This may be insufficient for the total amount of memory used by your surfaces. To increase the amount of memory that can be used for acquisitions, you can use the swiotlb boot option swiotlb = n where n is the desired number of swiotlb slabs (1 slab = 2KB).
Refer to DMA Addressing Capability for a list a products supporting 64-bit DMA transfers.
Notices for Linux 32-bit (all series)
Memory allocation
PAE —Physical Address Extension— is not supported. The memory allocated for MultiCam must be below 4 GB in the physical memory addressing space.
For systems with more than 2GB of RAM
Devices that do not support 64-bit addressing must use memory below 4GB for DMA transfers.
The mem kernel boot option can be used to restrict the amount of memory used by the OS. For example: mem = 3000M
Refer to DMA Addressing Capability for a list a products supporting 64-bit DMA transfers.