NI PCIe-1433 Camera Link frame grabber programming using VC++

Hello, I have a Basler Camera Link-compatible camera and they use the NI PCIe-1433 Camera Link frame grabber as the image acquisition device.
Right now, I want to develop some applications on that camera and need to do programming on the NI PCIe-1433 by VC++.
So I want to know where I can find the software development kit for the NI PCIe-1433. For example, I can control the camera to grab the image by using the different functions(such as imgGrab(), or somthing like that ) from that software development kit.If there are some sample code that would be better.

Hi Wrsbj,
The IMAQ functions that you mentioned are contained in the IMAQ driver, which is used to acquire from Camera Link frame grabbers. I would also check the compatibility chart, to make sure that you get the version you need. As for example programs, you can take a look at this KnowledgeBase article concerning building and running the IMAQ examples in VC++.
David S.

Similar Messages

Code example link frame grabber Dll in LV

Hi,
As example to develop my own Frame grabber driver for LabVIEW
Where can I find the sources of a LabVIEW driver for a frame grabber,
linking the grabber's Dll ?
Thanks in advance
Sebastien

seb wrote:
> Hi,
>
> As example to develop my own Frame grabber driver for LabVIEW
> Where can I find the sources of a LabVIEW driver for a frame grabber,
> linking the grabber's Dll ?
Install NI-IMAQ and look into the VIs. But really don't expect to much
here. This is specifically for the NI-IMAQ DLL which has its own
concepts most likely quite different to what your frame grabbers card
DLL does. In addition the NI-IMAQ VI code is not exactly the most well
designed and nicely wired VI code you could possibly find.
In short if you do not know how you would have to access the DLL from C
(not familiar with the API or even more difficult not have some good
C knowledge) it will be a though exercise and most likely never work and
you would be better of payin
g someone in your area who does know.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Synchronisation of frame grabber and DAQ board

I want to aquire images and analog voltage signals at the same time, and synchronised, using a NI PCI-1428 Camera Link frame grabber and a NI PCI-6014 DAQ board. Can this be done using the RTSI trigger functions? I know that the frame grabber supports this, but what about the DAQ board?
How about synchronising a NI-board with a non-NI frame grabber?
Thanks a lot!
Peter

Hi, Peter,
No, the PCI-6014 DAQ board does not support RTSI. However, most of the low-cost E-series NI data acquisition cards do support RTSI, such as the PCI-6024E or PCI-6036E, so you might consider using one of those boards instead.
If you decide to go that route, there is a useful tutorial that describes the signals that can be routed over RTSI for NI DAQ and IMAQ boards:
Developer Zone Tutorial: Synchronizing Motion, Vision, and Data Acquisition
as well as several example programs:
Developer Zone Example: Integra
ting IMAQ and DAQ with Single Display
Developer Zone Example: Low-level Triggered Ring (with DAQ-supplied triggers)
As for a non-NI frame grabber, that would really depend on what support the frame grabber has for timing and synchronization. You could route a trigger signal or scan clock out over the PFI pins on the PCI-6014, but you would need to see if the frame grabber is designed to receive these types of signals.
I hope that helps!
Best regards,
Dawna P.
Applications Engineer
National Instruments

Issue setting baud rate for IMAQ using Camera Link

I have a PCIe-1433 camera link board, with a Basler camera. I found that I can set the gain and exposure times directly in the camera using the serial link and serial commands. This works very well. I'm doing this programmatically using the CLAllSerial.DLL.
The serial commands take too long to send in my application due to the default baud rate of 9600, so I was able to send a command to the Basler camera to up its baud rate, then change the baud rate of the camera link serial com port to match it. The result is that I can talk very quickly to the camera. Sweet so far.
However, with both the Basler camera and the camera link com port set to the higher baud rate, I can no longer acquire images using the IMAQ imgXXX commands. I get a timeout from the serial commands that IMAQ must be using to control the camera for image acquisition. Essentially the IMAQ driver doesn't know about the baud rate change. I cannot see how I can tell the IMAQ driver what baud rate to use either. NI MAX also becomes unusable in this situation.
How can I, through the IMAQ driver, increase the baud rate of the serial commands to the camera over the camera link?
Cheers,
Wayne
Solved!
Go to Solution.

