IVI - c. in TestStand

Hello

right now Im using the trial version of TestStand 4.0 if it suits my requests. I saw in the "Palette of Insertion" steps of the IVI - C. Whith them it should be possible to connect to a DMM or scope or...

So I installed the IVI Compliance Package and driver for my device "hp34401a". But how do I set up the driver to address good feature? In the documentation and help files, I read that MAX is communal, where can I get it from?

Frank

(I just TestStand installed no LabView or LabWindows or Measurement Studio)

I knew I need to activate a special Max dll to access my Gbspecifications card to (agilent).

now it works almost well

Tags: NI Software

Similar Questions

  • Unable to remote control Tektronix TBS1062 with USB Interface

    Hello

    I recently downloaded IVI Driver for Tektronix TBS1062 of national instruments.  I use the USB communication. I have configured the instrument NI Max and can identify the instrument successfully. However I'm unable to use other functions using the driver of the IVI. Stage of IVI to NI TestStand always runs without error and Trace of e/s OR watch VI_SUCCESS but I don't see any channels settings horizontal scaling and scale veritical configured by the IVI step. The horizontal and vertical scales are always the same.

    I'm not really sure, but would it be because of the USB interface? The driver supports USB?

    Anyone have the same mistake or could someone please help solve this problem.

    Thank you very much

    First thing I would do, is to ensure that the instrument is configured correctly to accept orders via the USB.

    After that, try to send commands through MAX to see if the range reacts.

    Make sure that you are not using a simulated IVI session.

  • Keithley 2000 not identified NOR Measurement and Automation Explorer using GPIB

    Hello

    I recently used NI TestStand and NI MAX with IVI drivers to get my working(using USB) peripheral. He has worked successfully for TG5011 and TDS1002B Oscilloscope function generator.

    Following the same procedure: I started with 2000 model DMM of Keithley with GPIB.

    I am facing difficulties in finding my camera on OR-MAX devices and interfaces. I use a GPIB KUSB - 488B USB adapter to connect.

    I can interact with the device of VISA Interactive Control and KUSB diagnosis tool and you can see the device in the device Windows and KI-Configuration Utility Manager. Surprisingly, I don't see GPIB Board in the NOT-MAX.

    Help, please.

    System details: NI-VISA 5.2 installed on Windows 7, KUSB-488 driver installed in command compatibility mode OR. (only ieee_32m.dll is present), installed UN NOR-488.

    Thank you

    Martin

    To help all those who have read this thread:

    I had the Keithley 2000 NOR-MAX and NOR-Test Stand using IVI Driver (for Keithley 2000 of NOR) using the KUSB - 488 B (GPIB to USB adapt from Keithley).

    Layer of keithley installed IO Keithley and I can see the unit property. I then followed the procedure for IVI MAX and TestStand pilot program and IT WORKED!

    Please find attached the screenshots for Visual clarity.

    Thank you and best regards,

  • PXI-5402 IVI TestStand 4.2 returned "niFgen_InitWithOptions" resource not found

    Hi, I am very new in TestStand.

    I hope someone could help me.

    I have a complete sequence in which an ivi should initiate a PXI-5402.

    (It is an old sequence that I inherited. It is now my job to make it work again).

    We have another system with a PXI-5401 (appears to the MAX as traditional-DAQ) which works very well with this sequence.

    I created a new sequence in order to simplify troubleshooting with just "IVI Fgen" step.

    When in click on 'Validate' and uncheck "Simulate" and hit "Init", I get:
    niFgen_InitWithOptions returned an error:-1073807343 (0xbfff0011). Insufficient location information or the requested device or resource is not present in the system. If the resource descriptor is a name of IVI, it must match the entry in the store of IVI Configuration in a case-sensitive manner.
    Source: TSIviStepTypes [error Code:-31619]

    In NOR-Spy I get following error
    > Status: 0xBFFF0011 (VI_ERROR_RSRC_NFOUND)

    I think that I have configured all correct. Please see attached screenshot.
    I tried different names IVI-logic...
    For this remove as first cause, I direct the pilot Session that appears correctly on the iviConfiguration of reference.

    Thanks in advance

    OK, I got it...

    This is the well known problem with DAQmx Configuration in MAX.

    Described in the title:

    http://digital.NI.com/public.nsf/allkb/22CF7E6B27B6995B86256DDB0058F39B

    I had post a logic-name link with DAQmx device instead of PXI-Device.

    Thanks anyway.

  • TestStand IVI read Test of numerical limit

    Hey all,.

    How to turn a DMM IVI reading in a test step pass / fail based on a test of numerical limit?

    I'm a novice TestStand so be gentle.  Search the Forum of TestStand IVI and success failure does not return anything useful.

    I can call the DMM through reading IVI that returns a Step.Result.Reading but I need to turn this into a past fails on a beach to limit.

    Any ideas would be very warmly.

    Thank you

    You can insert a step to limit digital none_adapter after she and assign the data source PreviousStep.Result.Reading.

    -Doug

  • IVI Configuration with the PXI-4110 in TestStand

    Hi all

    Implementation:

    PXI-1033 connected through MXI to a PC running Windows 7. LabVIEW 2014. TestStand 2014 (32 bit). DMM PXI-4110 food and PXI-4070.

    In MAX, I can open two soft signs and two control units and they work great.  In LabVIEW, I can control the two cards as well.

    MAX I put in place a pilot and a logical name for my DMM. This unit works very well within TestStand using one-step IVI DMM.

    I then configure the 4110 to the MAX with a pilot of the IVI and logical name. Here are my settings:

    Name: ni4410_PS

    Material: Immobilization of additional hardware and select the PS. This is checked, any other assets are checked.

    Software module: NOR-DCPower, 4110 is listed as a device supported.

    Virtual names: It is where I am confused, under the name of physics there are four options that arise (0, 1, 2 and 3). This power has only 3 exits, so I'm not sure why four rise. I've done 4 virtual names, one for each of the options. I named the ch0, ch1, ch2 and ch3 respectively.

    When I put a power of IVI step TestStand, everything seems to work. I open the configuration window and set my values for each channel. If I try to validate the configuration by deselecting simulate and click init I do not receive an error.  As soon as I click on 'Set up' or 'Show Soft Front Panel', I get the following error:

    "IVI operation failed set to the name of lgical"OR PS 1'. Details: Possibility of Extention not taken care of by instrument driver. (Base) (- 30717) »

    Any information would be appreciated.  I tried to play with it for a few hours yesterday and a few colleagues trying to help.  We are all under the assumption that it should work.

    Thank you!!

    Jesse

    Hi jesserzamora,

    Did you see this link: http://digital.ni.com/public.nsf/allkb/331F2717DBCD1F858625758200745773?OpenDocument

    It addresses a failure similar to the step of IVI Power Supply of TestStand.

  • I am using IVI step switch in TestStand 4.1.1 and also try to call the Actions of LabVIEW using IVI

    I use IVI pass the stages and steps of IVI DMM TestStand 4.1.1 and then I have an Action step that IVI spend IVI DMM and features.  The problem I have is that if I run the VI in LabVIEW bear only functions without any error, if I run of TestStand without all previous calls to switch IVI or IVI DMM it works also, but if I run the sequence with a step of IVI teststand pass first I get the following error:

    Initialize IviSwtch with Options.vi
    The primary error: unknown status code (Hex 0xBFFA4001)

    «"" "String of full appeal:»»"»
    Initialize IviSwtch with Options.vi

    -1074118655; User-defined error code.

    I remember there used to be a problem with the steps of the IVI and IVI running LabVIEW, does anyone know if this problem has been corrected?

    Other ideas would be appreciated.

    Hello Kevin,

    It is a question of trying to open more than one session to a particular device of IVI.

    Here is a knowledge base on the issue. I found this knowledge base by searching '1074118655' or 'TestStand IVI Action no' to ni.com.

    Please let me know if you have any other questions.

  • To access the channels: Teststand - LabWindows, IVI

    Hi all

    I am trying to initialize a driversession with a logicalName which is stored in a variable of string teststand. Please take a look at the following code fragment. s_PMI_init (ViRsrc logicalName, idQuery resetDevice, ViSession ViBoolean ViBoolean * vi) is a function of my custom, class driver which I loaded dynamically. Someone at - it any idea why initialization fails? I think it's a simple mistake, but he drives me crazy...

    ...
    ViRsrc * logicalName = NULL; Char *.

    TS_PropertyGetValString (data-> errorInfo, "Step.LogicalName", 0, & logicalName & seqContextCVI);

    MessagePopup ("Info", logicalName); Watch logicalname right

    s_PMI_init ("drvsession", FALSE, FALSE, & session); works
    s_PMI_init (logicalName, FALSE, FALSE, & session); does not work why?
    ...

    Thanks in advance
    7even

    Hello

    Here is a small piece of passing the LogicalName direct to the function:

    This example test module acquires the session of the instrument by name.  Provided that
    There is another reference to the session, this module does not create or
    reset the session.
    void __declspec(dllexport) __stdcall ConfigureDMMForVoltageMeasurements (const char * logicalName,)
    short * errorOccurred, long * errorCode, char errorMsg [1024])
    {
    error int = 0;
    ErrMsg errMsg = {'\0'};
    ERRORINFO errorInfo.
    ViSession handle;
    Session CAObjHandle = 0;

    get a reference to the session
    tsErrChk (SM_GetSession (logicalName, & session & errorInfo));

    get the handle of the screwdriver (you need not to release)
    tsErrChk (SM_GetHandle (session, NULL, SMConst_ClassDriver,
    handle, & errorInfo));

    call the instrument as much as you want:
    errChk (IviDmm_ConfigureMeasurement (handle, IVIDMM_VAL_DC_VOLTS, IVIDMM_VAL_AUTO_RANGE_ON, 0.001));

    You can find this example in \TestStand 4.2\Examples\SessionMgr\CVI\

    Hope this helps

    Concerning

    Ray Farmer

  • How do I configureiDMM to work in Teststand 4 (IVI)?

    I try to use the validation step Dmm IVI - C TS and configuration using Agilent 34401. I check this set OR the last compatibility that it installed and latest of Agilent IVI driver as well. I have set up the driver Ag34401 in MAX but do not know what to put in the physical name and Configurable setting tabs if necessary. I put a pilot session and the logical name, but I don't know if entry for the virtual name or initial necessary setting. Under Labview code, the driver to behave normally in simulation mode and real mode. TS modify IVI Dmm, it will work in simulation mode. When I try to work with the DMM 34401 he will init and change of status from a distance but fail configuration or reset. I am attaching the file errors OR spy.

    The compatibility test found several problems with the Ag34401.dll, but I don't know if this means that the driver has some problems.

    Compliance test class: DMMspecific Instrument: Ag34401path of the Module: c:\Program Files\IVI\Bin\Ag34401.dllDate of the Test: 10/04/2009, 11:19:42   compliance summary of tests: the driver is compatible with the Inherent group capabilities.   The driver is compatible with the following IviDmm groups:   IviDmmMultiPoint IviDmmTriggerSlope IviDmmDeviceInfo IviDmmAutoZero ERROR: the driver is not compatible with the following IviDmm groups:   IviDmmBase IviDmmACMeasurement IviDmmFrequencyMeasurement IviDmmSoftwareTrigger IviDmmAutoRangeValue IviDmmPowerLineFrequency the driver does not implement the following IviDmm groups:   IviDmmTemperatureMeasurement IviDmmThermocouple IviDmmResistanceTemperatureDevice IviDmmThermistor please help by providing instructions or example. The example of TS for IVI does not work for the same reasons mentioned above. Thank you. Elik

    What surprised me that he did not show up while coding in Labview. Everything worked fine until I tried TS IVI - C.

    Thanks anyway.

  • DAQmx Switch vs NI Switch vs IVI

    Hello

    just had information DAQmx switch screws are recommended to use written.

    Just to be sure... If I use IVI TestStand switching, I don't have to worry about it, I do?

    See you soon

    Oli

    Don't you need not worry about this.

  • Type of step IVI supports NI-SMU-4112?

    Hello, guys

    I have a SMU-4112 and four of the PXI-4130. When I try to configure my SMU-4112 with PowerSupply IVI step Type, an error occurred.

    -------------------------------

    An error occurred the call "RunStep" in "ISubstep" of "ZNIUGOL of Types of step TestStand Ivi"
    An error occurred during the execution of the step.
    Component works IVI control error: IVI configure failed for logical name ' 4112 ".
    Details: Attribute or property not supported. Attribute: NIDCPOWER_ATTR_OVP_ENABLED, Channel: 0 [IVI. Error Code: BFFA0012]
    Source: TSIviStepTypes

    --------------------------------

    Surely, I disabled the checkbox "OVP on" editing it IVI Power Supply stage dialogue. My system configuration is,

    IVI Compliance Package 4.6

    NOR-DCPower 1.8.6

    SP1 OR TestStand 2012

    My PXI - 4130 s work well with the type of step of IVI. Type of step IVI supports NI-SMU-4112? Or I do something wrong about this?

    Kind regards

    Joonam

    Hi Joonam,

    PowerSupply IVI step does not currently work with the 4112.

    The 4112 can't stand the ÖVP.  If the NIDCPOWER_ATTR_OVP_ENABLED attribute is set to True, the error you described is expected.  If it is set to False, no error should be generated.  However, an error is generated when it is set to false.  This is incorrect behavior in the pilot and has already been documented under the Corrective Action report (CAR) #437105.  This question will probably be corrected in a future version of NOR-DCPower.

    Step PowerSupply IVI is hardcoded in the attribute set to true or false, depending on the value of the checkbox in the tab limits.  Workaround for this problem is to replace your PowerSupply IVI step with a step based on a code module that does not seek to set the OVP_ENABLED attribute at all.

    I apologize for any inconvenience that this is for you.  Let me know if you want more details.

  • IVI agilent Funcgen 33522 B

    Cannot get the IVI driver to work with Agilent 33522 B generator functions. (VISA funktions work well)

    I installed the driver of the IVI - C.  (http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=A1C02CABC2854F97E0440021287E6A...

    It adds a 'driver instruments Module' ag3352x. (IviDriver 1.1 IVI - C and IviFgen 5.0 IVI - C)

    Added a 'logic' and selected name the session "Driver" (ag3352x) and selected the material resource (GPIB0::11:INSTR)

    Tested with the "simulate with" set to the works of specific driver, but when I set it to not simulate I get "0xBFF0015 timeout expired" in LV and TestStand.

    33522B unit switches mode to distance and communication show 2 error: header not defined-113, query-420 UNTERMINATED.

    Is this a bug in the IVI driver? or have I missed something.

    PER DAY

    I got the job of communication. (after trying different drivers and settings)

    It seems to be the name of 'physical' and 'virtual' for 'channels' of MAX's name was the problem.

    The default physical name must be changed to something other than '1', although the Canadian standard requires that the name of the channel is '1 '.

    If it works if I have something like "Channel 1" the virtual name value and then use '1' in BT or Teststand.

    (In Teststand you must change the name of the channel pre-filled (in this case channel 1) to '1')

    PER DAY

  • Scope Agilent MSO6104A and IVI steps

    Hello

    I use scope Agilent MSO6104A that is connected via Gbspecifications FOR.

    I would like to control the scope by following the steps in TestStand IVI (TestStand 4.2).

    I have downloaded the driver 'IVI - COM, IVI - C Version for 5000, 6000, 7000, 546xx 1.3.20.0 series Oscilloscopes' of the Agilent site and installed.

    Agilent IO executable is installed as well.

    The logical name of the instrument is created in MAX.

    Then, I tried to communicate with the scope by TestStand IVI markets.

    I copied the scope of the steps of the sequence of the example.

    IVI step with the 'Init' operation tools works very well.

    But the IVI measures fail.

    For example, 'Configure 1 channel' fails with the following runtime error:

    Details:

    An exception has occurred the call "RunStep" in "ISubstep" of "ZNIUGOL of Types of step TestStand Ivi"
    An error occurred during the execution of the step.
    Error of component control works IVI: IVI configure failed for logical name 'MS06104A '.
    Details: IO error: %1. [IVI. Error Code: BFFA4214]
    Source: TSIviStepTypes

    Error code:

    -32032; User-defined error code.

    NEITHER spy errors also (see the attachment).

    Thanks in advance

    I think you might have more luck if you use the pilot of the IVI-C written by NOR.

  • TestStand crashes when you use the feature of LENGTH

    So I have a problem when you use the TERM built on stage.

    the first time I run my sequence everything goes normally...

    the second time I try to run the sequence it freezes teststand.

    I have notices that when I run my sequence. I can see on TRACK OR the following:

    niSE_opensession

    niSE_connect (routex)

    nise_disconnect.

    but after that the sequence is complete. It is not close to the niSE sesion. that this has something to do with the gel TestStand?

    If this isn't the case, have you had this question before?

    I contacted pickering... they got me new drivers

    Response of Pickering:

    It sounds like the problem which came first when NEITHER Visa has been changed, version 5.2 or higher, I think. In any case, I'll try first to install the latest version of the Pickering IVI driver.

    http://downloads.pickeringtest.info/downloads/drivers/IVI/pi40iv_4.10.1.exe

    I installed them and it works now...

  • IviAcPwr type available step by Teststand?

    Hello

    IM'using Teststand 2010 & Labview 2011 and I wanted to kind of step in the work with the IviACPwr class...

    I found Dmm, scope, Fgen, block (DC) power & switch...

    Could someone tell me if there is an update for the step of IviACPwr type?

    Thanks for help.

    GG

    Consistent IVI 4.4.0 package.

    There is not a stage built for IviAcPwr in TestStand type.

Maybe you are looking for

  • Encrypted files

    Boot drive is encrypted by using File Vault.  If I copy a file to a USB stick, this file will be readable on another Mac or PC?

  • Photos can not find the original files

    Since the switch to Photos for Mac, when I double click on a thumbnail to enlarge, a large percentage of my photos have a message that the original file is not found and gives me a chance to find the missing file. In iPhoto, where migrated most of my

  • How to reconnect the Mail on my Comcast account?

    Mail lost its ability to access my Comcast email account. He had lost the ability to send until I updated to El Capitan yesterday evening and changed my password for Comcast today. I can log in and access my account window and Comcast webmail through

  • Load Windows XP from external DVD drive

    Replaced the hard drive on laptop. DVD drive does not work on the laptop. How to install windows XP from an external DVD drive hard disk new?

  • I have a Dell OEM copy & Home Student 2007 office came with my Dell laptop.

    I have 2 machines from Dell and have now bought a laptop HP Mini 110 with XP. Can I install the copy Dell Office 2007 on the HP OEM or I have to buy new software? I use the trial version of 60 days on it now that expires in a few days.