Similar Questions

• VISA READ timeout error - several GPIB resources

  Hello

  I'm working on a network 3 GPIB instruments (Optical Attenuator, amplifier in fiber, spectrum analyser), controlled using VISA sessions in Labview. When it is run separately, the three corresponding screws (which are located in three different Labview projects) works as expected. However, when they ran at the same time, one gives them timeout-1073807339 VISA READ errors. These errors seem to occur when another instrument is sending / receiving data / instructions at the same time that she is.

  The exact context of the error is either:

  -an another VI is running, which includes sending several requests and responses every 100 ms, reading

  -by failing VI starts, I get an error of waiting time among the first Subvi containing a VISA READ operation to perform (sometimes initialize.vi (in situation 1), sometimes one of the subVIs connected the rest State (State 0) on the time-out of the structure of the event).

  or:

  -the default VI is running,

  -by starting another VI, which includes repeatedly sending requests and reading the responses, the failing VI up a mistake among the first Subvi containing a VISA READ operation to run (one of the subVIs linked the State of rest (0) on the time-out of the structure of the event).

  What I tried:

  -gradually increasing the delay between the VISA WRITE and READ operations to the relevant instrument (from 10 ms to 10 s), without success. More surprising are my observations which, by operating this single VI, increasing WRITE it / READ delay results in the same timeout errors. I have found no mention of such behavior through research google and forum. I hope that this may point to a solution to the main issue,

  -switching between synchronous and asynchronous VISA WRITE / READ operations.

  -reorganization of the network GPIB to a star to a linear topology topology (three instruments have different GPIB addresses in case anyone is wondering).

  My thoughts:

  It seems to me that the error is related to a delay introduced between a VISA request and its read operation by the transmission of another query associated another instrument in the same network GPIB. But I have no idea why pass a query to another instrument would introduce such a delay, or why this delay would result in a timeout error (and only an instrument, while writing / reading in each pilot screws are basically the same). Hopefully a more experienced Labview-er will be able to shed some light on my problem.

  Included is the project that contains the default VI (main.vi) and the driver custom made use of.

  There are a number of ways. If you want to keep separate projects for instruments, you can use semaphores often slandered around calls for screws in each project. Locking is not expected or predictable, but it would give controlled access to the GPIB resource.

