GPIB initialization

Similar Questions

• Initialization with 34970A on GPIB problems

  I have a built in LabVIEW 7.1 that takes data from a pair of 34970A executable and 34401, using comms NOR-488.  I have no problem at all to get data. My problem - an intermittent one - occurs during the initialization of the 34970A.  The problem has persisted for a few years.  I use 3.1 NI-VISA.

  The problem is that the 34970A puts in error during initialization, with an error-113 (undefined header).  When single-browsing the Initialize.vi HP34970A I can see that the error occurs as soon as the * IDN? request is sent to the 34970A via the function Write VISA.

  I tried many things: 1. concatenated in a line of constant power to the * IDN? query.  2 tried a 34970 driver later.  3 replace the 34970 A.  4. replace the cable release between 34970 and 34401 (although, as far as I can see, it is unimportant).  The only solution I found is to reset the 34970A.  Sometimes, it works.  In the attached picture you can see where the * IDN? request is sent to the instrument.

  Johnboy:

  I think the problem is with the command sent before this one.  Maybe something flying in the transmission of the buffer that the * IDN? query command gets added, causing the equipment to get confused.  Time out NI SPY max to check what is happening.

  Bill

• Place HP 34401 in Local with GPIB-USB-HS Mode

  Hello

  I'm using LabVIEW 2010 SP1 to control the 34401 HP with the NI GPIB-USB-HS device. I use I/O built-in 34401 instrument drivers.

  If I plugged in everything, the 34401 will be immediately placed in "Remote" mode when I run my software. However, I would like to be able to use LabVIEW to force the 34401 to 'Local' mode Unfortunately I could not find a way to do this. I tried Close.vi, but has no effect.

  Here are my planned operation if it makes things clearer:

  1. Launch the software
  
  
  2. Initialize the 34401
  
  
  3. Place the 34401 in the 4W resistance measurement mode
  
  
  4. Pass the 34401 in "local" mode so that the end user can adjust a knob until the desired resistance is obtained while seeing the value of the resistance to change on the 34401
  
  
  5. Re-initialize the 34401 when I need to switch to another measure

  If not, is there a way to get the 34401 to permanently display how it is taken in remote mode?

  Best regards

  Ian Williams
  Linear Applications Engineer
  Product precision linear, and remote sensing

  The feature I mentioned does exactly the same thing except that you have to do this awkward analysis of the address. It's a VISA function you have just used the search button to find (and have lit context-sensitive help) to obtain explanations of what he does.

• Synchronization and optimization of keithley-Labview with GPIB-USB

  I started an old thread on this subject, but I have some new problems. My vi is to control a Keithley sourceMeter to read measurements every 5 ms for 6 to 10 hours, using GPIB-USB. The vi simply sends the commands under a full script to the instrument and then bed measures (voltage and current) in a loop using the visa and saves the data and displays them in a second loop using a queue. I decided to use a queue and a second loop due to the delay caused by reading data, save them in a file + display, all in a single loop! I want to be able to see all the data with real time axis, so I used a xy chart.

  Having a shorter time in the upper loop isn't a bad idea.  Using the wait until the next ms multiple rather than just the Dequeue wait time can cause the occasional time jumps.

  I have no LV open now, so I'll try to remember your VI.  I think you picked up 3 data values and a timestamp of each 5 ms.  It is 800 items every second. If you want to save all the data but only write to the file every 5 seconds, you will have to accumulate 4000 items. Because file entries are not always made exactly when you ask them because of the behaviour of the OS, you must allocate a bit more wide open spaces.  You can initialize an array 2D as 1200 X 4 (1200 lines of 4 columns) of NaN. Place this table into a shift register.  Every time you Dequeue data, replace the next line with the data.  When you write to produce, use the subset of the array to get the part that was replaced with real data and write the part in the file.  Return the initialized array of NaN in the registry to offset and continue to replace the data.

  Lynn

