Writing of VISA problems

Similar Questions

• Writing series visa delays

  Hello

  I use the LabVIEW Vi series to send commands to a DUT. I use the a Sparkfun USB to Serial converter cable for the interface, by connecting directly to the TX and RX pins of my DUT (an MCU). I am able to send and receive data without any problem or data corruption, it is really slow.

  There are up to a 5 second delay between writing the message get written in series VI write and actually see me this post to the MCU. I have a scope attached to the TX/RX signals to see when this happens. Fortunately I do only 2 entries of 4 bytes, so there is only an additional 10 seconds of delay, but with it, wrapped in a teststand sequence, delays will be added through hundreds of iterations.

  Anyone seen this before? Any ideas what I might be able to try?

  Thank you.
  Mark

  Well, the post was premature. A co-worker pointed out my mistake.

  I use 2 queues, one for reading, one for writing on the port series. The problem is that I use the VISA Read.vi timeout for reading queue loop and the Dequeue Element.vi for writing loop. By chance, I had configured the read timeout set to 10 s. Given that the serial port is the same VISA session, these are not truly independent of queue loops. the function Read series was blocking the write function of occurring for at least 10 seconds. Once playback Vi has expired, the writing was able to sneak in and get the message written.to the port.

  -Mark

• VISA PROBLEM

  Hello

  I am writing a vi to acquire data of a multimeter Thurlby Thandar 1906. When I use Hyperterminal, I can use the commands 'LAD' (be ready to talk) and READ? (Read buffer). I can acquire the value measured in the unit.

  When I run the following vi I find that he regularly reads 0.000 which is incorrect.

  Everyone can see what I'm doing wrong?

  Nevica

  Hello

  I discovered what the problem is.

  The instrument has been waiting for a "line break" instead of a "carriage return" as the manual of the instrument said.

  The vi works now!

  Nevica

• Graphics refresh rate and the writing of text problem - error 5

  Hi guys,.

  I'm new to labview and have encountered some problems when I try to write to the file.  I use USB-6259 with Labview 2009 to acquire a number of channels I want to analyze later in MATLAB, all at the same time providing some limited analysis in real time.  The experience is to use lasers to calculate the position of a rotating cylinder.  I wrote a quick vi using the DAQ assistant to acquire channels and provide a polar diagrams showing the counterclockwise movement as it turns what is ideal.  The problem is that, because the cylinder rotates at up to 6 Hz, graphical needs updated very quickly I realized by using a buffer size lower compared to the sampling freq (sampling freq between 5 k and 10 k, buffer around 200).  This does not seem the best solution.  Also, when I try to write in the text, the following error is displayed after a few seconds:

  Error 5 has occurred writing to measure file-> Displacement_Rig.vi, or the possible reasons:

  LabVIEW: File already open.
  =========================
  NOR-488: Command requires GPIB controller system controller.

  Can someone point me in the right direction?  I tried to create a loop of producer/consumer, but I'm not convinced that it works with my limited expertise.  I attatched my vi, although I warn you, I'm new to labview...

  See you soon

  Hello Ipaza,

  I watched your VI and found that there are has some problems in the architecture of your consumer producer loops.

  You can get a pre built loop producer consumer using the templates on the start screen.

  I copied the majority of your code in such a model. Could you test this and let me know if this solves some of the question.

  With regrads,.

• Pilot NI VISA - problems of driver installation wizard

  Hello

  I generated a pilot with communication as to the NI VISA driver with a USB - HID Device Wizard. Driver and LabVIEW Application work fine - on the development system (Windows 7 x 64).

  Now, I want to move the application compiled to another PC, using the same operating system (Windows 7 x 64). I tried to install the generated driver by clicking on the inf file and choose install. After that, I will ask if I want to install the driver, which I agree. The installation process runs, but in the end, the device is not visible in the Device Manager.

  So I went in the development system and uninstalling the driver real. Now, I did the same steps as above (right-click inf-> install->...). Same problem, the device is not visible in the Device Manager.

  Now, I went back to the pilot NI VISA Wizard. With it, I am able to install the driver.

  How could install an inf generated on a system without a VISA NEITHER pilot Assistant?

  Thank you very much.

  Best regards

  Michael

  Hi Michael,

  OK, I thought he should there have generated one or more other files which can be transferred to another machine and that should be installed with the inf file.

  I did some research and discovered things about the problem. Please go through the links below and see is they solve your problem:

  Why can't NI-VISA to control my USB device? -National Instruments
  http://digital.NI.com/public.nsf/WebSearch/273BB58D3B52CE6886256F3B00714D03?OpenDocument

  Control tutorial USB Instrument - National Instruments
  http://www.NI.com/white-paper/4478/en/

  Why Windows won't install the VISA driver for my USB device? -National Instruments
  http://digital.NI.com/public.nsf/allkb/3C335141B64C038886257141000036F2?OpenDocument

  Kind regards

  Melanie