• Visa read stops execution

  Hi all

  I have a little problem with the control of my power supply E3631A Agilent via Labview:

  I downlaoded all drivers and with the help of you guys I even persuaded that it is running properly.

  At least that's what I thought.

  Turns out he didn't really. At some point the VI just stops.

  Using the execution mode of nail I knew where the problem was:

  The VISA read error query of the configure output has stopped working.

  I have no explanation for it. I get unpredictable and I have not yet managed to influence by changing the different settings.

  (And I tried it for a while now..)

  I built a very simple example VI to show you where the problem lies.

  Explanation:

  I'm basically feeding the output a voltage variable and at the same time measuring how long the vi fonctionnee already has...

  I thank you very much in advance,

  keksbold

  OK it looks like as the time to copy this section of the FAQ: (posted in a place not yet public ~ ~ ~ Hey Jordan? is still FAQ on the right way?)

  "

  In this topic, we will discuss some of the common problems that have been observed using devices with LabVIEW on Windows operating systems.  Many of these points apply also in other environments, but the examples will use the Windows 7 operating system.

  FAQ 1: USB device stops working unexpectedly.

  The first thing to look at is the OS power save options.  There is a global trend towards "Green" electronic development and energy the coast to stars become fairly common.  "If his is used not to turn it off" is not new.  Cave men learned how to Bank a fire in order to preserve the energy that would otherwise be wasted.  Similarly, the Windows operating system has an energy saving function to stop power to the USB hubs when no user activity is present.  In automated systems, this feature can cause problems since remove power USB hub will stop the USB device.   Solution: use Device Manager to change the Power Options USB hub.

  

  FAQ2: I put the power options and my device connection is still not reliable: Don't forget, the USB ports on the computer are often the least expensive that can be mounted on the chassis and system share the PC power supply USB-powered. Most of the uses of USB are temporary connections such as a USB key or a camera.  These connections don't require high reliability because there the user interacts with it.  Mounted sudden power and fault tolerance at worst cause the operator to retry the transfer of data.  Automated systems require a bit more robustness.  Solutions:

  1) ALWAYS use a free external powered hub. Perform your due diligence genius and to inspect devices specifications too - if you do not find them for this device which should clue pick you a product from a vendor who published their specifications.

  2) high noise environments require the use of ferrites on the USB cable- and do not buy the cheapest cable either! The good markets are poorly protected.

  3) PROTECT connections HUB-if you have a USB 2.0 device and Joe User plugs in a 1.0 device into an open slot, managed by the same hub-Bingo all ports on the rear hub can convert USB1.0.  WORSE, there are a lot of damaged or marginally engineered USB devices out there.  Joe User should cause power fluctuations when it is inserted or removed from the hub just don't let it happen!

  FAQ3: I test USB devices and the operating system can not find more.

  It is a Plug-and-Play feature that deserves exposure.  When you connect a device P - n - P BONE remembers his serial number in an entry in HKEY registry (hive-Key).  This is useful when (for example), you want a specific instrument, say a NOR-USB-6008, to appear as a device DAQmx with VISA Alias "MyDAQ1" whenever it is plugged.  On the other hand, if you want to test a range of USB-serial converters that can be problematic because the pilot of P-n-P will mount the first serial number like "COM3" and the other as "COM4" Add infinitum until the controller of the enumerator in the registry and the VISA recognized alias adjust upward.  Solution: use the Windows registry API and the API of hardware in LabVIEW to clear unused VISA alias and HKEY entered.   Speak with your professional COMPUTING staff structure HKEY and possible side effects before developing a plan to modify registry entries.

• VISA read timeout error - Keithley 2400

  I am using LabView 2010 to control a Keithley 2400 Sourcemeter on an RS-232 Interface. I want to set up a measure and take a reading (e.g. ground voltage / time)

  I took an example of "Keithley ReadOnly" library code, but the 1073807346 error to retrieve box "initialize". Then I looked in 'Initialize. VI"and found there is a VISA (timeout error?) reading error. I have attached two screenshots that shows errors. Can someone tell me how to solve the problem? Moreover, I am very new to labview, if someone could suggest a solution that is not too 'Advanced '? Thank you very much.

  
  

• VISA Read Timeout error when using stream protocol BUS

  Hello

  I currently use the BUS Flow for a MFC Protocol and I get a time-out error VISA Read:

  Error 1073807339 occurred at VISA read in Send Setpoint.VI-> test.vi

  Possible reasons:

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

  I extracted the part of the code and it attached to this message. Basically, whenever I hit OK to send a VISA just read set value times out. I tried to use the sub VI who is responsible to send the set value and it was fine (when manually, I copied and pasted the ASCII codes) but when I run the global function it times out.

  Any help is appreciated

  Thank you

  If you have a command string or a constant you enter a \r\n in, you MUST have '-' Codes view turned on in order to enter the actual control characters. If you enable "\" Codes to display and see \\r\\n, then you have used Normal display to enter the characters.

• Error with VISA Read (-1073807346)

  Hello

  I use VISA read/write to control a glucometer and read files in memory. When I run the file memory for the first time, I get the error 1073807346 and the explanation is "VISA: (Hex 0xBFFF000E) the given reference of session or the object is not valid."

  However, when I run again immediately after (without doing anything except click Run), it works perfectly every time until I have log and restarts (while I get the same error, but it works each time after this).

  I checked my settings, they are correct and I also tried to run the command with Hyperterminal and it works. I don't know why this does not work the first time around.

  Any help you could give would be great. I have attached the file ("read Mem").

  Thank you.

  Hello

  You choose the resource monitor correct (I assume you are) before starting the program?

  Why do you have a picture of sequence around your code? The sequencing is already accomplished by the data cables. The last wait is relaxed.

  And most important: why do you have a feedback node in your visa session just before writing.

  Delete and press cleaning diagram.