• Is the GPIB API allows programmers force material to use DMA?

  I'm in a situation where I have to disable DMA on maps GPIB is used with software for which I have no sources, and I'm not familiar with the API OR.   My question is, could the application was programmed specifically to require DMA, or the driver OR (if properly configured) will manage the required operations in a transparent manner for the application?

  Hi JBinTex,

  It is likely that this will be dealt with at a low level, and that the software is not affected. There is potentially a Boolean value which must be set/RESET button on the initialize function. Do you get errors when you run the code?

• Initialize the Visa Agilent No. 57

  I am trying to initialize a session on an Agilent N5764A. I get an error saying code-1074001254

  N5700 Writing instrument-> Config

  Limit.VI voltage-> N5700 is Strarted.vi->

  Initialize.VI Agilent 5700->

  Error sending command N5700:

  : 0 VOLT

  N5700 "SYSTEM: ERR?" returned:

  -410, 'INTERRUPT request '.

  The strange thing is that I have 2 of these agilents connected to a PXI via GPIB case. One of them has address 5 and 6 others (the one that gives the error). When I change the address at 5 and re - run the .vi, it initializes and works very well. I am using the tlabview initialize function, and I tried to log, clearing visa, as well as by restarting the computer and also move GPIB connections does not. Any advice would be great.

  Thank you

  I came to the realization that I tried to set up a 3rd agilent that was connected to the system, expcept it was a different model number so I was using the wrong .vi. Thanks for trying to help though.

• VISA READ timeout error - several GPIB resources

  Hello

  I'm working on a network 3 GPIB instruments (Optical Attenuator, amplifier in fiber, spectrum analyser), controlled using VISA sessions in Labview. When it is run separately, the three corresponding screws (which are located in three different Labview projects) works as expected. However, when they ran at the same time, one gives them timeout-1073807339 VISA READ errors. These errors seem to occur when another instrument is sending / receiving data / instructions at the same time that she is.

  The exact context of the error is either:

  -an another VI is running, which includes sending several requests and responses every 100 ms, reading

  -by failing VI starts, I get an error of waiting time among the first Subvi containing a VISA READ operation to perform (sometimes initialize.vi (in situation 1), sometimes one of the subVIs connected the rest State (State 0) on the time-out of the structure of the event).

  or:

  -the default VI is running,

  -by starting another VI, which includes repeatedly sending requests and reading the responses, the failing VI up a mistake among the first Subvi containing a VISA READ operation to run (one of the subVIs linked the State of rest (0) on the time-out of the structure of the event).

  What I tried:

  -gradually increasing the delay between the VISA WRITE and READ operations to the relevant instrument (from 10 ms to 10 s), without success. More surprising are my observations which, by operating this single VI, increasing WRITE it / READ delay results in the same timeout errors. I have found no mention of such behavior through research google and forum. I hope that this may point to a solution to the main issue,

  -switching between synchronous and asynchronous VISA WRITE / READ operations.

  -reorganization of the network GPIB to a star to a linear topology topology (three instruments have different GPIB addresses in case anyone is wondering).

  My thoughts:

  It seems to me that the error is related to a delay introduced between a VISA request and its read operation by the transmission of another query associated another instrument in the same network GPIB. But I have no idea why pass a query to another instrument would introduce such a delay, or why this delay would result in a timeout error (and only an instrument, while writing / reading in each pilot screws are basically the same). Hopefully a more experienced Labview-er will be able to shed some light on my problem.

  Included is the project that contains the default VI (main.vi) and the driver custom made use of.

  There are a number of ways. If you want to keep separate projects for instruments, you can use semaphores often slandered around calls for screws in each project. Locking is not expected or predictable, but it would give controlled access to the GPIB resource.

