Subscribe: Instrument Control (GPIB, Serial, VISA, IVI)
Added By: Feedage Forager Feedage Grade B rated
Language: English
command  commands  device  devices  error  gpib  instrument  labview  new  pulse wave  read  test  usb  version  visa  write 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (2)

Feed Details and Statistics Feed Statistics
Preview: Instrument Control (GPIB, Serial, VISA, IVI)

Instrument Control (GPIB, Serial, VISA, IVI) topics

Instrument Control (GPIB, Serial, VISA, IVI) topics

Published: Wed, 24 Jan 2018 02:34:22 GMT2018-01-24T02:34:22Z


agilent 33220A pulse wave problem (labview beginner)

Tue, 23 Jan 2018 13:16:45 GMT2018-01-23T13:16:45Z

I want to construct a pulse wave using 33220A as follows conditions.



sweep pulse wave 0V to 4V

edge time 8ns

width and frequency, it does not matter but the shorter it is the better.

I used Agilent 33XXX series example - standard wave form example to find the approximate pulse wave,
but this method was not able to set the edge time.

Conversely, if you try to apply pulse wave vi file (instrument I/O - driver - 33XXX - configure - pulse)  to example file,

it can only set period, width, and edge time in the pulse vi file. I could not find the voltage level setting.  

I want to know if I can construct a pulse wave with the following conditions using the labview 33220a example, and I want to know where to start.

GPIB interface self-test error -37051 shows in MAX

Tue, 23 Jan 2018 07:38:43 GMT2018-01-23T07:38:43Z

I have two on-board PCI and PCIe GPIB boards connected in one PC. The PC is running on Win7 Pro.

Using MAX application I run the self-test on both gpib boards. The PCI board self-test end correctly. The PCIe board gives an error message:

"An unknown NI-488.2 software problem has occurred. (-37051)"

I scanned the network for possible solution or more data and found nothing. There's one reference in the NI discussion forum about this error under the subject - "Self test error -37051 visa 488.2 USB GPIB interface" but this discussion trail remains unsolved.


Can anyone understand this error? What it means? Is there anything to do to fix the error?

P.S. I tried to RESET the gpib card using MAX on both Reset options and still the self-test shows the error.

Appreciate any help or support.

Thanks much

CHROMA 62012p power supply

Mon, 22 Jan 2018 09:50:37 GMT2018-01-22T09:50:37Z


I am trying to communicate with CHROMA 62012P power supply using labview 14 32-bit through USB. It is always throwing error. When I am passing IDN command from NI-MAX it detects the instrument properly.


I tried the same vi using labview 8.5 version and it works fine and I am able to get my result.


What could be the issue causing this error? 

keithley 6221 ethernet

Mon, 22 Jan 2018 07:43:13 GMT2018-01-22T07:43:13Z

Dear All,


I want to control 6221 through ethernet method. The 6221 and 2182A are connected to each other with RS232 and trigger link.

I try to use the demo program Keithley providing to test the instrument. Both instruments are connected to computer successfully, and all functions work by using the demo program.

However, when I use my program, the error show up when the command is sent to "VISA write".

(No error at "VISA open") Further, the instrument do not show any "REM" word.


Could you please give me some suggestions about this problem?

Very Thanks!!

Reason for GPIB delayed answers or unanswered

Sat, 20 Jan 2018 20:41:53 GMT2018-01-20T20:41:53Z


Hi everyone!

Thsi is te situation, some days ago I was looking for a way to know the commands to remote control an instrument for EMC it is a UCS (Ultra compact simulator), I finally found the commands but they don´t work on the correct UCS. The commands are for the UCS500M but works on the UCS500N. For example, I send EC;]\n to check the connection of the interface and I sometimes receive the identification of the device (UCS500N) but some other times I don´t have an unswer until I send one or two commands more. I´ve tried this also with the UCS500M but never had an answer. I have tried both Visa Test Panel and a VI using the visa subvi´s and observed the same bahaviour.

Does anyone have an idea of what is happening?


VBA ReadString error

Fri, 19 Jan 2018 17:14:46 GMT2018-01-19T17:14:46Z

