Similar Questions

• Possible timeout in VISA read/write in While loop

  As the title says, I have a while loop that is constantly written followed by reading using VISA read/write.  I'm waiting for buffer correspond to a certain one, which the true value would end the loop.  In this loop, I have an indicator showing how many times he runs. All of this is repeated in another while loop.

  My problem comes the counter arrives at 10, then stops at the "write" command.  Do not know why.  I tried to increase the time-out of the instruments, but nothing has changed.  I added a delay of 10ms in loop, which also has not changed anything.

  For reference, I use a tektronix scope series 3000 of the MDGS and checking its state of relaxation.

  You said chill to read earlier!

  But it is not supposed to have to write it either.  Experimentally, access all VISA nodes, right-click and choose the Mode of synchronous i/o.  Make it synchronous instead of asynchronous.  The watch symbol will disappear from the top right corner.  See if that changes anything.

  What kind of serial port are you using?  What is an integrated in the PC?  A USB to serial port adapter?  Makes the chips on that, Prolific and FTDI?  You can try with a different serial port or a brand of adapter?  A lot of people have had problems with prolific chips.  And I have also heard of people having problems using adapters who had fake chips in them.

• Watlow F4D Serial Communication problem error Code-1073807339 VISA Read in Watlow F4.lvlib:Utility MODBUS RTU receive message

  Hello

  I am trying to contact a Watlow F4D controller on a room using RS232. I use a cable converter USB-series and NI Watlow F4D Serial Driver.

  The code of error-1073807339 occurs in:

  Read in F4.lvlib:Utility MODBUS RTU Watlow VISA receive message-> Watlow F4.lvlib:Utility Register.vi reading

  I don't know what caused the problem. I am able to see the cable converter USB-Serial OR max. Please see the pictures for more details

  Thank you

  Felix

  
  

• Get the error message "Invalid stem Pipe" during the execution of the restore

  Original title: invalid stem tube

  Am not able to restore to another point, because it tells me that the stem of the pipe is not valid

  Hello

  
  1. What is the brand and model of the computer?
  2 are you getting this error message when running system restore or factory restore?
  
  Reply with answers to help you in a better way.
  
   
  Hope this information helps.

