IviSwtch specific Test IVI Driver compliance in CVI crashing

Similar Questions

• NOR tkds5000 LabWindows/CVI IVI driver not work for TDS5104, TDS5054B

  I'm trying to get the driver NI LabWindows/CVI IVI (tkds5000 version 1,212) working for the Tektronix TDS5054B scope.  When I execute the following functions, I have the warning 'Is not a valid value for the parameter or property' of 0xBFFA0010:

  IviScope_InitiateAcquisition

  IviScope_GetAttributeViInt32 for IVISCOPE_ATTR_TRIGGER_SCOPE and IVISCOPE_ATTR_ACQ_TYPE

  IviScope_ActualRecordLength

  This is not an exhaustive list of the functions that do not work, but just that I currently see.  There are several functions that work (see this joint SPY OR file).

  The strange thing is that everything works fine when I have an oscilloscope Tektronix TDS5104 connected (file SPY OR see attachment).  The code also works when I have an oscilloscope connected and selected through MAX TDS3054 driver tkds30xx IVI of NOR.

  Is it possible that the driver of version 1,212 tkds5000 does not support fully the TDS5054B?  I looked through the files tkds5000.c and tkds5000.h, but has not seen any dependencies on the model of the oscilloscope for these functions.  Any ideas?

  Thank you!

  Dave

  So, then I thought about it.  The tkds5000 driver AND works very well.  The problem is that the Tektronix TDS5054B scope do not "initialize" some of the attributes.  For example, I had a problem reading the value of the attribute of slope of relaxation because an invalid value was returned.  If I set the slope of the trigger, first of all, then read it, it works fine.

  Its strange because most of the attributes is set to the correct value corresponding to what is displayed on the oscilloscope screen and the Panel, but not ALL of them.  In addition, other Tektronix oscilloscopes did not require a writing before reading.

  Anyway, thanks a lot NathanT.  I appreciate your help.  You saved me a bunch of time to have to go back and add in a dedicated driver.

  -Dave

• Agilent 6812 B power cord does not work with the class IVI driver

  I try to use a power source Agilent 6812 B with class IVI DISARM on RS232 driver.  I have everything set up NI Max but I can't by the initialization routine.  I tried in LabView and LabWindows and nor will not work.

  I decided to follow the lines RS232 RX/TX and I see that he is sending the "* IDN?" command and it times out before receiving a response.  Unfortunately, it does not send the Terminal newline at the end of the string.  I can cross NI MAX and send "* IDN? \n' and he responds with the ID very well.

  So my question is, would be possible that the IVI specific driver is not written correctly to send a jump as an end of line character or do I need to configure the Compote to send this character separately?  The IVI driver has been downloaded from instrumement network driver of NOR and it says it is compatible with the 6812B, but has been tested with 6813B.

  
  

• IVI driver sessions shows no MAX

  According to the tutorial of the document "Getting started using National Instruments IVI with LabVIEW or LabWindows/CVI", I have install the sofware IVI Compliance Package2.1, NI VISA5.0 and hp34401a ivi driver, but I can't find any driver in MAX4.7 sessions, it should display "hp34401a" element according to the tutorial document.could you help me? Thank you.

  Hello

  IVI Compliance Package2.1is an older version of the PIC.  Please try to install the latest version of the PIC of drivers and updates, and let us know if you still have any questions.

• How to set the properties of the EOS in the IVI driver

  I am coding a compatible driver IVI (in LabWindows/CVI) for an old GPIB instrument that does not support the EOI. To read the response device, I need to define the character of the EOS and terminate read on EOS. MAX I can correctly set the properties of communication and communicate with the device, but I do not know how to set these values in my driver. I tried if various attributes (for example with viSetAttribute (io, VI_ATTR_TERMCHAR_EN, VI_TRUE)), but still get errors (I guess I should use the incorrect session handles). How to set these properties inside the device IVI driver properly? These parameters must be active for this specific device only - all other devices on the bus use EDI. So I think that I can not just in the world, set this property on the map.

  Any help is appreciated. Thanks in advance,

  Martin

  To change VISA attributes as parameters EOS via the pilot of the IVI, your application must first acquire the handle valid VISA (VISA session) or the IVisaSession interface. The first is applied when the uses of pilot IVI VISA - C API and the latest is applied to when the IVI driver uses VISA COM API. Session handle of the IVI - C (that was returned by the function _init() ) is * NO * a VISA manage so you cannot call the API C VISA with the session handle.

  I don't know if the IVI driver you are using has such a property or attribute allowing to access the handle VISA or IVisaSession interface, but for example, driver Agilent IVI COM "IO" property, which returns the reference to IVisaSession or any good VISA com interface.

  Makoto