Hey everyone. I'm Andrea, a technician who just started working with a Fluke 8845a which needs to be controlled by an Excel file to measure resistance every "x" seconds.


Now, I'm really just beginning. And I'm already in trouble. When inserting the code below  in VBA I get the error attached. The error pops up at the ReadString line.


It says "runtime timeout, automation error". What can it be?


P. S. Sorry if there is a presentation section, I'm from mobile and I couldn't find it.


Sub idn()
Dim ioMgr As VisaComLib.ResourceManager
Dim idn
Dim instrument As VisaComLib.FormattedIO488
Set ioMgr = New VisaComLib.ResourceManager
Set instrument = New VisaComLib.FormattedIO488
' use instrument specific address for Open() parameter – i.e. GPIB0::22
Set instrument.IO = ioMgr.Open("TCPIP0:: OCKET")
instrument.WriteString ("*IDN?")
instrument.WriteString "SYSTem:REMote"
instrument.WriteString ("READ?")
idn = instrument.ReadString

End Sub


How to know the GPIB commands for an instrument without seller information

Fri, 19 Jan 2018 02:25:27 GMT2018-01-19T02:25:27Z

This is the situation...

I have an intrument to generate tests for EMC, I control it manually and with a PC application.

What I need to do is proggramming a new application to control it but I don´t even know the commands that the actual application sends to the instrument. I read all the available seller manuals but there is no information about these commands. Is there another way to know these commands?

PD: As you realised I´m new at this forum

Problem with write subvi in Watlow EZ-Zone controller

Thu, 18 Jan 2018 15:57:38 GMT2018-01-18T15:57:38Z

Hello, I am a beginner with LabView and I am trying to control a Watlow EZ Zone PM controller using the Labview driver downloaded from their website (link) and a USB to RS485 adapter.