David,
I'll try to help if I can. Keep in mind that I'm using a stub into the DLL using Delphi as my development platform. That should not matter.
The DLL I'm tapped into is the IMAQ.DLL for the camera calls to get/set exposure time, gain, etc. The best reference I found for this is the NI-IMAQ help files that get installed with the normal NI install. There are important string constants that you need, to talk to the interface. I can't recall how I found these, but below are mine, in Delphi:
{ These are Basler camera attribute names we care about. }
BaslerCameraGainControlAttributeString = 'Gain'; { string result }
BaslerCameraGainValueAttributeString = 'Gain Value'; { numeric result }
BaslerCameraBitDepthAttributeString = 'Bit Depth'; { string result }
BaslerCameraExposureControlAttributeString = 'Exposure Control'; { string result }
BaslerCameraExposureModeAttributeString = 'Exposure Mode'; { string result }
BaslerCameraExposureTimeAttributeString = 'Exposure Time'; { numeric result }
BaslerCameraMaximumHeightAttributeString = 'Maximum Height'; { numeric result }
BaslerCameraPowerOverCameraLinkAttributeString = 'Power Over CameraLink'; { string result }
{ These are Basler camera attribute values we care about. }
BaslerCameraManualGainAttributeValue = 'Manual';
BaslerCamera12BitDepthAttributeValue = '12-bits';
BaslerCameraMaximumHeightAttributeValue = 2048;
BaslerCameraExposureControlFreeRunAttributeValue = 'Free Run';
BaslerCameraExposureControlTriggeredAttributeValue = 'Triggered';
BaslerCameraExposureModeAttributeValue = 'Manual';
BaslerCameraExposureTimeAttributeValue = 5;
BaslerCameraPowerOverCameraLinkAttributeValue = 'On';
BaslerCameraGainValueAttributeValueMinimum = 33;
BaslerCameraGainValueAttributeValueMaximum = 512;
MaxAttributeStringLength = 100;
The following code snippets, get and set gain and exposure times (I called it shutter speed), in Delphi:
function TNiVision.GetGain : double;
var
TheGain : double;
begin
if GetCameraAttributeNumeric( BaslerCameraGainValueAttributeString, TheGain ) then
Result := TheGain
else
Result := BaslerCameraGainValueAttributeValueMinimum;
end;
procedure TNiVision.SetGain( TheGain : double );
begin
SetCameraAttributeNumeric( BaslerCameraGainValueAttributeString, TheGain );
end;
function TNiVision.GetShutterSpeed : double;
var
TheSpeed : double;
begin
if GetCameraAttributeNumeric( BaslerCameraExposureTimeAttributeString, TheSpeed ) then
Result := TheSpeed
else
Result := 1;
end;
procedure TNiVision.SetShutterSpeed( TheSpeed : double );
begin
SetCameraAttributeNumeric( BaslerCameraExposureTimeAttributeString, TheSpeed );
end;
These then call into the DLL functions imgGetCameraAttributeNumeric and imgSetCameraAttributeNumeric. There is a formatting interface between the above and the actual DLL functions I didn't show that just reforms the Delphi strings attribute names into C null terminated char arrays.
I hope this helps. I've now moved on to using Pylon with GigE cameras, which is a much cleaner interface, but very different code.
Cheers,
Wayne

PCIe-1433与CamLink相机串行通信

PCIe-1433图像采集卡和Camera Link相机连接后，根据上下位机的通讯协议，上位机能够利用Camera Link协议中的串行通信部分，发送相应指令字符，以实现对相机的控制！我现在想利用LabVIEW编程，做一个控制界面出来，仅实现采集卡和相机之间的串行通信功能即可。PCIe-1433手册里提到，实现串行通信功能需要调用IMAQ Serial Write VI and IMAQ Serial Read VI模块，！初学LabVIEW，很多地方不懂，请问各位能不能指点一二或是类似的程序，以供参考！在此十分感谢！

安装了IMAQ模块，相应的子VI也看到了，不知道怎么用啊！

PCIe-1433, extension boards and multiple trigger outputs

