Problems in using Ivi driver ke230y in "IviDCPwr Measure [MSR].vi"

Hello all,
        I have a problem in using IVI driver (ke230y) to control keithley2303 powersupply with LABVIEW 2013.
 After I initialize and config ke2303 well and run to  "IviDCPwr Measure [MSR].vi", it ocurrs errors. While lasting about 15 seconds and then reports errors as attached:
The code (attached) when I test with other powersupplies such as agilent66309d and keithley2306(with ivi driver ke230x), it runs well.
So I've no idear about this problem with keithley2303 powersupply, can you guys ever meet this problem and may reply for me to fix it.
thank you for your reading and help!
best wishes,
Phil
Solved!
Go to Solution.
Attachments:
error.jpg ‏36 KB
code.jpg ‏43 KB

I don't have the any driver's source code (such as ividcpwr.dll source code), how can I modify the specific driver through labwindows.
Follow your advice I use I/O trace to get trace as follows:
1 IviDCPwr_InitWithOptions ("ke2303", VI_FALSE, VI_TRUE, "", 0x0C913064) VI_SUCCESS 14:45:10.675
2 IviDCPwr_ConfigureVoltageLevel (ke2303, "CHANNEL1", 3.8) VI_SUCCESS 14:45:11.405
3 IviDCPwr_ConfigureCurrentLimit (ke2303, "CHANNEL1", 0, 3) VI_SUCCESS 14:45:12.104
4 IviDCPwr_ConfigureOutputEnabled (ke2303, "CHANNEL1", VI_TRUE) VI_SUCCESS 14:45:12.824
5 IviDCPwr_Measure (ke2303, "CHANNEL1", 1, 0) VI_ERROR_TMO 14:45:16.207
6 IviDCPwr_GetError (ke2303, -1073807339, 0, "") 0x00000037 14:45:32.991
7 IviDCPwr_GetError (ke2303, -1073807339, 55, "Primary Error: ..................") VI_SUCCESS 14:45:32.991
8 IviDCPwr_close (ke2303) VI_SUCCESS 14:45:33.847
I cannot see any GPIB command in the trace but some IviDCPwr functions.
Besides, if I know any bug (eg. some wrong GPIB command) in ividcpwr.dll, how can I modify it before I get it's source code.
Pls teach me anytime in your conveneince.
thanks!