• Windows 7 hard drive stolen when idle and during programs execution system

  I can hear my hard drive C beating away when my system is idle, and even though my system is running programs.

  Think it might be Firefox that uses the hard drive much - checked, uses the hd a little, but not more than usual, but I can still hear the hard drive clicking suite. So I close Firefox. Still ongoing.

  Tried to switch browsers Chrome, and even has a lot more use of the disk by cycle Firefox did. But no matter whether Chrome is open or not, I can still hear the beating of hard drive.

  Tried to use IE as my main browser, still no luck.

  I checked on the Windows Task Manager, but no 1 process shows a lot of the use of the disc. I tried then to resource monitor and 'System' appears at the top of the list of processes sorted by use of the disk. But there are a lot of sub-thingos (forgive my ignorance of jargon) ongoing enforcement under 'System', while originally the beating of disc?

  I disabled the process that has been suggested on the forums, without any change in the use of Windows Media network share drive.

  Then I saw a thread in which someone talked about disabling Marvell / RAID drivers remains other manufacturers (where the system has no installed RAID array) slow down its use of the disk.

  I have no RAID array on my PC either and noticed a Marvell driver under the heading 'System' using SysInternals Process Explorer.

  I also noticed that some other drivers stray, maybe one of them is originally the use of disk problem?

  It is terribly random - will start and continue for 30 to 40 minutes and then stop for hours, then start again.

  I don't think it's a virus, as I have Avast! and can use the shield of file to control what files Avast! analysis - strangely, although I hear the hard drive in use, Avast! does not pick up/scan all files that the disc is supposed to be using.

  Here are the various screenshots that I downloaded in the hope that someone can help me solve this problem of disk hard until it wears out and dies a lonely premature death: P - thanks

  http://CID-b92b880a2eb0b50a.Office.live.com/self.aspx/computer%20Error%20Screenies/hard%20Drive%20Usage/stray%20Marvell%20Driver.PNG

  http://CID-b92b880a2eb0b50a.Office.live.com/self.aspx/computer%20Error%20Screenies/hard%20Drive%20Usage/stray%20AMD%20Storage%20Filter%20Driver.PNG

  http://CID-b92b880a2eb0b50a.Office.live.com/self.aspx/computer%20Error%20Screenies/hard%20Drive%20Usage/dump%20Disk%20Processes%201%203rd%20Oct.PNG

  I downloaded SysInternals Process Monitor of

  http://TechNet.Microsoft.com/en-us/Sysinternals/bb896645.aspx

  But the program is much more complex than Process Explorer and I have no idea how to use it.

  Can someone tell me please how to run a trace through the events that may help determine which of the processes analyzed in running process monitor is / are the ones that are causing high disk usage?

  An analysis more

  Restarted in safe mode (without network) and entered the resource (part of Windows 7) monitor and SysInternals Process Explorer (in Microsoft TechNet) to see if I could pinpoint the problem.

  All the time, I was in safe mode, the hard drive kept in fly! : O

  I started first of all resource monitor and saw that the 'system' with the PID of 4 remained the more intensive process of disk. Using the disc went from 100 KB/s to 1 MB/s as before when you are connected to Windows 7 normally.

  I also saw

  svschost (netsvcs),

  Svchost (secsvcs)

  Svchost (dcomlaunch)

  and like other processes

  wmiadap.exe

  wmiprvsv.exe appear. 2 wmi processes disappeared after a short while leaving svchost and remaining 'System '.

  I closed the resource monitor shot to the top of Process Explorer and found some weird-looking process:

  Under wmiprvsv.exe, there was a file called locale.nls, with no manufacturer name/description (unlike some other services/sys files having a "Microsoft Corporation" as their name)

  Under each of the svchost.exe process, out of all the files that have name descriptors (Microsoft Corporation), there was a little without name descriptors that caught my attention:

  A file that found in Windows/Globalization/Sorting/Sortdefault.nls

  A file called locale.nls (sorry don't remember the location of the file)

  A file that found in Windows/Registration/R00000000000.clb

  A file that found in Windows/System32/C_28591.nls

  All the files above with the exception of the R000000.clb one found in svchost, lsass and csrss.

  The R00000.clb file was found only in svchost.

  I noticed these files because they had no name description next to them - could all of the files I mentioned contribute to the problem of the use of disc?

  Hard drive stolen continues even after I Logout

  I have my own PC and use an administrator account (not the default "Administrator" account, but my own account with administrator privileges).

  I tried logging my regular account and another account limited, I have on the PC. Not only the disk thrashing hardcontinue while I was connected and on the screen of welcome,but he continued even after I had connected to the limited account.

  Weird Hey?

  UPDATED OCTOBER 12, 2010

  Tried to run performance monitor reports using perfmon /report in start search/run menu. Have not circumvented to André Xperf suggestion again, too complicated for me to understand, waiting for his response.

  Meanwhile, here's a screenshot of the 1 report and the complete HTML file of another taken report a few minutes later (did not know that I could save the report in HTML format at the first time, I did the screenie)

  http://CID-b92b880a2eb0b50a.Office.live.com/self.aspx/computer%20Error%20Screenies/hard%20Drive%20Usage/12th%20October%202010.html

  http://CID-b92b880a2eb0b50a.Office.live.com/self.aspx/computer%20Error%20Screenies/hard%20Drive%20Usage/Perfmon%20Report%2012th%20October%202010.PNG

  Nope,

  It was actually the power supply fan making a rattling noise that resembled the disk hard grinding/fly. This problem is solved. Thanks to all, especially to André, for your help.

• 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 (error BFF0015)

  Hi all

  I use COM VISA library and c# communication with my instrument via TCP/IP.

  I add the reference "VISA COM 3.0 Type Library ' to my c# project and try to establish communication using the following codes:

  *********************************

  Ivi.Visa.Interop.ResourceManager ResMsg = new Ivi.Visa.Interop.ResourceManager ();
  Ivi.Visa.Interop.FormattedIO488Class ioClass = new Ivi.Visa.Interop.FormattedIO488Class ();

  Imsg = Ivi.Visa.Interop.IMessage (ResMsg.Open ("TCPIP0::192.168.0.170::10001:OCKET", Ivi.Visa.Interop.AccessMode.NO_LOCK, 8000, "") as IMessage);
  ioClass.IO = Imsg;

  ioClass.WriteString ("* RST", true);

  ioClass.WriteString ("* IDN?", true);

  String ret = ioClass.ReadString ();

  Console.WriteLine ("ID:" + ret);

  **********************************

  I could write "* RST ' command to the device without errors. And I could see that the device really do a reset of the command.

  But when I send "* IDN?" and read the answer, I still get a TIME_OUT error. Even if I add "\r\n" at the end of the command and increase the value of the time-out period, can I still the same error. Not only "* IDN?" but also another order of reading as "* STB? ', they all can the same timeout error.

  But when I use the VISA-ReadSTB function, it returns the correct data.

  I also tried to use Labview VISA-open, entry VISA, VISA-read for the same test. I also have an error (BFF0015) after VISA-read.

  I also use a programm IO monitor to view the data. I find that I have seen the answer, but I still have a time-out error. Currently, I could only read the answer by Agilent IO control successfully.

  I'm using c# 2008, Labview 8.2.1, VISA 5.0.3

  Any notice will be really appreciated!

  Kind regards

  Please take a look at this KB. Maybe this can help you solve your problem.

  Why should I receive Timeout error-1073807339 on VISA Read or Write?

  http://digital.NI.com/public.nsf/allkb/874B379E24C0A0D686256FCF007A6EA0?OpenDocument

  See you soon

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

• 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 timeout on write and read VISA

  I'm having problems of error timeout with a VI who just writes and reads the necessary data and will be eventually added as a Subvi. Everything is set up the same as my camera. I tried to increase the timeout for the session, but it does not work and I don't know what else to try.

  Any help would be appreciated!

  The \r is the termination character (carriage return) and YOU set the constant/control channel for------display Codes. It is a right click option.

  The driver is located by help > find the instrument Drivers. The driver page main has links on what makes a driver is and how to use a.

  http://www.NI.com/downloads/instrument-drivers/

• How to run vi continuous when the VISA read timeout happens

  Hello

  I'm using LabView 2010 through a series of Agilent 6000 Oscilloscope. The Oscilloscope reads data from another experimental machine which will occasionally fail due to failure of the sample. When the machine breaks down, it ceases to send signals to the oscilloscope and leads to the error timeout of read VISA and the vi It is over.  Is it possible that I can run the vi permanently when the error occurs? For example, when the error occurs, it stores the error in the thread of the error. When the vi read the error code of the wire, it sends a command to stop my experimental machine then stop the vi.

  So far, it stops simply during the execution of the visa, playback function. In that case, why do we mistake in and out? Vi stop just when the error occurs.

  Thank you

  Laurent

  
  

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

  

  

  
  

• in VISA READ timeout

  Hello everyone,

  I am in training course of end of study and my mission to carry out an automatic test bench.

  Not being an expert in Labview and ASCII language and that no one in the company is now capable of answering my question, I turn to you because you're the only who can help me please.

  United Nations instrument of I Doi to communicate en RS232C with SEFELEC DMG50 + not the DATASCHEET (page 85) is attached via Labview program that I found in the examples of the United Nations and works not bad (as an attachment also), EXCEPT THAT at the time or I send a request with a response to return like e.g. IDN (* IDN?) Application solutions), the referral program an error timeout-1073807339.

  As I understand it he tells me that he doesn't have enough time pour answer. But he wrote the answer in almost all still...

  The question I ask myself.

  1 - Why he answers while it displays a Timeout

  2. is this a problem of parameters (for me everything should be fine)

  3 - Can you tell me if I have chosen my flow control and the character XON and XOFF parameters

  I will be very grateful if someone can help me solve this problem because I galley not bad on this thing

  Thank you

  solved

  Thank you very much, because both of you (Albert.geven & SAMUEL_NIF) has been essential to clear the timeout error. For this I have

  1. I separated VI Write and Read VI and made a VI wait... because VI Read needs time to respond as you said

  2 - I also used a property of node (VISA bytes to the Serial Port)... because it gives a necessary shot for reading

  the new program is attached to understand more

  Thank you

  Auto