• You have Keithley 2400 IVI driver KE2400_32.dll c# wrapper?

  I have download Keithley 2400 IVI driver to http://www.keithley.com.cn/support/data?asset=16504

  But it only supports vb6. The driver dll is C:\Program Files\IVI Foundation\IVI\Bin\KE2400_32.dll

  I search the Forum, Assistant .NET Studio Instrument pilot measure could generate the c# of the IVI driver wrapper.

  Unfortunately, I do not have measurement studio.

  So, could someone give me a help to generate a c# for KE2400_32.dll wrapper?

  Kind regards.

  Daniel

  Here you go - see attached, I don't have a chance to test you.

• With the help of IVI driver for delay in the MSO6104A of reading

  Hello

  I have the IVI driver NOR for the scope of the MSO6104A. The driver is functional, and I managed to use it.

  My scope has a function of delay between two different channels. But, how to read delay help scope step IVI measurement?

  Is there another way to read this measure?

  Thanking in advance

  As far as I know, without delay only is not supported a measure of IVI function. For example, you can complain to ivifoundation.org first. Or, in a code module, you can use the driver of specific instruments for the measurement. This would make the application "no - IVI" so in the first place, most of the grounds using IVI disappeared. Or retrieve the waveforms from each channel and calculate the delay in a code module.

• Exception during initialization of Lecroy Ivi driver using c#

  Hello!

  We bought a Lecroy WaveRunner 64MXI-a and tried to control remotely, we have already created a resource of Visa using MAX, tested using the Panel to test VISA and everything seemed ok, we interviewed without problem.

  The problem came when we downloaded and installed the driver of the ivi of lecroy http://teledynelecroy.com/support/softwaredownload/labview.aspx, we have added references as literature has declared and initialized in this way using c#.

  Mylec ILeCroyScope = new LeCroyScopeClass();
  MYLEC. Initialize ("TCPIP0::LCRY0621N67647:inst0:INSTR", false, false, "simulation = false");

  It throws the following exceptionSystem.Runtime.InteropServices.COMException Exception de HRESULT: 0x8000FFFF (E_UNEXPECTED).

  that the exception is not thrown when we simulate = true. And we already tested it using a session simple message in function, but no luck with the ivi driver.

  Has anyone encountered this problem and found a solution? any help is useful, thank you.

  PD: I have already contacted lecroy but no response atm, I'm looking for advice here.

  Hello Nelson.

  Just a tip, I just send you an email response to your support request by email TeledyneLeCroy.

• Agilent Power Supply E3645A IVI Driver Communication error

  Hello world

  I'm trying to communicate to Agilent power using IVI Drivers. I join you MAX Report, all the modules installed on the system.

  When I run initialization of the VI for Agilent power, using the simulation with 'Specific Driver', no errors appear. But when I select "do not simulate", I get this error:

  Initialize IviDCPwr with Options.vi
  The primary error: (Hex 0xBFFA0011) function or method not supported.
  Development: FunctionId: 3, FunctionName: InitWithOptions

  Communicate with instruments instrument using Driver works fine, but using the Drivers IVI is not.

  I tried all the steps in this topic .

  PROMT any help will be highly appreciated.

  Kind regards.

  Shane5ab

  Hello, Tanguy,.

  I am pleased that install the specific instruments IVI - C Driver took care of things.  The differences between IVI - C and IVI - COM can be confusing at first.  I hope the rest of your application development goes smoothly.

  See you soon,.

  NathanT

• Problems in the use of Ivi driver ke230y in 'IviDCPwr measure [MSR] .vi.

  Hi all

  I have a problem in using pilot IVI (ke230y) to control power electric keithley2303 with LABVIEW 2013.

  After I booted and config ke2303 well and executed for 'IviDCPwr .vi measure [MSR]', it multibordure errors. For the period of 15 seconds, and then reports errors that appear:

  The code (attached) when I test it with other food such as agilent66309d and keithley2306 (with ivi driver ke230x), it works well.

  I have no idea on this problem with power supply keithley2303, can you guys never encounter this problem and can answer for me to fix.

  Thank you for your reading and your help!

  Best wishes

  Phil

  
  

