Fglrx module conflicts with labview 8.2

Hi, i need your help.
My graphic card is ATI x1300, and i am using slackware 12.1. This distribution used mesa for graphic driving by default and worked well with labview 8.2.
After i disable the Direct Rendering Manager of linux kernel config and recomiled the kernel(2.6.21.5) and installed ATI officail driver successfully, reboot, labview got the "segmentation fault" error. I confirmed that fglrx module loaded with nothing error.
Then i remove fglrx module and use Mesa instead, reboot, labview works fine.
Any idea to deal with this problem? Or is this a known bug? I want to use fglrx for graphic driving.
Thank you!

On Oct 1, 10:10 am, jonasdias <[email protected]> wrote:
> i have a labview profissional developement system 8.2.1!i thinks that is is possible make a dll but i dont find this Tools»Build Application or Shared Library (DLL)
> i see this in this site: <a href="http://zone.ni.com/devzone/cda/tut/p/id/3063" target="_blank">http://zone.ni.com/devzone/cda/tut/p/id/3063</a>
Two suggestions
Double check and make sure you have the Professional Development
version of Labview. Do this by starting Labview ant then clicking on
"Help" and "About Labview" The "About Screen" will tell you what
version of Labview you have installed on your computer. If the "About
Screen" says you have the Professional Development version of Labview
installed on your computer and you don't see "Application Builder" in
the "Tools" menu then I suggest you talk to your local National
Instruments Sales Representative to get help.
Howard

