IVI, error-1074130425

Similar Questions

• Determination of 4070 self-calibration P/F

  I calibrate by automatic programming 13 PXI-4070 DMM-based daily and must determine whether or not the auto-cal spent on each. I never had a self-cal failure so I don't know really what to expect. An error or a warning will occur? If Yes, what are the possible error/warning codes I need to check? Currently I compares the date of the auto-cal obtained from the DMM before you run the auto-cal with the date of obtaining self-cal post. I guess that the date does not change if the auto-cal fails. What is a good hypothesis?

  Thank you.

  S-T-G,

  Depending on what environment you are programming in (b, LabVIEW, CVI, etc.) it will vary slightly know more precisely how you can determine whether or not any function going.  A successful return of a function returns 0, so you can check for this.  If you receive a nonzero number (you should if the call to auto-cal fails for some reason any), you can determine what means this error code. In LabVIEW, for DMM, you can use the IVI Error Converter VI niDMM to interpret the error.  If you are using CVI, C, or another text-based programming language, you can pass a value of nonzero return to the niDMM_GetError() function.

  Regarding the specific error codes that can be returned a failure of automatic calibration, there is a little, it is difficult to give you an exhaustive list but it can fail for various reasons (excess of scale, driver not installed correctly, etc.).  The proper way to check for failure is to check against IVI_SUCCESS or equal to zero, then if she is unable to call the function appropriate to obtain descriptive error string.  If you're curious, nidmm.h comes with the driver contains a list of the NOR-DMM more specific error codes.

  For a better idea on how to do it, I suggest to take a look at examples of automatic Calibration that are provided with the driver.

  I hope this helps.  Let us know if you have any other questions.

  Thank you

  Tobias Gordon

  Software engineer

  Digital Multimeters
  National Instruments

• The IVI Drivers: RangeCheck of initialization option set to true: failed to get an out-of-range error

  Hello

  I'm new to IVI drivers (started using them last week) and I have a problem with the option of initializing RangeCheck.

  So get used to the IVI drivers, I used the example provided with the AgilentE36xx IVI - COM driver (on my computer, it is located in C:\Program Files\IVI Foundation\IVI\Drivers\AgE36xx\Examples\VS.NET\Cpp\Example1).

  I could do everything I wanted except get an error out-of-range, during the passage of an out-of-range value to a function. I put the RangeCheck init option to true, but I don't have any error in the simulation, nor with the connected equipment.

  Attached is the code (from the example of Agilent) but modified so that it should throw an out-of-range error when adjusting the tension on the following line: spOutput1-> VoltageLevel = 1000; ... why no error.

  Still, it runs correctly. Can someone tell me what I'm not doing correctly.

  Kind regards

  Roman

  Hello

  I posted the question on the Forum of Agilent.

  Here is the link to the post: http://www.home.agilent.com/owc_discussions/thread.jspa?threadID=33348&tstart=0

  The problem is now resolved. Thank you for your help.

  Kind regards

  Roman

• 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

• Driver IVI does not not after the creating application. Get the error 103 "no IVI class session open...» »

  I have an application that is really great to work in Labview and control a bunch of test via the IVI drivers equipment.  I want to build it and make a request.  First of all, I want to just make a request.  Then, I want to do a stand-alone application through the installer.  When I integrate it to an EXE file, then run it on the same machine with installed Labview; It gives me an error:

  "No don't open class IVI session. You must call the class driver VI Initialize before calling a specific driver VI. This error can also occur if the logical name IVI control is set to the IVI evil class. »

  Same computer on which it runs well in Labview.  I don't see any option when generating that look like they have nothing to do with drivers.  Any help?

  He was the driver.  I think I have downloaded the driver at a bad time, when it has been updated.  I got a new today and it works great.

• Problems to show the driver IVI and property loader error messages when you use a type of operator interface

  I use UI operator (programmed in ICB, with asynchronous timer) in the folder OP1 in attached zip file. This operator interface does not have the error message from the driver of the IVI, properts, charger etc. on the screen (messages as in the photo attached error.jpg in zip file attached). Due to stability problems, I use this operator interface, but I need these error message. One other operator interface is OP2 in attached zip file. This operator interface puts the error message from the driver of the IVI, charger properts... on the screen (messages as in the photo attached error.jpg in zip file attached). Now, I want to have this feature with OP1 for reasons of stability I use OP1. How can I implement this in OP1? I tried and tried a lot of time, but I have not found a method to implement this. can someone help me? Thank you kind regards Samuel

  Hello, Johann,.

  I'm not sure you understood my problem. My problems are not the IVI and loader drivers error messages property! But my problem is, that errors of the IVI drivers and property loader operator interface does not bring on the screen. So to test this situation, cause an error of the driver of the IVI or shipper of property, then you can see that with a PC, you have an error message and with another IO no error message takes place and the test of stocks without a message. Do you know why this OI does not show the error messages and how showing the error message can be implemented in this operator interface

  concerning

  Samuel

