GPIB and Ehternet

Similar Questions

• GPIB and VISA support

  I need help to understand how VISA reads from GPIB. By using LabView 8.6, I'm applying to communicate with a customized by using GPIB controller. He is currently working, but I'm not sure of how to use the Enable property of termination.

  I read of GPIB using VISA Read. I use 1000 for the number of bytes. VISA expiration time is set to 30 seconds. The controllers stop character is a ' > ' (ascii 62).

  1 how VISA knows when to stop reading if there are less than 1000 bytes to be read, the stop character is disabled, and it is during the period? VISA stops when more no byte is coming in? It works for me with endpoints off, but with an ending to this topic is much slower and I don't understand why.

  2. I also use the GPIB-RS232 converter for certain situations. The PC has the GPIB and RS232 controller. Using the converter, I need to activate the stop character so that it works correctly.

  A GPIB read should end when EOI is detected. It is one of the management interface, and is a requirement for the GPIB. A stop character of > is very strange. If any type of stop character for a GPIB instrument designed over the past 20 years or more, is, to put it politely, unusual. Your calling a controller raises another question. There is usually only a single controller in a GPIB system and it would be a device as the NI PCI-GPIB or GPIB-USB-HS. You are trying to design your own controller?

  RS - 232 with none of the lines of management GPIB, you need another mechanism to put an end to a reading.

• RT GPIB and office

  I am running the following:

  In time real Labview Desktop 11.0

  NI-VISA Server 5.1

  and using a NI PCI-GPIB card to connect to a couple of different pieces of laboratory equipment.

  When I connect to this remote system from a different workstation using MAX, I see GPIB0 (PCI-GPIB) under devices and Interfaces on the RT machine, but I can't find a way to see the GPIB instruments that are connected to the bus.

  I don't think it's an electrical on the bus problem because when I start my computer windows instead of RT, I can see the instruments very well using Max on this machine.

  Rick

  PS: My computer that I use to connect remotely to the machine RT running a current version of Labview

  Hey Rick,.

  I did some tests and it seems that it is just how the GPIB devices appear on targets real-time VISA Interactive Control.  It may seem a little confusing, but yes, they are supposed to appear on the local host.  It seems that apart from the confusion there doesn't seem to be a real problem, I'm correct?

• PCI-GPIB and controller movement legacy Newport Orion-CM - timeout in MAX but not MATLAB

  I kinda a weird GPIB problem which seems to be related to the legacy quirks of implementation of GPIB.  The system I use is an Orion of Newport-CM, which has a controller of electrostrictifs actuator in him as a monitor of power on separate GPIB addresses, but a physical port.  I have it connected via a<= 2m="" cable="" to="" an="" ni="" pci-gpib="" board. ="" i've="" tried="" both="" the="" 2.6="" and="" 2.2="" ni-488.2="" drivers="" and="" both="" act="" the="">

  I found that when I try to query the device through MAX, I can see a SPY OR that the first FindLstn mark 2 units, but expires (probably to try a * IDN? command, because it signals no response).  After that, if I try other commands via MAX or MATLAB, all the GPIB commands time out, so I have to power cycle the Newport before being receptive again.  I tried every permutation of the GPIB driver located in MAX without result - always the same behavior settings.

  Curiously, however, when I use the device only in MATLAB (with the instrument control toolbox), I can have some success, but with delays every now and then are not paralyze the MAX in the same way, it was.  I am able to open the device with:

  mcobj = gpib ('nor', 0, 1);

  fopen (mcobj);

  and query with:

  fprintf(mcobj,'*IDN?');

  data = fscanf (mcobj);

  and get the good * IDN? response.

  In addition, I can do writing and reads the device (with intermittent downtime... I found I need to leave at least 0.3 seconds between commands, which leads to a slow operation).

  It left me speechless.  Of course, it appears the interface GPIB works, maybe slowly, but if I'm not mistaken, the same driver should be usage of communication for MAX and MATLAB, why so MAX time so that I am able to have the operation in MATLAB?  Are there some low level which may be different that I cannot change in MAX or GPIB configuration, but is defined by MATLAB?

  Any thoughts appreciated.  Newport is as usual MOM on obsolete parts, and their job is not much help outside retailer orders GPIB (Nothing on the specifications of the bus).

  Thank you

  Scott

  Thanks for the tips.  It seems that the old Newport is just really, really slow (must be material and mid-1990 s), so he needs a good break between her send GPIB commands.  I installed the 1.7 legacy drivers, and those at least have correctly the * IDN? the device response.  Gpib MATLAB interface is quite simple you can give sufficient breaks between commands to send to the Newport, so in it, I am able to control the time between orders.

  It seems that it is just a matter of a slow device.  I know not what look like the internal FindLstn characteristics and, therefore, why the new version of MAX expires while the old ones do not, but for really old hardware that there could be GPIB read/write in the new pilot who are too fast to actually really old equipment sufficient time to respond.  Thanks again for the input.

