VISA: (Hex 0xBFFF001E) the State specified, the attribute is not valid or is not supported as defined by the resource.

Similar Questions

• VISA (Hex 0xBFFF001E) error the specified state, the attribute is not valid or is not supported as defined by the resource.

  Hello

  First of all that I must say I just starting with control of the instrument using Labview. For this reason, it is possible that the problem I have is easy to solve. However, I am looking for any solution for the forum, but unfortunately I can't fint anything.

  While the situation is this: I'm looking to plug a power Analyzer (Yokogawa WT1800) with the PC through GPIB. To achieve this, I use the USB/GPIB Interface of Agilent 82357 B. The connection is done correctly because I can see and communicate with him through the Explorer NI MAX.

  In order to achieve control of the instrument using Labview, I downloaded and installed the driver of Yokogawa WT1800 (Driver instruments ykt1800) using the NI Instrument Driver Finder tool. The problem I have is that when I run the examples, I find the following error message:

  Error 1073807330 has occurred to the property (arg1) node in Yokogawa WT1800 Series.lvlib: Initialize.vi-> Yokogawa WT1800 series continuous measurement Normal.vi

  Possible reasons:

  VISA: (Hex 0xBFFF001E) the State specified, the attribute is not valid or is not taken in charge as defined by the resource.

  I tried to change the input of the open Visa arguments vi because I think that this is where is the problem, but I can't reach any solution. The following image is attached to the block diagram of the initialize.vi:

  

  Any help is appreciated.

  Thank you.

  I suspect the redirect property. Try to remove it.

• DbType attribute does not support dynamic

  I am new to CoulFusion and I'm trying to use the CFQUERY to validate data from Sql Server 2000 with the following code:
  
  < cfquery name = "GetUser" datasource = "GMP" >
  SELECT USER NAME OF GMP. GMPUSER
  WHERE USERNAME = ' username # #' AND PASSW = "#passw #
  < / cfquery >
  
  The GMP DNS was created and validated.
  
  I get the "ColFusion 6.0 the dbtype attribute is dynamic notsupport ' error validadtion."
  
  How can I fix this error?
  
  Thanks in advance.

  To begin troubleshooting, try this
  
  SELECT count (*)
  OF GMPUSER
  WHERE 1 = 2
  
  If that works, start adding things until it crashes.

• blank resource visa info during the first round

  Hi all

  I am trying to run the pilot of 6100 fluke on a fluke remote 6100.  When I run the initialization of the remote device, I always get the following error message:

  VISA: (Hex 0xBFFF000E) the given reference of session or the object is not valid.

  I followed the problem and saw that the visa being passed resource name contains no valid information (see below).  That is not sensible, since when I select the name of the resource from the drop-down list, the program has clearly recognized the remote device.  Why the program allow the user to select the resource of visa but won't visa valid for driver information?

  This error occur only during the first inning.  If the user run the program again, the error disappears.  Can anyone help?  Thank you!

  Yik

  When the program is run for the first time, visa name contains valid information:

  General

  The resource name of the canonical VISA = blank

  Visa refnum = white

  Session ID = 0

  I/O timeout = 0

  Type = 0 INTF

  Value = empty

  Stop? = True

  Condition

  session valid? Fake

  Instr is? = False

  Stop? True

  AHA!

  You select the resource from the drop-down list BEFORE the start of the loop?  An SR might help

• VISA: (Hex 0xBFFF003A) using a RS232 USB converter

  Hi, I'm reading a pH meter and it is connected to my computer by USB using a USB RS232 converter. NOR-MAX recognizes the instrument, but when I try to play the instrument in the testpanel I timeout error. When I read the status byte, it gave me the following error VISA: (Hex 0xBFFF003A) cannot start the operation because the installer is not valid (because of attributes defined in an inconsistent state). I looked in the attributes and saw the following error VISA: (Hex 0xBFFF001D) the specified attribute is not defined or supported by the resource referenced. the pH meter is a unit of office of simpel with the following characteristics: baud rate 9600 8 data bits years 1 stop only bit no control flow or parity.

  Why try to read the status byte? It is not an instrument based GPIB is?

  What attribute? I asked in your original post to attach a screenshot of MAX. Why should someone have to guess? I suspect this attribute doesn't apply to serial devices OR and is not relevant to try to read the status byte.

  Check if you are using the right type of cable and check to see if you add the correct end character. You also do not mention if you write what whether in port or just do a reading. You mention also the seller or the model number of the meter.

