Similar Questions

• Problems syncing with GPIB Read on a SR400

  I'm using LabView to control a meter of photons SR400 of Stanford research systems. Can control the box easily, I'm having problems with reading the correct data in the box of. I get incorrect values of 0 ', 6 and 134' rather than real account numbers. I see the correct values on the display screen, but GPIB reads bad.

  It's what I've tried and what I've learned:

  • At first, I was getting random 6 error LabVIEW (from reading GPIB) which would prevent my program to run. To resolve this problem, I put a case Error statement after she and simply write the word ERR in my data file and move on to my next point data. This stopped my cessation program, but started badly reading the values using reading GPIB.
  
  
  • The SR400 takes data for N periods on two channels, A & B. The first column of the channel A every 6 seconds and the rest of the columns on both channels would be regular values. However, the problem got worse and my first column of the channel began to write 0s, the second column of the channel A would be 6 s with some 134 s and the rest of the columns would be nice. But, if I had only 1 time for each column, I now have data lost on two channels A and B. A channel would be of 0 s and channel B 6s and 134 s.
  
  
  • This problem is sporadic. I can't control when it arrives. Today he works. Yesterday's didn't.
  
  
  • It seems to be a timing issue, but I don't know what I can do about it.

  My questions for you are:

  1. Is it better to use GPIB or VISA to communicate? I use GPIB cabling, so be it.
  
  
  2. How can you correct problems of timing in GPIB?
  
  
  3. Any suggestions on how to improve this?

  I joined code of 8.2 and 2011. I'm trying to convert our code in 2011 to see if it solves the problems. The VI with GPIB Read is CollectData/TakeData and it is called by a VI, where he gets called frequently, but the reading and writing of all MTP recharge time is done by data files CollectData/Take.

  Thank you all in advance for your help. I'm a grad student and still learn from these electronic and LabVIEW.

  Start by lowering of the busspeed. I think that 1 uS is more fast enough for the handshake and then I would disable autopolling.
  You can do it in Max settings for your gpib card.
  Low level visa uses gpib, but never use it directly. In any case the speed is completely determined by the slowest device on the bus, complaining the sr400

• Problem with 2 GPIB instruments

  Hello everyone,

  I work in a program with LabView 2015 this control 2 instruments, the Rohde & Schwarz Smiq02b signal generator and Analyzer of spectrum n9010a Agilent EXA. I use the cable Agilent - 82357 B USB/GPIB to connect my laptop with these two instruments (PC-> EXA-> Doganovic). I also installed the two drivers of instruments from their official websites.

  The program worked correctly until I had to format my computer and reinstall LabView but something wrong now.

  The problem comes when I run the program, is unable to initialize the SMIQ02b, the program stops and opens a new window of block diagram. This block diagram belongs to a block driver the instruments within this scheme, there is a VISA write flashing block.

  

  This only happens when I'm initializing two instruments in the same program, if I create a new VI and use the Doganovic only, I have no problem.

  I don't know what is happening, it is very strange that it worked well before, and now this happens.

  That's what I installed in my laptop:

  -2015 LabView
  -NI Device Drivers (included NI-VISA 14.0 and NOR-488. 2 14.0)

  -Agilent IO libraries Suite (configured as secondary VISA) 17.1

  -Passport OR VISA for tulip IT

  I'll be very grateful if someone could help me with this.

  Thank you!

  You set a breakpoint, it's what's causing the break.