• VISA, read and write checks are block after there is no more lines to read

  Hi all

  I am developing a communication continuum between a microcontroller Arduino Uno and LabView. The issue I'm having is to 'Write' and even 'Stop' controls are block once all the initial reading lines are read in. I'm pretty sure that this is because the reading line prevents the complete completetion of the while loop, suspending all the loop until it indicates something else. I tried a number of Boolean operations and I can't work around the problem. The code itself needs a way to detect has nothing to read and ignore the read statement and continue a loop until the user activates the "write" command and writes something. The read command would have would be to read and wait again for user input.

  Any suggestions and help would be great! Thank you!

  * Note that I was using labview for all of 2 weeks. I'm getting used to it but I'm not a pro for sure.

  Also, I would like to give credit to physicslight @ https://physicslight.wordpress.com/2014/07/14/arduino-labview-serial-write-read/ for provide an arduino auto detect sub vi for easy then to initialize the VISA controls

  Seems I solved my problem. Using the Instr:Bytes function of the Port, the reading error is fixed. Addition of a few cases to see entry written and that it is received and a delay just incase seems to have fixed my code! If anyone has a similar question see my attached code

• VISA read timeout

  I don't know why the function of reading im getting an error of timeout to the VISA (error that says "timeout expired before the operation is over"). I made sure the serial port of Labview and my cameras are serial port configured exactly the same. I even tested hyperterminal with the same port as in labview settings and it works perfectly, but my labview program gives me an error. My device ends each order he sent with a carriage return, then I mounted VISA READ to stop playback of data when he meets the CR character. I also made sure the carriage return was infact sent by my camera. Any thoughts?

  

  

  
  

• VISA Read.vi time-out

  Hello

  Recently I happened to use Labview drivers of NewPort (ESP301) and Lakeshore (Lsci218) and I encountered the same problem of "time out" every time that a Subvi driver called VISA Read.vi for serial communication.

  I first thought has problems with driver Labview provided by the manufacturers, but after trying the pilot different LV from different companies, I started to think that the problem might be the Read.vi VISA itself.

  I use LV2010-spring, also tested with LV2011SP1. Both give the same timeout problem.

  I asked businesses about the problem, they have not found answers, nor they have LV2010 or LV2011.

  Someone had the same problem?

  Screw joint are FYI for what I tested.

  'test initialize.vi 218' is 218 Lakeshore pilot, with a change of the addition of "\r\n" in the "* IDN? the Subvi called VISA Read.vi. and a timeout error.

  "test initialize 218 - md2.vi ' has the same function, but call VISAWriteRead.vi instead of VISA Read.vi. and works OK.

  How can I know that the VISA Read.vi in LV2010 or LV2011 works correctly? or can I replace the VISA Read.vi with LV8.6 one?

  It seems to me that Newport and pilot LV lakeshore have been developed under version LV does not exceed 8.6. and I think that they tried their driver before release or I hope.

  any suggestion is appreciated.

  Xiaofeng

  The version of LabVIEW is not relevant.

  In the read/write, you add the LF/CR. In the other, you add CR/LF.

  Avoid platform dependent end consistent line in the communication of the instrument.

