Remote GPIB

Good Day, Ladies and Gentlemen. I am trying to read a TRAK Microwave GPS clock. The clock is a GPIB instrument attached to a 488 card in a remote PC. The VISA address for this device is GPIB0::7::INSTR. I want to issue the command "RQLT\r", but have not been successful. See attached screen shot.
I suspect the problem is the instrument address. I have no problem accessing the clock using Vee Pro. I thought the instrument may not yet be registered with LabVIEW, but cannot find any app to pull this instrument in.
Solved!
Go to Solution.
Attachments:
CLOCK-VI.jpg ‏59 KB

For remote visa, you need to provide a fully qualified path to the instrument.
I haven't done this for a long time, but it should be the name or address of the computer hosting the gpib board followed by the board number, address and type:
something like:
visa://192.186.1.23/GPIB0::7::INSTR
You also have to have the NI-VISA Remote Server running on the computer hosting the GPIB card.
See this Knowledgebase entry: Remote Instrument Control with NI-VISA
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Similar Messages

Occasional GPIB Error -1073807342/-1073807300

Hi
I am running a test with a CSA7404B (Tektronix Communication Sigal Analyzer). The system is expected to run for about 7-8 days without interrruption while communicating to this instrument. Occasionally (after 48 hours of running without problems), I get the one of the two errors mentioned above. I dont have multiple open visa sessions. Any ideas?
Thanks