Similar Messages

  • What are the different 'Add-on modules' available with LabVIEW?

    What are the different 'Add-on modules' available with LabVIEW?
    What are the types of 'Add-on Cards'?
    Cards and modules are different,thats true.Is it that modules means software and are they same as 'add-on toolsets'.Please give the details/URL which would give me various toolsets in detail and also the specifications of various add-on cards?
    Kindly do the needful
    I require these details immediately.I am an Engg student and learning LabVIEW

    duplicate post

  • B&R Powerlink Ethernet module support with LabVIEW

    Hello Guys,
    I wanted to use the B&R Powerlink Ethernet module for one of my industrial applications where in I am planning to use cRIO system for the control but my drives ACOPOS 1022 servo Drive requires this module B&R Powerlink Ethernet module. The link is
    http://www.br-automation.com/cps/rde/xchg/br-productcatalogue/hs.xsl/cookies_allowed.htm?caller=prod...
    So i wanted to check the compatibility of LabVIEW with this particular module and if there is any option for me to program or atleast communicate with this module directly via LabVIEW? This will help me finalize my system and go ahead and start building.
    Looking forward for some responses from everyone who has worked with similar setup.
    Thank you so much in advance.
    Regards,
    Priyank Desai.

    Hi,
    unfortunatelly servodrives from B&R have no open programming interface, so you can not programm them from LabView.For operating B&R servodrive, B&R CPU is a must. This is because operating system of servodrive and all necessary parameters are stored at B&R CPU to guarantee trouble free run always. B&R serfvodrive ACOPOS is not for "component business".
    You can listen and command them, when there is a B&R master CPU and servodrive is configured for that.
    Following B&R product are Powerling standalone with no need for CPU:
    ACOPOSinverter P74/P84
    X20 IO system
    X67 IO system
    B&R CPU is required for ACOPOSmicro, ACOPOS, ACOPOSmulti ACOPOSm65 servodrive systems.
    I suggest to contact local supoort of B&R at your country and they will help you how to connect this drive with LabView.

  • Intel Hyper-Thre​ading Technology conflicts with LabVIEW utilities (VISA, Scope GUI, IO Trace...)

    I would like to share a pretty hard-to-troubleshoot issue we are experiencing for the last few months.
    Our company used to get DELL T5500 for our engineers. The PCs work just fine with all LabVIEW utilities. But DELL has discontinued T5500 series and replace them with T5600. I got one of them few months ago and after installing LabVIEW, I tried to run VISA console via MAX. It immediately crashes MAX and destroy MAX database. After that I try to run other utilities like NI IO Trace, VISA Interactive Control, Scope Soft Front Panel, ... All of then crashed. I am running 64-bit Windows 7  + 64-bit LabVIEW. And we know that most of NI Utilities are 32-bit.
    After a lot of frustration I went down to researching the computer BIOS level. And try to side-by-side compare with T5500. T5600 has much newer CPU and has  lot more performance enhancement features. I tried to turn of/on one by one to see if any affect LabVIEW utilities. To my surprise I found that Intel® Hyper-Threading Technology (Intel® HT Technology) is the sinner. After turning it off all LabVIEW utilities start to work just fine. All T5600s are shipped with this feature enabled by default.
    We know that DELL Precision PCs are almost industry standard for all engineering department. I think in the next few years a lot of people will be hit by this issue. I already notified NI and DELL R&D so they can find a good solution. But I just would like to make this issue Google-searchable so that anybody see this issue may get some help.
    Give me any feedback if you encountered the same problem.
    Thanks,

    This means that you were on a witch hunt and hyperthreading is not the problem. (I always had doubts).
    The original thread was about crashes in the visa console, but your problems seem to be much more generic:
    "- The application stalls unpredictably after some time, sometimes a minute, sometimes hours. After clicking into the GUI it starts working again. This repeats in an unpredictable way. Competitive activities on the computer seemed to increase the stalling-frequency.
    - Sound Input VI stops unpredictably and has to be restarted."
    Are you sure you don't have a general code issues such as race conditions or deadlocks. Maybe you should start a new thread and show us a simplified version of your program that still demonstrates the problem. If there are race conditions, moving to a different CPU can cause slight changes in execution order, exposing them.
    Did you repair the LabVIEW and driver installation? What are the power settings of the computer? Did you update other drivers (such as video, power management, etc)
    What is the exact CPU you are using? What third party utilities and security software is running on your PC?
    LabVIEW Champion . Do more with less code and in less time .

  • Help with x64: fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'

    Hello, I am trying to complie some C code for some applications I am working on in labview (I am using Labview 2012 64bit).
    When I try to build my code in Visual C++ 2010 ( I have set it up to be able to use x64) I get the following fatal error:
    nivision.lib(StartupShutdown.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
    Which I understand that .lib does not have a 64bit compatability. However, if I were to use 32bit code, how can I link/emulate it to my 64bit labview? Is there a good tutorial on this application? The problem is the rest of my application uses and requires 64bit labview, so I am stuck in this enviroment.
    Thanks.

    dbrittain wrote:
    Thanks for the reply. The C code I have cross correlates images, and it does reference the image inputs and size variables from the nivision classes. I am thinking of using a side by side labview environment with shared variables. I have not done this before, do you have any good examples? Can you make the library function node a shared variable or only the elements within it? 
    I guess I could try to convert to labview, but the are a lot of lines of code that I would prefer not to try to wrap my head around in translation.
    The LabVIEW API in Vision Development Module has functions that let you get access to all those parameters as well as the raw image data pointer. A common design is to query those items on the LabVIEW diagram and then pass them to your DLL. This would mean you wouldn't need to make any calls into the Vision DLL from your C code.
    As for examples showing how to use shared variables, keep in mind that it isn't just like doing a function call. The more appropriate way to think of it would be communicating with another VI by getting and setting controls and indicators while it runs. You could put all your arguments into a shared variable and set a boolean indicating it is ready, then wait for another boolean to go high indicating the other code has finished and placed its results in another shared variable. Your application code interacts with the shared variables just like a control/indicator/local variable. This of course is a simple description and I would not be surprised if there are well-defined frameworks/examples searchable in the forums that use shared variables in this manner.
    Eric
    Eric

  • Unload All Modules sometimes doesn't work with LabVIEW

    TestStand's File >> Unload All Modules (and its RunState.Engine.UnloadAllModules() function) sometimes works and sometimes doesn't (with LabVIEW). When it doesn't, I have to quit LabVIEW to make TestStand unload LabVIEW VIs, otherwise I can't edit them.
    Is there an "Unload All Modules" command that works all the time?

    Hm, i assume that you have callbacks defined which do call those modules. Possible callbacks to look first are: SequenceFileLoad/Unload, FrontEndCallback.
    Another possible reason is that there are components running in the LV RTE (runtime engine) calling into the VIs you try to debug/modify in the development environment.
    Can you pinpoint the "lock" to specific sequences/modules? Do they lock only after specific sequences/modules have been executed?
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Can LabView FPGA module work with non-NI FPGAs?

    Simple Question: Can the LabView FPGA Module work with other FPGAs? Im assuming yes, but id like ot make sure first. Normaly I go with NI for most of my stuff, but they just are lacking in the FPGA hardware for what I need, but Im accustumed to LabView so I would like to stick with that to program it.
    Thanks!
    -Mark

    Using LabVIEW and LabVIEW RT you can access the registers on any PCI/PXI card using the NI-VISA driver. NI-VISA also allows you to handle interrupts and DMA data. For interrupts you will not actually write an interrupt service routine (ISR) in LabVIEW. Instead the VISA driver will acknowledge the interrupt to the card and then pass a VISA event to the LabVIEW application letting the application know that it needs to process the interrupt. Detailed information about this type of programming is available in the following documents.
    Using the VISA Driver Development Wizard and NI-VISA to Register-Level Program a PXI/PCI Device unde...
    Configuring LabVIEW Real-Time and NI-VISA to Recognize a Third Party Device
    Configuring LabVIEW Real...
    Developing a LabVIEW Real-Time Driver for a PXI or Compact PCI Device
    Porting a Windows PCI Device Driver to LabVIEW Real-Time
    Considerations in Implementing LabVIEW Real-Time Drivers
    Christian L
    Christian Loew, CLA
    Principal Systems Engineer, National Instruments
    Please tip your answer providers with kudos.
    Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
    or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
    to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense

  • Module machine type 'x64' conflicts with target machine type 'X86' - opencv_highgui

    Hi , 
    Im trying to setup the opencv for c++ in visual studio i have completed setting it up. when i run the sample code i get the error as 
    error LNK1112: module machine type 'X86' conflicts with target machine type 'x64
    C++\FinalPro\FinalPro\opencv_highgui249d.lib(opencv_highgui249d.dll)
    I have set also x64 instead of win32 default but still its not working the lib of open cv are all 64bit
    Thank You , Shan Ali Khan

    Hello,
    Welcome to MSDN forum. But your issue is out of support range of VS General Question forum which mainly discusses
    the usage of Visual Studio IDE such as WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
    and Visual Studio Editor.
    I found some thread with similar issues, maybe they can help you:
    http://social.msdn.microsoft.com/Forums/en-US/34cf5a42-16a7-4d77-b708-0830276bbab9/module-machine-type-x86-conflicts-with-target-machine-type-x64?forum=vcgeneral
    http://social.msdn.microsoft.com/Forums/en-US/d5bc5b38-6086-4f7c-a011-fc50901b9288/lnk1112-module-machine-type-x86-conflicts-with-target-machine-type-x64-error?forum=vcgeneral
    If no help, for Visual C++ development issues please post them in
    C++ forum, but those issues related to OpenCV which belongs to third-party are not supported in MSDN forums, you could consider consulting its publisher to get supports.
    Thank you for your understanding.
    Best regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Conflict of visa32.dll​, since update to Labview 8.0 conflict with TEK software

    We are Tektronix customers and with Labview
    7.1/MAX everything was working ok with their software to communicate
    with the oscilloscope from the PC. However, since upgrading to Labview
    8.0 on system startup (XP) we get a message:
    >
    >"Tekvis.3
    >
    >The iInstalled visa32.dll is not a Tektronix
    version of VISA. Either disable this program by removing it from the
    startup directory of re-install TEKVISA."
    >
    >Obviously we would like to carry on using
    Labview 8.0 and MAX, but also the Textronix software to grab
    oscilloscope measurements without having to swap between these two file
    versions. I re-installed Tektronix software but then MAX stopped working
    from the NI suite, hence no devices could be seen. I presume that NI
    will not be re-writing their new visa32.dll file to be backwards
    compatible, will Tektronix be releasing a newer version of the software
    that can use the new visa32.dll file? Or perhaps a visa32.dll file
    compatible with MAX etc?
    I have contacted Tektronix but I got this: "Unfortunately I only have LV 7.1 and, like you, it seems to work fine
    for me. A collegue of mine tried this out with abview 8 and didn't seem
    to have any problems. Have you contacted NI regarding why TekVisa works
    with Labview 7.1 but not version 8?
    >Hope you can help,
    >
    >Best regards,
    >
    >
    >Daniel Hill

    Hi DaniBCN
      What versions of software are you using? LabVIEW 8 but what about NI-VISA? . You can download the lastest versions from ww.ni.com/downloads.
      What scope are you using? What bus (GPIB, ENET, USB)? Here is a great resource to comunicate with tek scopes
    http://digital.ni.com/public.nsf/websearch/202E144​63D2D819F86256C39005D7828?OpenDocument
      I know NI has a great relationship with tektronics (tek has a LV version inside the open scopes, NI has develop a specific version of SignalExpress for Tek scopes)
    Hope it helps.
    Javier Gutiérrez
    NI Aplication Engineering

  • Fglrx: module mismatch after last upgrade

    Ok, I know what it means and I know that everything should work...but it doesn't 
    After yesterday upgrade of xorg-server the ati-drivers conflict with the new version
    X Window System Version 7.1.1
    Release Date: 12 May 2006
    X Protocol Version 11, Revision 0, Release 7.1.1
    Build Operating System: UNKNOWN
    Current Operating System: Linux kortirion 2.6.17-beyond #1 PREEMPT Sun Jul 30 13:09:32 CEST 2006 i686
    Build Date: 09 September 2006
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 11 12:12:22 2006
    (==) Using config file: "/etc/X11/xorg.conf"
    (EE) module ABI major version (0) doesn't match the server's version (1)
    (EE) Failed to load module "fglrx" (module requirement mismatch, 0)
    (EE) No drivers available.
    Fatal server error:
    no screens found
    XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
    after 0 requests (0 known processed) with 0 events remaining.
    I've done some researches and even using startx -- -ignoreABI doesn't help:
    X Window System Version 7.1.1
    Release Date: 12 May 2006
    X Protocol Version 11, Revision 0, Release 7.1.1
    Build Operating System: UNKNOWN
    Current Operating System: Linux kortirion 2.6.17-beyond #1 PREEMPT Sun Jul 30 13:09:32 CEST 2006 i686
    Build Date: 09 September 2006
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 11 12:15:57 2006
    (==) Using config file: "/etc/X11/xorg.conf"
    (WW) module ABI major version (0) doesn't match the server's version (1)
    [R200Setup] X version mismatch - detected X.org 7.1.1.0, required X.org 7.0.-1.8
    (EE) Failed to load module "fglrx" (module requirement mismatch, 0)
    (EE) No drivers available.
    Fatal server error:
    no screens found
    XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
    after 0 requests (0 known processed) with 0 events remaining.
    I've tried also the newest ati drivers ( 8.28.8 ) with no luck (and btw the current PKGBUILD doesn't work too, it complains about a already existing links to Makefile.lib.c; applying the patch ati-makefile-2.6.16.patch correct the problem).
    The open source's ati drivers work, and I'm using them now. xorg.conf hasn't changed at all and, no, generating one new with aticonfig doesn't solve the problem.

    I got it working now 
    At first, compiling ati-fglrx-beyond with the Cerebral's pkgbuild they gave me this error:
    make: Entering directory `/usr/src/linux-2.6.17-beyond'
    ln: creating symbolic link `./Makefile.lib.c' to `../scripts/Makefile.lib.c': File exists
    make[1]: *** [scripts/Makefile.lib.c] Error 1
    make: *** [_module_/var/abs/local/ati-fglrx-beyond/src/lib/modules/fglrx/build_mod] Error 2
    make: Leaving directory `/usr/src/linux-2.6.17-beyond'
    ok, let's remove that link then, I thought. But after having done that:
    make: Entering directory `/usr/src/linux-2.6.17-beyond'
    CC scripts/Makefile.lib.o
    gcc: scripts/Makefile.lib.c: No such file or directory
    gcc: no input files
    make[1]: *** [scripts/Makefile.lib.o] Error 1
    make: *** [_module_/var/abs/local/ati-fglrx-beyond/src/lib/modules/fglrx/build_mod] Error 2
    make: Leaving directory `/usr/src/linux-2.6.17-beyond'
    That was weird  :?
    After googling a bit, I've found an idea from the ubuntu forum where it says to run
    make scripts/
    from /usr/src/linux-$kernver/ ; after a little wait time to allow the compiling, I retried to make the driver compiling and this time they worked flawlessly 
    No more module mismatch, I wonder why I didn't have that Makefile.lib.c in the kernel source directory....
    Anyway, thanks for your help Cerebral

  • Flash Player 10 does not work in IE or Firefox. What could it conflict with?

    I'm  using Firefox 3.6.8 (and sometimes IE 8.0.6001.18702IC) on Windows XP Pro, SP 3.
    For some weeks now, I have been unable to hear any sounds on anything Flash-based, from YouTube to games at MSN.com or embedded videos on any site using Flash.  Initially I had assumed it to be because of having QuickTime installed because I know QT likes to hijack everything.  I uninstalled QT (and Real Player) and Flash Player then reinstalled Flash Player (and Shockwave Player just in case) and guess what?
    Yup.  Nothing.  When I uninstalled everything, I used a program called Revo Uninstaller, which includes a registry cleaning option.  I then used Abexo and WinASO's registry cleaners to make sure I got everything else that even looked like QuickTime off my hard drive.
    When I reinstalled Flash, the following programs appeared in C:\Windows\system 32\Macromed\Flash:
    Flash 10i.ocx (10.1.82.76)
    FlashUtil10i_ActiveX (10.1.82.76)
    FlashUntil10i_Plugin (10.1.82.76)
    genuinst (6.0.2800.1531)
    FlashUtil10i_ActiveX.dll (10.1.82.76)
    NPSWF32.dll (10.1.82.76)
    KB931433
    FlashInstall
    Install
    Flashplayer.xpt
    When I check IE's "Tools" and look for add-ons, it says that Flash (Shockwave Flash) is enabled.  I even enabled the other Adobe add-ons for Acrobat and such just to be sure.  Firefox shows Shockwave Flash and Shockwave for Director both to be enabled.  The Flash control panel settings don't help: I have all sites set to store about 100 KB on my computer to make sure there's enough room for everything but still nothing.
    Before anyone asks, my audio drivers are up to date, thanks to the manufacturer's website.  I have DirectX 9.0c installed and everything else works fine.  I can play audio and video elsewhere with no problems.  It's only Flash that's showing me this trouble and there's no hint as to what else could be interfering with Flash.
    Any ideas?

    Well, great.  I tried the uninstall/reinstall before, but not with the uninstaller, so I was hopeful that this time might do it.  No such luck.  The video still plays, but no sound.
    All the sound settings are working with everything else from games to media players.  I set Windows' firewall to allow both the ActiveX and plugin for Flash, just in case.
    In the Flash folder, I now have:
    Flash10l.ocx (10.1.102.64)
    Flash Util10l_ActiveX (10.1.102.64)
    FlashUtil10l_Plugin (10.1.102.64)
    Genuinst (6.0.2800.1531)
    FlashUtil10l_ActiveX.dll (10.1.102.64)
    NPSWF32.dll (10.1.102.64)
    And the setup and text files that went with 'em.
    I've also done a system restart since then and zip.
    I went through IE and Firefox and looked for any file associations (like .flv) that I could manually change over to using Flash, but no go.  The settings panels for Flash have all been set to allow YouTube specifically (as a test) and to allow 10KB of storage space for all affected sites.
    Now what?  I'm really not looking forward to a reformat and reinstall, but it's looking like that's what it's going to take.
    Date: Sun, 14 Nov 2010 17:37:07 -0700
    From: [email protected]
    To: [email protected]
    Subject: Flash Player 10 does not work in IE or Firefox. What could it conflict with?
    Something is strange with your list of modules; you list FlashUntil10i_Plugin (10.1.102.64), but this is really 10.1.85.3
    I recommend that you uninstall Flash Player completely (using http://kb2.adobe.com/cps/141/tn_14157.html), then restart Windows, and delete all remaining files in C:\Windows\system32\Macromed\Flash.
    Next reinstall both ActiveX (http://fpdownload.adobe.com/get/flashplayer/current/install_flash_player_ax.exe) and the plugin (http://fpdownload.adobe.com/get/flashplayer/current/install_flash_player.exe).
    After that, if the problem persists, have a look at this page http://kb2.adobe.com/cps/837/cpsid_83739.html
    >

  • Windows 7 Compatability with Labview 8.0 and missing files while interfacing the FPGA with LV

    I am trying to use an FPGA (PCI-7830R) with Labview 8.0. The computer has Windows 7 OS. I installed LV 8.0 in the proper order with the FPGA Module and labview is able to see the FPGA when I open a .lvproj (the FPGA is in the tree) however there is a warning symbol next to the FPGA selection and when I try to open a .vi file that is used on the other stations in my lab (it works on all the other stations), labview is unable to find a whole bunch of files. There are some pictures.
    Missing File (there are a bunch more but this is the fist one).

    According to this LabVIEW Compatibility LabVIEW 8.0 is NOT compatible with Windows 7
    Visualize the Solution
    CLA
    LabVIEW, LabVIEW FPGA

  • Is it possible to get 2-ch signals from TDS2012 oscilloscope at the same time with LabVIEW "7.0"?

    Hi, everyone.
    I've been trying to get the signals from 2-ch of Tektronix TDS2012 oscilloscope at the same time using IVI connection with LabVIEW "7.0"
    I've already searched this developer zone for the answer.
    I've tried the famous example: "IviScope - Acq Dual Wfm Edge Triggered.vi"
    and it gave me the error message like:
    Error -1074110451 occurred at IviScope Initialize With Options.vi
    Possible reason(s):
    Driver Status:  (Hex 0xBFFA600D) Primary Error: (Hex 0xBFFA600D) The Config Server module is not present on the system.
    I think I've installed all~ the required softwares for IVI. For example, ICP 2.2, IVI engine 2.0.46, and tktds1k2k ivi (instrument driver for tds2012, in fact this one is for LabVIEW "7.1"... :-P)
    TDS2012 and my computer is connected through HPIB(GPIB) and it is shown on the MAX (a GPIB instrument as well as an IVI hardware asset)
    I've tried GPIB connection but it gives me asynchronous signals...
    Is it possible to get 2 signals at the same time with LabVIEW 7.0(not 7.1 or higher) by any means?
    What in the earth is the "Config Server" in this case?
    I don't need to sticking to IVI and any method to achieve my goal will be welcome.
    Could anyone give me the hint for this problem, plz?

    I think your problem is that the instrument specific driver is version 7.1 and you are using the class driver with 7.0. You can create your own 7.0 driver by downloading the LabWindows driver and using the Import CVI Instrument Driver under the Tools>Instrumentation menu.
    Since you don't seem to have a good reason to use IVI, why don't you try the native LabVIEW driver at http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9139659CE034080020E748.... I believe you have all of the functions to setup each channel and then when you trigger the scope, both channels will be captured. You would then transfer each waveform separately. The data is always read sequentially but that's not important as long as both channels are triggered at the same time.

  • Need instructions on how to get Quanser working with LabView 7.1

    I need information on what LabView modules or addins to install in order to run Quanser (QNET Experiments release 2.2).  LabView 7.1 is loaded but we also have LabView 7.0 if needed.

    Hello JND,
    The Quanser website indicates that the QNET products are fully
    compatible with LabVIEW and NI Elvis. However, I could not find more
    information on any drivers they provide for LabVIEW, so I suggest you
    contact them directly about this. If they have drivers written for
    LabVIEW, that should be enough to communicate with the board from
    LabVIEW. In order to communicate to NI Elvis, you need to install
    NI-DAQmx and NI ELVIS drivers available at this page.
    Good luck and best regards,
    Shakhina P.
    Applications Engineer
    National Instruments

  • How can I set the SRQ bit on GPIB with LabView ?

    Hello,
    I am developping an application with LabView RT on a PXI RT system. This application acts as an instrument (non controller GPIB), and I need to assert the SRQ line. How can I do that ?
    I know the ibrsv function, but I can't find it in LabView, and I can not use it through a DLL call since GPIB DLLs are not compatible with Real-Time.
    Thank you.

    Hello Alfonso,
    It sounds like you might be getting errors -200279 and -200278.  (In the future, if you post the actual error codes, it helps us to know exactly what is happening).  Error -200279 happens when you are performing a hardware-timed acquisition (meaning the data is sampled according to a clock signal on your board), but your LabVIEW program is not reading the values from the buffer allocated for that task in computer memory fast enough.  Basically it's a buffer overflow error.  It means older samples have been overwritten before you attempted to read them out.  As the error message suggests, "increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all available samples might correct the problem."  For more information on this error, please see the KB (DAQmx) Error -200279 During a Continuous, Buffered Acquisition.
    Error -200278 happens most often when you have configured a finite acquisition, but are calling the DAQmx Read function in a loop.  If you want to perform a finite acquisition, you should only call DAQmx Read once.  For more information on this error, see the KB Error -200278 at DAQmx Read.
    Finally, please refer to Abhinav's earlier post about the sample rate on the 9237 module.  As he described, the NI-DAQmx 8.3 driver will only allow you to set the sample clock to integer divisions of 50k (50,000/n, where n can be 1, 2, 3...13).  Since the maximum divisor is 13, the smallest sample rate that can be used is 3.846 kS/s.  You can check what value the driver is actually using for the sample clock by reading from the SampClk.Rate property of the DAQmx Timing property node.
    I hope this helps!  Let me know if you have any questions about what I've described.
    Best regards,

Maybe you are looking for