• Setup of the 4.1.0 IVI compliance 'Photos E:\My' package error is not available

  I try to install ICP4.1, on the XP machine without maps OR or the software installed.

  The installer says:

  This installer needs to access "my images". However, this 'E:\My Photos' location is not available. Make sure that this directory exists and is available, and rerun Setup.

  I don't have any drive "E:\. » ! so I can't create it!

  OK, I found the problem!

  I needed to add this to the registry database:

  HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\My photos

  must be set to %USERPROFILE%\My Documents\My Pictures

  with type REG_EXPAND_SZ

• Unknown channel or name of the repeated feature - settings MAX IVI

  Hi all

  I have problems with the creation of a pilot application based on IVI. I use Agilent N6700B PowerSupply simply configure and output voltage via GPIB with LV2009 (and Win7). The main issue is with the name of the 'channel' I need to specify in the application. Could someone please confirm ChannelName should I use and if the MAX settings are correct? I have attached all necessary files.

  When I run my application I get following "IviDCPwr IVI Converter.vi error error message

  The primary error: unknown channel (Hex 0xBFFA0020) or
  name of the feature repeated.

  Complete calling chain:      IVI IviDCPwr
  Error Converter.vi IviDCPwr
  Configure the output Range.vi GPIB.vi"

  Any help is very appreciated

  Kind regards

  PK

  Hi, PKI,

  The correct physical name for the channel is '1' and it was filled for you by the driver under the advanced > Instrument Driver Software Module (see MAX1.jpg). You can name your virtual channel name well you want under the pilot Sessions > section virtual names, but the physical name must always be 1 as specified in the driver (MAX2.jpg). In your application, make sure that you use exactly the same name for the virtual channel as recorded in MAX.

• IVI go check if routes are connected

  Trying to connect a route connected already will generate an error.

  What is the best way to check if a group of route is connected before you try to establish a connection?

  I m using IVI and Switch Executive to connect/disconnect the route groups.

  Try to build a switch sequence something like that.

  Get the name of the group as an argument road. First, check if the routing group is connected (avoiding an error). If not, connect the Group itinerary, otherwise do nothing.

  Using the 'Get information' operation and entering the "route"(not groupe) in the channel 1 and channel 2 and checking the status seems to work ".

  But it seems to work by using road names (not the itinerary for group names).

  And I can't find how to resolve route of group names to links using IVI switch stage. (can make using Labview. but you can't combine LV IVI and IVI switch)

  PER DAY

  You are looking for routes multiconnect. This is a setting that you can configure in the NI Switch Executive (NISE) for routes individually.

  Enabling this setting allows a road linking several times without generating the error that you have mentioned.

  However, a way of opening must be as often that you closed before. It is the task of the calling application to keep track on how many times you have closed or you just repreat by opening the road until you get an error of NISE.

  I think that already there is the feature request NISE stores the number of closures by route and add functions to query this information. Unfortunately, I have found it in less than a minute so maybe you want to spend more time to find. If you can't find, please do not hesitate to post (in the idea exchange forums!).

  Thank you

  Norbert

• 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.

• 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

• Steering switch error

  Dear all,

  I get the following error when you try to create a new virtual switch Exec feature. I also have similair reported errors when you try to use current virtual devices that worked for a while with no problems.

  Can someone shed light on why this happened and what I can do to solve it? All the other functions and Labview code work as expected.

  

  Thank you very much

  Matt

  Thank you very much English.

  I had changed the Alias of Visa for the switch (logical name IVI = Eagle_Audio_Matrix), but failed to change the descriptor resources on the Hardware tab in the pilot session.

  Obviously a slightly more informative error message would have helped, but I'm happy that now it works again.

  Thanks again.

  Matt

• Error-1074118625 with the PXI-4071 and PXI-2527

  When you use the LabVIEW and PXI-4071 PXI-2527 IVI drivers, I get a 1074118625 error in TestStand.  The sequence that initializes the MUX, init DMM, connects the MUX, expected debounce, and then to the DMM reading, I get this error.

  Error: niDMM .viExplanation of waveform (waveform data) reading is not found for the requested status code.

  Check that the required status code is correct.

  [Error code: error code defined by the user of 1074118625.]

  This sequence of events is used successfully several times elsewhere in the TestStand.  This error does not appear in any section of the knowledge base, or any help.  Any explanation would be greatly appreciated.

  I found this with google that seems like it could apply:

  http://digital.NI.com/public.nsf/allkb/A593DEBFD86A69C68625727900748EEC

• 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.