• USB-to-serial VISA read problems

  Hello

  I'm trying to control several mass flow controllers attached to a hub series Alicat BB9. The hub is then connected to the computer via RS-232 series. The computer on that what is done is not a serial port, so an adapter series / usb is used. When it is plugged in, the computer (XP) recognizes the series / usb and requires a driver. I installed a driver from the manufacturer of the adapter, downloaded from the internet. The same driver is used on another computer (Vista) without any problem.

  I am able to verify that the device is installed and operating correctly via the Device Manager. I am also able to see what the device COM port is turned on. Opening OR measurement and Automation Explorer (MAX), I am able to see the COM port listed under serial devices. I am able to validate the port settings and open a VISA session with the device. However, any time I try to read from the device, what happens to expired. I get the error xBFFF0015. I have for the parameter timeout at 5000 and 10,000 without change.

  When you run a VI that is used in the laboratory to control the same configuration, I can trace the error to a VISA read Subvi. The returned 'buffer' is not a value and will raise an error. I can plug the USB key into a laptop that has the same VI and it will run without problem. The Subvi "VISA read" return a value when running on the laptop.

  I'm under LabView 8.5 and 4.4 of VISA.

  If anyone has a suggestion that could get this to work I would appreciate it a lot. Also, I am a graduate. student who is working on this issue and my understanding of LabView is not terribly large, so dumbed-down responses would be nice

  Thank you for your help.

  Connor

  Thank you for the follow-up. However, I was able to solve the problem already... It was simply a driver update that solved my problem. The driver being used is "Prolific usb-to-serial" and version 1.. I upgraded 2.0.2.1 and it works fine now. I thought I had updated to the most recent before and apparently I had not... kind of delay. But thanks anyway!

• Leak memory in real time caused by VISA Read and timed loop of data nodes? Is not supposed.

  In collaboration with LV 8.2.1 in real time to develop applications that monitor or emulate computers on bus RS-422.   The following screenshots have been taken an application that monitors a transmission of 200 Hz.  After a few hours, the PXI station would break a range impressive messages angry... most involving something about memory loss.  After much hair pulling and passing money, my partner has discovered while looking at the available memory on the controller of loss of memory occurred at each loop containing a VISA read and propagation of error using the data nodes (see Leak.jpg of memory).  He concluded that if he went to the propagation of the error to the regular old shift registers, then the available memory was rock-solid.  (has the Leak.jpg of No memory)

  Any ideas of what could be the cause?  Do you see not any problem with the way that we code these kinds of loops?  We always strive to optimize the way in which we use the memory on our urgent requests and VISA readings and DAQmx bed give us the heartache more than ever, we are able to allocate memory for these screws some tips?

  Dan Marlow

  GDLS

  Hi thisisnotadream,

  This problem has been reported, and you seem to be exactly reproduce the conditions required to see this problem. This was reported to R & D (# 134314) for further investigations. There are several possible solutions, of which one is the one you have already found the wiring error directly in the loop. Other situations which give rise to no memory leak are:

  1 if the bytes of the property node port is not there and has read lies in each iteration and time-outs resulting are ignored.

  2. If the structure of the deal is gone and just blindly check the bytes to the port and read each iteration.

  3. If the timed loop is transformed into a while loop.

  Thanks for the comments!

  Kind regards

  Stephen S.

• Windows Vista Step By Step-reading error in downloading the files.

  Windows Vista Step By Step-reading error in download of files do I need to talk to or call? by following the instructions in the book - I get the error in the charge process down. I buoght the book with the CD to learn and I can not even begin to learn!

  Hello Enrico Cassin,.

  There is a section of the book which should be able to help with the CD that came with the book. If you look at the Table of contents, there is a section called using the CD of the book. See the section to see if they can help you.

  What kind of error do you get when you download the file?
  Did you choose to save the files on your computer, or you chose run?

  You can also contact MSPress for a replacement CD if the CD is damaged.
  Contact telephone Microsoft Press customer service: (800) MSPRESS or (800) 677-7377

  Please give more details as to what is happening and we will try to help.

  Sincerely.

  Marilyn
  Microsoft Answers Support Engineer
  Visit our Microsoft answers feedback Forum and let us know what you think

• Read error - SOLUTION system configuration data

  Today, I found a solution to the error of notorious boot not only on the toshiba, but some other brands also.

  The error is: System configuration data read error.
  He invites to start with 2 beeps which prevents the computer laptop Moldavian from.

  I tried everything I could to remve this message but noything helped me.
  Replace all, cmos battery, updated the bios, loader, drives, keyboard and etc.

  Today, I found a solution very simple that I want to share with you guys.
  This solution worked for me and I hope it will work for you too.

  Are you ready? :)

  Go to the Bios and change the Bios language french.

  Post here if it works for you also.

  Thanks for sharing your experience with us. But its really hard to believe that your solution would be linked to all devices such problem

  However, good to know that this small change in the BIOS has helped you to resolve the issue

