GPIB controller "sre 0.

Similar Questions

• Can you change the type of device to 'USB Raw resource' to GPIB controller?

  I'm trying to configure a GPIB FL Contec GP - IB (USB) controller in MAX.  I could so he can register through the creation of a pilot of the Assistant driver VISA, but it fits as a "gross resource USB" rather than as a GPIB controller.  I can send and receive information from the controller, but it does give me an option to search for connected devices of GPIB communicate with them.  Is it possible to change the type of the device, maybe by manually changing the driver created by the wizard of the NI-VISA driver?  Thank you for your time.

  N ° do not use MAX at all. You can just create a GPIB-USB controller on your own. You should contact the seller.

• For the USB Hi-Speed and Licensing policy GPIB controller

  Hello

  I wanted to confirm understanding licensing NI VISA.

  If I use the GPIB controller OR to the USB Hi-Speed, is NEITHER VISA license are included?  488.2 NOR pilot is that CD is included along so I guess its license.

  In accordance with the licensing policy as long as you are using hardware NOR the license included.

  Here is the sentence that does this is clear.

  "Are examples of products that include the driver NI-VISA LabVIEW, CVI, TestStand, NOR-488. 2, GPIB controllers, PXI controllers, etc. If you do not use a software or hardware, you can buy NI-VISA development software separately. »

  If my understanding is 488.2 and NI-VISA OR license is included if you use the NI GPIB for Hi Speed USB controller.

  Thank you

  ANI

  It's true and you can deploy a runtime of NI-VISA smaller with your executable file.

• LAN at impact software GPIB controller

  I wrote a Labview program on a PC with a GPIB controller to copy card to control an electronic load GPIB using NI VISA and provided seller Labview VIs that use NI-VISA.  I now have to implement the same program on a laptop using a LAN to the GPIB converter or him to talk about the electronic load.

  What is the difference in how this LAN to the GPIB device gets programmed verses a gpib controller direct for the same instrument?  Is the code I wrote already not usable?  What should I write orders direct TCP/IP now out of my Labview program?

  You replace the resource only if you change the instrument gpib address or number of the controller. If you use aliases, you wouldn't change all your code.

• How old, a driver can be used with the USB-GPIB controller?

  Hello, I have a litter of Nicolet who I'm trying to control using an NI USB-GPIB controller and a Nicolet provided the program. The software were made in 1995 and told me it was made to work with the NI AT-gpib cards and I would need to use a pilot more OLD, BUT I don't have access to one of these cards for a purchased a USB-GPIB, hoping that it would work. A pilot more FORMER will support the GPIB-USB?

  Sorry for you, but not

  This is a really old software and works only on the driver to the gpib.

  Written in LabVIEW software would go from before this date.

• If I use my like my DAQ GPIB controller to control my instruments?

  Hi, I am a beginner in BT and need your help for dead on my undrestanding clarification:

  Suppose I want to control 7 instruments (such as temperature sensor, osciloscope,...), instruments using my GPIB controller, in other words, my pieces as my DAQ GPIB (am I right this step?) doesn't not need to communicate between them, but whenever I read the temperature value, I'm doing some calculations in my code LV and then decide what changes apply to instruments for example reduction of the frequency of the signal generator , pls I would like to know if I have done my DAQ correctly? (I mean if the GPIB controller acts as my DAQ) then comment how to decide what kind of GPIB is suitable for my work

  I really need your help,

  Thank you

  elahetal,

  If you have all the tools you need, you now have the following equipment (to summarize)

  (1) to a computer.  It must be decently fast, especially if you order 5 + machines, but it should not be surprising.

  (2) a GPIB card that works with your computer (PCI slot or PCIe, etc.).  I HIGHLY recommend a NI GPIB card, especially if you use it to write a labview program.  3 party cards can complicate your life village.

  (3) GPIB cables to each machine (if you have 2 computers, there are 2 cables).  If a machine is not a GPIB connector, it can not be controlled of GPIB.  There may be a RS-232 or USB drive.  These connections need not a GPIB cable, they need their respective cables.  Some machines also cannot be digitally controlled.  A DMM from the 1960s is probably not the connectors or the internal hardware to be part of your installation.  Make sure that each piece of equipment can be controlled by the computer

  Things I would do to get started on your code LV.

  (1) download the drivers for each instrument.  The drivers are code LV, when it is executed, allowing you to communicate with your instrument.  Some drivers are pre-assembled with interfaces that resemble your machine controls, others come with orders but no interface.  The quality of each driver can vary.  If there is no such thing as no driver, reading extensively the manual of the instrument and the protocols of the connection you are using (GPIB, USB, etc.).

  (2) get each work unit separately.  If you can get each device to be controlled entirely by computer, you are 80% of the way.  This can take a long time.  I know that I took several weeks to get each device works correctly.  Once, you have separate codes and know that each device can be controlled by the computer (or only dump information), then you are ready to code.

  (3) build the master code by bringing together the different parts.  If you think of him as Fortran or C programming, it becomes very easy.

  Regarding semantics, data acquisition is the whole plant; instruments + computer + GPIB.  Your computer is the controller and the bus is the GPIB cables where are transmitted data, commands and responses.  Read up on it.

