DAQmx device not no projection in LabView 2009

Similar Questions

• Imaging Source DFG/SV1 acquisition card is not correctly recognized in LabVIEW 2009

  I have an Imaging Source DFG/SV1 frame grabber/capture card (I think that this example uses a Bt878 chip) that I am using with LabVIEW 2009 (Fall edition 2009 academic Site license), including elements of acquisition of vision (NEITHER Vision, NOR-IMAQ (4.3) OR-IMAQdx (3.4), etc.). I have all the latest sources of imagery support drivers and software for the Board of Directors (http://www.theimagingsource.com/en_US/products/grabbers/dfgsv1/ drivers: v6.0.3.0, IC Software v2.1 and IC Imaging Control v3.1) with drivers being compatible DirectShow. The DFG/SV1 is detected in MAX under devices NOR-MAQdx / DFG/SV1 / cam0 and I can grab and preview images, however to 320 x 240 resolution, I have a higher resolution camera and know that the jury is capable of greater resolution using IC software manufacturing and also via TWAIN with ImageJ software drivers. Interesteingly, if I try to acquire an image of the card purchase using the Vision Assistant, the DFG/SV1 card is not recognized as a card acquisition, but listed under IEEE 1394 or GigE peripheral, revealing with it being direct device that I can't understand. Despite this I can acquire images, but I am limited to 320 x 240 format and change the type of image (RGB, UYVY etc) causes an error. Once again, oddly enough, I can use "enter and select mode example VI" which should only be compatible with IEEE 1394 cameras.

  I'm not sure why LabVIEW is not seen this card properly, I contacted Imaging source who were also intrigued by the fact.

  Any information on how this could be resolved would be much appreciated.

  Thanks in advance.

  Hi OCastell,

  With this Council Imaging Source, the only interface supported with drivers of NI Vision Acquisition is through using IMAQdx DirectShow interface. It is possible that their DirectShow driver does not properly support all of the capabilities of their Council. Given that ICR software and TWAIN support can be routed to a different implementation of one of the DirectShow support, you can see the different features available. Unfortunately, you probably go through Imaging Source to determine why their DirectShow driver does not support the full resolution. You can confirm that it isn't IMAQdx this limiting trying other software such as Windows NetMeeting or AMCAP DirectShow and see what capture resolutions are listed.

  Because the DirectShow interface is managed by IMAQdx driver, it will not be detected as a framegrabber IMAQ using the IMAQ driver. This is expected since it fits in the same category as firewire and GigE Vision cameras and is supported with the IMAQdx driver instead.

  The "Grab and select the Mode" example VI isn't really specific FireWire, although he was certainly intended to highlight the various video modes that generally expose FireWire cameras. Since the DirectShow devices are similar and have several selectable video modes, it's why he's probably working. In any case, IMAQdx abstracts usually differences between all supported camera types and in general a single VI can run on all cameras IMAQdx-taking in charge unless you rely on buses or the camera-specific features.

  Regarding Vision Assistant marking the camera as 'IEEE 1394 or GigE', I think it's just an aesthetic issue (which may already be fixed in new versions). When IMAQdx was out, these are the supported types of cameras and so Vision Assistant was trying to say clearly what driver was used for the type of device. Now that IMAQdx supports a multitude of new interfaces (including DirectShow and some IP cameras) that the label is inaccurate.

  Finally, looking at the specs for this capture card, it looks like a standard reference BT878/848 model and then you could try potentially replace your Imaging Source driver with one here:

  http://BTWinCap.sourceforge.NET/

  I used this with a with IMAQdx BT878 capture card and can get it to capture an image full resolution (but of course, your results may vary...). It goes without saying that this solution using DirectShow is much more limited than using an industrial camera on 1394/firewire or a framegrabber IMAQ.

  Hope this helps,

  Eric

• LabVIEW host could not download my_subvi.vi Labview 2009

  My problems started with the jump in Labview 2009. When I try to deploy my project during execution of the façade on my host and the remote control code, I get:

  Host LabVIEW cannot download my_subvi.vi. "my_subvi.vi" is a random under vi of the project. It can be different every time. This happens to my RT PC and so far not for PXI box.

  After talking with OR I downloaded the 2009 SP1 update and all other updates to run the RT kernel to version 9.01. I've updated the remote computer does not change.

  I also did a little test. I can run a simple empty code as a moment of pure looped and that is fine, but when I add a Subvi it gives me the same error each time.

  I have a quad core 2.4 GHz with 4 GB of RAM. A lot of memory and time processor. I used to run it with 8.2, 8.5.1 and had no serious problems.  My RT PXI seems to be good so anyway...

  Ideas?

  After talking to the consultant NOR I found the solution.

  It's all just stupid but works. I removed the second stick of memory - I have 2 + 2 GB of RAM; It works now. LabView RT apparently has problems with address more than 2 GB of RAM. I wonder if it has something to do with memory dual channel or not. What happens if I had 4 + 4 GB memory - would I have to buy 2 GB mem?

  Oddly enough, it was working fine with this configuration under Labview 8.2, 8.5, 8.6 and stopped at 2009 and 2009 SP1.

• Bluetooth device not no projection in sound-> output

  My bluetooth (speaker) device indicates 'Connected' in the list of bluetooth devices (in preferences-> Bluetooth system).

  However, I don't see it as an option when I go to Preferences-> sound-> release system.

  Any thoughts why? This has worked in the past, but not at the moment. I have not tried to restart my machine.

  Hi JVogue,

  Looks like you are unable to select your bluetooth device paired as a source of audio output to system preferences. I would start by pairing not your device:

  Remove a device from your Mac

  If you want to remove (désapparier) a device from the list of devices on your Mac, follow these steps:

  1. Choose the Apple menu > System Preferences, and then click Bluetooth.
  2. Place the pointer on the device you want to remove, and then click the button which appears next to the device name.

  Note: After you delete a Bluetooth device, you need to repeat the pairing process, if you want to use again.

  From: using a Bluetooth mouse, keyboard or trackpad with your Mac

  When that is done, start in safe mode. This will clear some system-level caches and perform a disk check and repair if necessary:

  Follow these steps to start in safe mode.

  1. Start or restart your Mac.
  2. As soon as you hear the startup tone, hold down the SHIFT key.
  3. Release the SHIFT key when you see the logo Apple appears on the screen.

  After the Apple logo appears, this may take longer than usual to reach the login screen or your office. This is because your Mac performs a check of directory of your drive to boot in safe mode.

  To leave safe mode, restart your computer without pressing any keys during startup.

  From: try safe mode if your Mac does not start-up

  Once you log in safe mode, that's all you need to do there, then restart your computer as usual using Apple > restart. Pair the device again, and then check that you can select as output. Thank you for using communities of Apple Support, all the best!

• cRIO-9073 not appearing is not in devices and Labview 2009 targets

  In MAX, I show the following: a cRIO-9073 with NOR-RIO 3.0.0 installed. My system software has NEITHER-RIO 3.0. In LabView 2009, when I try and add the cRIO to my project in LabView 2009 in New-> targets and devices, I don't have a list in time real CompactRIO and my cRIO does not appear. I tried to add manually with its IP address, but it does not work either. I've updated the cRIO to LabView real-time 9.0 software.

  Is there other software that I need to update on the cRIO so that it is visible in LabView 2009? Do I need a new version of NOR-RIO?

  Thanks for any help.

  Todd

  I upgraded from NEITHER RIO NOR-RIO 3.2.1 3.0 and LabView 2009 seems happy.

  See you soon,.

  Todd

• Failed to retrieve the DIAdem DataFinder research data, using data-finder toolkit LabVIEW 2009

  I am facing problem to retrieve the DIAdem Datafinder data.

  At first, I developed this project in LabVIEW 2010. But because of a problem that I met in LabVIEW 2010, I thougth to work on the project in LabVIEW 2009.

  Then, I reused the project that I created using LV 2010 using option economy for the previous version.

  When I tried to retrieve the data from the tiara using data finder toolkit. I got a 305505 warning. Please see the attached message of Warninig.

  But I have not seen this warning while I was working in LabVIEW 2010 and also, I was able to get the data from the tiara.

  Please suggest me a way to solve this problem.

  Hi Nanda,
  There is a bug when using the SDK use in combination with DataFinder Toolkit 2009.
  This bug is already fixed in LabVIEW 2010 and use SDK 2010. But as you said there is another question in LabVIEW 2010, forcing you to LV 2009.
  I suggest you use LabVIEW 2009 with use SDK 2009 and DataFinder Toolkit 2009 and instead to use the "Waveform.vi results" to read the search results, I would recommend to use the screw storage. I spread your example VI and it attached to this message. You will still see the dialog box to search for "lvStorage.dll" but it will automatically disappear and the VI works anyway because in this case LabVIEW will find the dll itself.
  My extended VI uses the '_openWithRoot.vi' to open a file with a different use than CT or PDM. This VI is also described in the following knowledge base article: http://zone.ni.com/devzone/cda/epd/p/id/4181
  With LabVIEW 2010 use support has been enhanced and fully integrated in the standard palette of storage screws. So in LabVIEW 2010, you can replace the "_openWithRoot.vi" with the 'Open Data Storage.vi' standard but with LabVIEW 2010, you can also use "Waveforms.vi results" to read the search results.

  I hope this helps.

  Kind regards
  Eva

• problem with a block of memory in labview 2009

  Hi all

  I have "ERROR: MapLib:979 - LUT4 symbol" during the compilation process (lots of errors like this), and I discovered that the reason of my problem is block of MEMORY.

  To be sure that the problem is in this block, I did a very simple project in LabView 2009 (on FPGA Target PCI5640R) only with the use of this block you can see in the photo, as well as in file test_memory block.lvproj attached link: https://www.dropbox.com/sh/u87f1oihelmm4dq/Jo_6-bICSf

  

  I have a problem with compiling VI with this block, and I have so many errors like:

  ERROR: MapLib:979 - LUT4 symbol
  "window/Thatcher/n_00000036/nSCTL_00000013_00000014/n_000000A3/cOutLoc<0>1.
  (output = window/Thatcher/res000001ed_wi<2>) is the input signal
  "window/Thatcher/res0000020d_wo<1>" that will be deleted. See Section 5 of the
  Map a report file to find out why the input signal will become conveyors.

  or

  ERROR: MapLib:978 - LUT4 symbol
  "window/Thatcher/n_00000036/nSCTL_00000013_00000014/n_000000A3/cOutLoc<23>1.
  (output = window/Thatcher/res000001ed_wi<25>) is an equation that uses
  input pin I2, which no longer has a connected signal. Make sure that all the
  the pins used in the equation for this LUT are signals that are not cut
  (see Section 5 of the report file map for details on which signals were
  adjusted).

  Entire report, you can see in the file report.txt on the attached link.

  I would appreciate if someone could take a look at my problem with simple project and suggest me a solution.

  I'm really stuck with my biggest project which need to have this memory block.

  I'm looking forward to hear from you,

  King looks

  ING. Damir Hamidovic

  Hi all

  I find a sollution to my problem.

  In memory-properties-general-setting up, I changed the block to look up Table memory, and I compile memory.vi and run it successfully.

  I did change as you can see on the picture:

  

  Just, can you tell me is it all "bad properties" and limits the use of this type of memory (Look up Table) of the implementation?

  King looks

• How to get USB-6009 DAQmx device instead of a USB device

  I undertook a LabVIEW app from a Windows XP laptop work a windows7 (32 bit) laptop. When I connected the USB cable from the laptop to my Flow Bench machine, that contains an NI USB-6009, he appeared in MAX under USB devices and not, as he always did before, under NOR-DAQmx devices. If the USB-6009 case is not recognized in my application.  When I tested the example Acq & chart voltage-Int Clk - SW Trig Restarts.vi, when I try to navigate to this device in this example, the search box is empty - no DAQmx device not found!

  How can I get this device 'live' under NOR-familiar DAQmx devices instead of strange USB peripheral area? What is going on?

  Thank you!

  Finally, you looked in the right place. As indicated in the page file or the file read me download, this version is not supported on windows 7. Download a newer version. Click on the 'Support' link at the top of the page.

• Can not find the daqmx device in project

  • In my project, which is great, now I can't access physical peripheral DAQmx using constants, the controls or express DAQ VI help.
  • When I try to use a constant or control [DAQmx physics channel] or [the DAQmx device name] no device appears.
  • LabVIEW stop half the time when I try to open the constant [DAQmx physics channel] or [DAQmx Device Name] project.
  • When I use NI MAX I can see the device, and control.
  • The unit is a box of data acquisition National Instruments M 6289 USB series. I have only this style of machine. I have two of 6289 and have tried both.
  • If I create a new VI not in my project it works.
  • I've updated the NEITHER-DAQmx software on my PC and found no change.

  There the project settings for DAQmx? I can't found.

  Everyone comes through this?

  LabView 2014 f1

  Measurement and Automation explore 15.0

  NOR-DAQmx ADE 15.0.1 support

  NOR-DAQmx Base 3.4.5

  NOR-DAQmx Device Driver 15.0.1

  NOR-DAQmx Max Configuration 15.0.1

  Material:

  Model: NI USB-6289 M Series data acquisition device

  Calibrated: 10 June 2017

  Driver version: 15.0.1f3

  Driver name: NOR-DAQmx

  System:

  Dell Vostro 460

  CPU i7-2600

  memory 8 GB of ram

  Operating system Windows 7 pro

  

  

  This error is cleared after two days.  I'm unable to replicate. regardless of the question has been reset is not a cure.

  It's the second mystery LabVIEW question who cause great suffering which allowed himself without any reason.

• How to synchronize or trigger OR-DAQmx devices in LabView

  I'm using LabView 2009 with a cDAQ-9174 chassis which includes an NI 9263 analog peripheral and an NI 9222 analog input device. I learned in the examples that I can synchronize the devices at the same sample rate. But I'm looking to sync devices such as the exact moment where I start to acquire input channel 9222, the 9263 begins to generate output. Secondly, I am interested to know when to use just this material, is it a way to very precisely to trigger a device turned off each other with a certain delay. So in summary I am interested in two behaviors:

  (1) to synchronize an output channel 9263 to an input channel 9222, such as the beginning of a measure of analog input 9222 triggers a 9263 analog waveform output. and,

  (2) have the analog output of the 9263 beginning for example EXACTLY 100 samples (provided that the sampling rates are synchronized) after that the 9222 starts to collect data. In other words, a trigger delay.

  I guess that preference for it in hardware such as no software delays occur. Is this possible using these devices? Or do I need an external synchronization mechanism?

  Thank you!

  Hi tzoom84,

  Back to your original question,

  (Make 1) and (2), I don't think you should use counters.

  Shipping example LabVIEW 2010\examples\DAQmx\Synchronization\Multi-Function.llb\Multi-Function-Synch I - AO.vi is probably a good starting point for 1). (Possible problem: If you use several engines timing to HAVE at the same time, the hypothesis of this example that the task of the AI "AI/StartTrigger" is not valid.) If this proves to be a problem, you may need to replace the name of Terminal get with device Prefix.vi with the trigger DAQmx > Start.Term property and add a call to the reserve of the task.)

  For 2), add the trigger of DAQmx > Start.Delay and trigger DAQmx > Start.DelayUnits properties of the task of the AO:

  

  If you really need to use counters, you can do without the NI 9401 using cDAQ1/_ctr0 by cDAQ1/_ctr3, which are internal channels: How to internal access on any device DAQmx?

  Brad