• VISA viOpen strangeness and linking them to an Agilent N6700B Power Supply (GPIB and C/C++)

  I noticed a strange behavior with connection to a power supply Agilent by GPIB, but if all goes well, just something miss me.

  If I power on and connected via GPIB to a card PCI of National Instruments and launch my app, viOpen gives me VI_SUCCESS and I can handle the desired power (voltage, power on/off, etc. exit exit evolution). However, if I run the application with the power supply off the power (output not only people with disabilities, but completely off) then viOpen gives me no error found resources, as it should because the instrument can not be detected. My request is scheduled to retry the connection every 10 seconds, and also long the power is turned on, it does as expected. The strangeness is when I turn the power supply on when the application tries to reconnect. Even if the power is connected, viOpen still gives a failure condition. In addition, using the Agilent IO connection Expert software, it lists the instrument in an error state. It becomes strange when I open MAX and click on "Contact Instrument." Simply by clicking on this option restores the instrument being error-free and call viOpen to my app works perfectly. Is there something that MAX is to initialize the instrument when you want to communicate with it? If so, is there a way to recreate it using software VISA controls? For reference, here is the code that I use to connect to the instrument (and subsequently tries to reconnect if the connection fails). Thanks for any help in advance.

  In a header file:

  ViSession session, defrm;

  ViStatus VISAstatus;

  In a file:Code .c is performed every 10 seconds

  strcpy (IOaddress, "GPIB0::5");

  VISAstatus = viOpenDefaultRM (&defrm);)

  VISAstatus = viOpen (defrm, IOaddress, VI_NULL, VI_NULL, & session);

  If (VISAstatus! = VI_SUCCESS)
  {
  viStatusDesc (session, VISAstatus, statdsc);
  Print an error message

  return;
  }

  Else if (VISAstatus == VI_SUCCESS)

  {

  viStatusDesc (session, VISAstatus, statdsc);

  Print the success message

  initializeStuff();

  }

  Seems I spoke too soon, I just fixed the problem.

  The Agilent VISA library was used as the main VISA library. I completely uninstalled the Agilent IOSuite (including his VISA) software and uninstalled the VISA National Instruments as well. I then reinstalled the IOSuite and allowed the most recent NI-VISA for overwriting. The first time I ran my application after I did this, it worked perfectly.

• Interface and installation of my instrument with lab view and keithely, GPIB-USB-HS

  Hai...

  We have 236 Keithleu and software vision lab and GPIB-USB-HS. I had the GPIB software installed is OR-488. 2 3.1.1

  Now, I had the indication like that.

  1. in Kethely no indication

  2. in GPIB +'s got orange led in ready icon.

  3 but if I runt the program I found no results.

  So can you me the interfacing of the keithlye and alo for the GPIB and also computer.

  Regads.

  The pilot here can help you. I suggest you first learn how to set up the action manually. Then study the programming guide to understand what commands you need and the settings for them. Good luck.

• Can't control RS232 and GPIB devices simultaneously with labview.

  Hi all

  I have a thermostat that has a RS232 to my computer connection and a counter from the source which has a GPIB to my computer USB connection.

  I have screws that allow me to control each device separately. But when I did a VI to fight them together that I can communicate with the GPIB device, but not with the RS232 device. I think that the VISA GPIB and RS232 VISA having a problem to determine this.

  Do you know what I could try to fix this?

  Thanks for your help.

  
  

• How to synchronize streams RS232 and GPIB in labview

  Dear all, SOS.

  I built a system with 2 instruments GPIB and serial RS232 1 instrument.

  The VI works well with high light performance. But when I run the program normally with games step by step, what I get is only the stream GPIB. The serial data is not found after reading the GPIB data.

  I wonder if there is a sync issue. If so, how can I get these two data streams synchronized?

  BTW: I was trying to use the RS232-GPIBCVA converter to connect GPIB, but always had error6 at visa read. I still can't understand. Without the GPIB-RS232 converter, data can be read with the series making.

  I'm fighting this case several days, hope you guys can give me some suggestions!  Thank you very much!

  Zhenxing

  A quick glance and I don't know why you need all local variables. And even if you have bunches of error wired inside all of these structures from sequence (you should also get rid of), you have not connected to the indicators or pass them to the sequence of the sequence. I have a question some of your other codes. With each iteration of the inner loop, you can reset each instrument. It is highly unlikely that you need to reset or initialize the serial port more than once.

  You will need to also get rid of the constant cable outside during the end of the Terminal loop. Using the button abandon, this isn't the right way to stop a program.

  Highlight the performance slows down the program in a little. You may need to add some delay. Run in normal mode and set breakpoints so that most of the code that runs at a normal speed. By the process of elimination, you will finally find the area problem.

  p.s. These are Keithley instruments, you should really try the drivers that are available.

