Similar Questions

• Problem to Keithley 6485 picoammeter to communicate with the PC. Receive code timeout error 1073807339 or BFFF0015 at initialization.

  More information:

  • It is connected to the PC via a RS232 - RS232 cable
  • I downloaded compliance IVI, IVI drivers and layer Keithly e/s
  • Measurement and Automation Explorer:
    • Parameters: baud rate 9600, data bits 8, zero parity, no flow. The baud and flow are certainly correct for the instrument, but I don't know what are the other parameters.
    • Panel test VISA: write * IDN? \n returns 6 characters without error. When I try to read, even only 1 byte, I get a time-out error.
    • The port is never exceeded the query and analysis stage when checking this. I tried termination characters \n, \t, \r and no (all that were available) and yet it returns a time-out error
  • LabVIEW (v 8.2): I use ke6485 drivers have been installated opening initialization of ke6485 vi and then others to read my measure. Ever it gets past the initialization phase and will return the error: 1073807339 "timeout expired before full operation".
  • Crescent thetimeout period is not correct the problem.

  Any help would be much appreciated!

  Check what type of cable you are using. It requires a null-modem cable, but if you use it, try a straight through cable. The manual should specify the type of cable.

• Visa timeout error-1073807339 reading

  Hi all

  I'm doing a command autoscale on a DSO-A4034A Agilent (Keysight) connected by ethernet.

  But for some reason, I get a time-out error. When cheking to find system errors.

  I have set up the session visa in 'MAX' and use the name of the session of the instrument of the call in the VI.

  I founded these screws on the Agilent instrument driver. and I can do all the other stuff I have to do without errors. EMPLOYMENT INSURANCE. the installation type measures Aqusition read data and so on without error.

  The error is caused by reading order just after the ": SYSTEM: ERR?" command under the request of error VI.

  I have updated the firmware of the scope and upgrated 15.0.1 VISA but so far without success.

  There is no problem when I turn the "climax of the performance"...

  Is there someone who can give me some advice about where to look this anomaly? Any help would be gratefully recived.

  / Best regards Rasmus

  Rasmus.Olesen wrote:

  There is no problem when I turn the "climax of the performance"...

  Crying just "timing issue."  Add a little wait between ordering autoscale and error checking.  It is likely that the oscilloscope does not resemble incoming orders when he assures the autoscale.  If you wait for it to do the job.

• Error 1074000000 has occurred in a place not identified and error 1073807339 occurred at VISA read

  I worked with it for a few weeks. I am a student doing research for a professor and I'm new to LabVIEW (about a month).

  We calculate impedance in an object with a pulsar. The pulsar will pass through an area of resistance before and after the charge for the calculation of v1 and v2. This will help us to find the current which will help us to find the impedance of the load. In this case, the charge will be a potato. The pulsar will send piulses so we want the program to record the waveform on the trigger.  We have v2 and v1 of two channels. We must record the results of v1 and v2, more than an hour. In addition, if v1, v2, and timestamp are in the same excel file then our lives would be easier. A waveform by file.

  -TL; DR Two channels to be recorded with a timestamp

  The oscilloscope is the WaveRunner LeCroy_64xi.

  We use LabVIEW 2014 SP1.

  I connect to an oscilloscope via an ethernet connection. The connection should not be the problem, but I connected the oscilloscope using NOR-MAX. The oscilloscope is an ACIP device with a remote system, passport and alias. The instructions step by step are http://forums.ni.com/ni/attachments/ni/140/43120/1/VICP-NI-MAX.doc.

  After you connect the oscilloscope, we took a sample program from the driver and changed that to do what we want. We got a few results. FetchWaveform strives to get the shape of wave, but after four or so waveforms, it gives two errors. We tried to add delays, loops and run the program once at a time. I'm willing to start one of these well. This worked well enough at some point, but I think it was because we had a few labVIEW programs open and he was capture the waveform at every second. I think it was because the LABVIEW program has been slowed by the natural delay. It was exactly what we were looking for, but mistakes don't happen often. After the computer restarts and the program, the waveforms are extremely fast registered and errors occur. It is not consistent and we do not know how to register only when the waveform is triggered. Trouble downloading my code here.

  Moving this, we tried ReadWaveform. For some reason, we cannot get readWaveform to work. It does not display the waveform and gives the second error or timeout error. We understand why he will not really connect with the oscilloscope. I do not change one of the examples that use readWaveform for this problem.

  I'll be here tomorrow, but I'm almost done for today. If there is anything I missed, I'm sorry and I'll it download tomorrow. I'm out of ideas. To message me please and thank you very much for your effort.

  Hi Tnorm007,

  I appreciate the level of detail you have included; It seems that there are a lot of things here.  However, it still seems to be inconsistencies and ambiguities in the errors that you receive.  You are able to get a consistent result by running the code you provided?

  For example, if you run the code once, it works as you want?

  If you press run is once again, it works the way you want?  (I assume that you configure the writing on a measure VI file to add the data to the current file?)

  Does it fail after a number of iterations, or it does not depend on the speed at which it runs, back to back?  Which two errors are thrown into this case?

  Also, just a general tip, if you want to receive signals continuously, you want only portions of reading/writing the code of the loop (and initialize/close the task only once), rather than put all the code in a large loop or by pressing the button several times run

  Best,

  David Randolph

  Engineering applications

  National Instruments

  www.NI.com/support