• problem with Agilent GPIB 8510C Network Analyzer

  Hello

  I downloaded the Plug and Play (project-style) driver for Agilent 8510C Network Analyzer. The basket has address suite:

  Address of HP - IB 8510: 16

  The system bus address: 21

  HP - IB source address: 19

  Criterion address HP - IB: 20

  Plotter HP - IB address: 5

  Printer HP - IB address: 1

  The basket includes 8510A processor, source RF, series of tests and tracer. There is a GPIB port on the plotter that connects 3 8510A processor, RF source GPIB port, and the value of Test. I connect the GPIB PC port to the GPIB port. The grid gives me an error: "ADDRESS ERROR: SYSTEM BUS ATTENTION."

  My driver for LabView Plug and Play (project-style) cannot detect any address on the bus.

  I tried IO libraries Suite Agilent, but he could not detect them.

  Is there a problem in the connection ports 3-module GPIB interface in the basket or am I missing something? I'd appreciate any help.

  Thank you

  Nabil Gharib

  yasmain62 wrote:

  Hello

  I downloaded the Plug and Play (project-style) driver for Agilent 8510C Network Analyzer. The basket has address suite:

  Address of HP - IB 8510: 16

  The system bus address: 21

  HP - IB source address: 19

  Criterion address HP - IB: 20

  Plotter HP - IB address: 5

  Printer HP - IB address: 1

  The basket includes 8510A processor, source RF, series of tests and tracer. There is a GPIB port on the plotter that connects 3 8510A processor, RF source GPIB port, and the value of Test. I connect the GPIB PC port to the GPIB port. The grid gives me an error: "ADDRESS ERROR: SYSTEM BUS ATTENTION."

  My driver for LabView Plug and Play (project-style) cannot detect any address on the bus.

  I tried IO libraries Suite Agilent, but he could not detect them.

  Is there a problem in the connection ports 3-module GPIB interface in the basket or am I missing something? I'd appreciate any help.

  Thank you

  Nabil Gharib

  You really should read the 8510 manuals C.

  Page 4-10 of the 8510C on-site repair, it indicates

  For systems equipped with controllers, connect all devices and
  the controller on the GPIB connector the 85101.

  The 8510C of operation and programming manual includes steps for checking the system setup.

• How can I configure the GPIB Tektronix tds2024 he is detected by MAX

  I try to connect the Oscilloscope Tektronix of TDS2024 to use in LabView. I use the GPIB port. I have to do something with the TDS2024? Or it should automatically detect it. I tried 2 different cables and are detected by the LabView "Measure & Automation Explorer" when connected.

  Hello

  All you have to do is plug your instrument, MAX throw if you have not already done so and scan for instruments.

  You should see the instrument listed under the GPIB device.

  Hope this helps

  Concerning

  Ray Farmer

• Problem with PCI-GPIB card control Agilent 8648 D generator interface

  Hello

  I downloaded the driver Plug-and-Play (project-style) for Agilent 8648 A generator of signals. I use LabVIEW 2011.

  I open the file project and resource VISA name menu, select COM1. Note that I use 82350B of the PCI-GPIB Interface Card.

  I run the project, and I get timeout error.

  Is there a problem in the PCI-GPIB interface or am I missing something? I'm new to LabView and PCI-GPIB interface, and I'd appreciate any help.

  Thank you

  Nabil Gharib

  Given that you do not use a NI GPIB, go to MAX, select software and NI-VISA. In the right window, click the Options of VISA, and then select passports under general settings. Check on the passport of NI-VISA for Tulip.

  I'm assumimg you loaded the driver of Agilent and tested the communication with their software.

• Problem of earthing GPIB-USB-HS connecting to a laptop?

  Hello

  The installation guide for the GPIB-USB-HS asks to "ensure that the computer and the GPIB devices are at the same potential on the ground."  I was wondering if there could be problems with the connection of portable computers (because they float)?

  What should / could happen if the computer was at a different potential on the ground?  A short circuit?

  Where the potential of the Earth is different, the installation guide also mentions to use isolated a GPIB bus isolator/Expander or a USB hub.  I guess that laptop USB ports are "isolated" and so should be good.  Is this true?

  Thank you!

  Meister,

  Because your laptop is "floating" it's referance (mass to the chassis) has nothing to do with your referance of material (Earth) unless you take measures to link the laptop chassis to earth potential.  Attach a GPIB cable to your laptop and your equipment will provide a way to fulfil the potential difference between your laptop and chassis of the Earth through the GND signal on the Gbspecifications FOR bus.  The GPIB bus is not intended to carry large currents (great potential of discharge) and you can force entry on the laptop protection circuits or equipment when you connect the GPIB cable.  Its kind of like touching a doorknob one day dry after you walk on the carpet of wool - you will get a 'static' shock when make you initial contact.  Do it at your equipment and laptop often enough and you will damage them.

  A worst case is when the chassis of the laptop is linked to a different potential that the grounded equipment (usually due to strengthening of wiring errors).  In this case there must be a current constant circulating in the commonly known GBIP GND signal ground loop.  Noise and / or damage will be celebrated according to potintial unlike.

  The cure is ALWAYS connect the chassis of the laptop on the chassis of the equipment by an external wire before connecting the GPIB Bus.

  I hope that clarifies the reasoning of 'Warning' that you see in the installation guide.  Kudos to you for reading your guide and to pay attention to the warnings!  Never be afraid to ask when you don't understand warnings

