Teststand 4.0 IVI-DMM Step error

I have Teststand 3.5 and 4.0 installed on a computer and a NI-4060 in a PXI chassis.  When I try running a sequence that has an IVI-DMM step in it in 3.5 everything runs fine.  When I try the same sequence opened in 4.0 it gives me the following attached error (both attachments are the same error one is just scrolled down so you can see the whole thing.)  I have tried adding a simple IVI step from scratch in teststand 4.0 and I get the same error.
Any ideas?
Brian
Attachments:
untitled1.JPG ‏107 KB
untitled2.JPG ‏106 KB

Ok, I used the version selector, went back to 3.5, and ran the sequence and it ran fine like I expected.  When I switch back to 4.0 and ran it it worked (first time in a dozen tries.)  So I switched back to 3.5 ran it and then ran it 4.0 again and it failed.  I attached a spy capture from 3.5, 4.0 worked, and 4.0 didnt work.
Brian
Attachments:
DMMConfig_TS40_Capture_Didnt_Work.spy ‏1 KB
DMMConfig_TS35_Capture.spy ‏11 KB
DMMConfig_TS40_Capture_Worked.spy ‏12 KB

Similar Messages

  • IVI DMM step won't connect

    When I try to connect my IVI DMM Acquire step to a 34411A, I get the following error:
    ivi_IviDmm Configure Power Line Frequency [PLF].vi<ERR>
    Primary Error: (Hex 0xBFFA0011) Does not support this class-compliant feature: method %1
    Elaboration: FunctionId: 69, FunctionName: ConfigurePowerLineFrequency
    <b>Complete call chain:</b>
    ivi_IviDmm Configure Power Line Frequency [PLF].vi
    ivi_subDMMPreExecute.vi
    ivi_InstrDMMBlockState.vi:1
    I'm guessing that the IVI Dmm Acquire step is attempting to call the IVI 'ConfigurePowerLineFrequency' function, which is (apparently) not supported by the 34411A driver. Is there any way to work around this?
    Thanks,
    Aaron

    Hi Aaron,
    I currently have not found any resources that allow SignalExpress to ignore initialization errors. However I did find a resource that has the command for the power line frequency for your device (page 8). http://www.home.agilent.com/upload/cmc_upload/All/34410A_Quick_Reference.pdf?&cc=US&lc=eng
    You can modify the 34411A library so that this command is not used during your IVI DMM Acquire Step; however, I was unable to find the subDMMPreExecute.vi in a search of the project. 
    Sam B.
    Applications Engineer
    National Instruments

  • Failed to acquire a wave using ivi dmm step with a FlexDMM NI-4070

    I tried to acquire wave with a FlexDMM NI_4070 and a Read Multipoint ivi step from TestStand, it didn't went thru. Configuration step is: DC volts, 0.01 resolution, immediate trigger source, auto once range mode, 0 trigger delay, 100 multipiont sample count, 10 sample interval, 1 trigger count, interval sample trigger, none meas complete dest; Read step is: wave data type, Step.Result.Reading meas dest, 5000 time out, "failed" status on time out. What I get is failed status due time out.

    Try setting your Timeout to 30000. The Timeout is in milliseconds, while the Sample Interval on the Advanced tab of the Configure step is in seconds. You have this interval set to 10. Setting your timeout to 30 seconds will give your Read operation time to complete.
    Regards,
    Eric M.

  • Error when editing IVI Scope Step in TestStand 3.1

    When I open the edit box for an IVI Scope Step in TestStand 3.1 I get the following error: Method '~' of object '~' failed (-2147417851).  I get the same error again when I click on the Logical Name dropdown box in the edit window.  I have an IVI logical name of 'TekScope' in MAX that was created when I installed the IVI drivers for a Tektronix DPO7000.
    Software Installed: TestStand 3.1, NIMax 4.3, NI IVI Compliance Package 3.2, Windows XP Pro. SP2
    It seems that TestStand is unable to communicate with MAX.  I don't think it is a version compatibility problem because I had the same problem when using MAX 3.1.1.

    Nick,
    Thanks for the reply.  This problem went away when I opened the IVI example sequence that is installed along with TestStand.  It has not repeated since.  I can now access my defined 'TekScope'.
    I am having a problem getting the IVI code to run in simulation mode.  I modified the TestStand 3.1\Examples\IVI\IviStepTypes.seq file to change the Fileglobals.ScopeLogicalName value to TekScope which is the scope name in the dropdown box for edit IVI tools.  I then selected the scope steps and selected Run Selected Steps.  I get the following error:
    An exception occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types'
    An error occurred while executing the step.
    IVI Error: The IVI instrument failed to initialize for logical name 'TekScope'.
    Details: TekScope_InitWithOptions returned an error: -1074134964 (0xbffa004c). The option string parameter contains an entry with an unknown option value.
    Source: TSIviStepTypes
    -1074134964; User-defined error code.
    In MAX the TekScope.DriverSession - Simulate With setting is nisScope, Driver Setup is blank.

  • Using Offset Compensated Ohms from IVI DMM in TestStand

    I am using TestStand 3.5 with a PXI-4070 DMM and I want to be able to use the Offset Compensated Ohms function from the TestStand IVI-C DMM steps.  I cannot find this functionality from the TestStand step, even though it is shown on the front panel of the Soft Front Panel DMM, and is stated as a IVI function.
    Anybody with any ideas would be greatly appreciated.
    A.

    Good afternoon A,
    The Offset Compensated Ohms function that you are looking for is more
    specialized than what the IVI driver has to offer.  Instead of
    using IVI DMM, try NI-DMM.  This is a free download off our
    website, which can be found here:
    NI-DMM version 2.5 for Windows 2000/XP--LabVIEW Real-Time
    http://digital.ni.com/softlib.nsf/websearch/1F1A167276498327862570AC005199D5
    Regards,
    Mike Torba
    National Instruments

  • Latest IVI Class Step Types in TestStand

    IVI instrument classes have recently been defined for RF Signal Generator, Spectrum Analyzer and Power Meter. There are IVI drivers for these classes available for download from the Instrument Driver network. However, TestStand3 does no contain step types for accessing these drivers. Does anyone know when NI plans to add support for these to TestStand? Has anyone created step types for these classes, or have an example of how to do this?

    David -
    There is no documentation on the low-level workings of the TestStand IVI step types. As with many of the step types that have source code, it is available as examples of developing a step type in various languages.
    The additional work to add the a new class to the TestStand IVI step types is not small, that is why to date we have not done it. The amount of work could be divided into the following areas:
    * Update the TsIviStepTypes to add the new class to the enumeration.
    * Create the new step type definition (subproperty structure) based on the IVI spec.
    * Upcate the TSIviStep and TSIviSFP code to allow you to edit and perform the work to process the expressions and initiate the various IVI class operations.
    * Add low level
    IVI class layer logic to talk to the IVI class driver. This piece was previously done in a VB ActiveX control written by the Measurement Studio group in NI.
    The last two items are the biggest and they would take some time. That is why I was suggesting creating specific Action steps that call into custom code modules to talk to IVI directly, that is, no edit dialog box, no SFP, etc.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • Setting step error during Post-Step substep execution

    There is custom step type, which defines Post-Step substep:
    void __declspec(dllexport) __stdcall PostStep(struct IDispatch* pSeqContextDisp)
    AFX_MANAGE_STATE(AfxGetStaticModuleState());
    PropertyObjectPtr spThisContext=pSeqContextDisp;
    try
    return PostStepEx(spThisContext);
    catch(_com_error& xComErr)
    void PostStepEx(PropertyObjectPtr& spThisContext)
    SequenceContextPtr spSeqContext=spThisContext;
    StepPtr spStep=spSeqContext->GetStep();
    PropertyObjectPtr spResultStep=spStep->AsPropertyObject();
    bool fSomeCondition=false;
    // Evaluate fSomeCondition
    if(fSomeCondition)
    spResultStep->SetValBoolean("Result.Error.Occurred", 0, VARIANT_TRUE);
    spResultStep->SetValString ("Result.Error.Msg", 0, "Some error message");
    spResultStep->SetValNumber ("Result.Error.Code", 0, -1);
    return;
    // Continue ...
    When step of this custom step type is beeing executed and fSomeCondition evaluated to true, the error is displayed:
    Details:
    "Error executing substep 'Post'.
    Some error message"
    How to instruct TestStand to not to add prefix "Error executing substep 'Post'." ?
    thanks.misha

    Hello Misha,
    If you do not want the "Error executing substep 'Post'." string added to the beginning of your error message, you could use the following method. 
    You can set only the Error message (Error.Msg) and Error code (Error.Code) and not the Error Occurred Flag (Error.Occurred) in the post step code module.  In the post-expression of that step, you can then detect whether the error code is non-zero and set the Error.Occurred flag to True if necessary.  See the screen shot below.
    Let me know if you have any questions implementing this solution.
    Message Edited by JettR on 03-27-2008 02:00 PM
    Best Regards,
    Software Engineer
    Jett R
    Attachments:
    ScreenShot.jpg ‏88 KB

  • Multiple Step Error Caused by SQL Syntax?

    Hi All:
    I am getting a multiple step error when I do this:
    rs.Fields("MyField").Value = MyValue
    I finally tracked down the error to being caused by this syntax:
    SELECT a.* FROM MyTable a
    or
    SELECT a.MyField FROM MyTable a
    However, this syntax works just fine:
    SELECT * FROM MyTable
    or
    SELECT MyField FROM MyTable
    So what's the big deal here?
    Note: Both statements work fine in SQL Server; Oracle chokes on the aliased one.
    Doug.

    Hi Doug,
    I am having very similar problem while runnig the following statments:
    SELECT DESCRIPTION FROM ITEM, LOCATION WHERE ITEM.LOCATIONID = LOCATION.LOCATIONID "Updatable"
    SELECT DESCRIPTION FROM ITEM JOIN LOCATION ON ITEM.LOCATIONID = LOCATION.LOCATIONID " Not updatable"!
    if you figure out something pls let me know!
    Abdullah Obeid.
    Hi All:
    I am getting a multiple step error when I do this:
    rs.Fields("MyField").Value = MyValue
    I finally tracked down the error to being caused by this syntax:
    SELECT a.* FROM MyTable a
    or
    SELECT a.MyField FROM MyTable a
    However, this syntax works just fine:
    SELECT * FROM MyTable
    or
    SELECT MyField FROM MyTable
    So what's the big deal here?
    Note: Both statements work fine in SQL Server; Oracle chokes on the aliased one.
    Doug.

  • NI-DMM vs. IVI-DMM - Soft Front Panel

    Hello All,
      I have been developing a testing application that will eventually use a PXI-4070 DMM (currently simulating it in NI MAX).  I had been using the IVI DMM functions, but ran into a problem when I couldn't do a diode test (diode test is apparently not officially standardized by IVI yet).  So I switched to using the NI-DMM functions. For the most part, it was a pretty seamless transition, but there is one thing I have not been able to replicate with the NI-DMM simulation that I could do with the IVI-DMM.  When I used the IVI-DMM functions, and ran the VI, a popup opened that allowed me to enter in the simulated value that I wanted the DMM to read.  I can't get this to work with the NI-DMM functions.  Is it possible?  If so please let me know how to activate.  Thanks.
    GSinMN 
    Solved!
    Go to Solution.

    The advanced simulation exists only on the IVI class driver level (IviDmm). The IVI class drivers implement simulation features by using simulation drivers. The IVI Compliance Package (ICP) installs a simulation driver for each IVI class driver. Each simulation driver plugs in to the corresponding class driver and performs flexible output data simulation. The NI-DMM driver is a specific driver that supports series of NI DMMs, and therefore does not include the advanced simulation feature.

  • Time step error

    HELLO SIR,
    I am doing my M.E.,project in  power converters area.i have successfully designed my converter in multisim.For designing a PI controller i had linked my multisim model with labview.As per my design my switching frequency is 10KHZ.In multisim,my maximum step size is 1E-005.but in labview my minimum step size is 1E-005.so i am getting time step error.But when i run the simulation with frequency 20KHZ my desired output is reached without error.Also for duty cycle 0.5 i am not getting on time and off time equal.I have no idea how to correct my problem .Can u pls get me the solution?i have attached my snap shots over here.
    Attachments:
    forum.docx ‏121 KB

    Miguel_V 已寫：
    Hey,
    So I found out the problem with the model. Seems that when this instrument you created was made, the supply pins were switched. So you created a model with the -VS pin to be the input for positive voltage and the +VS pin with the input for the negative voltage. I would recommend double clicking on the model, Value » Edit component in DB » Symbol » Edit and change the position of VS+ and VS-. Or simply to test your circuit switch the supply and ground.
    Cheers,
    HI 
    thanks you respond
    i use TLC2274MN spice model with work 

  • TestStand Process Hangs on Wait Step

    From time to time we have experienced TestStand hanging on a wait step configured for a constant time period (e.g.. 0.2 seconds).  The execution will enter the wait step but never return from it, hanging the execution thread indefinitely.  The only way to clear this is to break the execution, then terminate, killing all threads and restart TestStand.  We all using TestStand 2010 SP1 running on Windows XP but have seen this issue on previous versions of TestStand (4.2 and 4.0).  Most of the time we execute these sequences via a .NET operator interface based on the Fully featured example shipped with TestStand, but I do not believe this is an Operator Interface issue, as it only occurs when executing wait steps. Memory and CPU usage look normal to me at the time of the lock up and we have experience this on multiple PC's.  Its just like TestStand enters a wait process but loses the plot and never returns.
    Has anyone else experienced this sort of issue, or have any ideas on what may be causing it?
    Regards,
    David

    We are still seeing this issue although we had experienced it in Teststand 4.2 (but not earlier versions of TestStand - I have been using TestStand since the days of TestStand 2).  There are no post step call-backs or post action steps of any kind.  Almost all of our sequences run in single threads. The issue is as far as I can see a lock-up on a simple wait step configured for a time period. The problem is that it occurs so intermittently it is difficult to pin down.  For instance we are running nine automated RF test stations, executing tests for up to 4 days at a time.  There can be a lot of wait executions over this period of time, as we have to wait for the product we are testing to cool to within a reference temperature window.  On average we may see one lock-up in a month, but when it occurs it can kill a 3 to 4 day test requiring it to be restarted - very frustrating for the users.
    We do execute via a run-time operator interface based on the NI example with a few modifications.  However, we have never had any problems running this, and as it is the wait step causing problems I cannot think it is just caused by the operator interface.
    Regards,
    David

  • Maximum step error count exceeded OR fatal error encountered.

    Hi All,
    I am inserting distinct records into a table. I am able to execute mapping when I call it from script. Tables are getting loaded properly bur duplicate records are getting inserted. While de-bugging
    Encountering "Maximum step error count exceeded OR fatal error encountered" error.
    Please suggest me, how to resolve this issue.
    Thanks & Regards
    Nagaraja Akkivalli

    Hi Sutirtha,
    Thanks for your response.
    I am using Oracle OWB 11g. I am adding an aggregator and minus operator to get distinct values of transaction from a table in the existing mapping and inserting the same to transaction the table.
    Please let me know if you need any information.
    Thanks and Regards
    Nagaraja Akkivalli.
    Edited by: 850144 on Apr 23, 2011 10:17 PM
    Edited by: 850144 on Apr 23, 2011 10:20 PM

  • Error from IVI switch step in Teststand

    We have the following issue when using Teststand. A reboot sometimes clears the problem, but other times it requires many reboots.
    When starting our test sequence, we undertake a Disconnect All using the IVI Step type to ensure the switches are all disconnected.
    We then get the following message:
    An error occurred while executing the step. Unexpected Error: Switch Executive failed to initialize for virtual device 'Joyswitch'
    Details: Joyswitch_init returned an error -1074118644 (0x%3)
    Source: TSIviStepType
    Any help would be gratefully appreciated
    I have attatched the actual run-time error.
    Attachments:
    Switch_Exec_error.jpg ‏122 KB

    The suggestion to try the validate option under MAX for Switch Executive would be a good idea. The error that you are seeing appears to be coming back from the IVI driver.
    Question that come to mind are:
    - You say that the Disconnect All fails, but does a Connect work?
    - What hardware and IVI driver is the Joyswitch using?
    - It appears that you are using TestStand 3.0, but what version of the Switch Executive are you using?
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • TestStand 3.1 Run Selected Steps generates Visa error -1073807346?

    When using Run Selected Step in TestStand 3.1 to interactively execute previous steps in a sequence a Visa error (-1073807346 The given session or object reference is invalid.) is generated even though the selected step has previously executed with no errors.
    Some history:
    The sequence in question was developed with TestStand 2.0 and LabView 6.1 and does not exhibit the above mentioned issue. The error began after migration to TestStand 3.1 and LabView 7.1. The sequence executes without errors in all other conditions. 

    Hi,
    When your sequence halts, does that mean it's closed the visa sessions and if so when running the selected steps are you running the setup with the open visa sessions or are you just reusing the sessions stored in the Station Globals (I assuming when you said globals you were referring to Station Globals).
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Error occurs, repair DMM software, error goes away - rinse and repeat

    This error first happened early last year, then it occurred last month and now it's popped up twice this week.  What could cause a missing library to repeatedly go missing?
    The error is in TestStand, but the origin in in LabVIEW:
    I can't recall what I did the first time I saw this error, but the last three times it happened I fixed it by repairing the NI-DMM installation:
    Jim
    You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
    Solved!
    Go to Solution.

    Jeff Bohrer wrote:
    Jim,
    What's the hardware?  TS Version and license type?  LV version?  Adaptor? (might help point to the bug)
    What are the TS step settings for load/unload? (thinking that you might be unloading the DLL in a rarely executed step then trying to reload)
    Are the sequence modules all LabVIEW code or are you calling into DMM or DAQmx from other languages as well
    I notice that your drivers are a bit out of date.  Consider upgrading DAQmx and DMM to latest. (lots of bugs have been removed in DAQmx and DMM)
    But do try setting the regisrty key first
    I'm using a PXI-4065 DMM in a PXI-1042 chassis.
    TestStand 4.0 Development System License.
    LabVIEW 8.2
    LabVIEW Adaptor
    TestStand load/unload settings don't seem to apply.  This is a well-established production sequence that is running on two ATEs and I only have trouble with this one.
    All modules are LabVIEW.
    I'm leary of updating DAQmx & DMM, but I will once I image my HD.
    I don't want to edit the registry because the problem is intermittent on only one machine and repairing the DMM installation temporarily fixes the problem.
    Jim
    You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice

Maybe you are looking for