• Using Agilent USB-> GPIB controller possible

  Hello

  When I have an Agilent USB-> GPIB controller so normally, I have to install the Agilent IO libraries for the windows driver.

  What should I do when I want to use the USB-> GPIB controller in Labview? There, I have NEITHER - MAX-> is the driver included in MAX or what I have to install both programs?

  thx for the help

  No, when you use a controller of NOR, you must NEITHER-488. 2. remember, the VISA is just one api that is above the actual hardware drivers. There is a specific hardware for the controller of Agilent driver and a driver of specific material for a controller OR.

  Where the driver is depends on your version of LabVIEW. On my 8.6 distribution, there is a separate DVD called NI Device Driver DVD.

• Using NI USB-GPIB controller Zeiss C90 CMM control

  I have a Zeiss PCDMIS CMM running 32-bit on Windows XP with PCI GPIB (488.2 2.7.3)

  If the controller is 8 bits, but work with my 32-bit system already, can I export the config VISA file, change on a 64-bit of Windows 7 with a USB to GPIB computer, and import this file into a newer version of the driver 488.2?  (change of bits or a more recent version of 488.2 will be a problem?)

  Hi Ryan,

  As long as you save this export config file, you should be able to load it into the second computer MAX.  I can't find anything that says that there will be problems with the little change.  If you are really worried about it however, give it a try without getting rid of your original computer.

  It seems that you already know how to transfer the settings above, but here's a KB on how to do this http://digital.ni.com/public.nsf/allkb/BF528312C9A5423A862565BC00731EC0.

