CRIO 9067 remote USB vision image acquisition

I have a 9067 connected to a Basler USB camera.  I'm able to successfully view images via MAX and via the Grab example as long as I run the Grab example on the RT Target.  However, I don't need the images processed on the RT or FPGA in this application.  Is it possible to open a remote connection to the camera from my host computer using IMAQdx?
I was hoping I could use something like "[cRIO IP Address]::cam0" in the camera address, but that doesn't seem to work.
Is this possible or do I have to manually pipeline the images from the RT target?
Thanks,
Omar
Solved!
Go to Solution.

Hello Omar,
You cannot access the camera image directly by addressing it through the cRIO. You will have to implement image transfer between the cRIO and host PC. Fortunately you can do this rather easily by using an image shared variable or network stream.
Earl C
Applications Engineer
National Instruments

Similar Messages

  • Two Simultaneous USB Camera Image Acquisition and Saving

    Hello everyone,
    Recently my friends and I have begun a project which requires the simultaneous acquisition of images from two independent USB cameras. Throughout our project research we have encountered many difficulties. The major problem appears to be how to successfully interface two USB cameras and properly save the image to a median for further processing down the road.
    Our first attempted at this was with the USB IMAQ drivers. Unfortunately, to our surprise, it does not support two independent and simultaneous camera acquisitions. To combat this problem we implemented a crude loop of closing a camera reference, then opening the other, acquiring an image, then closing, etc... This did provide us with functionality but was very inefficient, resulting insufficient acquisition speeds.
    Afterwards we began looking at other ways of capturing and writing the image, which are listed below.
    Various Acquisition Interfaces / Strategies
    USB IMAQ Driver - USB interfacing kit available for public download, (not officially supported by NI) zone.ni.com/devzone/cda/epd/p/id/5030
    Status - Abandoned because of the lack of dual web camera support
    Avicap32.dll - Windows 32 DLL responsible for all web camera communication, and other media devices.
    Status - Currently acquired two streams of video on the front panel but with no way of saving the images
    Directx - The core Windows technology that drives high-speed multimedia on a PC.
    Status - Currently researching.
    .NET - Microsoft .NET framework, possibly a valid interface to a video stream.
    Status - No development until further progress.
    We are still currently developing the Avicap32.dll code but the major bottleneck is the learning curve on the property nodes, library calling nodes, .NET and other references. So far it’s been a tedious effort of trying to understand example code and piece them together. As a former programmer of C I know this is not the proper way of writing code web I can’t seem to grasp how these functions work. (Property nodes, library calling nodes, .NET and other references). Learning this may allow us the knowledge to code a proper system. Does anyone know any good tutorials or learning material for such functions? So far my research has come up empty handed.
    We are currently working with these interfaces and other reference examples on the NI site. Unfortunately we cannot seem to properly integrate the code for our system. Does anyone know if this setup is even possible? Also, if anyone has any experience with similar systems and can offer advice, code snippets, or any other assistance it would be greatly appreciated.
    Our current projects will be posted below if you have any suggestions. (More will be added when I get to my desktop tomorrow)
    Two Camera Avicap32.dll - Currently stuck on how to save the image, various tweaks have gotten us stuck at this point ( will have another Avicap32.dll implementation posted tomorrow)
    USB Capture Example - This USB capture VI was an example that immediate had problems. We used it as a baseline for crude open-close camera image grabbing system. (Will also be posted tomorrow)
    Thanks for any help, it's much appreciated.
    Taylor S. Amarel
    Thanks,
    Taylor S. Amarel
    Learning is living.
    Co-Founder and CEO of http://3dprintingmodel.com/
    "If we did all the things we are capable of, we would literally astound ourselves."
    -Thomas Edison
    Attachments:
    Two Camera Avicap32.dll.zip ‏84 KB
    USB Capture Example.zip ‏17 KB

    Thanks for the information but that's not exactly what I'm looking for. I've been to that URL and read the information before. I don't mean to disparage you help but I'm looking for ways that I can successfully implement a functional system, not information on an unfunctional method. Maybe I was unclear before, I'm looking for any advice, knowledge or help on how to make this system properly work.
    Thanks, have a great day.
    Taylor S. Amarel 
    Learning is living.
    Co-Founder and CEO of http://3dprintingmodel.com/
    "If we did all the things we are capable of, we would literally astound ourselves."
    -Thomas Edison

  • CRIO 9067 to recongnize SiLabs USB RS232

    Hello,
    I have a cRIO 9067 and would like to interface to an instrument that has a SiLabs USB-RS232 converter.  I can comminicate with this instrument easily on a Windows PC.  I am able to see the device in MAX when its connection the cRIO.  IT shows up under "Devices and Interfaces" as "USB0::0x1FB9::0x0100::121A00A::RAW"  with the Model number and the device description.
    I've followed the description at this link, but I don't get a ttyUSB# devices.
    https://decibel.ni.com/content/docs/DOC-34827
    Is there any chance to get this working on the cRIO as a serial port?
    Thanks.
    Solved!
    Go to Solution.

    After some digging, talking with NI Folks, google, and Talking with Folks at lakeshore.com (device vendor) here's what I've piece together on how to get this to work:
    In Linux, usb devices are enumerated automatically, and, by default, will show up as a USB RAW device
    Once the USB device has been enumerated, it can then, subsequently be linked to a driver
    Linux determines if and when to link each USB device based on the Device's on Vendor ID (VID) and Model ID (MID). These are typically 3-4 digit hex strings.
    For the case of the Lakeshore 121 current source, VID=1FB9 MID=100.       I could see these in MAX for the USB Raw Device.
    There are two levels of drivers for USB-Serial Devices. The first driver: usbserial.ko is a generic driver that handles all USB-Serial devices. This must be loaded for all USB-Serial converters.
    The second driver is specific to the chipset of the USB-Serial device.       For the cRIO, there are three options that are pre-installed (FTD, SiLabs, and some other)
    The drivers reside at       /lib/modules/3.2.35-rt52-2.0.0f0/kernel/drivers/usb/serial/ (where the kernel version directory may vary)
    The Lakeshore 121 use the SI labs CP210x chipset, so we chose this one.
    The device drives first need to be loaded by Linux. Linux can automatically do this by adding zero length files to the module.autoload.d directory. To do this execute the following:
    cd /etc/modules.autoload.d
    touch usbserial
    touch cp210x
    reboot cRIO
    execute dmseg | grep usbserial to confirm that the usbserial driver is loaded
    execute dmesg | grep cp201x to confirm that the cp210x driver is loaded
    The next step is to associate our USB device with the cp210x device driver. Remember that linux associates the device with a driver based on VID and MID. Whomever installed the cRIO linux base, I'm sure, knew nothing about the Lakeshore 121 VID and MID.
    Lakeshore recommended getting the source code for cp210x, adding the VID and MID to the list of recognized devices, recompiling the cp210x.ko file and installing to the cRIO. This would work, but is beyond my current Linux capability.
    Linux gives the ability to dynamically add MID, VID so that a device can be recongized on the fly
    When the CP210x driver is loaded, an whole directory struchture is created. Ther is a file in that directory structure called new_id where we can dynamically added VID,MID's.
    Create a startup script to execute the following command. Be mindful of cr/lf line termination issues between operating systems. It's usually easier just to create the script on the cRIO with the VI editor to avoid any issues.
    echo 1FB9 100 >/sys/bus/usb-serial/drivers/cp210x/new_id
    Startup script info: https://decibel.ni.com/content/docs/DOC-38960
    Now on reboot (or execution of the script), you will get a /dev/ttyUSB[0-9] device
    Unfortunately, the default creation of the ttyUSB[0-9] device does not allow write permission, so we need to create a UDEV rule to automatically give write permission
    Add the following lines of code to udef.conf in the folder /etc/udev
    #typical devices
    ttyUSB[0-9]* root:tty 666
    Create a file named 99-ttyUSB.rules in the folder /etc/udev/rules.d
    Add this line of code to that file:
    KERNEL=="ttyUSB[0-9]*", OWNER="admin", MODE="0666"
    Reboot the cRIO. This should be it! It worked for me.

  • Is vision development module in labview 8.6. sufficient for real-time image acquisition and analysis using a webcam

    Hi, 
    I'm new to labview and trying to develop an eye-tracker using labview 8.6. It has the vision development module and i was wondering if this was sufficient for real-time image acquisition and processing or would i be needing any other software tools.
    Solved!
    Go to Solution.

    Hello, certainly it is possible and sufficient for real-time tracking!
    About eye tracking - if you need an example, you can find the code here:
    https://decibel.ni.com/content/blogs/kl3m3n/2013/10/08/real-time-face-and-eye-detection-in-labview-u...
    The code uses OpenCV functionalities along with the LabView UI (and some other functions like overlay).
    Hope this helps a bit.
    Best regards,
    K
    https://decibel.ni.com/content/blogs/kl3m3n
    "Kudos: Users may give one another Kudos on the forums for posts that they found particularly helpful or insightful."

  • Image acquisition not functioning after upgrading computer

    Hi all,
    I've run into a bit of a snag with our LabVIEW program. This program was written by someone that no longer works at my company and his VI scripts and installer do not exist, at least no where that we can locate. We've migrated the executable as well as the LabVIEW runtime environment over to a new Windows 7 PC (the original computer was running Windows XP). The program loads as it should but when it comes to the image acquisition within the program, the camera image is garbled and basically useless.
    Using NI MAX, I am able to detect the camera and I can set it to the settings from the original PC but the image is even scrambled inside NI MAX. The camera in question is an ATV Oscar F810C which is detected as such by NI MAX. I've updated the Vision runtime to the February 2014 build available on NI.com (about a 2GB download). Here are some screenshots of the original PC's settings in NI MAX:
    In reality, the image in NI MAX should look like this:
    On the new system with the same settings it looks like this:
    And when running the program on Windows 7 it looks like this:
    If I change the Video Mode to one of the lower res ones, such as the first greyscale 1024 x 768 option, the image stops being scrambled inside NI MAX and I'm able to see the image properly. However, the image acqusition inside the program still does the same thing. Without having any information on the contents of the program or access to the original files, it would appear to be some kind of driver issue since the setup works fine on the old system.
    Any ideas on what may be the issue?

    billko wrote:
    It may be that you have to download a WIn7 driver for the camera.  Dll(s) might be incompatible.
    Sorry, I did not see that that was one of the first things you did. 
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

  • How do I convert an IMAQ image buffer into an IMAQ Vision 'Image'?

    Using NI IMAQ and IMAQ Vision with LabWindows/CVI 6.0...
    I have some acquisition code that uses IMAQ img functions to set up a
    triggered image acquisition and stores the image into an 1D unsigned char
    array buffer.
    I would now like to add code that uses the IMAQ Vision functions. The IMAQ
    Vision function use an Image data type, which from what I can glean from the
    ..h files, is a structure.
    Is it possible to convert the 1D unsigned char array image buffer to an
    Image? How would I do this?
    An inefficiant brute-force way would be to write the image to a BMP file
    from IMAQ using imgSessionSaveBufferEx, then read the same file back in
    using IMAQ Vision imaqReadVisionFile. I am hoping there is a more elegant
    way to perform the conversion in memory without needing to write disk files.
    Thank you,
    Robert Rafuse
    Etec, Inc.
    tel: (978)531-5025
    e-mail: [email protected]
    web: http://www.etec-inc.com

    Bob Rafuse wrote:
    > Is it possible to convert the 1D unsigned char array image buffer to
    > an Image? How would I do this?
    Never mind. I found:
    http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3F11556A4E034080020E74861&p_node=DZ52490&p_submitted=N&p_rank=&p_answer=&p_source=External
    which indicates that the img functions actually return a 2D array, so I can
    use imaqArraytoImage after all.
    My bad.
    Bob

  • Image acquisition using video capture card

    I am developing an application for Single fiber fusion splicer...my application basically has to capture the picture from the splicer using a Video capture card...Is it possible to use IMAQ session to get the picture from the card,store it a file and display the same using labview??or is there any other suitable way instead of IMAQ???

    Cyril,
    A typical image acquisition system consists of the following
    components:
    Camera » Framegrabber board » Image Acquisition Software »
    Image Processing Software
    The software in this application is of course LabVIEW.  The ease of integration of it with your
    camera and framegrabber board is dependent on a number of variables and I
    discuss that further in the rest of this post.
    Camera
    It looks like you already have a camera picked out, but I could not find
    any information on the VHR-1000 on the internet.  Who is the manufacturer?  Can you provide a link to information
    available about it online?  NI does
    not actually make cameras; we simply connect with third party
    cameras.  We have a list of the
    various cameras that are tested and supported by our hardware available at
    http://www.ni.com/cameras
    Here are two more documents that will discuss camera options in more
    detail:
    Choosing A Camera
    http://zone.ni.com/devzone/cda/tut/p/id/3087
    Image Acquisition
    http://zone.ni.com/devzone/cda/tut/p/id/2808
    Framegrabber
    board
    The framegrabber board is what will be responsible for taking the signals
    from your camera, either digital or analog, manipulating them
    appropriately, and storing them in computer memory.
    The framegrabber board you choose will largely depend on the camera you
    choose and the interface it uses. (Interfaces are discussed in the Image
    Acquistion document mentioned earlier)
    It looks like you already have a Domino Maxi framegrabber board, which
    LabVIEW may or may not be able to interface with.  Could you please provide more
    information and possibly a link to some info on this framegrabber board?
    Choose NI Vision Hardware
    http://www.ni.com/vision/hardware.htm
    Image
    Acquisition Software
    The Image Acquisition software is the software responsible for bringing
    images into the computer in conjunction with the framegrabber board or
    IEEE-1394 bus.  Depending on your
    interface, you will need either NI-IMAQ (framegrabber) or NI-IMAQdx
    (IEEE-1394).
    Image
    Processing Software
    For image processing in LabVIEW, you will need the Vision Development
    Module.  It’s product page can be
    found here:
    Vision Development Module
    http://www.ni.com/vision/vdm.htm
    This software will enable you to do any type of image processing that your
    application may require.
    Those are the basic components of an image acquisition
    system.  Hopefully you will be able to
    follow those links and gain a better understanding of what exactly you need to
    be able to setup the kind of system you are looking for.  This presentation provides a great deal of
    general information and may be able to answer some more specific questions you
    have:
    Imaging Fundamentals
    http://www.ni.com/vision/vdm.htm
    It also discusses camera and lens selection with respect to
    the image size and detail that you need. 
    Please let us know if you have any further questions related to this.
    Regards,
    Luke H

  • Euresys Picolo image acquisition and LabVIEW

    Hi all,
    Unfortunately I have bee asked to use a Euresys piccolo image acquisition card in LabVIEW. I my case I only need to display the image on / on top of a LabVIEW front panel. Yes – I know it would have been much better to use an NI card but sometimes other people........
    Anyway my question is - has anyone out there managed a reliable interface to the piccolo dll yet? I’ve been looking at the ActiveX interface but it looks like an exceptionally tricky job. I see there are few previous discussions that will be of help should I have to start from a blank VI.
    Any advice appreciated,
    -Martin
    Certified LabVIEW Architect

    Hi Martin
    I have had a look for you this afternoon to see if I can find an example for you as to how to communicate to you Euresys frame grabber in LabVIEW but an example or driver is not available. It should though be possible to comunicate with your board using the manufacturers dll. You mentioned that you were aware of other forum posts that will be helpful in you starting to develope you code but I thought it might be helpfull to post some links below.
    Forum posts:
    Is it possible to use Euresys Picolo card with IMAQ vision and LabView?
    activex help!!!
    calling picolo.dll in Labview
    Other Resources
    Using External Code in LAbVIEW
    Integrating External Code with the Import Shared Library Wizard
    I hope this helps

  • Do I need LabVIEW RT for a simple 10objects/sec image acquisition/processing?

    I have a pretty simple application. A photoelectric sensor detects an object and triggers the image acquisition. The image of this object is then processed (a few morphological functions and particle analysis) and results are displayed in a table before a new image is acquired. The application also includes indicators for high/low limit, statistical calculations and a report generation. 7 to 10 particles per second are analyzed. Being still in the design phase, I use LabVIEW 7 Express. Do you think the LabVIEW Real-Time Module is necessary for my application?
    Thank you very much for your help.
    Bernd

    Hello Bernd,
    LabVIEW Real-Time is used to acquire robust and deterministic operation. It's basically a stripped down operating system that runs your application, and that's it. There's no additional software running in your background that can clog up the processing queue and lose the exact execution that your application requires.
    Yes, you could use Real-Time for your application, but I don't think it would be necessary. If anything, you may be limited by the hardware that you use and whether or not it will be able to acquire as many images as you would like in that short period of time.
    National Instruments does have a real-time Compact Vision System which you may not to inquiry further about. I would strongly suggest posting a very simi
    lar question to the Vision discussion forum to see what developers in that area think about your application. The numbers that you mention alone may light up a few light bulbs as to which LabVIEW target is generally used to reach the goal you desire.
    Hope this helps.
    Jared

  • When I buid an application, the vision image display is black.

    Hello !
    I have made an application using "vision image display". I have labview 7 express and vision builder 6.0. On labview, my application run very well and my image is displayed.
    I create an application with application builder 7 and I run it on a client computer with labview runtime engine 7.0 and IMAQ Vision 6.0 run-time engine. And my image is never displayed but stay black.
    Why ?

    Hello,
    I have a few questions concerning the problem. Where does the image come from, is it read in or is it from the harddisk. When the image is read in, which hardware do you use? I think you taked off the lens aperture and checked the contrast!? Check if the "vision image display" is correct licensed. Which Version is used from the "vision image display"? You can also check, when there is used any hardware if the drivers are the same on both systems. The current version is 2.6. With your answers, we should get a solution for the problem.
    ThomasD

  • Any way to repair iPad that has USB -- iTunes image without a computer?

    My parents‘ iPad won't boot and just shows a USB--> iTunes image.  They are using the iPad as their sole computer for a few months and are currently traveling, so they really need it. Is there any way to fix their iPad without hooking it up to another computer, or do they need to wait until they can get to an Apple store?

    Sorry, but there is no way activate the iPad, update the software, restore, etc. without connecting to iTunes on a computer.

  • By mistake i ereased my mackbook pro's disk. and when is restared it recovery page opened. and i did not purchase the osx mountain lion. do i have any other way to recory it without purchasing the copy of osx. can i do it using a usb having image file of

    by mistake i ereased my mackbook pro's disk. and when is restared it recovery page opened. and i did not purchase the osx mountain lion. do i have any other way to recory it without purchasing the copy of osx. ?can i do it using a usb having image file of mountain lion?

    Did you buy your machine second-hand? That's really the only way you would have to purchase OS X 10.8.x from the App Store... but, yes, if you have a USB thumb drive with a bootable installer (such as made with Lion DiskMaker) you can boot from that and reinstall OS X.
    Clinton

  • Why my image acquisition pci 1409 board could not be detected by matlab image acquisition toolbox?

    i have a National Instruments PCI-1409 image acquisition board that works very well
    with the software provided by National Instruments, whereas it could
    not be detected by matlab image acquisition toolbox when the command
    "imaqhwinfo" was executed. I don't know why. the system is XP and
    DirectX9.
    any of your advice will be greatly appreciated.
    thanks
    yours sincerely
    Jing
    [email protected]

    Is your matlab image acquisition toolbox DirectX based? If so, NI frame grabber will not work for your matlab image acquisition toolbox because it does not provide WDM or VFW drivers.
    Irene He
    [email protected]
    www.hytekautomation.com

  • The I Pod Touch Is Frozen. Only I Tunes Logo and USB Cable Image

    I was doing the new download and it said there was an error completing the upload..
    Now the only image on the screen is the I Tunes logo and the USB cable image. It will turn off but do nothing else.
    I tried resetting it and nothing happens. It will not do anything. It does not show on my computer or I tunes.

    This happened to me when the logo and cable comes on it either means that you have clicked to restoreit already try connecting it to itunes and click on the small little icon on the left of an ipod scroll down and click restore as nothing will happen if you don't restore it and syncing will not help it will stay the same.

  • CanOPEN cRIO-9067 & LabVIEW 2014 support

    Hello,
    We have cRIO-9067 and NI 9881 CANOpen communication module.
    According to the NI 9881 product description page the module should work with cRIO-9067. However, the latest NI-Industrial Communications for CANopen 1.0.3 doesn't support LabVIEW 2014 and NI RIO 14.0. This means we can't use cRIO-9067, can we? If so, when the next release of the driver will be availiable? Will it work with cRIO-9030?
    Thank you in advance,
    Nikita.
    Nikita Prorekhin
    Certified LabVIEW Developer
    DigiMetrix GmbH
    web www.digimetrix.com
    Solved!
    Go to Solution.

    Hi Nikita,
    This is an error on the webpage.  Currently, it should actually read:
    The NI 9881 module requires the NI cRIO-911x/9068/908x chassis and the LabVIEW FPGA Module.
    Support for the 906x and 903x targets will come with the NI-Industrial Communications for CANopen 14.5.  Typically, the release is around the time of the LabVIEW 2014 SP1 release.  I apologize for the inconvenience, and have reported this to the person in charge of the page to correct this error.
    Thank you!
    Matt S.
    Industrial Communications Product Support Engineer
    National Instruments

Maybe you are looking for