Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Driver issue with PCI-1426

Using: PCI-1426, Visual Studio.NET C++, MAX 3.1.1, NI-IMAQ 3.1.3
 
I am attempting to communicate to a camera via the CameraLink standard library (clsernat.dll) and then follow that (in a seperate block of code) with a call to the 'imgOpenInterface()' for acquiring data.
 
The results that I see are that if I make a call to the clsernat library first - it is successful, but then I can not open the interafce to begin acquiring data (device already in use message appears).
 
The reverse also seems to be true - meaning the cameralink serial port can not be accessed (via the clsernat.dll) if the interface has been opened via the 'imgOpenInterface()'.
 
Therefore what I believe to be happening is that the driver opens an interface when called by the clsernat.dll library and then the device is 'in use' when attempting to use the 'imgOpenInterface' function.  This means there is no way to get a handle to the serial port and open an interface for acquiring data at the same time.  I do not want to use the 'img*' serial functions because I am trying to standardize the serial communications according to the cameralink specification and keep them seperate from the acquisition process.
 
Is what I am seeing and reporting valid?
 
Can it be fixed or is there a work around?
 
Thanks,
Mike Haberle
Lumitron
0 Kudos
Message 1 of 2
(3,315 Views)
Got my hands on IMAQ v3.5b1 and it resolved the issues described above.
0 Kudos
Message 2 of 2
(3,299 Views)