• GPIB-USB-HS + on CentOS 7?

  Hello

  I don't know if this question is appropreate for this forum, if not, please excuse me.

  I had trouble installing the driver for the GPIB-USB-HS +. I could not see error during installation, but when I try to launch gpibexplorer, the window appears and disappears immediately with the following message:

  libnipalu.so, failed to initialize
  Maybe you need to run updateNIDrivers

  So, I did once again updateNIDrivers without any error. After the restart, he always says the same thing.

  I did it on CentOS 7 (3.10.0 - 229.14.1.el7.x86_64, 64-bit version, apparently). Does anyone have an idea?

  Hello

  According to Jason Smith in a similar discussion on the GPIB-USB on RHE 7 support:

  http://forums.NI.com/T5/instrument-control-GPIB-serial/USB-GPIB-HS-support-under-Red-Hat-7/TD-p/3235...

  The list on the web page is wrong and that you make reference to the list of hardware supported in the Readme.txt:

  http://download.NI.com/support/softlib//GPIB/Linux/15.1/Readme.txt

  We are still working to get the correctly implemented web page up-to-date. Sorry for any confusion this has caused!

  gpibtester

• GPIB error message (VISA?) when you access a power meter HP E4419B (double channel)

  Hello

  I used a GPIB-USB-B adapter to access the E4419B meter, via a Calibration of IFR application software. The required initial standard test equipment is an E4418B. During the initialization process, there is always a message:

  "Initialization error: initialization of the HP4418 Power meter, error error: interface type is valid, but the number of specified interface is not configured."

  He was waiting for me that software has always controlled the unit later in some way (i.e., cal sensor, etc.). But that would creat some other comm failure in the race.

  I would like to know, if E4418B and E4419B are compatible with each other insofar as NEITHER Visa is concerned, and it is ' has some sort of screening OR the part number? The software itself is not all flexbility to do.

  Thanks in advance.

  Simon

  Simon,

  For the 19 do not work which suggests that there are no channel selection. Looking at the programming specification for E4418/E4419 (Yes, it the same specification) suggest the same programming codes the only difference is that the E4419 has two channels.

  The other would probably be during initialization and query software maybe be looking for E4418 instead of E441x and ignoring the last character.

• Watlow F4 HS USB GPIB communication problem

  Hello

  I'm trying to communicate with the Watlow F4 controller on a room of environmental Tenney. The only available is a GPIB port. I've successfully installed the GPIB-USB-HS cable and I can see this device under devices and interfaces MAX. However, no instrument find when scanning for default settings of the interface GPIB instruments. I also downloaded the Watlow F4 VI drivers and try to run away. I got a 1073807346 error occurred at VISA opened in Watlow F4.lvlib:Initialize.vi-> up.vi set Watlow F4 system

  I use Labview 8.5.1 with 488.2, VISA, DAQmx installed.

  Please see the pictures attached for more details. Any suggestions would be greatly appreciated.

  Concerning

  FliU

  Try the VI is useless if the instrument is not detected by MAX. I suggest that refer you to the manual or the seller to see if there is something you need to do on the instrument for GPIB communication.

• A single / Multi channel divergence in VI for unit piloted by GPIB

  Hi all

  I'm hoping to get help with a VI that I edit. VI control an Agilent 34970 A via a NI GPIB-ENET 100/1000. I have downloaded the driver for this instrument and had it works such that I can select a channel (or more channels) and monitor the voltages when I run.

  The problem I have is that the current set up requires channels to initialize every time that a reading is taken. This happens in the first two subVIs of the structure of matter in the attached screenshot. This is unacceptable because the VI is intended to control more than 200 channels very high frequency and I don't want a mechanical switch to return on and outside every time a reading is taken.

  Initially, this VI had not the case around the subVIs structure first two and switching has been constant whenever a reading was taken. The change has been added with the consideration that the channels would be be initialized in the iteration 0E while all subsequent iterations (1 or by default in the structure of the case) would have a direct link in avoiding initialization.

  The unfortunate problem is that this fix works only for a single channel. When only one channel is selected, the switch is heard once at the beginning and is silent for all of the following readings. When many channels are selected, however, the instrument goes back to the State of the structure of the case and the switch is heard whenever a reading is taken. I tried everything I could think of, but I can't understand why to choose several channels does much less to solve the problem.

  Any help is greatly apreciated.

  Thank you

  Yusif Nurizade

  You are far away from the base. As I said, every time that you run an analysis, each relay will open and close. You seem to be under a serious misunderstanding of the material. Look at the included diagrams in the manual. There is a mux to multiple relay linking multiple points to a single DMM. One point at a time may be connected to the DMM. Under your belief, keeping all the relays closed after the initial scan would have all of your short connections together.  With a single point, of course there no need to open and close several relays.