• Why I get this: VISA: (Hex 0xBFFF00A5) interface type is valid, but the number of specified interface is not configured.

  I searched the knowledge base NOT found Document ID: 5389BHR7. I went through the 'solution', but I already had NiVi488.dll - NI-VISA passport to the GPIB controlled. I can't find anything else on the matter. Any help would be appreciated.

  Note: this deployment has worked in the past. I upgraded from LV2009 to LV2013 last year and this is the first run my Installer on a new PC since the upgrade. I have all my VI migrated to the format of 2013. A PC running all my previous VI has been upgraded, but I did was install the runtime in 2013 and then copied all the new .exe. They all work. I imported my hardware configuration as part of the installation process.

  I found the solution. I had taken off my VISA Alias names and had the GPIB::6:INST because I had problems with a version of the VISA. This has been resolved once I got an appropriate VISA version installed. Now, this VISA was installed proplerly, I actually had to give a 'name' for each piece of equipment. This is why the error "interface number specified is not configured" message. Once I reassigned all instruments VISA on my GPIB bus with a name, everything started working again.

• VISA: (Hex 0xBFFF0015) timeout expired before the operation is complete.

  Hello

  We use LabView to control a sequencer of high-voltage (HVS448LC 3000 D) LabSmith using LabView drivers from the manufacturer, power supply. Everything works well in our program (attached) until we try to use another program on the computer at the same time. For example, if we try to open a window for our camera, or even a folder in Windows, the program gives the following error:

  1073807339 error has occurred in the CITATION read in FromHVS448.vi-> CommandHVS448.vi-> RegulateVoltage.vi-> Gated timed injections version 06.the vi

  Possible reasons:

  VISA: (Hex 0xBFFF0015) timeout expired before the operation is complete.

  We would like to be able to control the camera software and the power of LabView by using the same computer, but we do not know what could cause this problem. We would appreciate any suggestions! Thank you!

  You should really put a lot of orders of pre-instrumentation in parallel.  Force an execution order by using the wire of the error.  Serialize all commands to the instrument.  You may have an order interfere with one another.

