KUSB 488B not operating with LabVIEW

Hi, I'm trying to establish a connection between an instrument and LabVIEW by using an USB to GPIB Converter (KUSB 488B). Although I installed the driver of KUSB-488B, LabVIEW always shows the same error:  Error connecting to GPIB driver or device (Error 0). The computer recognizes the instrument and also its GPIB address. I use LabVIEW 2011.
It would be great if someone could help me.
Thanks.

Here is a list of things to check...
First, verify you have the correct driver installed:
Be sure that NI-488 is uninstalled (found listed in Control Panel -> Programs and Features (or Add/Remove Programs) -> National Instruments Software -> NI-488,2
Be sure that you have installed the latest version of the KI-488 driver (which currently is version 3.12 for the KUSB-488B).
(Recommend you install it as NI Command Compatible).
http://www.keithley.com/support/data?asset=56984
Second, verify that the KI-488 GPIB driver and a connected instrument work correctly:
If you have a properly installed KUSB488B and an instrument cabled and connected...when you open the Program Files -> Keithley Instruments -> KI-488 -> KI-488 Configuration Utility you should see two things:
1. GPIB0 <-- this confirms GPIB0 interface exists
2. An icon for an instument in the GPIB0 tree with a name next to it of the form "Keithley Instruments Model xxxx ....(PA:24)" <-- this confirms there is an instrment at address 24 connected to GPIB0
If you only see GPIB0 and no instrument, then the instrument is not cabled properly or is not on or is not in GPIB mode.
Third, verify that the GPIB driver works correctly with NI-VISA:
If you open VISA Interactive Control, then you should see any connected NI Compatible GPIB cards (e.g. GPIB0::INTFC) and connected instruments (e.g. GPIB0::24::INSTR). (This program can be found from the start menu as follows... Start -> All Programs -> National Instruments -> VISA -> VISA Interactive Control).
If you do not see the GPIB0::INTFC listed, then open NI MAX (Start -> All Programs -> National Instruments -> Measurement & Automation) and under Software -> NI-VISA -> VISA Options check that your NI-VISA Passprt for GPIB is enabled ON.
Finally, communicate with your instrument using :LabVIEW as follows:
Open LabVIEW and create an new blank VI using either...
- VISA Read/Write: Recommend using VISA Read and VISA Write to talk to the instrument (this should work if you were able to communicate with your instrument using VISA Interactive Control)
- GPIB Read/Write: If you prefer to do GPIB Read and GPIB Write, you must use the ones supplied with the driver, not the NI GPIB ones. The KPCI-488 driver ones can be found from any LabVIEW block diagram by selecting View -> Functions Palette -> User Libraries -> paletteMenu.

Similar Messages

  • MC-4 Controller Not Working with LabView

    I have a Klinger MC-4 Motor Controller and am trying to control it with LabView. I have thus far not been able to get the motor to move with the driver that I downloaded from this website. If anybody has written anything for this same purpose, I would greatly appreciate your insight. Any help with this problem in either LabView 5.1 or 6.0 would be great. Thanks.

    Hello-
    It may be possible to modify the existing driver to work with this instrument. Otherwise, drivers are developed and modified based on demand and popularity so the more requests, the greater the possibility that one will be modified. Please send an email to [email protected] about this issue. It would also be beneficial to notify the instrument manufacturer.
    Randy Solomonson
    Application Engineer
    National Instruments

  • OPC Server Connection not possible (with LabView 7.0 it is working)

    We have used LabView 7.0 to view OPC items on a remote server (Windows CE).
    On WindowsCE it's not possible to browse the remote registry, therefore we
    make the registry settings on the client Computer and are setting the
    "RemoteServerName". For LabView 7.0 it was working.
    With LabView 7.1 when we try the same with the sample "Browse to OPC Item.vi"
    we get the Message Box "NI Network Browser Error!" "This OPC Server does not support
    the interface: IOPCBrowseServerAddressSpace error code - 0x80070005 Access denied!"
    Has any one an idea what has changed since LabView 7.0.
    The OPC Server has also an OPCEnum running. Is there any way to read this information?
    Here are the whole registry setting for the local machine to connet to remot OPC-Server:
    REGEDIT4
    [HKEY_CLASSES_ROOT\AppID\{4841A238-5E78-48AB-A9ED-666AD68F4841}]
    @="Inficon Quadrupol Massenspektrometer DA"
    "AuthenticationLevel"=dword:00000000
    "RemoteServerName"="192.168.0.206"
    [HKEY_CLASSES_ROOT\Inficon.Quadrupol.Massenspektrometer.DA]
    @="Inficon Quadrupol Massenspektrometer DA"
    [HKEY_CLASSES_ROOT\Inficon.Quadrupol.Massenspektrometer.DA\CLSID]
    @="{4841A238-5E78-48AB-A9ED-666AD68F4841}"
    [HKEY_CLASSES_ROOT\Inficon.Quadrupol.Massenspektrometer.DA\OPC]
    [HKEY_CLASSES_ROOT\Inficon.Quadrupol.Massenspektrometer.DA\OPC\Vendor]
    @="Inficon"
    [HKEY_CLASSES_ROOT\CLSID\{4841A238-5E78-48AB-A9ED-666AD68F4841}]
    @="Inficon Quadrupol Massenspektrometer DA"
    "AppID"="{4841A238-5E78-48AB-A9ED-666AD68F4841}"
    [HKEY_CLASSES_ROOT\CLSID\{4841A238-5E78-48AB-A9ED-666AD68F4841}\Implemented Categories]
    [HKEY_CLASSES_ROOT\CLSID\{4841A238-5E78-48AB-A9ED-666AD68F4841}\Implemented Categories\{63D5F432-CFE4-11D1-B2C8-0060083BA1FB}]
    [HKEY_CLASSES_ROOT\CLSID\{4841A238-5E78-48AB-A9ED-666AD68F4841}\Implemented Categories\{CC603642-66D7-48F1-B69A-B625E73652D7}]
    [HKEY_CLASSES_ROOT\CLSID\{4841A238-5E78-48AB-A9ED-666AD68F4841}\ProgID]
    @="Inficon.Quadrupol.Massenspektrometer.DA"
    [HKEY_CLASSES_ROOT\CLSID\{4841A238-5E78-48AB-A9ED-666AD68F4841}\VersionIndependentProgID]
    @="Inficon.Quadrupol.Massenspektrometer.DA"
    Regards, Robert

    Hi Robert
    LabVIEW 7.1 implements some new security features dealing with DCOM that were not in 7.0. Windows is moving in this direction, and National Instruments decided to follow suit. 7.1 requires a certain level of authentication from the server. If this is the issue in your case, it can be resolved with the following steps (this is for Windows XP; CE will probably be different):
    1. On the computer hosting your OPC server select "Start >> Settings >> Control Panel >> Administrative Tools >> Component Services.
    2. On the tree on the left, expand "Component Services >> Computers >> My Computer >> DCOM Config.
    3. Your OPC server should be registered as one of these items. Right-click on your server and select "Properties."
    4. On the "General" tab, change the "Authentication Level" to "Connect."
    If this property is already set to Connect or Default (and the default setting is Connect) then this will have no effect.
    You can also try checking some of the other settings:
    1. On the computer hosting your OPC server select "Start >> Settings >> Control Panel >> Administrative Tools >> Component Services.
    2. On the tree on the left, expand "Component Services >> Computers >> My Computer
    3. Right-click on My Computer and select "Properties."
    4. On the "Default Properties" tab, make sure "Default Impersonation Level" is set to "Identify."
    You may also want to look at the "COM Security" tab to make sure your computer has the right permissions.
    If all else fails, you can try adding the line "ole.AuthnLevel = 1" to the LabVIEW.ini file. This should reverse some of the changes to 7.1.
    regards
    Manuel Wielander
    National Instruments

  • "open recent" from file menu not operating with snow leopard?

    is anyone else having trouble with this?
    did i accidentally disable this option? if so, how do i enable it?
    thanks

    PeterBreis0807 wrote:
    I can understand why they have done this, although agree it is not a good idea.
    Apple has made accessing the applications harder than need be, by nesting them inside the iWork folder. Without the manuals.
    The User Guide says nothing about the need to leave the iWork components in the iWork '09 folder.
    Is it difficult to understand that we don't buy three separate applications but one package?
    The soluce of three apps in one package may have several reasons:
    (1) developping Keynote then Pages then Numbers was more efficient in terms of cost than developping them as a single app.
    (2) keeping them as separated items gives the ability to load an item smaller than a treeinone app so it requires less time and use less memory.
    (3)…
    If users are too numerous to break the 'rule', I'm afraid that Apple decide to pack the three apps in a single item so the problem would be definitely solved.
    If someone want to have direct access to iWork components from the Applications menu, the correct soluce is to create aliases of thes apps and store these aliases in the Applications folder. Neat, simple and free of the described oddities.
    as in the +Open With+ in File information,
    The operating system apply a default setting for the "Open with" feature.
    There is a problem for those which want an other setting.
    But, as every user has its own needs, there will always be necessary to make individual choices.
    Which app must open a .doc file ?
    For me it's a moveit_to_thetrash tool
    for some users, it's Word
    for some, it's openOffice
    for some, it's neoOffice
    for some, it's Bean
    for some, it's Pages
    for some, it's TextEdit
    and I know users having all of them installed.
    Automatic link between a kind of doc and an app is an inaccessible dream.
    The user action is required.
    and the +Keyboard Shortcuts+ preferences.
    The decision to apply this or that shortcut to a menu item is part of the design task. I think that it's the designer which must define them, not the user. You don't change the commands of your motorcar, I don't understand why you would change those of an application.
    If you don't like the application GUI, use an other app.
    Yvan KOENIG (VALLAURIS, France) vendredi 11 septembre 2009 17:24:59
    The user is here to use program, not to design them.

  • ActiveX not working with LabView 6.0i Evaluation Version

    I am trying to run some ActiveX container samples in LabView 6.0i Evaluation Version.But it is not working and no error message is displayed. Is ActiveX supported in LabView 6.0i Evaluation Version.

    [email protected] (pl) wrote in <506500000008000000CD610000-1031838699000
    @exchange.ni.com>:
    >I am trying to run some ActiveX container samples in LabView 6.0i
    >Evaluation Version.But it is not working and no error message is
    >displayed. Is ActiveX supported in LabView 6.0i Evaluation Version.
    >
    Don't know for sure, but with the Student editions this is certainly the
    case so it is possible.
    The student editions do not allow:
    1.AxtiveX
    2.External Code (DLL's, CINS)
    3. and somethjing else that escapes me at the moment.
    Try simple examples such as the MSBrowser and the Adobe PDF reader AX
    controls - these always work if Ax is going to work at all.
    Not a solution, sorry ;-)
    cheers, Alex.
    Alexander C. Le Dain, PhD
    ICON Technologies Pty Ltd
    http://www.icon-tech.com
    .au
    * The LabVIEW FAQ http://www.icon-tech.com.au/thelabviewfaq.html *

  • At-mio-16xe-50 does not work with labview

    I am putting together another system. I set the daq board with the values recorded from the first system using ni-daq. The setup passes the test in ni-daq. I get the correct readings using ni-daq, but when I go to my labview application I do not get the right readings. The readings seem to be just noise.

    In my experience if you get a correct reading in a test panel in MAX you should get the same reading in LabVIEW. Are you using virtual channels? How are you viewing the data? If you are looking at the data in a chart, is the chart auto-scaling making the signal appear to be noise? What type of signal are you reading (analog, digital, etc.)? Have you changed the default input limits for the board? Is the signal you are reading a constant source? If you are able to answer some of these questions it might be able to give you a more definitive answer.

  • NI Goop Wizard not working with LabVIEW 2009

    I have added the NI Goop Wizard using VIPM (VI Package Manager) into my LabVIEW 2009 SP1 installation however it is not working. Whenever I select Create New Class from the drop down (same applies to menu selection) nothing happens and the drop down returns to it's default selection. I have tried this on 2 PC's both with 2009 SP1 installed, both exhibit the same unwanted behaviour. One of the PC's also has LabVIEW 8.2.1 installed also with NI GOOP Wizard and this installation works fine.
    Anybody using GOOP Wizard with 2009 ?
    Cheers
    Chris
    Don't forget to give Kudo's for a good answer !
    LabVIEW Champion
    Certified LabVIEW Architect
    Certified TestStand Architect

    Hi there Chris,
    Off the top of my head it's my understanding that NI GOOP wizard is legacy software that was made redundant by the native GOOP tools in LabVIEW 8.2.0 and later.
    In light of this it's a bit confusing that everything is working fine with 8.2.1 for you. Is there a version to the NI GOOP Wizard that you are using?
    I had a search across the website but I'm afraid I haven't found any other examples or poeple using the GOOP Wizard in LabVIEW 2009 or 2010.
    Kind Regards.
    Rhys
    Applications Engineer
    National Instruments

  • LV 6.0 runtime engine not found with labview 6.1

    I recently upgraded to LabView 6.1.
    Now when I try to run an exe built under 6.02, I get an error that the 6.0 (or compatable) runtime engine could not be found.
    I have the developers version of labview 6.1 installed, and the labview runtime engine 6.1 installed.
    Do I need to install 6.0 runtime too? (in that case do I need 5.1 ruintime instaled too for exe's built a log time ago)?
    Shouldnt the 6.1 RTE be able to run older exe's?
    I could find no solution searching this web site.
    Thanks
    Larry Junek, Certified LabVIEW Developer

    Did you install 6.1 wheer 6.0 was?
    You may have lost the 6.0 RTE you did not realize you where using.
    Yes you need the version of RTE that matches the app.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Signal Express not activated with Labview Full Development System Volume License

    I'm using a volume license manager to generate license for disconnected machines.  I just upgraded to Labview 2009.  The license files work for labview but are not working for signal express.  I have the Labview full development system which included signal express in the past.  Both labview and signal express work fine on my computer that also has the volume licensing manager software installed.   This computer is connected to the license server.  I need to get signal express activated on my disconnected machines. 

    LabVIEW Full Development licenses still include Signal Express. Are you saying that whenever you are connected to the server you can run Signal Express just fine, but whenever you create a disconnected license Signal Express is not able to launch? Can you verify that you are, in fact, checking a license out from the server whenever you are connected to the network?
    If you still have trouble I would recommend calling NI support so we could get more informatioin (such as your license file, contract ID, etc).

  • Go-Back 1 page & Forward 1 page buttons are not operative with v.4.0, why?

    After upgrade to v 4.0, the Go-back 1 page and Forward 1 page buttons do not work (are "greyed out"). I uninstalled and re-installed v 4.0, but same problem exists. Never had any problems with previous versions. That feature still works OK with Internet Explorer.

    Start Firefox in [[Safe Mode]] to check if one of the add-ons is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Appearance/Themes).
    * Don't make any changes on the Safe mode start window.
    See:
    * [[Troubleshooting extensions and themes]]

  • Will our existing drivers work with LabVIEW 8.x?

    We have drivers for some of our DAQ products that were developed in LabVIEW 6 or 7.
    Is there any reason these drivers would not work with the latest versions of LabVIEW?
    We ask because there seem to be some customers in Europe who believe our drivers do not work with LabVIEW 8.5, but we know there are users with LabVIEW 8.0 and 8.1 using the drivers without problems.
    Any thoughts or suggestions, or are there any known issues with older drivers in LabVIEW 8.5?
    Regards,
    Roger Hammerquist

    Hi Roger,
    In general, the latest versions of LabVIEW will work with older
    versions of the DAQ drivers.   However, it is certainly possible that some of
    the older drivers could have some conflicts. 
    How “old” are the driver versions that your customers are
    using?  Specifically, what version of the
    driver does your customer report seeing the errors with?  Is  the
    customer using the same operating system that the original program was written
    for?  Is the customer seeing problems
    upgrading the VIs from LabVIEW 6 or 7 to LabVIEW 8.5?
    The suggestion to work with someone to try it out is excellent.
      Posting the specific driver versions
    seeing the conflict, might also shed some light on the issue.
    Jared T.

  • Where should I start from to use HP4145B with LabView?

    I am not familiar with LabView, but I have to set up LabView to make it work with HP4145B.
    I downloaded the driver from NI, placed it at the correct directory, and can see VI's in function palette.
    Also, when I run MAX, it shows "Instrument 0" under GPIB0.
    When I click on "Scan for Instrument", it says something about IDN query, but now I know HP4145B is too old to understand IDN query.
    I saw a lot of posts that say they can write to the instrument but cannot read.
    However, I don't even know how to test whether my labview can write to 4145B or not.
    My questions are....
    1. 4145B manual says it has "ID"  code.
    I tried testing it by using "Interactive Control"
    And I got this by NI Spy
    1.  ibsic(GPIB0)
    Process ID: 0x00000C1C         Thread ID: 0x00000EB4
    Start Time: 15:23:22.485       Duration 00:00:00.000
    ibsta: 0x160       iberr: 0             ibcntl: 0(0x0)
    2.  ibsre(GPIB0, 1)
    Process ID: 0x00000C1C         Thread ID: 0x00000EB4
    Start Time: 15:23:26.070       Duration 00:00:00.000
    ibsta: 0x160       iberr: 1             ibcntl: 0(0x0)
    3.  ibcmd(GPIB0, "@?1", 3 (0x3))
    Process ID: 0x00000C1C         Thread ID: 0x00000EB4
    Start Time: 15:24:18.606       Duration 00:00:00.000
    ibsta: 0x178       iberr: 0             ibcntl: 3(0x3)
    4.  ibwrt(GPIB0, "ID", 2 (0x2))
    Process ID: 0x00000C1C         Thread ID: 0x00000EB4
    Start Time: 15:24:30.242       Duration 00:00:00.010
    ibsta: 0x168       iberr: 0             ibcntl: 2(0x2)
    5.  ibcmd(GPIB0, "? Q", 3 (0x3))
    Process ID: 0x00000C1C         Thread ID: 0x00000EB4
    Start Time: 15:25:12.333       Duration 00:00:00.010
    ibsta: 0x174       iberr: 0             ibcntl: 3(0x3)
    > 6.  ibrd(GPIB0, "", 20 (0x14))
    > Process ID: 0x00000C1C         Thread ID: 0x00000EB4
    > Start Time: 15:25:23.289       Duration 00:00:16.784
    > ibsta: 0xc164       iberr: 6             ibcntl: 0(0x0)
    There are four LED's on the front panel of HP4145B.
    It shows status of HP4145B whether it is talker or listener.
    LED changes properly to my command. (So I don't think there is any problem with harware connection)
    But, I still get nothing but EABO error when I want to read something.
    What am I doing wrong?
    How can I test "ID" code?
    (I do not have ultra-fast typing speed so I think I gave 4145 enough time to respond before I typed new command)
    2. I tried to use driver I downloaded from NI.
    Other posts say that people used "HP 4145 Example.vi" for testing.
    However when I put "HP 4145 Example.vi" on the block diagram, I cannot run it.
    How do I test with "HP 4145 Examble.vi"?
    3. I tried testing other vi's such as "HP 4145 source setup.vi".
    I put that vi on the block diagram window, added constant of 17 to GPIB address,
    and other constants to other inputs and run it.
    A new window popped up, so I ran it again.
    However it does not seem to work since I see no change when I go into source set up menu directly from HP4145 front panel.
    Again, LED indicator changes to LTN(which means HP4145B is in listener mode) when I run vi.
    What would be the problem?
    I'm experiencing a lot of trouble with this HP4145B, and I know too little to solve this by myself.
    Somebody please help me with this.
    Thanks in advance.

    My 4145b uses address 17.
    I checked switch setting on the backpanel of 4145b and CRT on the front panel says "HPIB(17, COMMA, EOI)". Also, when I change address to 16 and execute vi file, it gives me an error message of "HP 4145 Define Channel; HP 4145 Send Message"
    When I change back to 17 and execute, error message disappears(and no more error message comes in when I send command to 4145b), but nothing happens on 4145b.
    As I said eariler, LEDs on 4145b seems to be saying that 4145b understands basic command such as "change to listener" or "change to talker".
    In addition, when I try to read from 4145b from "HP4145 example.vi", for example by clicking on "Display Graphics and Plot" and execute, I get error message "HP 4145 Take Measurement; Wait for Interrrupt (GPIB)". However, reading is not the problem to think right now because I don't even know how to read.
    I have Newport 1830-C with me, and I checked this instrument with same GPIB-USB-HS and same PC I am using with HP4145b.
    It works with 1830C. Therefore, it doesn't look like there is something wrong with  my PC and GPIB-USB-HS.
    Anyway, thank you for your attention.
    메시지가 06-25-2008 01:28 AM에 Min Yoon에 의해 편집되었음
    메시지가 06-25-2008 01:36 AM에 Min Yoon에 의해 편집되었음

  • Is Max 4.1 compatible with Labview 7.0?

    I see that Max 4.1 comes with daqmx 8.3 which is NOT listed as Labview 7.0 compatible.  I also see that installing the last daqmx for labview 7.0 (ie daqmx 8.1) would install max 4.0.3.  Therefore, if i have max 4.1 installed with labview 7.0/daqmx8.1 am I expected to have issues?

    degenste,
    Just to clarify a bit, Measurement and Automation Explorer (MAX) displays a list of NI devices and software on your computer, but it does not install support for those devices.  The DAQmx driver is responsible for installing support for our Data Acquisition products.  Support for USB M-Series devices was not added until version 8.3 of DAQmx.  This knowledge base article describes why the USB M-Series product line has to be used with DAQmx 8.3.   
    You are correct when saying that DAQmx 8.3 is not compatible with LabVIEW 7.0 as stated in this document.  With this set up, your only options would be to upgrade your LabVIEW version or choose a different form factor such as PCI for your device.
    Regards,
    Ryan N
    National Instruments
    Application Engineer
    Ryan N
    National Instruments
    Application Engineer
    ni.com/support

  • LabView (8.2) hangs when using I/O operations with traditiona​l NI-DAQ 7.4.4 after aborting LabView program

    Hello!
    We have the following problem:
    LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program
    We freshly installed LabView 8.2 (2006) and NI-DAQ 7.4.4 on a PC running Windows XP (Service Pack 3). We built a larger vi that remotely controls a traditional NI-DAQ card (AT-AO-10) on a second PC via NI-VISA 5.0.3. We were successfully running this program until a power failure caused the first computer to crash. After this crash we were unable to start the program again: LabView freezes while loading the vi. LabView itself can be started but freezes when adding I/O operations from the NI-DAQ palette to a block diagram.
    We have tried to re-install NI-DAQ 7.4.4, but it did not help. We then re-installed all NI software, but still no improvement. In the end we decided to reinstall ALL software, first Windows XP, then LabView and finally NI-DAQ 7.4.4. This worked. However, after a few days of running the program we had to abort LabView via Windows Task manager and afterward we again experienced the same problem as before: LabView freezes when loading the program.
    Obviously, we cannot afford to reinstall Windows every time. Are there any known Windows XP / NI-DAQ issues that might cause the freezing of LabView? We would be very grateful for any idea.
    Best regards,
    Matthias

    Hello Sprice,
    Browse the shipping examples according to “Directory Structure” and then select
    DAQ to find the Traditional DAQ examples. 
    There a lot of examples that are written for counters (Counter >>
    daq-stc.llb >> Count Edges (DAQ-STC).vi). 
    What kind of signals are your photons creating?  Are they TTL compatible at a certain
    frequency?  You don’t care about overwriting
    your buffer?
    Respectfully,
    Rob F
    Test Engineer
    Condition Measurements
    National Instruments

  • My operating system windows XP not working with photoshop cloud, why not?

    I need to add 2 more licences for photoshop cloud and I'm being told my operating system windows XP does not work with Photoshop cloud. We already have 2 pcs using it in our office so why not?
    Please help
    Roy

    Do you have the latest version of iTunes?  If not, get it at:
    http://www.apple.com/itunes

Maybe you are looking for