VISA Driver Development Wizard

I found a reference to this great document called
Using the VISA Driver Development Wizard and NI-VISA to
Register-Level Program a PXI/PCI Device under Windows.
As I described in another post, I am having performance problems
using AccessHW to talk to a legacy ISA board under XP compared to
Win2k where performance was decent.
To rule out AccessHW as the problem and confirm that it is an
XP/hardware issue, I'd like to try another method of
reading memory at address 0xE0000-0xEFFFF.
Since the legacy ISA bus on my motherboard is actually
bridged from the PCI bus, is there anyway to hack with the
VISA Driver Development Wizard to do memory reads
on the ISA bus?
Perhaps making a fictious PCI card with a VISA driver?
any thoughts?
mlewis

Hi Graham,
Which version of the NI VISA drivers are currently installed on your system?
Thanks,
Applications Engineer

Similar Messages

  • Instrument driver development wizard strange behavior

    Hi,
    I was using the driver development wizard and I started getting strange results.  It started creating VI's where the text builder portion ws seperate from the VISA communication portion of the code.  I had to delete indicators and controls and wire the seperate sections.  Also, the VI's dropped the VISA commands and replaced them with nonsense commands.  Very strange.  I closed and re-opened LabVIEW, but no change.
    Has anyone had this happen to them?
    Mark Ramsdale

    Hi Mark, 
    That does seem like some strange behavior. Could you fill me in on some more information? 
    I'd like to see if I can recreate the issue on my end. 
    What OS are you running?
    Version of LabVIEW?
    Version of Measurement & Automation Explorer? 
    DAQmx Driver?
    VISA Driver?
    What were you trying to build a driver for? At what point did it start having issues? 
    Any other useful information you can think of? 
    Applications Engineer
    National Instruments
    CLD Certified

  • Where to download visa driver development tool

    I need visa driver development tool ,but I don't know where to download it? HOPE TO GET HELP.

    Under Tools>Instrumentation, is the Create Instrument Driver Project. Is that what you are talking about? That's in LabVIEW 8.x and I did not have to select or download anything. Since I did a full install of LabVIEW and all drivers, it may be that it is included with the installation of NI-VISA but that would be just a guess to try if you don't have it.

  • Driver development for custom PCI card

    Hi friends,
    I've a PCI card developed in-house. How to prepare a driver for the same in LabVIEW? Can I develop drivers in VISA? I don't have a manufacture id. Is there any other method to develop a driver for PCI card? Once developed, can I use them for other platforms like VC++? My OS is Windows 9X/NT & 2000. I need a driver to use for all these. Lot of querries! hope I made it clear.

    THE ANSWER IS THAT YES YOU CAN DO THIS IN NI-VISA!
    Some have said that you need a kernel driver. This is partially true in that a PXI or PCI card (they are the same as viewed by the OS) must have a kernel driver. NI-VISA provides one for you.
    You said that you do not have a manufacturer ID. This is a requirement of all PCI cards and no kind of driver will work until the card has one. Once you have this ID, run the VISA PXI Driver Development Wizard and it will generate an INF for you for all supported NI-VISA environments that support PXI/PCI. Read the instructions in the appropriate INF file for how to install it into the system so that the OS will attach NI-VISA to your device. It's really simple. NI-VISA supports PXI/PCI on Windows 95, 98, ME, NT
    4, 2000, XP, and LabVIEW RT.
    Some have said that MAX will just show you all PXI/PCI devices in your system. Your device will not show up until NI-VISA can see it, and that won't happen until you generate an INF as described above.
    Since the INF file associates NI-VISA itself to your card, the ADE you use does not matter. NI-VISA supports PXI/PCI in LabVIEW, CVI, MSVC, Visual Basic, or any other ADE that normally works with VISA.
    NI-VISA works well even with more advanced devices because we support all types of register accesses (config, I/O, memory) as well as interrupt handling. Just look at the visa.h that NI ships in the VXIpnp directory. If you are using C/C++, make sure you define NIVISA_PXI before including visa.h. If you use LabVIEW, you need to use the address space numbers as defined in visa.h.
    Good luck.
    Dan Mondrik
    Senior Software Engineer, NI-VISA
    National Instruments

  • Driver development for 6221 card in RTX & VC++

    Hello All,
    For my application, I need to use NI-6221 card in RTX (Adrence/Venturcom) and VC++ environment. Since NI provides RTX support only in LabVIEW environment, It was informed that we need to write a register level program.
    I have got some examples (for register level program) from NI website (MHDDK) which when I try to compile, it throws an error looking for some RTX functions.
    1. I am using RTX v6.0 for development. Is there something else i need to install to get those RTX functions. What is the procedure that i should follow to compile the examples?
    2. In my application, I have the register level program for NI-6013 (E-Series) card in RTX environment. Is the acquiring procedure same for both E-series and M-series cards?
    3. I also need the base address for accessing the cards memory. Is there any document that gives the details of the base address and other offset addresses?
    Any information on this regard will be of great help to me.
    Thanks,
    Ashok kumar A.

    THE ANSWER IS THAT YES YOU CAN DO THIS IN NI-VISA!
    Some have said that you need a kernel driver. This is partially true in that a PXI or PCI card (they are the same as viewed by the OS) must have a kernel driver. NI-VISA provides one for you.
    You said that you do not have a manufacturer ID. This is a requirement of all PCI cards and no kind of driver will work until the card has one. Once you have this ID, run the VISA PXI Driver Development Wizard and it will generate an INF for you for all supported NI-VISA environments that support PXI/PCI. Read the instructions in the appropriate INF file for how to install it into the system so that the OS will attach NI-VISA to your device. It's really simple. NI-VISA supports PXI/PCI on Windows 95, 98, ME, NT
    4, 2000, XP, and LabVIEW RT.
    Some have said that MAX will just show you all PXI/PCI devices in your system. Your device will not show up until NI-VISA can see it, and that won't happen until you generate an INF as described above.
    Since the INF file associates NI-VISA itself to your card, the ADE you use does not matter. NI-VISA supports PXI/PCI in LabVIEW, CVI, MSVC, Visual Basic, or any other ADE that normally works with VISA.
    NI-VISA works well even with more advanced devices because we support all types of register accesses (config, I/O, memory) as well as interrupt handling. Just look at the visa.h that NI ships in the VXIpnp directory. If you are using C/C++, make sure you define NIVISA_PXI before including visa.h. If you use LabVIEW, you need to use the address space numbers as defined in visa.h.
    Good luck.
    Dan Mondrik
    Senior Software Engineer, NI-VISA
    National Instruments

  • NI-VISA driver wizard and SCPI command

    Hi,
    I had a go with a NI-VISA driver wizard. I wanted to create a driver for MH3114 DAQ. Wizard went trough very smoothly, and the driver has been installed.
    However when I did *IDN? under MAX I've received an error.
    Does it mean I have to create/implement any SCPI command? 
    How the wizard is intened to work?
    Solved!
    Go to Solution.

    Hi MimiKL,
    As Dennis has said, instruments are either designed to work with SCPI commands or not. If the user manual does not state the device is SCPI compliant then SCPI commands aren't going to work.
    All the driver wizard does is generate a number of VIs which will send the standard SCPI commands to an SCPI compliant instrument. Depending on how you are communicating with the instrument (which bus) you may need to modify these VIs subtly to work with different instruments. But, as mentioned, if the device you are trying to communicate with isn't SCPI compliant then this is never going to work. For future reference, when using the driver wizard, all of the generated subVIs will have comments in them telling you exactly what you need to replace and change to get the driver working for your instrument.
    If your device isn't SCPI compliant and you have a dll which works then you should continue using it.
    Best Regards,
    Chris
    National Instruments - Tech Support

  • NI VISA driver wizard找不到

    我安装了Labview2013,和ni visa540_full.exe，现在我想用NI VISA driver wizard做一个usb的.inf文件，可是我找不到NI VISA driver wizard这个程序啊！
    能给个下载链接吗
    还是现在现在Labview2013合并了这个功能
    已解决！
    转到解答。

    你好！
             正确安装了VISA5.4版本驱动后，选择开始》程序》National Instruments》VISA》VISA驱动程序开发员向导，即可打开

  • NI VISA driver wizard 驱动安装问题

    我在使用NI VISA driver wizard生成了一个USB设备的驱动，例如叫devicedrv.inf，然后在下一步的过程中如果选​择直接安装这个驱动，driver wizard会调用DriverWizardInstallInf64.exe（我的电脑是64位的，如果​32位的最后就是inf32）去安装这个drvier。安装成功后就能在电脑上识别我的设备了。
    我的问题是，我现在想把这个驱动部署到另一台没有安装NI-VISA的计算机上。我做过的尝试是，直接把这​个inf文件和拷贝到目标计算机上，右键单击后Install；拷贝winusb.sys至系统驱动文件夹​下。但是这样操作之后插上设备并没有正确识别 。然后我又尝试过去使用DriverWizardInstallInf64.exe这个程序，但是发现它并​没有任何可以跟的参数设置，也没有帮助文档，无法安装这个inf。
    求助NI工程师及各位高手，请问大家是如何解决这个问题的？多谢
    已解决！
    转到解答。

    您好，
             您在开发机上生成的USB设备的驱动已经调用了NI VISA的底层函数，简单的拷贝到另外一台PC上是行不通的。需要在另外一台PC上安装NI-VISA Run-Time Engine
             详情请参考http://digital.ni.com/public.nsf/allkb/EF7934DAC49​B4FAD4825723D00089627

  • Develop visa driver

    I'm new to Labview. I have a Hardware, connected vie etthernet to a desktop computer. I want provide labview code, to easy connect to Labveiw with this hardware.
    A code in VC C++ already exists connecting to the hardware, with
    1) Init function, initialising the hardware, prompting first time the user for ip address and finding all modules connected to the hardware
    2) start function, starting thread for each module, writing and reading data to an form each module with a given period as parameter
    3)IO functions reading and writing to each module, parameters: module, bytepos and value for writing.
    Is the Visa Driver developemnt the proper way of doing it?
    open -> 1)
    configure -> 2)
    peak, poke -> 3)
    It is a good idea to use the c-code library functions in an dll library connecting to labview?
    Or should I use an other approach?
    Thanks in advance.

    Thanks for all the links,
    I went through many of the documents.
    Again the description: In Visual C++ is already existing code, where the user can write an application using API functions for Initialising, Starting and I/O. Only in the background threads, the data are transfered and recieved via Ethernet to the hardware.
    Rewriting the C code in Labview would only increase the maintanace work.
    All what i read about VISA functions, they are interfaces to a card, serial port, TCP/IP devices. In my case, Labview should access the c- API functions, so that code will handle the access to the hardware. What is the best way for this access.
    It is a good idea to import them through a library dll as vi's, put them into the private section of my Labview driver, and use Labview standard public function signitures  to provide a uniqe interface for my code? Exist such an standard, and if yes, where I can find it?
    Or it is better way , to run the VC Application with a socket server, and using VISA with TCP/IP as resource?

  • NI-VISA Driver with Interrupt detection

    Hello everyone,
    I am new to PCI and PCI driver, encounter an problem when use the NI-VISA to program a PCI driver with the interrupt detection.
    Here is the situation:
    This PCI card is made of two chips : the PCI9030 pci bridge chip and ET1100 chip (the local chip that connected to PCI9030). The memory of ET1100 is mapped 1:1 to the PCI9030 memory starting at BAR2. Now I want the PCI card generates an interruption when the content of register at offset 0x221 changes.  
    I add the interrupt detection (see the figure above or the attachment), interruption removal and disarm following the guide "Using the NI-VISA Driver Wizard and NI-VISA to Develop a PXI(e)/PCI(e) Driver in Windows". However, when I completed and installed this driver in the LabVIEW RT OS, the system can recognize the card, but cannot generate the interruption when the register at offset 0x221 changes, therefore does anyone tell me the reason ? Or tell me how to program this driver using NI-VISA?
    Any suggestions is welcome.
    And Thank you in advance!

    Duplicate post here: http://forums.ni.com/t5/PXI/NI-VISA-PCI-driver-with-interrupt-detection/m-p/2618341
    Bobby Breyer
    Applications Engineer
    National Instruments

  • USB Visa driver stops responding

    I have currently developed a production test for a USB device but am coming across a very strange bug.  I go through a test sequence via case structure (i.e. Test 1 = Button 1 test, Test 2 = send command to device and read response back, Test 3 = button 2 test, etc).  I send commands through a control transfer and/or read data through report 8.  Also when the button is pressed, I read it through the interrupt endpoint.  I am using a VISA driver for this USB device that I created through the NI-VISA driver wizard.  Of course I open the VISA when I start the test and close the VISA once the test sequnce is completed (whether it passes or fails).
    However, I sometimes get a strange issue where the USB device stops responding between test sequences.  For example, test 1 passed but when it gets to test 2, the dongle does not seem to respond to the command and therefore, test fails within a certain amount of time that I specified.  But, if I leave the device plugged in and I restart the test, it will go through the sequence just fine. 
    I have used a USB sniffer (i.e. CatC) to monitor the USB traffic on the USB line.  When I press buttons, I can see that there is still data transferring wirelessly (this is a wireless joystick) via an LED that blinks on the dongle whenever it recieves data from the joystick, however, I see no USB traffic on the sniffer.  If I leave the dongle plugged in and I simply restart the test sequence, I see USB traffic again. 
    This is very strange to me and I suspect that Windows is somehow losing the USB dongle and then reenumerating it (but I am not sure).  However, when this is done, the VISA session is now lost in the middle of my test sequences and I cannot recover until I open up the VISA again.  Has anyone ever come across this type of issue before?  It is strange because most of the time it works, but sometimes it does not and it is giving me false failures.  I am not sure if the dongle is "reenumerating" during my test sequence or if some reason, the VISA session is getting lost.

    Is it possible that the device is getting reset? I have seen some devices that do no reset themselves correctly and Windows does not detect that they have been reset. The net effect is that the 2-way communication becomes a 1-way pipe. One experiment you can try when you see this happen is to unplug and plug the device back in. If you begin reading data again then Windows and the device are getting out of sync for some reason.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • Error while trying to install NI-VISA driver on SUSE LINUX 11.1(The version of gcc in the path does not match the version of gcc used to compile the currently running kernel.)

    hi i am trying to install NI-VISA driver on SUSE LINUX 11.1.
     the error message it shows is
              ******************************** ERROR ****************************************
    * The version of gcc in the path does not match the version of gcc used to    *
    * compile the currently running kernel.  This can cause unpredictable         *
    * behavior in kernel drivers and should be fixed.                             *
    * gcc version: Linux)                                                          *
    * kernel compiled with: 4.3.2                                                 *
    ******************************** ERROR ****************************************
    my kernel source version is 
       linux-8nes:/home/admin # rpm -qi kernel-source
    Name        : kernel-source                Relocations: /usr/src
    Version     : 2.6.27.29                         Vendor: openSUSE
    Release     : 0.1.1                         Build Date: Sun 16 Aug 2009 03:43:52 PM IST
    Install Date: Sat 24 Oct 2009 02:13:12 AM IST      Build Host: rinck
    Group       : Development/Sources           Source RPM: kernel-source-2.6.27.29-0.1.1.src.rpm
    Size        : 309251954                        License: GPL v2 only
    Signature   : RSA/8, Sun 16 Aug 2009 03:57:25 PM IST, Key ID b88b2fd43dbdc284
    Packager    : http://bugs.opensuse.org
    URL         : http://www.kernel.org/
    Summary     : The Linux Kernel Sources
    Description :
    Linux kernel sources with many fixes and improvements.
    Authors:
        Linus Torvalds <[email protected]>
        see /usr/src/linux/CREDITS for more details.
    Source Timestamp: 2009-08-15 17:53:59 +0200
    GIT Revision: 8a413546901c407e96f7fba18574cceeb40452af
    GIT Branch: SLE11_BRANCH
    Distribution: openSUSE 11.1 
    i had also installed GCC 4.3.2.
    it shows the error message as i had posted.
    please kindly help me on this.
    Thanks and regards,
    P.karthick

    Check this solution

  • Is there a USB Instrument driver developer tool for CVI

    Is there a USB instrument driver developer tool/guide for CVI?
    Thanks
    Chip B.
    Solved!
    Go to Solution.

    Hi! ASIC LabRat,
    I agree with your comment.  IVI drivers take too much overhead and the executing speed can be very slow compared to the drivers developed using VISA platform.  The previous link sent by the NI engineer was very old (2001) and doesn't really help you at all. 
    Please take a look at this one instead: http://zone.ni.com/devzone/cda/tut/p/id/4713. 

  • Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)

    HI,  I am having query regarding; Does LabWindows/CVI: IVI Instrument Driver Development Course contain subject like Communicating with Instruments(SCPI commands)
    LabVIEW: LabVIEW Instrument Control Course Day 1 coves subject like Communicating with Instruments This lesson describes how you can use LabVIEW tocommunicate with instruments. You will learn how touse NI-VISA, NI Spy, SCPI commands, and theInstrument I/O Assistant to perform instrument I/O. My question is to you,Does LabWindows/CVI: IVI Instrument Driver Development Course covers similar kind of training like Communication with Instruments? I am more interested in learning How to use SCPI commands to perform instrument I/O. Will you please guide me? So I can choose correct training course. Thanks & Regards,Jay +91 90110 62790EXFO Electro Optical Engineering India Pvt. Ltd.701, 7th floor The Ceribrum IT Park,Kalyani nagar. Wadgaown Sheri India, Maharashtra, Pune 411014  

    stick to the original thread.

  • LabView 2010 - CVI Driver Import Wizard

    I have previously downloaded and used the driver import wizard to create LabView VIs from a CVI driver. Specifically with Labview 8.x and 2009.
    However the latest version of the wizard (v1.3) will not install with LabView 2010 and there isn't a newer one to download w- So the question is, does anyone know if there is an intention to update this wizard so I can use it with LV 2010 ?
    Thanks

    Hi,
    I am having the same problem. Please let me know if this has been resolved yet.
    I tried copying the following directories to labview 2010:
    from     C:\Program Files\National Instruments\LabVIEW 2009\resource\CVIFpConv
    to          C:\Program Files\National Instruments\LabVIEW 2010\resource\CVIFpConv
    and
    from     C:\Program Files\National Instruments\LabVIEW 2009\project\_DriverCtoLV
    to         C:\Program Files\National Instruments\LabVIEW 2010\project\_DriverCtoLV
    and the wizard loads and runs until I specify a .fp file and then I get the error in the jpeg attached. When I try to open the block diagram (FC_RFL_Initialize.vi), it says you need a password to view it, so that stops my debugging.
    Attachments:
    Error using Instrument Driver Import Wizard in LabView 2010.JPG ‏88 KB

Maybe you are looking for