• VISA: (Hex 0xBFFF0011) insufficient location information or the device or resource is not present in the system.

  See the other post on this subject, but my situation appeared a bit different (http://forums.ni.com/t5/LabVIEW/VISA-Hex-0xBFFF0011-Insufficient-location-information-or-the/td-p/69...

  My device manager says that the device is functioning correctly, MAX also tells me that the device is working properly, but I still get this error when I try to open a panel of test VISA in MAX or log VISA in labview.  When I click on validate in MAX under port settings that she even says that he opened a successful session of VISA.  But it does not connect in the Panel test VISA or in labview.  See the screenshots below.

  No device manager said that all was well with COM1, see the pictures attached.  I was able to get this working to uninstall the device and the removal of all the drivers and reinstalling.  Don't know what the problem was, but from the entire apparatus of zero was able to fix it.

• VISA: (Hex 0xBFFF001) timeout expired before the operation is complete. I get this error when you run a VI (instrument is set up to be controlled remotely using the TCP/IP Protocol)

  VISA: (Hex 0xBFFF001) timeout expired before the operation is complete. I get this error when you run a VI (instrument is set up to be controlled remotely using the TCP/IP Protocol)

  Please suggest a solution.

  Thank you very much, it worked!

• Paper size error: the custom paper size specified is not supported in the selected state bar

  I am trying to print on custom size paper (9.25 "x 3,875").

  I have OSX Lion and a 8600 Officepro more.

  I inserted the paper into the tray of my 8600 Officepro more.  I adjusted the sliding walls to match the size of the paper.

  I created a new custom in my print settings format.

  But the printer says:

  Paper size error: the custom paper size specified is not supported in the selected tray.

  What the...?  How that recalcitrant monstrosity to behave and do what I have to say?

  Here is the link to the manuals for the 8600 Pro JO.

  You want the user's guide.

• VISA devices with the same serial number and the vendor ID does not work (0xBFFF003A)

  Hi all

  I need to acquire the data of two meters of power YOKOGAWA with VISA driver (USB connection).

  They work very well if used alone, but they do not work when are used toghether. In particular, when I plug in and turn on the two of them, NOR MAX shows me the following error message:

  0XBFFF003A (VI_ERROR_INV_SETUP)

  viFindRsrc return 0xBFFF003A (cannot start the operation because the installer is not valid (because of attributes defined in an inconsistent state).)

  Please make sure that VISA is properly installed on this system.

  Possible causes of this error:
  1. more than one passport may be to attempt to claim the same resource.  You can try to disable passport to understand which Passport is the cause of the error.
  2 you have connected multiple no configured plug-and-play devices that have the same name of the resource. For example, the vendor ID and the serial number may be the same.

  In fact, according to MAX, both power meters have the same serial number and the same vendor ID; so, this seems to be the reason why they do not work together.

  Can someone help me?

  Thank you all

  
  

• VISA driver on the connection type unknown

  I can't be the only person having this problem in LabVIEW and I have not worked on the solution.

  Let's say for example I write a driver for a power supply, this device is off the shelf, but the manufacturer provided driver is *!

  Instrument is connected through GPIB. in this case.

  3 months later, I would like to re - use the driver but due to the implcations cost I can not have the flavor of the instrument GPIB and need the RS232 version, so I re - write the pilot so that all the functions of R/W are shrouded by a VI using the right process for the reading of serial ports if a RS232 device and repeat the initialization of the process too.

  3 months later I get my hands on a USB version of the PSU - he uses the style GPIB code and does not take long to change.

  The question is this:

  Is it all as anyone knows (alias VISA ignoring) that will allow me to determine the physical to the PSU from the PC connection, if someone changes and therefore to use the correct part of the code driver to initialize and communicate with the power supply.

  Specifying the Intf Type is a fix SW for a HW problem that causes more problems if the connection is changed, how can I allow someone to use RS232/USB/GPIB and detect the connection type myslef in LabVIEW, before making a * IDN and the harbor onpen?

  Thanks in advance for any ideas

  James

  Have you looked at all the drivers NOR? The example of the expedition of the Agilent 34401 is sufficient. In the Initialize function, there is a test to see if the resource VISA is a serial port. The case statement for the true condition sets up the port. There is no other changes such as GPIB, USB connection or Ethernet works exactly the same way.

• VISA IC returns the 0xBFFF003A error code when reading the USBTMC device

  Hello

  I'm creating a USBTMC device and have some difficulty to determine why a viRead returns the 0xBFFF003A error code. Strangely enough, it reports also to read the correct byte number and the buffer contains the correct data. I use VISA IC 5.1.2 but I had the same problem with version 5.0.3. I have no problem with the device recognized by VISA IC, MAX, LabVIEW SignalExpress or LabVIEW. Using the previous version of VISA IC performing an async read would return a code completion, 0x3FFF009B (VI_SUCCESS_SYNC).

  The attachment of the utility Trace all communications from e/s or watch for when the USB cable is plugged into the computer.

  Lines 1-18 LabVIEW SignalExpress 2011 has begun

  Lines 19-35 VISA IC: open the selection

  Line 36 VISA IC: claire

  Line 37 VISA IC: Read - 10 characters

  Line 38 VISA IC: Read - 21 characters

  Lines 39-44 LabVIEW: open, read 21 characters

  Line 45 VISA IC: Read - 18 characters

  Line 46 VISA IC: claire

  Line 47 VISA IC: Read - 18 characters

  Line 48 VISA IC: closed

  Note: LabVIEW crashed on line 44.  At the moment I know not whether that is related to this problem or not.

  Full error description: failed to start the read operation because the installer is not valid (because of attributes defined in an inconsistent state).

  I'm confused by why it says it cannot start operation when in fact, it returns the requested data and attributes that it refers to? I reviewed the USB descriptor values that I use, and they look correct to me.

  Any ideas?

  Thank you

  Hi Perry,

  I found the problem.  The TransferSize didn't get converted from big-endian to little endian and 0x0A was considered 0xA000000.

  See you soon,.

  Airaki

• VISA: Is denied access to the resource or to the remote machine.

  Hello.

  I use a cRIO-9076 to communicate with a Keithley 2400 via port RS-232 on the cRIO. I have a vi test which is built using the Keithley 2400 drivers and it works perfectly fine with the vi is located under 'My Computer' in my project. If I'm moving that vi on the potion of distance OR cRIO9076 of the project and try to run the vi I get a

  VISA: (Hex 0xBFFF00A8 to the resource or the remote machine access is denied...

  I realized I need to add something to the list of remote access on the cRIO that I find a little confusing. I want to use the serial port on the cRIO by VISA to communicate to the Keithley, so I need to give permission to cRIO on the cRIO? I'm obviously confused.

  I tried to add a simple * (wildcard) to the list of access as a temporary solution but I still get the same error.

  I would like some advice.

  Thank you

  Roth

  cRIO 9076

  Lab View 2013

  Keithley 2400

  NI-VISA 5.4.0

  If you want to move the vi to the CRIO, you can change the name of the resource.

  my example is based on the cRIO-9068. When running at MAX on my local host, it can show as below.

  The resource for the cRIO-9068 should like 'ASRLx:INSTR '.

  

  Good luck!

• Instrument not listed is not in the resource of VISA

  I have a GPIB resource.  He appears in MAX, but not on behalf of the constant resource.  I checked I/O filtering and updated the name of the resource, but the problem persists.  What is going on?  See attached picture.

  I tried some of these approaches, but they are not what I'm looking for.  It seems that even if the resource does not appear on labview, and I'm still able to talk to her if I manually enter the name of the resource.  The GPIB-USB instruments are those that gave me problems, because I would like to know the address specify the instruments but not their interface IDS. They use different controllers.

  I've written a vi this loop by interface 0-4 with a primary issue specified address id the * IDN? command and check the answer.  With this method, I am able to find the address of the GPIB string and speaks with the same visa instruments does not have this resource.

  I hope that this method will be held up through time.