• Error time-out random - 1073807339 using pilots of series Oscilloscope Tektronix TDS 200 1000 2000

  I am trying to make measurements of waveform of an oscilloscope Tektronix 1052 B using LabVIEW. My program is intended to be run for hours at a time, and it works perfectly as expected for the first few hours. However, I noticed that after a few hours, there are apparently random of chances that a VISA to read or write the block function will produce the error - 1073807339. After that happens once, all read or write functions also produce this same error for a while. This happens even using subVIs new driver provided by OR (http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=047216EC20B66FABE0440003BA7CCD... Meanwhile if I stop the program, I can still bring up the oscilloscope in MAX and read and write commands him. The error seems to occur within a VI. I already read this page here: http://digital.ni.com/public.nsf/allkb/874B379E24C0A0D686256FCF007A6EA0?OpenDocument, but none of the solutions helped. I know that this is not a matter of actual timeout because I tried increasing the timeout of 30 seconds, but the error always occurs immediately as soon as the function of reading or writing block is called.

  I would like to know why this is happening and what can be done to remedy this. The Subvi in question is provided. This VI is called at various points in the program do acquire a waveform. The inititialize and narrow subVIs are called outside the Subvi.

  Then check your powersettings. Windows may unexpectedly turn off usb power

• Error reading the attached viSA-1073807339 using Subvi, but why?

  Hello

  First of all, thanks to all who respond!

  I read N9020A Agilent MXA Signal Analyzer data.  It is successful if a Subvi is used to playback VISA; otherwise "Read Error-1073807339 VISA' rears its ugly little head.»  The Agilent gives the message "REQUEST not COMPLETED" just as endearing.

  The on error-1073807339 OR Knowledge Base article talks about the need to put an end to the chain of command correctly and explains how to check it by double-clicking the control of chain of command on the front and changing the display of '-' Display Mode of the Codes.  I call the VISA Read VI in the block diagram; It does not have a chain of command of front panel control, so I don't know how to apply these tips.

  In any event using a Subvi to perform the Read VISA takes care of the problem, but I have no idea why.  The VI image that does not work is "Agilent MXA Sig Gen vi.png."  A big thank you to Mike on the Agilent forum which provided workaround.

  Nina

  Mark, Fan of the crows and any other interested person:

  I found the error in Agilent MXA GIS Gen.vi.  There is typo in one of the VISA WRITE commands.  Originally, it was

  : MMEMORYATA:? "D:\TEST. PNG"

  It should be

  : MMEMORYATA? "D:\TEST. PNG' (remove: before?)

  Your comments have been invaluable.  Thanks a lot for your help and your patience!

  Nina

• 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

  
  

• How to solve the communication error series of HP34970?

  I want to use the serial port to commnucation between pc and hb34970. Using gpib, it's ok. But in serial mode, report the error. just like that:

  for com2 layout:

  16:11:47.359 26-8-2009 [Init_dq_Device] error:-1073807339 - HP34970A Initialize.vi-> Init_DQ_Device.vi-> main_app.vi VISA read.visa name: ASRL2::INSTR

  for the implementation of com1:

  16:13:25.921 26-8-2009 [Init_dq_Device] error:-1073807339 - HP34970A Initialize.vi-> Init_DQ_Device.vi-> main_app.vi VISA read.visa name: ASRL1::INSTR

  I don't know the meaning of 1073807339 and if I should together: ASRL1::INSTR for com1. Can someone help me on this problem.

  Thank you very much.

  fix my Subvi.

  MMM,

  I think that you can check your cable again.  Cable series come two types, Straight (patch) or null.  This is because the serial devices can be DCE (Data Communications Equipment) and DTE (Data Terminal Equipment).  You have proven the cable is good using it with another piece of equipment, but you have not proven that it is the right TYPE of cable frompg 273 of the manual you need a null-modem cable is the DTE instrument

  Consult the manual of user 34790A.  You must also implement the 34790A wait RS232.  From the front panel, you will need to access the menu of the interface and select RS - 232 and configure the port settings. Did you do that?  Verify that the port settings match the yourPC com port settings

  Another problem with Set - very common up is to connect to the interface of trigger/alarm by mistake.  The serial port is the lower connector 9 pins on the back panel of the 34790As

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

• 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

• VISA Write / read error

  Hello

  From what I saw this was not posted before.

  It seems that the error of read/write VISA is quite common and after reading through a few posts and try as proposed solutions, I find that nothing works. I am trying to contact my motor controller. I have implemented the correct COM port and the interface parameters (such as baud rate, parity, etc.). In the terminal program, termites and the measurement and Automation Explorer I can access and send commands to the controller and it works (the read buffer returns an error but always returns the correct answer).

  The format of the command is EN1\r 1 where 1 is the header and address, EN1 allows the disc and \r is the carriage return. Send orders in this format works. BUT in the program I wrote that I get error infamous timeout as in the attached photo. I tried to remove playback VI but nothing works.

  Please any help would be appreciated.

  Kind regards

  Richard

  I'm quite sure your error (-1073807339, timeout) was published thousands of times before.  So if you haven't seen, you may not have tried.

  The constant string in your diagram, what is the display for this mode?  Is this normal mode or \codes?  A common error is to have it in the normal display and you send a backslash followed by an 'r', rather than send a carriage return character who presents himself as '\r' when the string constant is displayed using the backslash.

• What should I do when I can communicate with my instrument NI MAX through other programs, but not of LabVIEW?

  Hi all, this is a question that I had a few times before in one form or another.

  I use a Boxcar Integrator (245 SRS is the interface) for my experience. I connect to it via GPIB using my Agilent GPIB/USB interface. My program runs in LabVIEW, and I used it successfully in the (very recent) past.

  However, sometimes if I get LabVIEW or something, some weird stuff starts past trying to connect to it. For example, after the LV exit and go back to the top and any attempt to run my program, it throws the error:

  Error 1073807339 has occurred in the CITATION read in OR_Boxcar_ReadAnalogPort3.vi-> OR_Boxcar_SimpleTest.vi
  
  Possible reasons:
  VISA: (Hex 0xBFFF0015) timeout expired before the operation is complete.

  Which essentially means that he cannot connect for some reason or another (don't worry, I'm on the right GPIB address).

  So I go to equivalent NI MAX or Agilent (Keysight connection Expert), proceed to part communication from VISA to either and manually, connect with the machine. And it works! If clear my computer is communicating with the machine at this point, but not of LabVIEW.

  This could be the cause, and what I might try? Thank you!

  Oh shit, I forgot about it! I solved the problem, it was actually a 'me' problem is not a problem of LV. Even my solution would not be to help someone else who finds it. I was trying to read from my instrument, but it is in synchronous mode, so it generates an error if you try to read her when a data point has not been loaded in its buffer. I did something unusual, so it was not a point of data loaded into its buffer.

• result of the difference between the message of exception and results of VisaStatusCode

  Hello

  first time poster here. Everything has started to learn the ins and outs of instrument control.

  I have been using Visual Studio 2010 to create a c# program to set up and use an instrument of digital power meter
  (via USB connection), and I noticed that send a defective Query() (on purpose) to an instrument will result in a
  exception (as expected). Specifically "timeout expired before the operation is completed.  Code error-1073807339 (0xBFFF0015), ErrorTimeout of VISA"

  For communication with the instrument, I use the following library: NationalInstruments.VisaNS

  But when I use VisaStatusCode (LastStatus) in making the exception, to see if it gives the same error code.
  It only returns the 'success'

  The exception error message includes everything I need, but I was wondering why I get a different result.

  The LastStatus value isn't supposed to be used for that? Can anyone suggest what is happening here?

  
  

• Porting to ARM LM3S811, PWM and serial port issues

  Read my previous post: http://forums.ni.com/ni/board/message?board.id=420&thread.id=1996

  I have problems again, I
  corrupted data sent through port sΘrie 0 when you use the OR
  pilot series on the LM3S811. I also get code error-1073807339 when reading that
  data inside labview with VISA, sent my arm to my PC.

  I have
  think the timings may be wrong, but I put t know
  where to look for baud rate divisor for
  UART0. S 3, 811 is Xtal 6 Mhz, 8 Mhz not like the 3S 8962.

  I have
  also tested the PWM on the frequency and scope dosen t match if I ask
  for 1 kHz, I'm moving 666 Hz. Seems like affecting the Xtal 6 Mhz in
  uVision is not enough.

  THX

  Lukasz

  OK, here's the solution.

  Open 'startup.s '.

  Goto line 193:

  ; set the system clock to run at 50 MHz
  ; SysCtlClockSet(SYSCTL_SYSDIV_4 |) SYSCTL_USE_PLL |
  ;                SYSCTL_XTAL_8MHZ | SYSCTL_OSC_MAIN);

  LDR R0 = 0X01C002C0
  BL SysCtlClockSet

  B __main

  Replace R0, with the right values in "sysctl.h" line 236:

  in my case the value of the 6 Mhz Crystal which is "0x000002C0".

  Calendar of PWM is restored and serial port works fine now.