• Connection of an instrument with GPIB-USB connection.

  I am trying to use a GPIB-USB adapter to control a unit of Source of LabView. However, I have problems my instrument drivers to recognize the GPIB address specified for the device. I have attached an image below the address specified by IO Keysight connection Expert. I am currently trying to initialized the EMS with the GPIB driver I have attached below. Because of my knowledge limited in LabView instrument control, how should I approach of collecting the correct address of GPIB and recognize it in my VI?

  Hi wyattcurtis824,

  Before we dig into the LabVIEW code, I would recommend a Test Panel of max aperture and trying to communicate with. Are you able to send orders via Keysight connection Expert or NI MAX and see the valid data?

  In addition, when you run the vi in LabVIEW, is pilot it returns an error in the error on the box? If so, what the error is?

  This shoule information help us to the root of the problem.

  Best,

• Installation of NI-VISA and NOR-488. 2 on Mac

  I have a new Mac on which I am trying to install instrumentation OR (VISA and GPIB) pilots, and things don't work any tips would be appreciated. I downloaded the most recent version of these two (14.0 visa) and 3.0.1 for the GPIB, ran the installers (restart the computer between the two installed) and then tried to run the VISA configuration utility and the GPIB configuration utility to verify that the drivers were ok (at this point, no measuring equipment is attached to the machine (ultimately, the material will be a USB-> RS232 adapter and a USB-> adapter GPIB).

  The two configuration utilities crashed running. Config GPIB obtained in what concerns to the top of its window and then crashed a few seconds later; NI-VISA never even managed to finish to display the home screen.

  In reviewing reports of incidents, accidents seem to be in the OR-PAL driver at low altitude. The report indicates that

  / Library/Frameworks/nipalu. Framework/versions/1/nipalu

  Abort() called

  Poking around the list of files mentioned in the uninstall NOR-PAL guide, it seems that the kernel extension nipalk.kekt was not actually installed correctly (it is absent of/Library/Extensions and/System/Library/Extensions, and according to the uninstall folder, it should be present in both. I tried to copy the kext above a machine that does not have a functioning VISA/GPIB install, but OSX refused to load because it has not actually been installed.

  My plan right now is follow the uninstaller for VISA, GPIB and NOR-PAL and then try to run the installers, but I fear that I will end up in the same place. Y at - it something special or something needed to get these drivers to install correctly (i.e. should things be installed in a specific order, should I try to install VISA 5.4 and then do an upgrade installation 14, try to sacrifice a goat, stuff like that)?

  The material is a Mini Mac OSX 10.9.5 running.

  Thanks for any help.

  And just to follow up with a few additional details, I went through the same procedure on a second Mac that was fresh out of the box. When running Setup for NOR-488, one of the things that we tried to install was an "Update" the subsystem NI Core Services of pilots. This was despite the fact that the VISA facility has implemented a much newer version of the kernel drivers.

  Thus, it seems that the problem is that NEITHER-488 Setup does not correct version control before overwriting the subsystem of pilots. He obviously checked that the driver has been installed, since the action has been listed as "update" instead of "install".  At least in principle, running the installer of NOR-488 first, then the VISA installer should work, but for some reason some the only time where I tried in my tests, it did not work. Maybe, I haven't had a full work of sanitation among other failed attempts. Just for the record, is the sequence that seems to work

  (0) remove all traces of any agreement, failed to install. Follow the steps described in the files uninstall.txt for NOR-488. 2, NI-VISA and NOR-PAL. The uninstall for this latter guide is located in/Library/Application Support / National Instruments/NOR-PAL

  (1) perform a standard installation of NI-VISA 14.0. Restart the computer. Check VISA works (just run the config utility)

  (2) perform a standard installation of NOR-488. 2 3.0.1. Restart the computer. The VISA and GPIB crash when access

  (Optional) curse (2A) to the length

  (3) perform a standard installation of NI-VISA 14.0. Restart the computer. The VISA and GPIB should now be functional.

  Tested on a pair of 'Late 2012' Mac mini OSX 10.9.4 running. One machine was Labview 2014 before you install the drivers for the instrumentation, the other had not installed LabVIEW.

• How to use traditional nidaq with a USB-GPIB installation

  Hello

  When I tried to install the interface GPIB-USB on my computer it tells me I must uninstall nidaq traditional, but I need nidaq traditional also.

  Is it possible to have both installed and functional? Is there a work around?

  Help, please... Thank you

  Darryl Huggins

  Thank you for your response Dennis,

  When I went back to look at the message I think he wanted me to uninstall a driver inherited NOR-488, so I advanced and uninstalled.

  But he said traditional legacy of NOR-DAQ. I was unable to see my card GPIB with Max is why I wanted to install the USB-GPIB.

  After installing now I am able to see the card GPIB and USB-GPIB interface. Must of had a bad driver, I suppose?

  So now I will run another test to make sure that NEITHER-traditional DAQ still works also. But so far so good.

  Thanks, Darryl

• How visa or GPIB

  Dear Sir / Madam,.

  I do a program of measure of stability by using Labview and GPIB-USB-HS connected to Keithley. But I have a few questions.

  (1) I can read the signal from the Keithley by using . I saw this method to an example on the site. My question is why should I write before I read? And how can I stream (using the while loop)?

  (2) I also read the signal from the Keithley by using my question; What is the best way (more accurate) read the input method or voltage signal? Why I can't just READ without writing.

  (3) I want to draw the samples I've read in a chart.  X - is the time, Y is the amplitude, but I need your advice for that? !! .

  Thanks in advance

  Ali Al-Omaishi

  PS: Both VISA and GPIB programs in the file attachment.

  Hello

  VISA is the preferred method, as with VISA, you can read and write to the instruments on all buses available on this instrument.

  e.g. GPIB and USB and series.

  You should open the connection of visa that only once in your program, make the necessary entries and read, just before the end of your program, you need to call close.

  On your question, why make an entry if you want to only read is that the instrument has no way of knowing that you want to read, and especially what you want to read.

  PS what Keithley instrument you speak? And there is not an available instrument driver at OR or Keithley?

• Version track for GPIB instruments

  I'm new to instruments GPIB, I want to know if GPIB and VISA works in Trail version or labview 2010.

  I guess you mean the trial version.

  There is no limit to a trial unless the license 30 days version and the transparent message.

  You will also need to install devicedrivers and then you can program really.

• (My Labview executable built) has encountered a problem and needs to close.

  All,

  I built a labview executable that interacts with the GPIB and the Texas Instruments EV2300 via USB.

  The VI works beautifully on the development computer and I built the VI in an executable file and it works fine on the development computer.  So, I built a Setup program that installs running Labview 2010 on the target computer.  I ran the Setup program on a computer on the production line I know can run GPIB and the EV2300, but when I try to run the executable I get an error that says: ""(votre demande) has encountered an error and needs to close.""

  I can get labview executables that do not speak of GPIB or USB to run on the target computer, then it is not the execution environment.  And I VB6 applications that can run EV2300 and GPIB interfaces smoothly.

  I don't do anything weird with the paths to files in my program, only the creation of the railways using the VI canned to convert strings into paths.  Under the program, I've read some text files and write a.

  Is there anything that I need to know how to build an application with an installer?  I need to get up and running so the test program can work on a production line.

  
  

• I have two devices gpib-usb-hs; two of them work in MAX, but will only work in labview, help please?

  Hello

  For my application, I need to communicate with two instruments by using both devices gpib-usb-hs. I use Windows XP, Labview 6.1, MAX 5.1 version and NI488.2 version 2.42. I checked and this ni488.2 driver should be compatible with my devices gpib-usb-hs and my versions of windows and labview. I also tried versions older and more recent NI488.2 without success.

  I can communicate with my instruments properly in MAX, tell me that the devices themselves are functional. When I try to connect with my instruments using labview (using the example of gpib of labview), only devices gpib-usb-hs communicates with success. The other device returns the EDVR error: connection to the device or driver error.

  I don't really know where to go from here. The only thing I found strange was that the gpib-usb-hs work was has an alias name assigned visa while the unworking device does not. I tried to give him an alias name, but this did not help.

  Any suggestions would be greatly appreciated.

  There are many free tutorials on GPIB. It should explain how the various instruments can be connected to a single controller.

  That being said, even if it's unnecessary, you should have no problem with multiple controllers on the same pc. The two being connected, they pass all the tests in MAX? You are using an old driver and seem to have tried several different versions. I suspect a driver issue, and I advise you to uninstall all the drivers GPIB and VISA and then start again. But not all necessary can be done to satisfy your curiosity.