Error -1073807342 mostly is caused when the resource name passed to VISA Open is incorrect. Try to adress your device directly such as: GPIB0::5::INSTR. Make sure not changing GPIB adress on your target device ((Tektronix) while communicating with it.
As a precaution for error -1073807300 prove following. Is there really only one session opened ?
If one of both errors occur, try to open a VISA session and communicate with your instrument via MAX (Measurement & Automation Explorer). Further try to reset your remote GPIB device.
How do you procedure when this error occurs ? Do you restart your VI which is responsible for communication ( or LabVIEW completly) ? Do you reset your GPIB device ? Do you restart your PC ?
Is this error dependent on your GPIB device (does this error also occur if you communicate with an other
instrument) ?
What GPIB Card you are using ?
Maybe you can attach your GPIB communication vi realized with VISA VI´s ?

A GPIB remote panel question

Hi all, I have created a VI that make use of GPIB to control some of my lab equipment. The problem now i face is how can i set this VI as a remote panel for internet. I have a free website under www.bravenet.com . How can I do such a remote panel thing? thanks

Hello Jackolim,
Thank you for contacting National Instruments.
What do you want your remote panel to do? There are basically two different methods. In one you just monitor your front panel over the internet, like screen shots. The other method allows you to actually adjust the controls remotely.
If you need the first method then you just need to periodically upload the front panel image to your website. You could then have your site periodically refresh itself.
The second method however is not do-able, unless you have LabVIEW on the server. When you are hosting a VI remote panel, the LabVIEW web server is actually used. So the machine running LabVIEW hosts the website on itself, and has direct access to the VI that you are running. There is not a w
ay I know of to somehow route all the information through another web site. You will just need to host the VI on the computer running the VI.
I hope this helps.
Sean C.
Applications Engineer
National Instruments

How remote/local mode for GPIB instruments works?

Remote/local mode for GPIB instruments is being controlled by REN one of five interface management lines. That's the only information available on this subject. Where can I find some more detailed explanation? I still don't know what conditions have to be met to put device in remote/local mode.

REM indicates whether or not the board is in the remote state. REM is set whenever the Remote Enable (REN) GPIB line is asserted and the GPIB board detects that its listen address has been sent either by the GPIB board or by another Controller. REM is cleared whenever REN becomes unasserted, or when the GPIB board as a Listener detects the Go to Local (GTL) command has been sent either by the GPIB board or by another controller, or when the ibloc function is called while the LOK bit is cleared in the status word.
A call to the function ibonl clears the following bits:
END LOK REM CIC TACS LACS DTAS DCAS
You can find more information in the NI-488.2M Software Reference Manual (see link below).
http://digital.ni.com/manuals.nsf/web_productcurrent/43AB49D953CE104E8625665E0
07D11FF?OpenDocument
All of our manuals are available online at the following site.
http://www.ni.com/manuals/
Thanks,
Kim L.
Applications Engineer
National Instruments

How to resolve the error -1073807339 when using Agilent LAN/GPIB Gateway (E5810A)?

Dear Sir/Madam,
Appreciate that you could advise me on the following error occur when connect power meter E4419B to computer via E5810A LAN/GPIB Gateway(remote interface) & run with Labview:
-1073807339
VISA Write in E4419_read_power.vi
I have added 5s timeout to Labview program but the result as previous.
There no error occurs when the power meter to computer via USB/GPIB interface(82357B).
Is it related to E5810A driver or the program I wrote?
How to resolve it?
Attachments:
E4419_read_power.vi ‏16 KB

Hi.
I'm experiencing the same problem when connecting a laser controller (New Focus Vortex TLB-6000) via the Agilent E5810A to a PC.
There are no problems when connected through a regular serial port, but timeouts arise every few seconds through the E5810A. I have another controller (SRS LDC501) which works very well with a second Agilent console.
Have you managed to find a solution to this problem?
Thanks,
Orel.

System design for remote control

I just wonder which tech of ni I should use.
My system is one data center and some remote DAQ site. The communication is through WAN.
It need to
- start stop and schedule DAQ card from remote data center
- send realtime data back for display
- report the DAQ running status, such as online.
- send history data from site pc to center database
there are many choice, such as tcp/ip, data socket server, shared varible, remote panel, remote vi server, web server.
May I know which one is more fit for the application?
Thanks a lot.

krishh wrote:
Hi all,
I am very new to Labview, but I have to deal with somewhat difficult problem of remotely controlling the Laser in next room. The PC I will be using has already built labview software to control the laser if laser is closeby. But the laser is next door (~200-300 feet), and the PC which controls the laser also have the labview software to control the laser. Please suggest me how should I start communicating from my first PC to the laser (may be using the laser labview software or not). To start with I would be glad to find some reads or demonstrative examples or any suggestion which will head me to right direction.
I hope for great help.
Regards
Krish
It would probably be a good idea to start a new message on this rather than continue in this message thread. It seems to be a different situation you are asking about then what the original poster was doing.
How does the PC communicate with the laser if it is close by? Is it a serial connection? ethernet connection? GPIB? something else. If it is serial, is it RS-232, RS-485, USB? 200-300 feet is too far for an RS-232 or USB connection. But there are numerous products on the market that will adapt those serial protocols to either an RS-485 wiring setup, or put it out over an ethernet connection. So you can go RS-232 to RS-485 on one end. RS-485 goes to 4000 feet (depending on baud rate). Then on the other end another adapter converts it back to RS-232. I have also used a remote USB hub that connects to a LAN connection, and with driver software installed on the PC, it turns that remote connection into virtual serial port connections.
These are good devices that have worked for me. But if they would work for you all depends on how the PC connects to the laser now.

How can I connect to a remote firewire camera?

We have a system that has the following peripherals connected to it:
1 - firewire camera
2 - serial port devices
2 - emulated serial port devices (on VCP USB drivers)
1 - Ethernet device
We have developed an application using CVI 8.1, NI Vision 8.6, and NI-IMAQdx 3.2 (it's an older cam). I would like to make this system accessible remotely (not remote desktop) and was looking for a way to program a server/client setup. Although it will be a lot of work, we can easily take care of a protocol for the Ethernet and serial devices. Where I'm getting stuck is the camera.
I've searched the forums and it seems that people can use the RT software module on specific host hardware to do just that. We don't want to invest in purchasing a separate software module or another piece of hardware, so I was wondering if it was possible to configure MAX or the NI vision server somehow to connect to a remote win7 PC to grab frames and configure the camera OR is there an easy way that I can transfer the stream over TCP/IP?
The only solution I can come up with is the grab a frame, save to .PNG, transmit it, and then load it on the client side. This seems very wasteful (and slow considering the harddrive will constantly buffer the data) and I would need to do a lot of encapsulation for changing camera settings, etc. Further, I'm not sure how well this would work for when we try to calibrate the camera with the IMAQ drivers. Is there a way to get the size and all relevant data structures in memory of the vision server so I can transfer them?
Finally, if there is a simple way of configuring and doing all of this for the camera that I'm missing (through MAX), then is there a similarly easy way of mapping the remote serial ports and of bridging the Ethernet data? I know there are a few pieces of existing software for the serial ports, but was looking to make a single software solution.
Thanks for taking the time!
-Stan

Hi Stan,
Welcome to the NI Discussion forums! Thanks for posting your application here. There certainly are more efficient ways of streaming IMAQ images over a network. One such method would be to convert the IMAQ image type to a 2D array and then pass the data through TCP/IP, as you eluded to. Do you have access to LabVIEW? If so, you can look at this community example and base your CVI code on it. Although it is meant for a Real-time CVS acting as the remote system, you should be able to run the code on a regular PC. If you don't have access to the LabVIEW development system, the overall code structure for the server system is as follows:
- Open IMAQdx reference, initiate a TCP connection, Create IMAQ image buffer
- Initialize an IMAQdx grab
- Loop:
- Call IMAQdx grab
- Use the IMAQ Flatten Image to String to convert the IMAQ image to a string
- Call TCP Write to send the string length first, then again to send the actual string data
- Dispose of the IMAQ image buffer, close the IMAQdx reference, close the TCP connection
On the client end, you just need to open the TCP connection and call TCP read to read the string size and then the string data. Then, you can use the unflatten from string function to convert the string back to an IMAQ image data type. After this, it is up to you how you want to process the data (display it on the screen, write to an AVI file, etc).
If you are not sure how to implement TCP/IP programs in CVI, please take a look at this tutorial. If you have more in-depth questions about implementing the TCP/IP side of the program in CVI, you may wish to post that specific question on the CVI board.
With regards to mapping the serial ports remotely, if you are already using NI-VISA for COM port communication, take a look at this document on Remote Instrument Control with NI-VISA. Essentially, you should be able to access the VISA resource (e.g. a COM port) remotely by enabling the remote NI-VISA server on the client machine. For more specific help with this aspect of your code, please post to the GPIB/VISA board.
Feel free to post again here if you have more IMAQ and vision-related questions. Hope this helps!

Connecting hp 8508a vector voltmeter with agilent 82357a usb/gpib converter

Hello
For my experiment, I need to connect to a HP 8508A vector voltmeter by using an agilent 82357A usb/gpib converter. I have a serious problem about communicating with my device using NI-VISA. I tried to do the steps indicated at following links which were indicated at the forum posts by people using 82357A:
http://digital.ni.com/public.nsf/allkb/F7C187DBF09EBE1186256F550065BD32?OpenDocument,
http://digital.ni.com/public.nsf/websearch/3B3626D9C1F999218625694200791AD7?OpenDocument,
http://cp.literature.agilent.com/litweb/pdf/5990-3731EN.pdf?cmpid=1273CN.
The version of MAX is 4.3.0f0 and i am using labview 8.5 with NI-VISA 8.2. I am trying to configure my 82357A using agilent io libraries suite 14.1.
First, I tried to configure my usb/gpib controller using agilent connection expert and set the visa interface id to GPIB6 and connect to the 82357A without any problems. Then I connect this gpib converter to my vector voltmeter. The gpib adress of the voltmeter was 6(gpib address of the interface converter was 10) so visa address GPIB6::6::INSTR was assigned to voltmeter by connection expert. I tried to connect to the voltmeter from the connection expert by using the agilent interactive IO. Send *IDN? command and took the proper response from the voltmeter. The voltmeter went into remote mode and I tried to read the voltage values by using the FETCH? command of the device and got the voltage properly which means I successfully connected to the device.Then I went to MAX and enabled the NIVISATulip.dll and restarted the MAX. Then I went back to agilent connection expert and checked the box: "use agilent 488 library where possible" for side-by-side communication between the NI and agilent visa. By the way agilent visa was installed as the secondary library. Then when I went back to MAX, I start to see the voltmeter under miscellaneous VISA resources with the address GPIB6::6::INSTR. But the problem started here. When I tried to send commands from MAX to voltmeter with the "open visa test panel" I encountered an error which exactly says:"unable to open session to GPIB6::6::INSTR, return status code:0xBFFF009E, status name:VI_ERROR_LIBRARY_NFOUND, a code library required by VISA couldn't be located or loaded." As I said before i enabled the libraries of agilent 488 from the options of the agilent connection expert. When I went back to connection expert and unchecked the box for using agilent 488 libraries nothing changed. Also when I went to NI-VISA interactive control I couldn't see my device under the tab of VISA I/O.
I tried to read some posts from this forum. People are using this usb/gpib converter successfully without any problems by performing the steps I have done. I have some questions about possible subtle points specific to my application.
First question is according to the manual of the voltmeter(this is an old device by the way from 1988):"vector voltmeter is capable of remote operation via the HP-IB which is HP's implementation of IEEE standard 488.1 "So, what I understand from this sentence is my device is communicating remotely with IEEE standard 488.1 and not 488.2 Does it make any problem? What kind of modifications should I do to my setup for overcoming this if it creates any problems? As I said before I was communicating with device very properly from the agilent connection expert. In manual there is also a sentence like "HP-IB commands used in the vector voltmeter conform to the standards set by document IEEE 488.2 1987."
Second question is should I install newer versions of agilent io libraries suite or MAX or NI-VISA. I wrote the versions I am using before are they compatible? Where can I install newer versions? As I know the newest version of the agilent io libraries suite is 15.1 or 2. Is is compatible with 82357a?(maybe I should ask this question to agilent people)
Third question I don't remember how I did it but agilent visa is indicated as secondary visa resource in agilent connection expert(I think I did it while installing agilent io libraries suite.) . How can I switch between NI and agilent visa as primary visa resource? Do you think think this will help?
I terribly need measurements from this set up and really appreciate your help if possible.
Sincerely
Caglar Yavuz, University of Michigan,Ann Arbor,EECS department.

Caglar,
The documents you mention ahould include the proper prcedure for using this hardware in LabVIEW. Here are my recommendations:
The version of NI-VISA you mentioned is not valid. The most recent version is 4.6.2. I would recommend ugrading if you do not have this version. After the upgrade,ensure that tulip is enabled as well as the other settings and see if this helps.
When talking about the instrument, the biggest concern that usually is relevant with 488.1 is that it will not respond to *IDN?. In your case, it looks like it does, and should work as 488.2 is backwards compatible. It seems to me, the issue is still with the 82357A, and we have not yet reached the voltmeter.
In order for NI-VISA to work with your device, NI-VISA must be the primary visa driver.
Hope this helps, let us know how the upgrade turns out. If you continue to have issues, take some screenshots of the preferences in MAX and upload them on the forum.
Regards,
Peter Flores
Applications Engineer

Using a lan/hpib gateway (Agilent) with a NI GPIB pci card

Need to be able to use a E2050 lan/hp-ib gateway (Agilent) together with a NI GPIB pci card on the same workstation (windows). I need 2 seperate gpib busses but also need the remote functionality or the lan/hpib box. I would use ni enet but it will not work together with a installed gpib card, only one or the other. Read information on useing an hp card with a ni card in the same system but cannot get it to work with the lan box. I do not have a hp card to install in my computer to see if that works or not. Has anyone attempted a similar task?

Hello-
It is possible to use a PCI and ENET board in Windows 9X/ME. The solution for Windows NT/2000 is to use the new VISA server technology using two computers.
Computer A:
This is a computer that will not use a GPIB plug-in board, but is on the network. Install the GPIB-ENET/100 driver and VISA 2.6. Then, set the appropriate VISA server permissions and run VISAServer.exe (see the VISA Programmer's Reference for more details ni.com/manuals).
Computer B:
Install the PCI-GPIB driver and VISA 2.6. Use Remote VISA to access the ENET/100 through the other computer's driver.
This is also a very useful technology for remotely controlling numerous instruments throughout a distributed laboratory.
Randy Solomonson
Application Engineer
Natio
nal Instruments

Can I call a built in LabVIEW function remotely?

I would like to call a bunch of LabVIEW's built in GPIB functions on a
remote computer to talk to a device attached to that computer. I was
able to do this using VI server and by wrapping the GPIB function in a
custom vi (this vi was just GPIB Write with controls and indicators)
Is there a way to avoid making a "wrapper" VI for built in functions
such as GPIB Write? i.e Open a VI reference to built-in LabVIEW
functions remotely using VI server?
Thanks,
Brian
Sent via Deja.com http://www.deja.com/
Before you buy.

That is one of the built-in functions and not a stand-alone VI and the best way to call it is to create a VI with it on the block diagram.

GPIB-USB libraries that need to be included with Installer

Hi,
I need to make a small application executable, and the application needs to communicate with a power supply over a GPIB-USB-B connection. MAX can communicate with the power supply on this PC, and the second PC that I have my Base LabVIEW 7.1 installed on runs the executable application successfully. When I try to run the executable on the first PC, however, the process hangs. I included an Installer in the original executable build for the first PC, and in this build all the options under LavVIEW Run-Time Engine were checked (although LabVIEW RT Support wasn't available for checking.) However, none of the other options (Remote Panel License Support, Serial Port Support, Port I/O Support, and Hardware Configuration) are checked because I didn't think that I needed any of these for the basic GPIB communication I'm performing (just VISA Open, Read, and Write). Do you have any idea which of these libraries I need to include in the Installer to make this work? Or is there some other problem I'm not thinking of?
Thanks,
Mark

What makes the situation odd is that MAX was capable of communicating with the device, but my application was not. In the interest of making it work, I stuck a spare license of Base LabVIEW onto the PC, and then the application (even the compiled, executable one) worked fine. So clearly something wasn't loaded along with the GPIB-USB-B drivers (or my application installer) that WAS loaded by the full installation of LabVIEW. But, again, the oddness of the situation stems from the fact that before loading the full LabVIEW, MAX (loaded by the GPIB-USB drivers) could communicate fine with the device. This set of circumstances doesn't make any sense to me, but maybe someone else can come up with something.
The PC is a W2K box, and I assume whatever driver information that came in the installer and the GPIB-USB drivers has been overwritten by the full LabVIEW that's since been installed on the machine. I didn't actually oversee the installation of the GPIB-USB drivers, so it's possible the engineer who did that put the card into some odd state--it's also possible he didn't reboot after the driver installation. If the resources come free I'd like to clear out the machine and start fresh and recreate the sequence of events to see if I get the same result. I wouldn't be surprised if the problem stemmed from issues in the driver installation. But I want to hear if anyone's been in a situation like this before I go and do everything over again.
Thanks for your help, and for the additional installer information,
Mark

Why do error comes when trying to use NI ISA GPIb and NI DAQ card (both PnP)together while they work well when one at a time?

we configured gpib pnp and at-mio-64e3 cards (isa) in the same pc.gpib function was invoked to take the device to remote and listen mode.now when daq function getDeviceInfo is called the remote mode of the device is removed and after this it always shows no gpib board until pc is rebooted

Hi,
I have some questions:
What OS are you using?
What driver versions?. You can find the driver versions in the Windows Add/Remove programs utility. DAQ driver is NI-DAQ anmd GPIB driver is NI-488.2.
Is there any error code?
I haven't found any known issues between these two drivers. How are the board's resources configured? Base address, IRQ, DMA.
Let see if with this information we can clear out what is going on.
DiegoF.

GPIB and Desktop RT

I am running the following:
Desktop Labview Real Time 11.0
NI-VISA Server 5.1
and am using an NI PCI-GPIB card to connect to a couple of different pieces of lab equipment.
When I connect to this remote system from another workstation using MAX, I do see GPIB0 (PCI-GPIB) under devices and Interfaces on the RT machine, but I cannot figure out how to see the GPIB instruments that are connected to the bus.
I don't think it is a electrical problem on the bus because when I boot the workstation into windows instead of RT, I can see the instruments just fine using Max on that machine.
Rick
PS: The workstation I use to connect to the RT machine remotely runs a current version of Labview
Rick Foster
MIT Kavli Institute for Astrophysics and Space Research
Solved!
Go to Solution.

The current VISA Interactive Control layout is a bit differenent from the tutorial.
I do see the instruments now, but they are listed under localhost and I get an error when I try to list them on the remote machine that the GPIB controller is installed in.
I can now access the instruments in my code, but this Localhost versus Remote machine bit is confusing.
Rick
Rick Foster
MIT Kavli Institute for Astrophysics and Space Research

Old transient recorder, new GPIB-card (+Labview) How?

Hi, we have an old 12 channel 200kHz transient recorder
(Krenz TRC 6410). Until now, the software is still MSDOS. Since we have a GPIB NI card, I wondered if we can't get this to work together, but I'm a complete newbie. I had a look at some other VI's for a Yokogawa Freq. generator, but the recorder's documentation looks
quite different. Here's what I found out:
1. Once I managed to find the device in MAX. It registered under PA 4, SA 0, like the manual said. But after some trials (which got me nowhere) and a reboot, the device won't show up anymore.
2. In IBIC, when I use ibln 4 0, it says Listen: True,
so this device is there.
3. I would be very glad if I could somehow switch the Voltage selector remote!
To do that I have to transmit two bytes, e.g. 129 and 4 (129 is adc-channel, 4 is new voltage level). But before the first byte, I have to send GET, and after the first byte, SDC.
Help, I failed miserably so far :-)
Any help is appreciated, e.g. ibic sequences, labview examples, whatever. I what to make sure that this works
before investing to much work into it.
Thanks in advance,
Dirk

Hi Dirk,
1. Please go to www.ni.com/support. Then celect GPIB and after that, select Interactive Control Utility. Here you will find a list of command sequences.
I hope I have understood your problem.
2.Regarding LabVIEW examples, please go to www.ni.com>>NI Developer ZONE>>Development LIbrary>>GPIB. There are a lot of examples. And I hope this will help you.
P.S:
I could not understand what do you mean by trials. Because how can the trials prevent the device from showing up.
In IBIC where you did ibln, also try ibwrt and ibrd and see if it works.
Please do get back if you have any further questions.
Sincerely,
Sastry V

PCMCIA-GPIB won't pass Troubleshooting Wizard but Device Mgr reports no conflicts. WIn2000 OS.

GIPB Interfaces Sequentually verified fails. There are no IRQ or Address conflicts according to the Device Mgr. The Event Viewer says "... event ID (3) in source (gpibtnt) cannot be found. The local computer may not have the necessary registery information or message DLL files to display messages from the remote computer...".
I have uninstalled & installed the NI-488.2 s/w & the GPIB driver multiple times w/o success in passing the troubleshooting wizard.
I get a blue screen when I try to "Scan Devices".
I get a blue screen when I compile & run Microsoft C sample programs.
VISA seems to be working. At least it sees the devices that are on the bus.
I need t
o write a MS C program to talk to a HP E4408B Spectrum Analyzer. I need to setup the analyzer and then log data on disk. My main Calls will be "send() & receive()" and probably a few others. Is the problem with the troubleshooting wizard going to cause problems with these calls. What NI libraries will I need to do this using ANSI C with the Microsoft Developers Studio v. 6.0.
I am using WIN2000 on a Toshiba Tecra 8000 laptop.
Thanks,
Dave Diener

Dave,
This could be an issue with the socket service being used to allocate the resources on the laptop. The posting below has a pretty good explanation of how to troubleshoot this (refer to the posting by Jason Hobbs). If that doesn't work I'd call into the NI Support center.
Best of luck,
Kamran
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000D10A0000&ECategory=Instrument+Connectivity.GPIB

Remote GPIB

Similar Messages

Maybe you are looking for