I can initialize and read, but everything crushes when the "" element executes. When using the example provided (Standard Bus LabView the communication with the controller breaks down. On the other hand, when I use it in the VI I want to create, the program completely crushes. Apparently, the problem in the latter might be in the "ILabview In" and "ILabview Out" elements (see image below).(image) The error coming out is 1172. I should also say that when I opened the VI (both the example and mine), these warnings appear:


C:\Program Files\National Instruments\LabVIEW 2011\instr.lib\Watlow Std Bus\Public\ (
- The .NET assembly expected to be at "C:\Program Files (x86)\National Instruments\LabVIEW 8.6\instr.lib\Watlow Std Bus\Public\Watbus.dll" was loaded from "C:\Program Files\National Instruments\LabVIEW 2011\instr.lib\Watlow Std Bus\Public\Watbus.dll".
C:\Program Files\National Instruments\LabVIEW 2011\instr.lib\Watlow Std Bus\Public\ (
- The .NET assembly expected to be at ":\Watbus" was loaded from "C:\Program Files\National Instruments\LabVIEW 2011\instr.lib\Watlow Std Bus\Public\Watbus.dll".
- Expected Assembly "Watbus, Version=, Culture=neutral, PublicKeyToken=null", but found "Watbus, Version=, Culture=neutral, PublicKeyToken=null."


Can anyone help me to identify the problem? I am using Labview 2011.

Thank you in advance!!

Connecting NI USB 6353 to ethernet

Thu, 18 Jan 2018 10:15:58 GMT2018-01-18T10:15:58Z

Hi, I'm using NI USB 6353 and want to control it remotely by connecting it over ethernet.. Al my other devices are connected using TP-LINK TL-PS310U. I'm able to connect DAQ over this server like on photo bellow, but I can't see it in NI MAX under devices, and can't find it when I try adding new network device.


Thank you for your time.


New NI USB-232 Cable Heated Up

Wed, 17 Jan 2018 23:47:19 GMT2018-01-17T23:47:19Z

My newly purchased USB-232 cables, serial# BTDD0219 and BTDD020A, when connected to the mt laptop USB (cable(s) all by itself) heated up after about 5 minutes. Initially, Device Manager recognized these cables but after the initial hook up, the RS-232 ends heated up and Device Manager drop the connection. And if I'm fast enough, I can run my MET/CAL program for a few steps until the RS-232 terminal heated up. Then it crapped out!


What's the solution? Please advise.


My other but older cable, same model# 188345C-02, has no issue at all. I had this old cable hooked up on the same laptop and ran all day long without issue!

Reading in Pyrometer Data to LabVIEW through USB

Wed, 17 Jan 2018 20:09:11 GMT2018-01-17T20:09:11Z

Note: Please let me know if this would belong better in another community and I will repost it there. 

I work in a research lab that requires a pyrometer to do non-contact temperature measurement of silicon chips that are heated by halogen lamps. Presently, we use thermocouples to read the temperature and then do closed-loop feedback to either turn the lamps on/off based on the heating trends that we desire. The issue with using the pyrometer (Model here: and the manuals are in the "Datasheets and manuals" tab) is that the software provided by the manufacturer just records the data into a text file after the test is run and doesn't allow for real-time integration with LabVIEW. There is a connector that plugs into the back of the pyrometer and has wires with the following designation:



Then there is a further USB adapter that we bought in order to communicate with the pyrometer on the computer. This is the connection diagram:


I'm new to LabVIEW - is there a way to get the temperature data (which I assume is coming from TXD, the yellow wire) into LabVIEW? Could I use a Compact DAQ on the digital side and plug the TXD wire into one of the channels to receive data? Or is there a way to still use the USB? Thank you so much for any help. 

Optimal GPIB commands sequence

Tue, 16 Jan 2018 19:09:51 GMT2018-01-16T19:09:51Z

Hello everyone,

I have at least 5 different devices sharing the same bus and I am using GPIB for the communication with them.

I am looking for an optimal command sequence for communication like

for write *rst; *cls; some_command; read ; *wai (or *opt? *opt).

Additionally, GPIB communication occurs from a different VI's simultaneously (I am not an original developer of these programs).

Sometimes the program froze when one of the devices reveals the error of the command from the remote program (i.e. VI).

So, my idea is to prevent the error organizing a timetable for commands, I mean Check if device is busy, wait, if too long -- Cancel; send a command; read; wait until reads; make a mark that device is free for another command.


Thank you in advance for any suggestions.




Best architecture for large number of VISA devices

Mon, 15 Jan 2018 16:01:45 GMT2018-01-15T16:01:45Z

I am about to begin developing a system that will communicate with about 300 devices via RS-485.  I am using the NI PCIe-8431/16, 16 Port RS485/RS422 Serial Interface.  I'm using 11 ports, each port has 27 devices on it.  Before I start development, I'm really just fishing for some advice on the most efficient/simplest architecture for a program like this. I'd like to monitor output from the devices as often as possible.  Based on these outputs, I'd send commands to the devices occasionally.  I plan on using the VISA vis for communication.


I'm thinking something like a parallel loop set up where one loop sends commands and the other reads the output.  This doesn't seem too tough until I start thinking about how to manage 300 devices across 11 ports!  Any advice, examples, or thoughts on setting this up would be much appreciated.  




Insufficient system resources to perform necessary memory allocation

Mon, 15 Jan 2018 15:50:02 GMT2018-01-15T15:50:02Z

I have been running an assortment of GPIB, VXI and TCP/IP devices through in-house device drivers via VISA. These interfaces have been run for more years than I care to remember. One of our test computers rebooted at some point and since then I cannot get all the devices to initialize without getting the error "VISA: Insufficient system resources to perform necessary memory allocation". At the most I can get perhaps 8 out of 20 devices to initialize without error. Adding one more device causes the last successful device in the list of devices to report the error (not necessarily the last device added).

Bear in mind that there have been no changes to the driver software or to the types and quantities of equipment connected to the test computer at that point. The computer in question was found to have a bad power supply and two failed hard drives. Replacement equipment was installed and the software re-imaged from backups. The problem still occurs. 

I don't know how I can get a sudden and continued failure and what could be causing it.

This is old software that has been in use for some time but was re-installed following the computer hardware replacements:

NICvisa ver 3.1     (NI-VISA for 32-bit Solaris)

NIpcigpib ver 2.3

NIpcimxi ver 2.1.0-2

multiple SPI device on myRIO

Sat, 13 Jan 2018 14:31:40 GMT2018-01-13T14:31:40Z


I need to acquire 2 PT1000 and 2 Resistance with myRIO for my application.

In order to achive a good measurements I thinked to implement a 4 wire measurements for the PT1000, and the resistance trought a MAX31865 device.

The MAX31865 has a SPI interface, so my question is how can connect 4(or more) SPI devices to myRIO?

Infact myRIO has only 2 SPI( one for the A MXP and one for the B MXP).

Can you show me an example of code to manage this four devices?




Multiple serial read overrun error.

Wed, 10 Jan 2018 14:35:05 GMT2018-01-10T14:35:05Z

Hello All,

I am scanning two serial ports (barcode scanners on usb ports with usb to serial converter) simultaneously and creating an array for the different entries as shown in VI


Apart from it I am also scanning Digital inputs (not shown in attached VI, in a while loop).


Sometimes, I get an overrun error, how can I overcome it or what changes should I made in my VI.

I am using LV 2013

Thanks & Regards


Can't restart cRio 9074 with Automation & Measurement Explorer

Wed, 10 Jan 2018 09:17:54 GMT2018-01-10T09:17:54Z


First, excuse me if my question is trivial, i'm new with National Instrument communication.

I need to restart a distant cRio 9074, programmed with labview 8.6.1. I installed NI-RIO 4.0, and I can see - very slowly - the cRio in Measurement & Automation Explorer V5.0. However, it stays "disconnected", and the "restart" command is disabled.

Any idea?


NI-488.2 Runtime 17.0.0 download fails

Tue, 09 Jan 2018 21:23:18 GMT2018-01-09T21:23:18Z

Whenever I try to download NI-488.2 Runtime 17.0.0 (target computer: Windows 7 64 bit), the download always fails at the very end. I've tried MSIE (version 11), Firefox (version 57) and Chrome (version 63) with no success. Firefox and Chrome say it's a network error, whereas at the end of the download MSIE hints that it may be a spam/phish link or other unsafe file. In the past, NI used to manage it's downloads with a downloader stub, but now it wants to download the entire 680 MB file in one huge chunk. Is there an alternate download link?

NI IO Trace

Tue, 09 Jan 2018 01:34:53 GMT2018-01-09T01:34:53Z

I have an old Mac running an old version of LabVIEW and I need to see if signals are successfully going out to a GPIB device.  Can I use NI IO Trace running on a new laptop with a GPIB-USB adapter between its UBS port and the stack of GPIB connectors and record any signals?

Simple VISA Write/Read not working in LabVIEW 2015 (works in LabVIEW 8.5)

Tue, 09 Jan 2018 00:29:24 GMT2018-01-09T00:29:24Z



I have an issue when I try to use LabVIEW 2015 to talk to a Tektronix TBS 1052B oscilloscope using VISA (with a USB connection). In particular, I seem to be able to write commands (e.g. '*IDN?'), but 'VISA Read' always returns nothing, and without errors. I know that VISA Write is working because I am able to write in a LabVIEW 2015 VI and then successfully read using the VISA Test Panel.


What is most confusing to me is that the both the VISA Test Panel as well as an identical VI written in LabVIEW 8.5 both Write/Read perfectly fine. I've attached screenshots to show the two VI's, as well as a log from NI Trace.


LabVIEW 2015:



LabVIEW 8.5:



NI Trace log:



You can see that in 8.5 and in NI Trace, the read commands return 'TEKTRONIX, TBS 1052B...' while 2015 returns nothing. All give no errors.


Things I've tried:

  • Playing with Termination Character. I thought that maybe 2015 VISA Read always immediately encountered a Termination Character '\n' and thus returns 0 bytes. I tried disabling the Termination Character in the Instr. Property Node before VISA Open, but this didn't change anything.
  • Adding a delay before VISA Read. I tried up to a 2 second delay to give the oscilloscope time before the Read command, but this didn't change anything.
  • Different version of NI-VISA. Both NI-VISA 17.0 and NI-VISA 15.0 give the same results. Note that LabVIEW 8.5 uses NI-VISA 4.4.

Anyone have suggestions? Another question: what are the differences in the LV8.5 VISA blocks and the LV2015 VISA blocks?


Thank you for the help (image)