NOR-488 command requires GPIB controller charge controller

Similar Questions

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

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

• 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

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

• NOR-488: The non-existent GPIB interface. During the generation of the Application in LV8.5

  Joined a vi that I'm building in an exe file.  It contains a single CONDUIT, but whenever I try to build it I get the following error...

  -----------------------------
  Error 7 is is produced to invoke the node in AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller

  Possible reasons:

  LabVIEW: File not found. The file may have been moved or deleted, or the path to the file would be incorrectly formatted for the operating system. For example, use- as Windows path separators: on Mac OS, and Linux. Check that the path is correct using the command prompt or file Explorer.
  =========================
  NOR-488: The non-existent GPIB interface.

  Name of the method: Build: Application
  -------------------------------

  I saw other people with this problem, and I tried their solutions.  I have quit labview, created a new project, new vi... no luck.  I can build on another box, but not mine.  He points to a configuration problem, but I can't.  Any suggestions?

  I just thought of it... While trying to think of everything that was different from when he worked in now... I realized that I turned off my firewall during installation!  I checked off and now the application will build.

  Thanks for the help of the crows Fan and I gave a congratulations for your post on the builder application error codes.

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

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

• error 7 GPIB / NOR-488

  Ladies and gentlemen,

  I am trying to contact a Keithley SMU 236 on Labview 2009 running on Windows XP.

  Write orders by VISA works very well, but written with functions GPIB does not work. I got following error messages:

  7 Fehler ist bei GPIB: Schreiben in GPIB_TEST.vi aufgetreten

  G is:

  LabVIEW: Datei nicht found. Die Datei wurde possibly is Debby, oder der path please angegeben ist oder. Use Sie zum example unter Windows als Pfadseparator einen umgekehrten Schragstrich (\), Mac OS of unter einen colon ( und unter Linux einen Schragstrich (/).) ME Sie based BACK-Eingabefensters Datei oder die Richtigkeit the Pfads explorers.
  =========================
  NOR-488: GPIB-Schnittstelle existiert nicht.

  Since it is the German here is a summarized translation:

  error 7 in GPIB:WRITE in GPIB_Test.vi

  possible reasons:

  LABVIEW: File not found.

  [..]

  NOR-488: GPIB Interface does not exist.

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

  The program is attached.

  Thx for your help!

  NOR does not sell Agilent GPIB boards. It's like Microsoft, selling Apple products. In order to use a Board of Agilent GPIB, you need to use VISA. In addition, read this:

  http://digital.NI.com/public.nsf/allkb/3B3626D9C1F999218625694200791AD7?OpenDocument

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

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

• LV 2016: LabVIEW could not create the required channel file permission error endpoint; NOR-488: Error of hardware detected DMA

  I just installed the new 2016 LabVIEW with the two patches and wanted to check the new feature.

  When you create a channel writer, there was a pop up select the Channel end point, but whatever the option chosen, there is a window saying "LabVIEW could not create the required channel endpoint", error ccode: 8 file authorization error

  NOR-488: Error detected DMA hardware.

  I have error permition from file to file, file that is?

  By chance, do you have re-defined the default data directory in LabVIEW?  LabVIEW uses to host files for the warp threads, and if you moved from its default position in your profile (C:\Users\\Documents\LabVIEW data), especially if you moved it to the root of C:, it could become unalterable.  This must remain in your profile!

  Bob Schor

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