• Satellite A300D-135 - BIOS - System Configuration data read error

  After starting a Satellite A300D-135 laptop computer, the following error message appears:

  
  3070M extended RAM passed
  512 KB of L2 Cache
  System BIOS with a shadow
  Video BIOS with a shadow
  ATAPI CD-ROM: TSSTcorp CDDVDW TS-L632H
  Fixed disk 0: TOSHIBA MK2546GSX
  Initialized the mouse
  ERROR
  System Configuration data read error

  Press to resume, installation

  After pressing F1 the machine starts Windows, very well, but the error message is quite irritating, while it comes with a loud BEEP

  I tried the following things so far (in that particular order):
  -Load BIOS default
  -Flashed the BIOS with the latest version of the BIOS (2.80) for this type of model
  -Reinstalled windows with HARD drive format

  All the these did not work.

  I saw the same message appearing on several places on the internet (on different laptops with a Phoenix BIOS in common), but so far I have not been able to find a working solution.

  It might me a hardware problem, but all devices (vga, soiund, lan, wifi, usb, hdd) seem to work perfectly under Windows, so this does not seem the question). Another solution that is mentioned in some forums, replace the battery. But because the phone keeps time correctly I don't think it's the case either.

  Any ideas?

  Kind regards
  GJ

  Hello

  The POST (power on self-test) BIOS checks and detects errors on the motherboard.
  I think it has something to do with the hardware on the motherboard problem.
  I doubt that you can solve this if update of the BIOS and the BIOS default settings didn't change that.

  What to say; I think that the technician of the ASP should run tests to check what's wrong or what cause this I think it is question of s mobo.

• Equium A300D - 13 X - Configration system data read error

  Hello

  I have a problem with my Equium A300D - 13 X laptop, everytime I turn on my laptop it starts and loads the initial startup screen as usual, Toshiba once asked that loud "BEEP" comes from my laptop, and lists the following information:

  Phoenix TrustredCore (tm) NB
  Copyright 1985-2006 Phoenix Technologies Ltd.
  All rights reserved

  Herring of the ITA (DDR2 + T/RS690M/SB600)
  CPU speed = 2000 MHz

  639K system spent RAM
  1918M extended RAM passed
  1024 KB of L2 Cache
  Occult system BIOS
  Video BIOS with a shadow
  ATAPI CD-ROM: MAST * ADVD-RAM UJ-850 S
  Fixed disk 0: WDC W2500BEVT-00SCSTO
  Fixed disk 1: Hitachi HTS542520K9SA00
  Initialized the mouse
  ERROR
  System Configuration data read error

  Press to resume, installation

  I replaced the hard drive and flashed the BIOS settings as advised by Toshiba Helpline but the problem persists.

  Help, please! because the "BEEP" is now getting on my nerves!

  See you soon

  Hi andrew_net82,

  It seems that the BIOS has detected an error with a certain part of material...

  Before doing something I recommend you load the default settings in the BIOS. If you are in the BIOS Setup, press the F9 key.

  If it doesn t work you need for professional assistance from an authorized service I think. Guys need to check which part of the material is defective and must be replaced.
  List of the ASP, you can find on the official website of Toshiba.