• VISA problem on a PC but not another

  Hello

  I've been successfully running a vi on a 32-bit XP computer to connect to an instrument via RS232. I have put the same vi on an old computer XP 32-bit, but getting a VISA error.

  I can control the instrument of the same old computer using the same port, but running an application tailored to the instrument, then the hardware and port works fine.

  I used a serial port monitor to watch what is happening. When I run the vi nothing appears in the port.

  Can someone give me some clue to begin looking?

  Thank you very much

  Have you installed VISA and what errornumber occurred

• driver usb visa problem

  I have a usb controller, I want to connect with labview... I did successfully usb raw driver using driver development Assistant... and it works well in my pc in which NEITHER labview is installed... now I want to run a labview application in a pc in which no labview (nothing not related to NOR) is installed... then I copied the visa to this pc... usb driver after plugging the device and install the driver it says unable to install driver completely... I tried with 2 PC... so I wondered outside the visa usb driver... y at - it something to install on a pc that does not have labview so it can communicate with the pc?

  I don't know the length of LabVIEW. I want to talk about the VISA duration.

• Writing LabVIEW visa question

  environment:

  -windows xp professional sp2

  -Labview 8.5

  Description:

  I have an instrument with rs232 interface, when I use the UartAssist tool to send the command, the instrument could receive successfully.

  but, when I start my labview application to use visa control and send the order exactly the same, there is no response.

  I trace the error in my control, there is no error after the send (successful submission) command, but the instrument has no answer.

  I do not know baud rate and other configuration is good, why the device cannot answer?

  BTW, I try to use HyperTerminal to send the same command, the instrument can answer too...

  AJMAL says:

  BTW, I try to use HyperTerminal to send the same command, the instrument can answer too...

  If you mean it is in the hyper terminal to work?

  I would say it is probably a Yes.

  The most likely cause here is a matter of simple termination. Most of the series commands must end by one or more characters. It varies depending on the instrument to the instrument, but it is usually a carriage return. You will need to check the programming of your instrument manual to determine what is this character and add this character of the chain of command. Individual character constants are available in the palette of the chain, the bottom row.

• Writing of the problems using Firmware Optiarc DVD RW AD - 7540 has 1.422006100200 and XP Home Edition SP3

  When you write on a DVD r using Nero software, the process is allowed up to 10%, and nothing is written afterthat. It seems that travel by car at top speed when reached this point and then writes the data on the DVD is corrupt all writing process.

  Thanks for the help.

  Swap for work known to test the disk. If all goes well, throw the original drive. They do not last forever. MS - MVP - Elephant Boy computers - don't panic!

• VISA problem read: after a while the device stops responding

  Hello world

  I am faced with a really strange bug than anything I've done him could not solve. I have a camera that I made myself communicating with LabVIEW by a RS232-> USB converter. Everything seems to be ok, but all of a sudden (it can last 30, 45 or 50 seconds), judgments of LabVIEW and data reception, as well as other buttons are no more, not even the stop button. I have to remove the usb converter to get the buttons answer once again, and then I got the error:

  

  Other programs that opens this same terminal can communicate with my camera for hours without errors. I have of course the session open and close only after the while loop. Can someone help me?

  How fast your VI reads the com port?... could he try to read too fast?... Add a waiting in your VI and see if that helps.

  Just a thought...

  Josh

• Problem writing DVD SD 6112

  OK, my DVD burner in my notebook SA30-404
  seems to be only able to write some
  really not expensive DVD-media brands.

  Where can I find which DVD, it will burn at?
  I've already bought two piles of 25 discs
  for nothing, because they do not work...

  Supported dvd-brands and media or types
  aren't anywhere to be found in the documentation.
  "use only dvd media supported by toshiba."
  YES THEN? WHERE ARE THEY?
  Really stupid if you ask me.
  Cost us a lot of energy and time and money wasted.

  Hi jult

  Media supported by Toshiba are probably tested media and they should be available in writing without any problem. Check this http://www.tdk-europe.com/index.php?id=34&sa_from=56&WYSESSID=pecthjsutge5g7 hup5t99epib1.
  I can really recommend to use.

  You are not required to use the media. I use just the TDK media for a long time and I am very satisfied. Have two cell phones and two of them have no problem to burn DVDs at all.

  Good bye

• Visa OR written closing serial port

  Hi all

  Currently in collaboration with LV2011 and NOR visa 2014.  In my application, I have 7 open including 4 serial ports I write for devices, 3 are simply listening.  Now, I write to 4 of these devices, alternating between them, the second time I try to write to a device, the writing is not received, but when I exit the application and close the port, the message is received. I saw this on 2 similar devices and it is a bit random. Possible, it is a matter of the unit, but I don't see this problem when you use the tera term.  We never seen it before?

  I can post code, but it is a great application and I use the AMC add on.

  Thank you

  Matt

  Using native serial or USB-to-serial adapters ports?  USB adapters often behave in certain circumstances wrong with LabVIEW.

  If he can be a bit of work around the problem, is it possible you can close the reference in LabVIEW just after writing of visa for 'forcing' the message, and then open again the serial port reference?