Hi All,
I am using two cameras and three LED lighting bars to take images of fabric from a conveyor. The cameras are interfaced with an NI PCIe-1433 card which has two extension boards attached to it. To synchronise the triggering of both the cameras and the LEDs I am using PhaseA of a quadrature encoder signal located on the conveyor. I need to produce six pulses to provide the external triggers at various points of the PhaseA waveform.
I understand that the PCIe-1433 only has 1 external output that can be used as a trigger although with the extension board this increases to 3. I am assuming that even though I have two extension boards on the same PCIe-1433 card I am unable to use the additional 3 external outputs, which would give me the total of 6 I require?
Any guidance would be appreciated
Kmor

Hi Kmor,
Can you tell me what extension boards you are using?
Fouad

Using GCC on SunSolaris2.8 to compile and link sample OCI programs

Hi,
Does anyone have sample make file (or modified version of demo_rdbms.mk) or command to compile and link OCI demo programs using gcc?? I am trying to compile and link cdemo81.c from rdbms/demo directory.
gcc related files are under /usr/local/bin and /usr/local/lib, /us/local/lib/gcc-lib/sparc-sun-solaris2.8/3.1
Thanks

Hi,
I finally got cdemo81.c to compile and link on Solaris 8 using Oracle 8.1.7.3. I got some help from one other person who had posted similar question on this forum. Following is the makefile that I am currently using to compile my oci code. Please note that you need to have $(ORACLE_HOME) and LD_LIBRARTY_PATH set before you try to compile using gcc.
************** Makefile Starts here ***********************************
CPP=g++
CC=gcc
LD=ld
CCFLAGS= -g
CPPFLAGS=-g3 -Wall
INCDIR=-I$(ORACLE_HOME)/rdbms/demo -I$(ORACLE_HOME)/rdbms/public -I$(ORACLE_HOME)/plsql/public -I$(ORACLE_HOME)/network/public
LIBNAME=liboralib
SOEXT=.so
DLLINK=-shared -ldl
###SOFLAGS=-shared -Wl,-expect_unresolved -Wl,-soname,$(LIBNAME)$(SOEXT) $(LIBPATH)
SOFLAGS=-shared -Wl
LDFLAGS=-shared -expect_unresolved * -soname
LIBPATH=-L$(ORACLE_HOME)/lib/ -L$(ORACLE_HOME)/rdbms/lib/ -R$(ORACLE_HOME)/lib/ -R$(ORACLE_HOME)/rdbms/lib/
ORALIBS= -lnbeq8 -lnhost8 -lnus8 -lnldap8 -lldapclnt8 -lnsslb8 -lnoname8 -lntcp8 \
-lntcps8 -lnsslb8 -lntcp8 -lntns8 -ln8 -lnl8 -lnro8 -lnbeq8 -lnhost8 -lnus8 \
-lnldap8 -lldapclnt8 -lnsslb8 -lnoname8 -lntcp8 -lntcps8 -lnsslb8 \
-lntcp8 -lntns8 -ln8 -lnl8 -lclient8 -lvsn8 -lcommon8 -lgeneric8 \
-lmm -lnls8 -lcore8 -lnls8 -lcore8 -lnls8 -lnbeq8 -lnhost8 -lnus8 -lnldap8 \
-lldapclnt8 -lnsslb8 -lnoname8 -lntcp8 -lntcps8 -lnsslb8 -lntcp8 \
-lntns8 -ln8 -lnl8 -lnro8 -lnbeq8 -lnhost8 -lnus8 -lnldap8 -lldapclnt8 \
-lnsslb8 -lnoname8 -lntcp8 -lntcps8 -lnsslb8 -lntcp8 -lntns8 -ln8 \
-lnl8 -lclient8 -lvsn8 -lcommon8 -lgeneric8 -ltrace8 -lnls8 -lcore8 \
-lnls8 -lcore8 -lnls8 -lclient8 -lvsn8 -lcommon8 -lgeneric8 -lnls8 \
-lcore8 -lnls8 -lcore8 -lnls8 -lnsl -lsocket -lgen -ldl -lsched \
-lc -laio -lposix4 -lkstat -lm -lthread -lwtc8
LIBS=$(ORACLE_HOME)/rdbms/lib/defopt.o $(ORACLE_HOME)/lib/sscoreed.o $(ORACLE_HOME)/lib/libclntsh.so $(ORACLE_HOME)/lib/nautab.o $(ORACLE_HOME)/lib/naeet.o $(ORACLE_HOME)/lib/naect.o $(ORACLE_HOME)/lib/naedhs.o $(ORALIBS)
##LIBS=$(ORACLE_HOME)/rdbms/lib/defopt.o $(ORACLE_HOME)/lib/sscoreed.o $(ORACLE_HOME)/lib/nautab.o $(ORACLE_HOME)/lib/naeet.o $(ORACLE_HOME)/lib/naect.o $(ORACLE_HOME)/lib/naedhs.o $(ORALIBS)
###LIBS=$(ORACLE_HOME)/rdbms/lib/ssdbaed.o $(ORACLE_HOME)/lib/nautab.o $(ORACLE_HOME)/lib/naeet.o $(ORACLE_HOME)/lib/naect.o $(ORACLE_HOME)/lib/naedhs.o $(ORALIBS)
ORALIBSO=-lnetv2 -lnttcp -lnetwork -lncr -lclient8 -lvsn -lcommon8 -lgeneric8 \
-lmm -lnlsrtl3 -lcore8 -lnlsrtl3 -lcore8 -lnlsrtl3 -lnetv2 -lnttcp \
-lnetwork -lncr -lclient8 -lvsn -lcommon8 -lgeneric8 -lepc -lnlsrtl3 \
-lcore8 -lnlsrtl3 -lcore8 -lnlsrtl3 -lclient8 -lvsn -lcommon8 -lgeneric8 \
-lnlsrtl3 -lcore8 -lnlsrtl3 -lcore8 -lnlsrtl3 -lnsl -lm -ldl -lm \
-ldl -lnetv2 -lnttcp -lnetwork -lncr -lnetv2 -lnttcp -lnetwork -lncr \
-lnetv2 -lnttcp -lnetwork -lncr -lnetv2 -lnttcp -lnetwork -lncr \
-lnetv2 -lnttcp -lnetwork -lncr -lsql
###-lnbeq8 -lnhost8 -lnus8 -lnldap8 -lldapclnt8 -lnsslb8 -lnoss8 -lnoname8 -lntcp8 \
#ORALIBS=-lnetv2 -lnttcp -lnetwork -lncr -lclient8 -lvsn -lcommon8 -lgeneric8 \
# -lmm -lcore8 -lnlsrtl3 -lepc -lnsl -lm -ldl
CPPOBJECTS=orabase.o orastmt.o
HEADER=orabase.h orastmt.h
.SUFFIXES: .cc .c
###.c.o:
###     $(CC) $(CCFLAGS) $(INCDIR) -o $@ -c $<
.cc.o:
     $(CPP) $(CPPFLAGS) $(INCDIR) -o $@ -c $<