• Connection problem-NOR-488 GPIB: connection to the driver or device error

  Hello

  I am trying to connect with my tunable laser "Santec" by GPIB-USB-HS. I received the file VI Labview (instrument driver) for my model of tunable laser STL-210 http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=2791 . When I run any VI, for example the "laser_on_off.vi" file I received the error message "NOR-488: connection to the driver or a device error. I checked the 'measurement and automation explorer' and Communicator of NOR-488. 2 gives me the following message appears when I send "interrogate" send string * IDN?

  ----------------

  It is meaningless.

  You have to step way back. The Setup instructions for the GPIB-USB-HS shows you first run diagnostics. Finally, you have done this and got a failure. That's why you get "NOR-488: connection to the driver or a device error. Until the diagnostics pass, you lose everything just your time with anything else. Please provide details on the failure when you run the diagnostic tests.

• With the help of the command on paper by emission of GPIB Tektronix TDS540

  
  

  Search the fboard for "screenshot". There were many posts and include some of the code. A recent is present. Model different but similar orders.

• GPIB-USB-HS will recognize any instrument in LabVIEW but somewhat done in MAX - help

  Hello

  I'm having a problem getting my GPIB-USB-HS device to recognize instruments in LabVIEW.  The unit has been running year last on many instruments.  I tried the GPIB-USB-HS other materials too just to make sure it wasn't a defective unit.

  NOTE: I installed the latest drivers for NI-VISA 5.1.1 and 300 of NOR-488. 2 for Windows XP

  See the images below:

  It's the idsplay to the MAX:
  I'm not sure why there is a yellow "!" next to GPIB0::INTFC, I think it's an indication of my question.  However, note that the instruments connected to my GPIB-USB-HS are counted in MAX.  As you'll see LabVIEW 8.5 does not recognize them.

  

  I get this error Max warning when I try to open TOOLS > NI-VISA > VISA INTERACTIVE CONTROL:

  

  It comes to the image of my LabVIEW 8.5 window when I try to select a VISA of an instrument (including MAX recognizes):

  

  Any help would be much appreciated

  Thank you

  -Brian

  Thank you all for your help,

  Problem solved after hours of uninstallation and reinstallation of all devices/software from National Instruments.

  Once all programs have been uninstalled (with a disk cleanup on my unnecessary hard-maybe records)

  LabVIEW 8.5.1 has been reinstalled

  NOR-DAQ has been reinstalled

  NI-Visa 5.1.1 has been reinstalled

  NOR-488. 2 worm 2.7.3 has been re-installed (correctly)

  Now, LabVIEW recognizes all ports/devices and connects to the instruments properly once more.

  My question must have been installing LabVIEW 8.5.1 after already installing LabVIEW 2009.

  Somewhere during the installation of 8.5.1 - main post problem occurred.

  Thanks again

• Write error in scan-1073807339 voltage Keithley 2400 to VISA, GPIB

  I'm working on a VI that sweeps the voltage across multiple PV devices, all in two States (light and dark). I use the SCPI and a GPIB commands to send scan to the Keithely and store it in a memory slot. So I ask this field using a sub - VI for each device in the two States.  The first State (light) still works fine.  VISA writing successfully sends the script to the Keithly and VISA read records of information successfully. But when the VI tries to run the same Subvi in the 2nd State (dark), I get the error of delay of 1073807339 waiting.

  Ways, I tried to solve this problem:

  -adjustment of the byte for VISA read rate (at one point given, I was getting the error on VISA read, not write)

  -adjust the setting of time-out of VISA by the suggestion of Web site of nor

  -loading of the script on the keithley each time for each scan

  In addition,

  I collect 100 points of data with each scan-05V to 2V.

  Whenever I get this error in order to get anything to connect once again, I have to close out of labview and could power off, power and reconnect the keithly

  Help, please. This could be a problem with my GPIB device? or my Keithley 2400?

  Thank you

  I tried all the solutions, but none of them helped. However, I have finally solved the problem on my own. The issue was that the VISA session was not properly closed / emptied after each scan.  To resolve this issue, I added VISA close at the end of each scan and clear VISA before each scan.