• Serial communication error VISA with LUDL stage controller

  Hello

  I'm trying to control a micro-positionnement made by Ludl stage. The model is Ludl MAC2000. It seems that the RS232 comunnication is implemented because I can talk to the controller using HyperTerminal. However, when I want to do the same thing through Labview, I can't answer the controller at all. The vi is roughly the same as the visa basic read/write in the example. Looks like a very similar problem in this post:

  http://forums.NI.com/T5/instrument-control-GPIB-serial/visa-serial-communication-problem/m-p/567065#...

  But the trick of nature of endpoint does not help in my case: I tried to toggle the termination character setting in the property node and different combinations of '\r', '\n' as termination characters, but nothing has worked so far.

  Seems to me there is some difference between the interpretations of the same order to Hyper Terminal in Labview. But I just can't understand what it could be.

  Anyone with a similar experience could give me some comments/suggestions? Thank you very much!

  Another difference between hyperterminal and labview is the speed of sending characters.

  LabVIEW breaks out the whole string to the controller

  HyperTerminal is this character by character. So much slower and slow the controller can be affected by this.

  You could add a loop around the writing of visa (to make it easy convert the string into a byte array outside of the loop and convert it to a string inside and you have a shipment char by char in LabVIEW

• Synchronization with Serial read/write problems. can not get the functionality of the terminal emulator

  Hello

  I am writing a VI to control PWM with a microcontroller via a serial port. I wrote a simple code for the microcontroller that allows me to set the ratio of duty cycle on a scale of 0-65535. It works very well with Termite of Compuphase (RS-232 plug); The microcontroller invited me to an entry, expected that I would one, updates and expected another entry when I decided to send him. Now, I'm trying to get the same functionality on a LabVIEW vi but hit a snag.

  When I tried to send my orders with a series read base and an example of writing, everything worked fine. I could see the prompt entry, write an entry and if I was quick enough, check out the update message. Even when I was not fast enough, I was able to check the update by monitoring the PWM pin with a Logic Analyzer. The problem with the basic example, however, is that I need to update the report to aura cyclical ratio, so I went for an example of reading continues writing. The problem I've met; is that I have to switch between reading and writing to make it work. When I do that, either I don't hold write it down long enough and nothing happens, or I get several updates when I switch to reading. Some of these updates don't even match and produce updates to defective upgrades for example; 16000 16000, 16000, 16000, 6000, 600, 60, 16000, 1600, 60, 0, 0, 0, 16000, 60, 0, 0 etc.

  I tried which allows characters of endpoint in the hope that the writing would end at the end and go to reading where he would receive a termination character and wait for me allow writing once again, but nothing helped. I still have to alternate between the two and either get no response on reading several updates of variable accuracy. I tried to remove her allows read/write and their structures of matter in the hope that the loop flow, associated with the characters of endpoint would the case, but then the updates don't register at all. The funny thing is I did a VI like this before with an Arduino and that there not even no need to switch between writing and reading (I'm now using a Board of Freescale FRDM).

  I was also the frequency of timeout errors; Error-1073807339 at VISA Read, reason Possible: VISA Hex 0xBFFF0015. I removed the option to stop the while loop if there is an error so I can run but always pops up an error on the judgment occasionally. Could the problem of synchronization always cause me problems?

  Would appreciate all advice really, I am providing my slightly modified example screws and can provide the code for microcontroller on request, even if it's very simple.

  Thanks in advance, it is
  Yusif Nurizade

  In other words, frankly, a good bad example you according to your code. Also, you have the order of writing and read upside down in your amendment if the instrument requires a command to return something. It should really be using a structure of the event. The structure of the event around a write and read and use a value change event. I have attached a quick change. This mod is still a reading after writing. If necessary, you may have two separate events to write and read.

• VISA with Keithley 236 questions

  I use the Keithley 236 in LabVIEW 8.5 and am having some VISA problems.  I can't find a write buffer command that works with the 236.  No one knows everything?  If you need more ask for details, but I can't provide you with the vi because his ITAR restricted.

  What is 'it' that returns IDDC? This isn't a VISA error code.

  What I suggest is that you forget to LabVIEW for now and concentrate on debugging of a GPIB communication base. In MAX, peripheral slot, and Interfaces your GPIB card must be listed and under who should be listed the instrument if you have followed the installation instructions. If the instrument is not listed, click with the right button on the controller and select 'Search tools'. When and if the isntrument is listed, you can right click and select "Communicate with instrument. You have the option to do a writing, reading or a query. This is where you should start to debug commands.