#lib: $(CPPOBJECTS) $(HEADERS)
#     $(CPP) $(CPPFLAGS) $(SOFLAGS) $(LIBPATH) -o $(LIBNAME)$(SOEXT) $(CPPOBJECTS) $(LIBS)
#clean:
#     $(RM) *.o core *~
#distclean: clean
#     $(RM) $(LIBNAME)$(SOEXT) so_locations
###ocimanager:     ocimanager.o
###     $(CC) -o $@ $(LIBPATH) $(LIBS) $<
ocimanager.so: ../obj/ocimanager.o
     $(CC) $(LIBPATH) -o ocimanager.so -G ../obj/ocimanager.o $(LIBS)
##     gcc -L$(ORACLE_HOME)/lib/ -L$(ORACLE_HOME)/rdbms/lib/ -o ocimanager.so -G ../obj/ocimanager.o $(LIBS)
../obj/ocimanager.o: ocimanager.c ocimanager.h
     $(CC) $(CCFLAGS) $(INCDIR) -o ../obj/ocimanager.o -c ocimanager.c
**************** Makefile ends here*********************************************
Hope this helps
Brunda

Control Camera Attibutes through serial port using VISA commands

Hi there,
I'm using a Basler acA2000-340kc camera through an PCIe-1473R FPGA as frame grabber.
I would like to be able to configure the camera through the serial port just in LabView, not using a third-party as Pylon (which I can do now).
According to this forum post
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/My-Basler-acA2040-180km-NIR-is-not-visible-in...
this is possible just taking the VI posted here
https://decibel.ni.com/content/docs/DOC-5049
and converting from IMAQ to VISA, as RIO frame grabbers cannot use IMAQ. I have been trying to do this by changing the IMAQ vi to their VISA equivalents, but I have no good results.
Does anyone know which are the steps to go from that piece of code to one that can be used to control the camera in my case?
Thanks a lot,