• Interactive Control VISA & VISA Read timeout expired

  VISA control gurus,

  I am trying to contact my wireless AGILENT N8300A Test set.

  I am able to do the same thing via NI VISA Interactive Control...

  (Attached is the captain)

  But if I tried to do the same thing with a sample program.

  (Also attached below)... program shows a

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

  I tried to use Async mode and synchronization in the VI... Reading VISA.

  But it always shows error timeout.

  I'm not able to understand what could be the difference, if it works well

  in an interactive control NI VISA, but not in my program

  Any help or pointers would be appreciated...

  Kind regards

  Diakité

  Hello

  very good that you have added the vi.

  You add a CR instead of a line break.

  You can do that in the string by selecting "------" mode for the string constant, you can use any string appearing in your comment as the display string constant.

  Good luck

• Error when executing VISA Serial Port reader

  Hi all

  I work with some lithium-ion batteries that gives every second through a RS-232 codes. With these codes you can get the battery voltage and other things.

  To read these values and store them in excellent I created a labview program using the player of VISA. I tried to run the program several times and it worked well at the start.

  After that, I also called in a function of data acquisition to read other values from a module NI 9206. When this change was made to the program the problem arose. I am able to get values and run the program for a while. But in a few minutes, the program gives an error saying "Error - 1073807252 occurred at VISA read in reader.vi series" (I have attached a screenshot for this).

  If anyone knows why this problem occurs? Any suggestions would be helpful. I'm new to read VISA and do not know why this error occurs.

  I have attached to VI.

  1. with the data acquisition function
  2. without the data acquisition function

  Thank you
  Piraux

  As the message says you do not read the serial data fast enough. As you say, the device sends data every second. If you do not read these data at least this fast, possibly the series buffer will be overflow because of no bytes will be replaced. Your acquisition loop is guaranteed to be more than a second. The DAQ Assistant takes a second to get the data because it is the time that you specified. Reduce the number of samples or place the DAQ Assistant, in a separate loop.

  p.s. Please clean up the code a bit. Get rid of all these statements of cases who do nothing and do not use local variables - particularly the response string series.