Similar Messages

  • Problems to show IVI driver, properts loader when using operator interface

    I am using the Operator Interface (programmed in CVI, with asynchronous timer) in folder OP1 in attached  zip file. This operator interface puts not the error message of IVI driver, properts loader etc... on the screen (messages like in attached picture error.jpg in attached zip file). Because of stability problems I am using this operator interface but I need these error message.
    A Other Operator interface is OP2 in attached zip file. This operator interface puts the error message of IVI driver, properts loader ... on the screen (messages like in attached picture error.jpg in attached zip file).
    Now I want to have this functionality with OP1 becaus of stability reasons I have to use OP1.
    How can I implement this in OP1? I tried and searched a lot of time but I have not found a method to implement this.
    can anyone help me?
    thank you
    regards Samuel
    Attachments:
    OP.zip ‏3405 KB

    Hi Sam,
    if you open the userinterface which comes with Teststand - the simple one - you should be able to find the difference. You can find it here:
    C:\Programme\National Instruments\TestStand 4.1\UserInterfaces\Simple\CVI
     I hope this helps.
    Greetings, RMathews 

  • How to use IVI Driver in Labwindows

    I want to use IVI drivers in LabWindows/CVI, but I don't know how! I know that it necessary to load the class driver. But how can I include the specific driver??? It is possible to add functions into a class driver? And what I have to do when the instrument should change?
    Thanks for your help!!!

    Hi Chris,
    If your goal is to create an interchangeable application, you do have to use a class driver. National Instruments provides Measurement and Automation Explorer (MAX), a Graphical User Interface for configuring IVI. MAX is usually installed with one of NI's Application Development Environments such as LabVIEW or Measurement Studio, or with one of NI's hardware product drivers such as NI-488.2 or NI-DAQ.
    The IVI configuration utility allows you to interchange instruments without recompiling or relinking your application source code by configuring logical names. The user defines which specific instrument he wants to associate with a logical name and IVI takes care of the rest. If at a later time, the user decides to swap the instrument and use a diff
    erent one, all he has to do is change the entry in the configuration utility so the logical name points to a different specific instrument driver (driver session).
    So, the important point is that you have to have both, IVI class and specific driver installed on your system, and then you need to configure them in MAX. MAX 3.0 now has a built-in help to guide you through the configuration process. In the case that you still do not have MAX 3.0, you can find an application note about the IVI configuration in MAX 2.x on NI's Developer Zone: http://zone.ni.com/devzone/devzone.nsf/webproducts/E2947DB2FF0DD9FE862569FD006EB939?opendocument.
    As for the adding functions into the class driver, the answer is no, that is not possible. You can certainly use the specific driver functions in the application which is written using the class driver functions but then your application will not be completely interchangeable in the future. However, this way you will just isolate a small portion of y
    our code that you will need to change later on when you decide to change the instrument.
    I hope this makes sense.
    Regards,
    Vesna Jadric
    Instrument Drivers/IVI

  • Using IVI driver for reading delay in MSO6104A

    Hi,
    I have the NI IVI driver for the MSO6104A scope. The driver is functional and I manage to use it.
    My scope has a function of measuring delay between two different channels. But, how can I read the Delay measurement using IVI scope step?
    Is there any other way of reading this measurement?
    Thanking in advance
    Solved!
    Go to Solution.

    As far as I know, interchannel delay is not a supported IVI measurement function. So, you can complain to ivifoundation.org first of all. Or, in a code module, you can use the instrument specific driver to get the measurement. This would make the application 'non-IVI' so most of the reasons for using IVI in the first place are gone. Or, retrieve the waveforms from each channel and calculate the delay in a code module.

  • Using IVI driver for Keithley 6485

    I am trying to learn how to use IVI drivers.  I installed IVI drivers for two instruments, an HP34401A and a Keithley 6485.  I was able to get the HP to work in simulation mode (I don't have the hardware).  I am also trying to get the 6485 working in simulation mode.  The attached vi was provided by Keithley.  I configured a logical name in MAX, but this name doesn't show up as an option when I edit the "logical name" control on the front panel.  I changed the Initialize vi to Initialize with Options and added a command string control to set the mode to simulation, manually entered the correct name in the control, and ran the program.  No error was indicated in the Initialize vi.  After the configuration vi runs, however, the following error was flagged:
    Error -1074135023 occurred at IviDmm IVI Error Converter.vi
    Possible reason(s):
    Primary Error: (Hex 0xBFFA0011) Function or method not supported.
    Elaboration: FunctionId: 46,  FunctionName: ConfigureMeasurement
    Complete call chain:
         IviDmm IVI Error Converter.vi
         IviDmm Configure Measurement.vi
         KE6485_ZeroChk_LV86.vi
    This error is being generated by IviDmm Configure Measurement.vi, which is apparently installed NI code.  Specifically, the error appears to be thrown when Call Library Function Node is invoked and IviDmm.dll is called.  I wasn't able to track down any further info as to the meaning of these error codes.
    Thanks for your assistance.
    Attachments:
    KE6485_ZeroChk_LV86.vi ‏14 KB

    Hello,
    3rd party devices will show in MAX only when that device is listed at a specific place within your computer's registry. Non-NI hardware may not show up in MAX.
    As far as the logical name is concened, unfortunately, you will have to contact Keithley to get a better understanding of their code.
    You could download our IVI driver from the link below as you might have better luck with it.  You can find any of our 3rd party drivers at www.ni.com/idnet.
    Keithley 6485
    http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=238
    Regards,
    Shawn S. | NIC
    Instrument Driver/IVI PSE
    National Instruments

  • Agilent E364XA IVI driver does not support measurement of 2nd channel?

    Hi,
    just downloaded the IVI driver for Agilent programmabel power supplies E364xA. It's supposed to support also the E3646A, a dual power supply. In my case there are two of 'em, connected via GPIB. I've configured 'em in MAX and have set up logical names, driver sessions and hardware assets. The two driver sessions use the hpe364xa as software module, the hpe364xa_32.dll as module path and show a whole bunch of supported devices, amoung of is also mine. I've set up two virtual channel names each for both driver sessions (4 channels over all). I can set the output voltage of both channels properly, but cannot read the voltage back. Get always the voltage level for the 2nd channel of the device. Hav
    e tried measuring both or just one channel, it always returns the voltage of ch2, either two times a very narrow level or just one result.
    Any idea?
    BTW, this happens both in LabVIEW 7.1 and in TestStand 3.0
    Greetings from Germany!
    Uwe Frenz

    Hi,
    the problem is that function does not set active channel. This function measure value from your last configured channel. For example: If you set volatge on channel 2, the measured value should be from this channel, if you set volatge on channel 1 before measurement, measured value should be from channel 1. :-(
    I attached fixed source code and DLL. Please try it, and let me know if the problem is fixed. I don't have instrument so I cannot test it. My email is [email protected] . Thanks.
    you should copy these files into [IVI] directory. The default path is C:\Program Files\IVI
    hpe364xa_32.dll => [IVI]\bin
    hpe364xa.h => [IVI]\include
    hpe364xa.c => [IVI]\Drivers\hpe364xa
    Zdenek
    Attachments:
    hpe364xa.zip ‏70 KB

  • Problems in using the driver coming with application in Crystal Report

    Post Author: StrongWare
    CA Forum: Data Connectivity and SQL
    Hi! All,
    I used the ADORecordSet to fetch data from tables, and pass it to ther report at runtime using AddADOCommand.
    I got the ActiveConnection and ActiveCommand from ADORecordSet and passed them as parameters of AddADOCommand, it seems the AddADOCommand opens an addional connection, which can be told from the ODBC trace, instead of using the ActiveConnection I passed in.
    Is that true?
    It causes the big problem for me, since the ActiveConnection I passed in was opened using our OEM DataDirect driver and I assumed the AddAdoCommand uses it directly, but it is not the case!! The AddADOCommand just uses the connection information from ActiveConnection and opens an additional one. Since the connection string contains the driver name, so this connection is also opened via our OEM DataDirect Driver. But the Crystal Report tries to unlock it using its own license/password {qecr.lic,brahmabrahmabrahmabrahma} to unlock our OEM driver, which of course raises the license warning from DataDirect Driver 5.2!! After a certain grace period, any sql operations under the cover of AddADOCommand fail and thus causing the failure of AddADOCommand.
    Now what is the solution?
    1. how to avoid open an additional connection? or any other API I should call to avoid this?
    2. How Crystal Report works with the driver coming with the application, and this driver needs to be unlocked before being used.
    Thanks
    Strong

    I don't have the any driver's source code (such as ividcpwr.dll source code), how can I modify the specific driver through labwindows.
    Follow your advice I use I/O trace to get trace as follows:
    1 IviDCPwr_InitWithOptions ("ke2303", VI_FALSE, VI_TRUE, "", 0x0C913064) VI_SUCCESS 14:45:10.675
    2 IviDCPwr_ConfigureVoltageLevel (ke2303, "CHANNEL1", 3.8) VI_SUCCESS 14:45:11.405
    3 IviDCPwr_ConfigureCurrentLimit (ke2303, "CHANNEL1", 0, 3) VI_SUCCESS 14:45:12.104
    4 IviDCPwr_ConfigureOutputEnabled (ke2303, "CHANNEL1", VI_TRUE) VI_SUCCESS 14:45:12.824
    5 IviDCPwr_Measure (ke2303, "CHANNEL1", 1, 0) VI_ERROR_TMO 14:45:16.207
    6 IviDCPwr_GetError (ke2303, -1073807339, 0, "") 0x00000037 14:45:32.991
    7 IviDCPwr_GetError (ke2303, -1073807339, 55, "Primary Error: ..................") VI_SUCCESS 14:45:32.991
    8 IviDCPwr_close (ke2303) VI_SUCCESS 14:45:33.847
    I cannot see any GPIB command in the trace but some IviDCPwr functions.
    Besides, if I know any bug (eg. some wrong GPIB command) in ividcpwr.dll, how can I modify it before I get it's source code.
    Pls teach me anytime in your conveneince.
    thanks!

  • Problem with using external drive in OSX

    Hi there, I have an external hard drive (seagate freeagent 1TB) and I am using Mac OSX Snow Leopard and Windows XP as bootcamp. Yesterday it suddenly happens that I find the drive extremely slow or even unable to read files. It cannot be unmounted as well. I thought the drive has problem and tries to repair it, however when I use bootcamp XP today and mount the drive. It is fast as usual and don't have much problem. Why is this and should I reinstall my OSX to solve the problem? Well I hope I don't have to reinstall but if I have to, I probably will upgrade the system to Lion...

    also sorry if this is a reposted question.....i tried to search around the discussions and couldn't find the answer to my specific situation....actually didn't even see anyone trying to do what i'm talkin about.......again thanks for any help

  • Problems in using IVI instrument drivers

    Hi all,
    I have created seperate IVI instrument vi's for each functionality e.g. PSUinit.vi for initialization, PSUsetVoltage.vi for setting the voltage in power supply etc. But whenever i try to run these vis using a IVI logical name "PSU", they dont work and I endup getting errors like "PSU(1)" logical name not found.."PSU(2)"logical name not found etc.
    Any suggestions on where am I making a mistake?

    And how should I connect logical name?..should I use method 1 or method 2?..I guess I am getting problems due to this coz I havent actually closed the logical name instance in each vi..But I am not sure about it.
    Also in plug & play drivers it doesnt matter which method (1 or 2) one follows and whether one has closed the instance or not. They still work but I think the same case is not valid for IVI.Is it true?
    P.S Please find the attached image for method 1 & 2
    Attachments:
    ivi2.png ‏8 KB

  • Error on using IVI driver to control Agilent E4407B

    Hi,
    I'm now using LabVIEW7 to control Agilent E4407B Spectrum Analyzer through GPIB. I can control it properly in MAX by sending GPIB commands. However, I got an error when I program it in LabVIEW by using the IVI instrument driver. The error code is -1073807339 which is timeout expired before operation completed. I just used the Getting started.vi to try but it failed in the initialize vi. I didn't change any setting and the address was mateched. The analyzer indicated that it turned to remote mode but it showed "Query UNTERMINATED" when the program run Call Library Function to access the ivi.dll. Do I miss any drivers or settings? Thanks.
    Bill

    Hi,
    I developed this driver with E4401B and I do not have any troubles. Please can you use NI Spy for VISA and attach spy report.
    NI Spy you can find in Start menu National Instruments>>Ni Spy. Press blue arrow icon. Now you can start Getting started example. In spy window you should see all VISA calls. When getting started example finish, stop capture in NI Spy and save report file.
    Thanks,
    Zdenek

  • Problems with using 3tb drives in RAID 1

    I'm using an MSi 870A-G54 mainboard
    Without going into major specifics at this moment here is the basic scenario:
    Added 2 new seagate baracuda 3tb drives in RAID 1 mode
    Updated the bios (AMI) to 7.20
    Updated windows 7 64 with the latest drivers.
    Updated RAID Xpert to the lastest version
    Everything worked. Added my data (movies and music), all was well with the world 
    Then, after a reboot windows no longer recognizes the drives, nor does RAID Xpert, however within the RAID config (BIOS) the drives are showing as being just fine and the RAID configuration is configured correctly.
    Anyone have any idea how I can retrieve my data from these drives (most important) and get it working again (important, but less than just getting the data recovered)?
    Thus far I haven't a clue what changed. There were no Windows, BIOS, configuration or other updates.
    oh what fun it is!!!

    Thanks for the info.. but...
    The motherboard recognized the drives (after upgrading the BIOS to 17.20)
    I managed to get it working (again!) last night. :-D
    I had to do some major upgrading by way of AMD (upgraded RAID drivers, chipset drivers, and AMD RAID Xpert) that were not available via the MSi site, but are directly compatible with the chipset I'm using. .. or ... so far appear to be. Too early to tell.
    So far, everything seems stable..
    Odds are I tripped over something, or missed a step during the initial set-up, when I was figuring out what needed to be done to get the drives recognized by the MB, and then then the RAID, and then the OS. 
    Right now I'm backing up all my data and, after verfiying that each drive in fact contains data, I'm planning on breaking the mirror via RAID Xpert, then see if I need to break it as well via the RAID console (this would provide confirmation that the windows based utility in fact has, or has not, correct connectivity and control to the MB RAID config). Then, do a low-level format of the drives and start over. ....
    By the way.. just so anyone reading this knows... the Live Update 5 utility is weak... very very weak. I pity the person that has minimal PC experience to try and figure out what it's doing (or not doing) and ... done..
    I'll post the final results of this adventure when I finalize the entire setup in about a month. :-D
     

  • Apple TV  sync problems when using external drive in iTunes

    I have my iTunes library on an external drive in order to save HD space. Unfortunately the external driver some times get disconnected and I need to mount it again.
    Since iTunes can not find the songs when the drive get disconnected, all songs are marked with an exclamation mark . So far no problem as the song will play immediatelly when i click on it.
    The problem is now with the Apple TV. It seems that as soon as a song get an exclamation mark it get removed (!!!) from the Apple TV playlists. I would expect that the song is still available in Apple TV although in iTunes is marked with an exclamation mark, as this is only a temporary non availability.
    The consequence is that one song in Apple TV may or may not be available for playing in dependency of the availability of the original song and its external drive in iTunes.
    may be "its a feature", but a very annoying one..
    Alex

    I believe you created this problem at the very beginning by not letting iTune to manage your iTune folder. When this occurs iTune can only play songs when your external HD is connected.
    You mentioned you want to save HD space. The better solution will be to put the most played songs in your HD and let iTune manage the folder and backup all the other songs to your external HD. Best way to find out is to check out the most played from your list and backup the least played to your external HD. Better yet, backup all songs.

  • IV characteristic using Keithley 2400, Labview IVI driver

    Hi...
    I'm Pradeep. I am trying to build a LV program for measuring LjV (luminance-current density-voltage) Characteristic of LED using while loop. I am in the first part of building a program for IV characteristic. I am using Keithley 2400 (connected through PCI-GPIB) for sourcing Voltage and measure Current through the device. I use IVI driver from Keithley website (2400-854B01) in Labview 2010.
    I have made a program (please find it in attachments), while running it shows an error code -110. I fear that the voltage that I want to send to 2400 is not communicated properly. Can someone please help in finding out where I made a mistake. I'm struck for two days. I have used Initialize, Configure SOurce DC, Enable Source, Configure Measurement, GPIB Write, Read and Close from the driver (though not sure of the order to be used)
    Please ignore the Luminance measurement in the LV program at 'XY graph' and at 'Write to Spreadsheet' which are for later use when I need to add a photodiode with Keithley 2000 DMM.
    (I did not do a structured learning of Labview. I have been learning from manuals and through discussion forums for a couple of weeks. Please pardon my ignorance)
    Attachments:
    LjV char.vi ‏22 KB

    duplicate

  • Performing a Vi_Lock in an IVI Driver

    I am using the Tektronix AWG520 IVI-C Driver. Here is the scenario of events: I call the Initialize function to obtain a vi session. It appears that this vi session is "owned" by the driver now. As soon as I attempt to write anything to the instrument through GPIB commands using that vi session, I get an error message saying that the session is invalid. I am assuming this is because the IVI driver is either not releasing the vi session or is releasing a sort of masked vi session. Does anyone know if this is the case? I have tried a couple of things to get this result: The first thing I tried was writing an identify function that would use the function vi_write to write the *IDN? query to the instrument. This did not wor
    k. Now I am trying to do something simpler, by just trying to send the vi_lock command to the instrument. I get the same error that the vi session is not valid. Is there any possible way to get around these "problems" with the IVI driver? Any help in this matter is greatly appreciated! Thanks in advance.
    Attachments:
    tkawg5x0.c ‏280 KB

    Hi,
    It seems that your are trying to use the IVI session handle to perform I/O operations. An IVI session is initialize using the Ivi_SpecificDriverNew function. From the function help:
    "Note: This function does not create a VISA session to any instrument resources. If you use VISA to communicate to the instrument, you must create a VISA session yourself and set the IVI_ATTR_IO_SESSION attribute to that value. Otherwise, you can use the IVI_ATTR_IO_SESSION attribute to hold a handle to whatever communications resource you use."
    Look at the callback functions as a reference for instrument I/O. First the session is locked and then the IO VISA handle is obtained using Ivi_IOSession. This function returns the VISA handle stored in IVI_ATTR_IO_SESSION.
    The driver needs to initialize this attribute with a valid I/O handle (usually VISA).
    The tkawg5x0_IviInit function in this driver initializes the attribute by calling viOpen.
    Hope this helps.
    DiegoF.
    National Instruments

  • IVI Driver code in labview

    Hi,
      I need to develop a code which will control  any DMM instrument using IVI driver. does any one know how to write the wrapper for this
    Regards
    Parthipan

    Hi,
     only wrapper but the same code should work for different model of iDMM(ex agilent and NI)
    that is if my wrapper is open input to my wrapper is model no. It should open the particular model DMM.
    I mean to say OPEN wrapper is generic to all DMM instrument.based on the input (Model no or something) provided to
    the open wrapper it should call the particular model DLL
    Regards
    Parthipan

Maybe you are looking for