• NEITHER route can be started with the minimized window?

  We have a problem, while the GPIB instruments will not work unless NO-Trace is running.   So we have NO-Trace in our marketing so that it works when we start our test station.  But this great Trace window is disruptive to users, until they minimize the window.  Is it possible to have start OR route running, but also start with minimized window?  (Yes I know there is the box to get the Trace from OR Trace execution, but we would like that the window is running in the background - (reduced) to allow our Test window to not be in conflict with the Trace window).

  Well, it changes things because this is very probably an executable VEE? problem. Just spitballing here, but I'm guessing it's a thing of Agilent VISA OR VISA vs. As I've never used vee, I'm guessing they're using Agilent IO libraries. It looks like you can access the VISA Agilent as secondary depending on p35 here and here.

  As I said this is just a guess since I'm not familiar with VEE. I would like to confirm on the Keysight forums.

• latest version of the driver for keithley 2400 sourcemeter instument

  Hi all

  I'm unable to connect with sourcemeter Keithley 2400 with GPIB / Rs232. (currently using the driver from keithley Web site)

  I did a search preliminary Forum and learned that there is some bugs in drivers.

  Then comes the last avilable pilot site OR the corrected version?

  http://sine.NI.com/apps/UTF8/niid_web_display.download_page?p_id_guid=25B255F3AA83660EE0440003BA7CCD...

  The one above IS suitable for the two abd GPIB, RS232.

  concerning

  Lorris Somasundaram

  I think there has been a problem in the GPIB bus address. I used MAX and tried triubleshooting and reattach the GPIB and finally the connected got intrument, sorry for the inconvenience.

  The driver loaded since NEITHER website works very well.

  Thank you and sorry for the inconvenience

• NOR tkds5000 LabWindows/CVI IVI driver not work for TDS5104, TDS5054B

  I'm trying to get the driver NI LabWindows/CVI IVI (tkds5000 version 1,212) working for the Tektronix TDS5054B scope.  When I execute the following functions, I have the warning 'Is not a valid value for the parameter or property' of 0xBFFA0010:

  IviScope_InitiateAcquisition

  IviScope_GetAttributeViInt32 for IVISCOPE_ATTR_TRIGGER_SCOPE and IVISCOPE_ATTR_ACQ_TYPE

  IviScope_ActualRecordLength

  This is not an exhaustive list of the functions that do not work, but just that I currently see.  There are several functions that work (see this joint SPY OR file).

  The strange thing is that everything works fine when I have an oscilloscope Tektronix TDS5104 connected (file SPY OR see attachment).  The code also works when I have an oscilloscope connected and selected through MAX TDS3054 driver tkds30xx IVI of NOR.

  Is it possible that the driver of version 1,212 tkds5000 does not support fully the TDS5054B?  I looked through the files tkds5000.c and tkds5000.h, but has not seen any dependencies on the model of the oscilloscope for these functions.  Any ideas?

  Thank you!

  Dave

  So, then I thought about it.  The tkds5000 driver AND works very well.  The problem is that the Tektronix TDS5054B scope do not "initialize" some of the attributes.  For example, I had a problem reading the value of the attribute of slope of relaxation because an invalid value was returned.  If I set the slope of the trigger, first of all, then read it, it works fine.

  Its strange because most of the attributes is set to the correct value corresponding to what is displayed on the oscilloscope screen and the Panel, but not ALL of them.  In addition, other Tektronix oscilloscopes did not require a writing before reading.

  Anyway, thanks a lot NathanT.  I appreciate your help.  You saved me a bunch of time to have to go back and add in a dedicated driver.

  -Dave

• Problem! Garland of two Tektronix scopes

  Hello world

  I'm having problems trying to string together two oscilloscopes from Tektronix TDS 210 identical GPIB port on a single computer. If only one scope is enabled, LabView can recognize, however when the two are put on rather than recognize them as two separate instruments, it seems to get confused and claims it is only an instrument that does not work.

  I managed to exclude certain fundamental issues, for example the GPIB leads the two oscilloscopes are known to work properly and a Garland of oscilloscopes and a different instrument of GPIB works very well. I also tried two possible configurations of the chain, that is to say; the two scopes directly into the computer or a single scope in the computer, then a GPIB drive between the staves.

  I have attached a few screenshots of errors that may be useful

  Any help is very appreciated!

  Thank you

  It would be explained in the manual. With some instruments, you put the dipswitches on the back. With others, it is made of one of the instrument on the menu screen.