Hi i.popa,
Basler makes the Basler Binary Protocol Library for serial communication with their cameras. If you make sure you're running the serial server section of your FPGA code to keep the serial port open, you should be able to use calls from this library to communicate with your camera. We have a community example with more information on using the Call Library Function Node to call a DLL. This DLL will take care of all the processes needed to write from and read to the registry, so this implementation will probably be similar to the example program you listed above, using calls to this library instead of the IMAQ Serial functions.
Good luck with your application!
Emily C
Applications Engineer
National Instruments

Camera File Generator Won't Run with MAX + PCIe-1433

Hi,
I am a camera developer and am trying to integrate a couple of new cameralink cameras with the PCIe-1433 NI frame grabber. I have installed NI MAX 14.0 and version 3.0.0 of the Camera File Generator.
I am trying to build a new Camera File for our companies cameras.
The NI MAX shows the NI PCIe-1433 device when it launches.
When I try to launch the Camera File Generator, it failis to load with the following message:
"You must have NI-IMAQ 4.6.0 or higher installed before running the NI Camera File Generator. NI-IMAQ 4.6.0 is installed with Vision Acquisition Software 2011."
The MAX configuration tree shows I have version 14.0 of the NI-IMAQ software available.
Is there any sort of developer's guide for creating a camera file to allow me to use my camera? I need to write some serial commands to the unit and thought tha tthe Camera File Generator would support this....
Thanks.
-Mike

Hi mawillia,
The latest version of the IMAQ drivers is version 4.9, and it would show up where you said, under the Software tab in NI MAX. Do you have this latest version installed? If you like, feel free to expand out your software tab and take a picture of it and post it here.
Also, you are correct that the serial commands can be set in the camera file. Here is a link to our support page for the Camera File Generator: http://sine.ni.com/psp/app/doc/p/id/psp-723/lang/en
Within it is a whole host of various KnowledgeBase articles. This one seems particularly helpful:
What framegrabber specifications do I need to know to create my camera file?: http://digital.ni.com/public.nsf/allkb/9B89C9FA43A6973A86257A62004658D5
Unfortunately, I couldn't find any articles specific to coding the serial commands for your camera in the camera file. But I recommend opening up one of the bundled camera files (I'm looking at the Basler acA2000-340kc (Base).icd ) and within that, click the Camera Control tab. The serial commands for each attribute will show up on the right side, and you can use this as an example for creating yours.
Let me know if you have any further questions!
Julian R.
Applications Engineer
National Instruments

How can i use PCIe 1433 and basler line camera to construct image and pocess it?

hello! every one ,I am new to machine vision.i have two problems to ask.First,how can i use line camera and 1433 to acquire 2-D image?second,if i want to pocess the 1-D signal ,how can i do it ?i expect for your answer ,thank you!

What you are trying to do is not something you can easily do in a forum, but I can give you the basics.
You have a CameraLink frame Grabber (PCIe 1433) and a LineScan Camera
The framegrabber needs to be configured to understand how to communicate with the camera. You need a file from the camera vendor. This file might already be installed. You can use MAX to check if it is, under Devices/IMAQ.
Assuming you can get to the point where you can communicate with the camera, you need to configure your acquisition.
Since the camera is a line scan camera, it captures image data one pixel ine at a time. You will need to configure the frame grabber to determine how many lines per image you want. The low limit is usually 1, and the high limit is either based on the framegrabber's internal memory, or that of the computer.
If you are using labview, you will need to open a sessing to the camera, acquire the image(s), and then close the session when you are done.
Once the image(s) are captured, you can performa analysis using the NI Vision Toolkit.
Sorry, but there is no way to condense years into one post.
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions

PCIe-1433 with camera MC1362 (Mikrotron)

Hello,
I would like to use my camera MC1362 (Mikrotron) with the frame grabber PCIe-1433. But this camera is not yet suported by NI, so I don't have any camera file for this camera. I tried to use the one done for the MC1310 (I have seen people on this forum who had used it with the frame grabber PCIe-1429 with success), but it didn't work too. I tried then to make a camera file with the camera file generator provided by NI, it didn't work too (no error message, but no image also!).
does anybody have successfully made a camera file for this camera and this frame grabber? Is it possible to obtain one from NI engineers, please?
Thank you in advance,
Bests

I just put a new Camera File Generator on the FTP site, which fixes some issues earlier versions had with the 1433. I would try this again to see if this works any better.
ftp://ftp.ni.com/support/imaq/pc/ni-imaq/cfgenerator/2.0.6/
If this doesn't work, we could help you develop a camera file. If you could provide your contact at Mikrotron, I could try to get a loaner camera to develop the camera file for it.
Thanks,
Brad

I am using PCI-6033E IO card and i would like to send 5 volts (high logic ) to the trigger box. the trigger box will trigger the frame grabber card, that i am using for image acquisition.

i am using PCI-6033E IO card and i would like to send 5 volts (high logic ) to the trigger box. the trigger box will trigger the frame grabber card, that i am using for image acquisition.

Hello;
The first thing you need to figure out is the shape of the trigger pulse needed.
In case you just need a logic high TTL pulse, you can use one of the digital lines of your DAQ device.
In case you need a pulse train (multiple trigger pulses), you will need to configure one of the general purpose counters to accomplish that task.
You can find examples in both Labview and NI-DAQ showing how to program your DAQ board to accomplish both approaches.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

Does NI offer a generic LabVIEW interface for the PCI-1424 frame grabber?

I am attempting to grab frames from a DuncanTech camera using a PCI-1424. The vendor's software was developed in the LabVIEW, but I only have the executable and they seem unwilling to provide the source file(s) - essentially, the vendor software only displays the images (no capture capabilities). In the interests of time, I would like to locate/purchase a generic LabVIEW image acquisition front-end, if available.

MJP;
Your PCI-1424 card should include several examples. Check the directory where the software for the camera was installed (Usually "Program Files\National Instruments\NI-IMAQ")
Also, if you have MAX (Measurement & Automation Explorer), you can access your card from there and snap images.
Other than that, I think you have to write your own code or ask somebody to do it for you.
Regards;
Enrique
www.vartortech.com

Camera frame grabber to laptop

Hi everyone,
I am using a frame grabber connect a camera to a laptop. The camera is Dalsa Piranha2 linescan, it is said that programmable integration time, line scan rate,... and there are commands for this through serial port. Can you show me how to send these command to changes camera parameters? How should I do that in Labview?
Thanks
Hannah

Hi Hannah,
if this properties are settable through serial port, you can first check to send this commands through hyperterminal. If this works see the shipped examples "Basic/Advanced Serial Read and Write.vi".
Mike

PCIe-1433 not showing 16bit x 2 taps as option in camera file generator

Trouble getting 16bit by 2 taps camera to display 16 bits. Instead, I get interleved columns of 16bits and 8bits, as if it is only doing 24bit. Camera file generator seems to configure it all correctly, oddly, it uses tap 1 and tap 3 instead of tap 1 and tap 2.
I noticed PCIE-1433 documentation doesn't list 2 taps by 16bit as an option,
http://www.ni.com/pdf/manuals/374001b.pdf
yet NI public information
http://digital.ni.com/public.nsf/allkb/9B89C9FA43A6973A86257A62004658D5
states it can support 2 taps by 16 bit. Chances I need to update IMAQ drivers?

Hi dre99gsx,
This seems like it could be caused by using the wrong camera file. I noticed you said that it's a two tap camera and it's using a different tap configuration than what is intended. Have you tried creating the camera file manually using our Camera File Generator (http://sine.ni.com/nips/cds/view/p/lang/en/nid/14207)?
Julian R.
Applications Engineer
National Instruments

NI PCIe-1433 Camera Link frame grabber programming using VC++

Similar Messages

Maybe you are looking for