• rs232 USB problem

  Hello world

  I've been in vain looking for a solution to a problem that I seem to have with standard equipment communication using a converter USB to rs232.

  I'm using Labview 2013 on a windows 7 computer and using a converter using the FTDI chip.  My computer recognizese converter and NOR-MAX recognizes as ASRL7::INSTR that I named "pc830."  I've attached a screenshot of my VI.

  I am tempted to write a command in a pc830 (p) 169 170 order of read/write ASCII) asking a piston position data. The problem I encounter is that, while I can send a command, I'm not receiving all data during the reading of my program and my connection time part (error-1073807339 occurred to read in PC830PosVelExtractor.vi VISA, VISA: (Hex 0xBFFF0015) timeout expired before the operation ended.).

  The first and obvious questions are if the serial port settings I use are correct.  I'm essentially rewriting of a previous Labview program that allow to control this piston even.  I took (and verified) that these are the correct values (baud rate, stop bit, etc.).  In addition, this old program sending the \02255\sR\s10034:96\r message takes up a replica of the equipment of series with the position data (for example \02V26057:148\r).  I checked that the hexagonal version of the message sent by my new program is the same as the old.

  Now, to check that the USB cable works in fact, I did a loopback test by opening a window to test VISA.  In this regard, bypassing the cable in a rs232 configuration, I'm able to successfully send and receive this same order of \02255\sR\s10034:96\r.  I got a timeout issue before, however, I activated the terminal character, and he went.  The message is sent and received without problem.

  Back to my program, I activated the same way the terminal character (\r) from the serial port hoping to get rid of the question.  When it is connected to my standard equipment, I always get the question of timeout during playback.  However, if I short the cable once again in a rs232 loopback configuration, I can send and receive my \02255\sR\s10034:96\r message without problem.

  I actually connected the old and the new program the cable just to see that I could talk with other devices.  It works very well, and I may as well read and write in both directions of each programs.

  My last attempt to diagnose/difficulty of the question was to add a "hunt read buffer" just before you perform the write operation.  It didn't matter, because as far as I know.

  I would like to hear from someone with suggestions that I am just about ideas at this stage.  We have no space to add a serial port of the computer, and converters with FTDI chips reviews seem to be good.  How can I get this thing to talk!