• LabVIEW 2009 32 bit does not not on xp 64-bit

  Hi all

  I tried to upgrade to LabVIEW 2009 LabVIEW 8.6 on the XP machine 64-bit windows. After about a deletion of 2 hours of installation 8.6 and later of LV 2009 it turns out that the device drivers are not compatible with a 64-bit computer. At the launch of LabVIEW 2009 (32-bit), an error box is displayed indicating that it is corrupt or missing files and to fix this using the control panel etc. I tried this and still the same error occurs and LV refuses to start.

  All license files are correct and the components are enabled.

  Someone knows how to fix this? Or do I go back to 8.6 and cancel my subscription?

  Second, I use a firewire camera and was informed that neither IMAQ legacy are more supported and go to ni.com/ifo and enter legacy1394 to see how to download drivers for that etc. I find myself on a page that says no "authorized".

  Any help appreciated gratefully.

  Dear Leeser

  Since 2006, National Instruments has annually released a new version of LabVIEW each month of August in order to establish a more predictable release schedule. This allows users to better plan the new developments and improvements for future versions of LabVIEW. In addition, this year, NOR changed the name of the product to LabVIEW + year (for example, LabVIEW 2009) reflecting the year of the release and setting the stage for future annual editions of LabVIEW. Please see the following site for more information on this:

  http://www.NI.com/LabVIEW/product_lifecycle.htm

  What about Windows XP 64-bit it is not officially supported by hardware or software drivers. For a list of drivers who have been known to work, please see the link below:

  http://Joule.NI.com/nidu/CDs/fn/p/SN/N19: Windows.7809/lang/en

  Now with Windows Vista x 64 is a 32-bit compatibility of excellent "windows on windows" mode which allows our drivers work correctly. In regards to LabVIEW 2009, there is now a dedicated 64-bit version is recommended for use with 64-bit operating systems. Yet once Windows XP 64-bit is not officially supported.

  More details on the compatibility of Windows XP x 64 is located in the following article:

  http://digital.NI.com/public.nsf/allkb/C4EC0C87B6D70AA886256E61006568C8?OpenDocument

  I hope this helps to clarify some things.

  Kind regards