• OR MAX see GPIB controller/board of Directors, but crashes on test/Scan troubleshooting

  Hello

  I have a new PC (Win7 64 bit) with a new GPIB PCI - E card and NI-VISA 14.0 (later). I can't get the map to 'do' something - he's not troubleshooting auto test, or search for instruments, and the ibfind in an interactive control command does nothing (they are all "don't hang up" no error reported). What is happening with two identical machines, each with the PCI-E card. My 6 monts test machine there is works very well, but it is 32 bit and has a different chipset/firmware of the provider (which was not planned, we ordered the same model, but the seller seems to think that it's little, they kept the model the same number).

  Any ideas on what to do? I demoted NI-VISA a couple of times already, and Windows reports gladly driver card / work properly. GPIB options all seem normal in case of default (GPIB0, controller of system activated, etc.).

  Thank you very much for your suggestions!

  -Rick

  Hi rnelsonee,

  Make sure you also have the NOR-488 driver. 2-day so you can communicate with GPIB devices correctly. You can follow this link to download.

  http://www.NI.com/download/NI-488.2-14.0/4802/en/

  If you still have questions, could you let me know what kind of errors you get when you fail the self-test NI Max? All codes error or screenshots you can provide will be useful. Thank you.

  Paul C

• Can I use the VXIpc-872 as GPIB controller for the slave VXI mainframe?

  Is this possible? Which means that if I can control a chassis VXI from a PC through the VXIpc-872?

  If this is possible, what should I do to put in place?

  Hello

  So as I understand it, you want to control your VXI PC chassis, connecting via the VXIpc card? What operating system is your VXIpc-872 race? You can probably use remote desktop to connect to your VXIpc from your PC. You can take a look at these articles:

  http://zone.NI.com/DevZone/CDA/tut/p/ID/4731

  http://digital.NI.com/public.nsf/allkb/C074C33F4DE3FA5186256D3D007788DA

• NOR-488 command requires GPIB controller charge controller

  I need your help, if you please! I added a few cases to a case structure and my program works very well. When I want to rebuild or build an exe again, I got error message attached. The solutions mentioned in this area and other platforms did not help. I don't know what to change because the program works very well, but I can't build

  Thanks to the support OR! There was a folder that had references which are no longer available on the hard disk. I've updated this file and reconstruction didn't work

• The code runs fine for 1 time. NOR-DAQ: command requires controller gpib controller

  Hi all

  My labview code is attached. He controls a powersupply lakeshore, keithley and sourcemeter multi-meter and a GM08 Gaussmeter.
  The code works perfectly on the 1st round.
  However, on the 2nd round, the initialization for the sourcemeter (KE2400) returns an error.
  The code works well again after cessation of the VI and it works again.

  I have no idea why this is happening, any advice would be helpful thank you! (as with all tips to make my code better in general)

  My big loop is of my readings on average.

  If the error occurs at initialization, then the question is not the shift registers. All of your entries to the initialization did not all local variables or something weird, so it has nothing to do with the values changing with each race. That leaves the issue lying with the instrument itself, or communication with the instrument.

  When you first run the application is complete, there are errors? Run VI close very well to close the connection?

  I suggest you do a little test VI passing right through the screw, using the Sourcemeter to see if you can dial in on the problem. If you test VI initializes and works fine again and again, then it might be a problem with your errors or manipulation of communication management.

• Command requires controller GPIB be supported on dequeue item

  I have some funky stuff pass in the attached VI. What is the VI is simply to save data to a text file. It is built as a state machine. State of creation of this VI is called from a mainVI (with the help of named queues). I have more than one error and it seems completely random. Usually, the error occurs if I stop the mainVI, then it starts again. The second (or following) times the VI RFP is called, I get random errors like the two below:

  Error 1 has occurred by the Dequeue item in DP.vi-> PSS.vi
  Possible reasons:
  LabVIEW: An input parameter is not valid.
  ---
  NOR-488: Command requires controller GPIB be in Charge.

  Error 1 occurred near file in DP.vi-> PSS.vi
  Possible reasons:
  LabVIEW: An input parameter is not valid.
  ---
  NOR-488: Command requires controller GPIB be in Charge.

  Why is this? I don't even have a GPIB controller?

  Are your uninitialized purposely shift registers?

  If you have an error in the dequeue item, shift registers will be filled with the error of the DQ and ref file empty.  on the next call to this VI, if there is an error in the CV, it will lift the ref of invalid file on the dialog close error. If it does not exist, the former error will spread and you get the dialog box for it.

  and I bet your DQ is to launch an error because your enum in the queue of DP QSM is a non-stricte typedef and you changed somewhere.  make strict!

  According to me, there's only something mixed with your selector error case and the case of your state machine error.

• Rearmament and automatic test of a controller (not the instruments attached to it!) GPIB card

  We have a Council NI GPIB in an operation of great trial.  Because reliability is absolutely crucial, I want to be able to force a reset of the GPIB controller card, but also run a set of diagnostic self-test on the Board of Directors.  Note!  I does not reset the instruments attached to the GPIB bus.  I want to be able to reset the card controller itself and run automated tests on it.

  I studied literature, but all I find are commands to reset instruments attached to the Commission.

  Is there a test suit for the GPIB card and a way to reset?

  -Carl Dreher

  
  

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