• Creating a program the evolutionary IVI driver installation problems

  I have problems when you try to create an upgrade for an IVI driver installation.
  I created the installer by using the creative installer included with LabWindows/CVI 2010 IVI. In my case, I have two versions of the IVI driver DLL and configuration (1.0 and 1.1).
  1.1 - the installation program was created using the option "install existing rebuild" of the creator of the installer.

  My problem is the following:

  • If the driver of the IVI is not installed the 1.1 - installation is completed without error.
  • However, if the 1.0 driver is present, the 1.1 installer gives me the error message following just at the beginning of the installation:
    "Setup has detected a third party IVI driver in the directory C:\Program Files (x 86) \IVI Foundation\IVI\Bin. Please uninstall the existing driver before proceeding with this installation. »

  I noticed the things so far:

  • The UpgradeCode MSI remains the same for both configurations (as expected). This seems to indicate that the installation program supports upgrades.
  • The installer contains a DLL (NiIviDriverDetection.dll) used in a CustomAction to the 3rd party.
    What this DLL seems to do, is to perform a control version of the currently installed driver IVI DLL (1.0 in my case).
    According to the results of this audit, the installation process is abandoned.

  If everyone has noticed this behavior or anyone has any suggestions on how to create an IVI driver installer which can be upgraded without uninstalling the old version first?
  Maybe I put just an evil version information field, but I do not know that which (if any)...

  Advice would be greatly appreciated!

  I seem to have found a solution:

  The problem is that the MSI CustomAction, seeking a third drivers IVI (DetectAction.C1C4DD2F_AD86_44E6_BA47_FC41E5C0DAAF) is performed before the FindRelatedProducts Action.

  So the DetectAction is not ignored if an older version of the IVI driver is located (looking at the MSI tables clearly was NEITHER).

  Move the sequence numbers of the 103 to 107 behind the FindRelatedProducts Action InstallExecuteSequence shares both InstallUISequence tables (for example starting at 370) will make it possible to do an upgrade of an IVI driver installation.

  This can be accomplished using the Orca tool included in the Windows SDK.

• IVI driver does not appear in NIMAX

  If I was having trouble with one of my devices and it seemed to have occurred after I have updated NIVISA and IVI compliance to the new version 15.  I tried to get back to NIVISA 5.4 and PKI 4.6, which was when it was all working.  I accedentially also uninstalled shared IVI 2.3 components.  Once I had everything installed back (older versions) the NIMAX completely reset and none of my previously installed IVI devices appeared in the fall down to the software tab on the IVI driver session.  I started to re - install them and this seemes to work as they began to re-appear in this drop-down list.  All those who have installed a MSI file restored very well, but those who install with a setup.exe file are not.  I tried to remove and then reinstalling them them and they still do not appear in the drop-down menu.  I tried to fix the modules NIVISA and ICP and still nothing.  Those I'm trying to install is all o-scopes.  Tektronixs.  The tkdpo3, series 3 and 5.

  Any thoughts?  I think that there is something in a file somewhere resets does not correctly.

  I uninstalled and reinstalled everything and it works fine now.

• VI Initialize with OptionsString missing the resource name field when creating the IVI Driver Generator LabView 8.6

  Hello world

  We have just uploaded the latest LabView version 8.6 and there is a nice tool called generator of LabView LabWindows CVI Instruments drivers. Our driver of the instrument is an IVI driver that has a LabWindows CVI interface that uses the generation of LabView tool to create all the VI that could be used to talk to the underlying driver IVI hollow discovery of .fp, .sub and .h files. No mistake and screws more than 30 are generated automatically.

  There is an inconsistency in the Initialize function IVI driver. There is a VI Initialize driver without an input of OptionString parameter and there is a second VI with the OptionString parameter.

  Two of these screws should have a required entry field that is the ResourceName of the instrument, but this field is visible in the initialization of VI that has no OptionString input parameter and is not at all visible in other VI initialize that has an OptionString input parameter

  No idea why the second version of Initialize does not display the ResourceName parameter?

  Thank you

  Sorin

  Hey Sorin and Heather,

  I've just built your IVI driver and can see the question you come through.  What version of LabVIEW and the tool are you using?  I am looking into this further for trying to dig your problem a little more.   If you add the connector to the connector pane, the created VI meets the needs that the name of the resource exists, it's just not in the connector pane.  This can do a right-click on the icon in the upper right of the front panel and selecting display connector.  Select where on the VI wish you add the connector, and then select the name of the resource.

• create IVI driver for HP 34401

  I searched and can't seem to find if there is a driver available for the HP/Aggilent 34401 IVI? Is it possible to create an IVI driver for this resource?

  Hello Dennis,.

  Please, try the following:

  1. make sure that MAX is closed

  2 re-run the IVI for IVI 34401 driver setup and use it to uninstall the driver

  3. make sure that MAX is always closed

  4 run the IVI installer from the IVI 34401 again driver to install the driver

  5 confirm that the installer put the files (.c, .fp and .sub) at the following location: C:\Program Files\IVI Foundation\IVI\Drivers\hp34401a

  5a. also confirm that there is a hp34401a_32.dll in the folder C:\Program Files\IVI Foundation\IVI\Bin

  6. open MAX and see if there is now a session driver for the specific driver of IVI hp34401A

  7. If there is not a session driver driver, you will need to create a

  Please let us know how it goes,

  NathanT

• The IVI Driver download for E3631A Agilent expects a C: drive - solution

  Exe self extractor for the Agilent E3631A IVI driver expect drive c to exist.  I don't have drive C: self extractor opens then C: drive is no reports and they closed the extractor.  Does anyone know a work around for this?

  How can you not have a c:\ drive?  What kind of PC are you running?

  Try to rename the .exe is a zip file.  Then see if you can open it using winzip or another zip program to be able to drag files manually.