• LabVIEW 2009 executable will not manually load screws

  Before LabVIEW 2009 I was able to create an executable file containing a main VI which was empty. When this executable has been launched, I could open the other screws on the system through file-> open from the empty main VI. I used this to check distributions of llb for missing/bad behavior screws on systems with just running LabVIEW. Now in LV2009 when I load a VI through this method... nothing. No charge. No error. NOTHING.

  'Function' or a bug?

  I have not tried to reproduce this, but a valid solution would be to add a couple of features to the stub executable to do the following?

  • Dialog box file to find a VI
  • Reference open VI
  • FP. Open method

• A distribution source created in 32-bit LabView 2009, explains that the screws are not executable when opened in LabView 2009 64-bit. How do the main screw?

  A source distribution was made for a VI using LabView 2009 32 bit. The distribution has been verified to work on another machine which ran 32-bit LabView 2009. However, when opened on a 64-bit LabView 2009, the VI was broken as indicated by the error message attached. How can I make the executable VI?

  The VI used the noise and vibrations and HSDL screw that I suspect don't are not supported in 64-bit.

• Match pattern does not not in LabVIEW 2009

  Hi all

  The match pattern does not not for ' [' this symbol in LabVIEW 2009] Kindly help me how to solve this problem.

  Thank you

  Sivabalan.V

  See the attached picture. Please check the response as a solution that you think best responds to your question.

  

• LabVIEW 2009 + Labview 8.6 vision = work not...

  Hello

  At my University, I got a license for Labview 2009 + Module Vision 8.6... Now, I installed Labview first of course. And when I was done I installed the vision module. The two facilities went very smooth. Now when I run labview I do not have access to any labview vi vision that must be provided.

  Like what I have read here http://www.ni.com/support/labview/lvtool.htm#vision_development the module must be compatible with labview 2009... If someone can explain to me why it is not appear in labview 2009?

  Hi Wouter,

  Please visit the following link: http://digital.ni.com/public.nsf/allkb/244E6DDF9A92A6CD8625730100629047?OpenDocument

  The NI Vision Development Module is not compatible with LV 2009.

  With sincere friendships.

  Casper