• 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.

• A GPIB device playback

  I tried to make a driver for the 181 keithley but got frustrated way, then I'm gone with the method of MacGyver thinking this would be much simpler, but I still have problems.

  My 'GPIB write' function works like a charm, the GPIB address is 5, and to interpret the great big chain (in case you are interested) here's what mean all the letters/numbers.

  X initializes communication

  T0 - affects continues in talk mode

  M0 - defines SRQ OFF

  R2 - affects my range to 20mV

  B1-tours on the Hi Res mode

  P1 - sets the filter off

  D0 - disables the depreciation

  The problem is that something goes wrong with reading GPIB or Fract/Exp chain to the number, and I can't get out the measure.

  5 is the GPIB address again (and is correct, because the upper part works very well)

  The value 0 is the mode which is the default

  and 14 is the number of bytes to read.

  My guess is either "14" needs to be a different number (did this question?  If I said to read more bytes, then the resulting string is in fact, not only will extra zeros?)

  I use a function badly, either read GPIB or Fract/exp chain number necessarily be replaced by another function GPIB.

  
  

• Could not receive data from GPIB system controller (PCI card of NI - 488-2)

  Hello

  We create a daughter card that will allow our product shipped to communicate via GPIB. This girl GPIB card must be able to receive the SCPI message send by system GPIB controller and reply to the message. In my current configuration, system controller is a card PCI of NOR-488. 2 installed on a PC running Windows XP.

  On the side of card GPIB girl, we have NAT7210 with 75160 and 75161 transceiver chips. NAT7210 is connected to the interface of static memory controller (SMC) an Atmel ARM9 embedded Linux OS running. We use the Linux GPIB library on sourceforge - http://linux-gpib.sourceforge.net/ .

  For now, chip NAT7210 initialization stage seems to be successful. Using Measurement & Automation Explorer software that comes with the NI GPIB PCI card, it is able to detect the daughter GPIB card; the cushion and the sad values are correct. However, chip NAT7210 has failed to receive the * IDN system controller message.

  Here's what I did to initialize the NAT7210:

  (1) set 0 x 99 in SPMR register. To make sure that we are 7210.

  (2) in AUXMR the value 0 x 02 (chip reset at the controls). To affirm the message local pon.

  (3) skip the step that defines the ICR and registered ICR2 because we use the default clock 8 Mhz.

  (4) the value 0 x 31 (addressing Dual mode) in the register of the ADMR.

  (4) together in ADR 0x01 to register.

  (5) contained SPMR 0x40. Initial response of series. I don't know what are reasonable values to settle here.

  (6) together to register 0x07 in hidden PPR. Do not participate in the parallel polls.

  (7) set TASKS and NTNL bits in the AUXRG register.

  (8) the value 0 x 51 (hldi to the order) in the AUXMR register.

  (9) to activate the interruptions; IMR0 = 0xC5, IMR1 = 0xBF and IMR2 = 0x4F (no plans for DMA transfers).

  (10) the value 0 (command pon) in the AUXMR register. Final step.

  The NAT7210 Linux configuration file content:

  minor = 0

  board_type = "gpib".

  name = "gpib0.

  PAD = 1

  sad = 96

  Timeout = T3s

  EOS = 0x0a

  together-reos = yes

  all-bin = no

  together-xeos = no

  together-eot = yes

  base = 0 x 70000000

  IRQ = 45

  DMA = 0

  master = no

  Any ideas on what could be the reasons NAT7210 has failed to receive the * IDN system controller message?

  Steve, thanks for your comments.

  It turns out that the deactivation of functions that print messages in the debug library has solved the problem of reception.

• 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.