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

Similar Messages

  • RTSI cable configuration with PCIe 1433 card

    Hi All:
    I tried to trigger my line camera with RTSI signal.
    The layout is: trigerr signal  is generated from one PCI card 6259 (Dev2/ctr0). The line camera is connected with one PCIe 1433 card, and the two cards were connected with RTSI cable.
    The problem is that how to register or configure PCIe 1433 with RTSI cable in MAX, it seems I can only configure PCI card within RTSI cable ......
    If it is true, how should I do to rout the trigger signal to the camera, such as "route Dev2/ctr0 to Trigger line 0"?
    Below is printscreen of MAX Configuration. Attached is my VI.
    thanks a lot.
    Bob
    Attachments:
    Triggered with RTSI from DAQ.vi ‏63 KB
    camera configuration.jpg ‏218 KB

    Thanks a lot, the post helped.
    But I am still confused with the details:
    To camera and PCIe 1433 configruaration, as the attached pictures shows: RTSI is configurerd as Camera Control Line as number "2"; the exposure control of camera is defined as "triggered".
    In previous attached VI, you may find that the IMAQ configurer trigger is applied to define trigger  type as "RTSI", trigger number as "2".
    About ttrigger signal from PCI 6259 (Dev2), digital pulse is generated and output terminal is defined as ctr0 ( seems only ctr0 or ctr1 is option).
    So I still do not know how to route signal from "Dev2/ctr0" to "Imag0 CCL 2" in labview.
    By the way, I read  the online example "LL Triggered Ring using DAQmx Pulse Train", http://www.ni.com/example/29476/en/.  Within this VI,  the DAQmx Connect Terminals VI is applied to route the counter's output to a RTSI pin so the signal can be used by the IMAQ device. However Dev2/ctro is not recognized as scour terminal, only other items such as PFI, APFI or RTSI are avaible, and output signal source is also limited with similar things, sounds like just internal connectrion with Dev2.
    thanks a lot.

  • Exposure time with externally triggered MC1362 and PCIe-1433

    Hi,
    I am capturing images using a Mikrotron EoSens CL MC1362 camera and NI PCIe-1433 frame grabber. I have a question about exposure time - which I'm not sure if it is related to the frame grabber, the camera, or the combination, but hopefully someone here can help.
    I'm running an external signal to the SMB connector on the frame grabber, and have the camera set to operate in "Pulse width mode", which allows the frame grabber to take control.
    My question is:
    How do I determine the exposure time from the parameters of the external signal? It's a square wave, and the duty cycle seems to control the exposure time.
    I would guess that the exposure time, E= (D/f), where f is the signal frequency and D is the duty cycle? e.g. for f=1kHz and D=80%, the exposure time would be E=0.8ms. Is that correct?
    The camera manual can be found here:
    http://g4.com.tw/web/file/product/usermanual/995-EoSens%203CL-MC1361-Manual.pdf
    and I have included a screenshot of the revelant portions which seem to describe how pulse width works. In particular it says "Exposure time is defined by the width of the external signal". Is that equivalent to my E=D/f idea?
    Thanks in advance for any help.

    Great, thank you!
    "The exposure stays on while the pulse is high."  -  I basically just wanted to double check this, because it doesn't really say that explicitly in the manual and I find their wording confusing and didn't understand what the three traces in the diagram are.
    Thanks again,
    Stu

  • 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 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++

    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.

  • How to connect external trigger PCIe-1433?

    I am having an issue getting the external trigger to work using a cameralink camera, a PCIe-1433 card and a signal generator.  The signal generator is connected to the SMB connector on the 1433 card and is providing a 20 Hz signal with a 20ms pulse width at TTL voltages (0-4V).  From memory, we are using the MAX software and under the Acquisition tab I have CC1 set to external, however the camera is not receiving this external trigger.
    I've attached a rough diagram of our setup.
    What could my issues be?  My thoughts are:
    1) Are there other settings in MAX I need to ensure?  I know the SMB connector can be an input or an output.  How can I make sure this is set to input?
    2) My input signal is 0-4V which is TTL, but does the signal need to be 0-5V?
    Any thoughts would be greatly appreciated.  Thank you.
    Attachments:
    ExternalTrigger.jpg ‏29 KB

    Hello tuckturn
    Thank you very much for getting in touch with us. 
    1)  In Measurement and Automation Explorer, the default is an input.  You would need to use LabVIEW to change the SMB connector to be an output. Can you please show me a screenshot of your camera attributes in Measurement and Automation Explorer.
    2)  Where does this input signal come from?  Do you have a 5V TTL compliant output to test this?  Can you please provide me the specification for whatever device is outputting the voltage?
    Thanks again.
    Sincerely,
    Greg S.

  • How to connect external trigger PCI-1433

    Hi all:
    I met the same problem as this old post: https://forums.ni.com/t5/Machine-Vision/How-to-connect-external-trigger-PCIe-1433/m-p/1677560/highli...
    however the post did not give solution.
    I am having an issue getting the external trigger( from PCI 6259) to work with a cameralink camera, a PCIe-1433 card . The PCI 6259 is connected to BNC 2111, the output trigger signal from CTR0 is connected to the SMB connector on the 1433 card and is providing pulse train at TTL voltages (0-5V).  Using the MAX SOFTWARE and under the Acquisition tab I have CC1 set to external 0, however the camera is not receiving this external trigger. The camera is Basler 4096-140km.
    I measured the ouiput signal from CTL0, the sigal seems good.
    I tried RTSI trigger before, failded. I thought SMB should be more straight forward, seems I was wrong.
    Looking forward to reply!
    Attachments:
    camera configuration.jpg ‏168 KB
    External Camera Trigger(SMB).vi ‏57 KB

    Bobjojo,
    You will actually need to affect the properties of both the camera and the frame grabber to take advantage of this triggering mode. I found a document that contains a good run down of the process to acquire in this mode (linked below). As far as the programming for the acquisition is concerned, the frames will be built at the driver level for the specified frame height. This means that the IMAQ driver will composite the line scans for you, and any simple acquisition (the document shows using the Vision Acquisition Express VI) will be able to pull the image into LabVIEW.
    www.ni.com/white-paper/13786/en/pdf
    Karl G.
    Applications Engineer
    ni.com/support

  • Software Trigger from CC1 on PCIe-1433

    Dear Sir or Madam,
    Now I am getting into trouble about NI Measurement Automation explore with my PCIe-1433. I like to make software trigger from this software into my cameralink camera. However I am not so familiar with this software. Is it possible to make software trigger ? If it is possible, I like to know how to generate it.
    Best regards,

    Hello,
    Check out this forum post. It goes through the steps necessary to set up triggering in MAX.
    -Erik S
    Applications Engineer
    National Instruments

  • PCIe-1433: pulse train to CC1, in C++?

    I'm sure this should be a simple question and there's a lot of good information from previous threads but I can't quite put it together.
    I have a PCIe-1433 and a Point Grey Gazelle; everything works okay, and in the Camera File Generator, I can put the camera into bulb-shutter mode and correctly control the exposure. So, through the camera file, control of CC1 works well.
    But now I want to programmaticaly generate a simple pulse train, to CC1 of this camera. CC1 is already set as "external" line 0 in MAX. I believe I am correctly putting the camera into external trigger mode because the frame rate drops to 0 (or the timeout rate). The commands are a bit confusing to me; currently I am using
    imgPulseCreate2(PULSE_TIMEBASE_50MHZ, 50000, 50000, IMG_SIGNAL_STATUS, IMG_IMMEDIATE,
    IMG_TRIG_POLAR_ACTIVEH,IMG_SIGNAL_EXTERNAL, 0, IMG_PULSE_POLAR_ACTIVEH,
     PULSE_MODE_TRAIN, &pulseId);
    imgPulseStart(pulseId, sessionId);
    No errors reported (after some trial and error), but I don't believe it's creating a pulse. I need to do this programmatically because I will need to vary the pulse rate to something the camera can support for different ROI's, although if there is a combination of using the camera file and code I would be happy to use that.
    Any help would be greatly appreciated!

    GREAT! Thank you Eric, starting with your tip and then some more trial and error, I've got it going now. A few things:
    * The attribute I was trying to modify actually only involved a pulse width, but it still wanted me to stop the acquisition.
    * The solution ended up being to code the camera mode (set by serial commands to first set the trigger source to CC1, then set the trigger mode to single) in the camera file.
    For some reason that I'll figure out one day, sending these same codes with serial write just did not work at all. Even if I told the camera file not to send any serial codes at all, ever, sending the same two commands myself didn't seem to work (even though I got acknowledgement from the camera). I'd like to solve this because I believe that calling AcquisitionStart resends these codes (for example, when I set up for a sequence acquisition) but this is redundant and slows things down.
    * So now I tell the camera file to send "trsrc line1\r" and "trm single\r", but with no pulse output. Then in the code, I use the commands below to set the pulse.
    imgPulseCreate(PULSE_TIMEBASE_50MHZ, 70000, 70000, IMG_IMMEDIATE,
    IMG_TRIG_POLAR_ACTIVEH,IMG_EXT_TRIG0, IMG_PULSE_POLAR_ACTIVEH,
    PULSE_MODE_TRAIN, &pulseId);
    imgPulseStart(pulseId, sessionId);
    then, to change the exposure time:
    imgPulseUpdate(pulseId, sessionId, delay, width);

  • My PCIe 1433 device does not show active channel in MAX

    I have a PCIe 1433 installed and it worked fine for a year. However, since last week, the channel "img0" was disappear from the device list in MAX as shown in the attached figure.
    The channel name is now list as "c0000039" instead of "img0", and there is no other menu except save and refresh on the right pane as shown in figure. 
    The labview based module, MAX, and the vision acquisition module is all 2014 version. I can locate the "img0.iid" file as well as the necessary camera file in my PC.
    Any idea what might cause this issue? Please feel free to ask me if you need some more info or suggestion.
    Thanks.

    Eric,
    Thanks for your reply.
    We recently switched to Labview 2014 64bit version about a month ago. But everything worked fine back then.
    The problem just happened last week. I confirmed that it worked just fine the week before. 
    Is it possible that this issue is cause by the 64 bit version?
    Here is the list of what I already tried so far that didn't solve the issue;
    - I did try repair installation of Vision Acquisition and MAX. --> Nothing change 
    - I did try connect another working camera --> Same problem
    - I put the frame grabber in another PC --> Same problem (exactly the same as shown in the previous picture) 
    Per your suggestion, I will try to run an IMAQ example with "img0" tomorrow.
    I'm not sure if I can get it run though since Laview programm did not recognize the "img0" either.

  • 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

  • How do I get LV2009 to see my PCIE-1433?

    Hi all - I think this problem is just a matter of picking the right download.  I'm trying to modify an LV application that was installed on demo system provided by a vendor. They very kindly provide all their source code, but it's written in version 2009, and they didn't include the development environment. I downloaded 2009 sp1 and installed it using my 2014 SP1 license. So far, so good. 
    When I opened the VI, LV couldn't find any of the IMAQ sub-vi's. Eventually, I figured out that I needed to install the 2009 version of the Vision Acq System. Downloaded and installed it, and that took care of most of the missing VIs. There were still a few that required the Vision Development Kit, but I don't have that license, so I just deleted those and tried to run the VI. I got errors that it couldn't open the framegrabber. It turned out I had unstalled the driver for the PCIE-1433.
    So I downloaded the Driver package, installed that, and the PCIE-1433 is still not recognized.  Now I'm stuck.  I know this system should work somehow, because the vendor's application worked before I started messing with it.
    Any ideas, folks?  Install everything in a different order (above is the actual order I installed things).
    thanks!
    MADman
    Solved!
    Go to Solution.

    It seems that the PCIe-1433 needs the IMAQ 4.4 driver or later, which is included in VAS 2010.03. You will need this driver and LabVIEW 32-bit.
    Getting Started with the NI PCIe-1433
    http://www.ni.com/pdf/manuals/374000a.pdf
    What Versions of NI-IMAQ, NI-IMAQdx, and NI-IMAQ I/O Come with My Version of Vision Acquisition Software?
    http://digital.ni.com/public.nsf/allkb/6C42133468D​66324862578BC00655CF8
    NI-IMAQ Compatibility with Different LabVIEW Versions
    http://digital.ni.com/public.nsf/allkb/DB928F6D5E9​D6B97862579A7006B2850
    Thanks,
    Frank
    Application Engineer
    National Instruments

  • PCIe-1433与CamLink相机串行通信

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

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

Maybe you are looking for