error 7 GPIB / NOR-488

Similar Questions

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

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

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

• Problem installing NOR-488. 2 for windows 7

  Facing some installation issues that need your support.

  Tried to install NOR-488. 2 for windows 7 and there is a window

  pop up. See attachment.

  CAN advice there at - it a patch of window to fix this?

  Thank you

  Mike.T

  Managed to solve the problem.

  I have uninstall all programs of NOR (Please make sure that all traces of programs OR is deleted).

  Website below can help guide by removing all programs of NOR.

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

  Then I proceed to the installation of the last worm NOR-488. 2 3.1, followed by the installation of the hardware (card GPIB).

  Finally the Labview 7.1.

  Now test to see if my old labview software and hardware can operate smoothly in windows 7...

  Thanks for the support!

• NOR-488. 2 missing

  Hello

  I made a kit of distribution for one of my programs, but then decided to add on the program. When I went to build another distribution kit, Labwindows stops halfway through and said that NEITHER-488. 2 could not be found in the directory and insert the Labwindows DVD driver. After that I inserted the disc, it still can't find the NOR-488. 2. This has happened on two separate computers with installed Labwindows. What can I do to get this driver?

  
  

• Cannot uninstall legacy NOR-488. 2

  I took a very old project that was created on a very old version of Labwindows. I built it on Labwindows/cvi 2010 and the distribution built OK.

  When I try and load the executable file on another computer, the load stops with a message that says to remove the legacy NOR-488. 2.

  There is no selection for the NOR-488. 2 in the software from National Instruments under Add / Remove programs.

  How can I remove this?

  Thank you!

  John W.

  Ok thank you!

  JW

• Device driver Upgrde-NOR-488. 2

  I am running NI 2.73 device driver on my Windows 7 system.  I want to update the device to the most recent driver and more great NOR-488. 2 (I think version 3.0.2).  I can just install the new device driver or do I need to uninstall the old stuff OR first?

  Thanks, Mike

  Done and done.  I wasn't sure if there was a setting to MAX to do.  Thanks for your help.  We will examine this topic 'closed '.

• PMC-GPIB with NOR-488 DDK very slow when sending the commands-GPIB

  Hello

  I use a PMC-GPIB Board and the NOR-488DDK allows to develop a GPIB Interface with VxWorks. Already, it works correctly, but sending a GPIB command takes about 100 ms, which is very slow.

  Are there opportunities to speed up data transfer?

  Hello again,

  I found a solution to my problem! I realized that the command execution is related to the vxWorks system clock! Of course, this is done in the DDK (driver development kit).

  The system clock is easily adjustable upper and then orders are shipped quickly.

  Thanks for your time

  Good day

  Cassidian

• 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 NOR-488 driver. 2 1.7 works with PCI-e cards

  Impossible to update driver and must use the 1.7 version as the version of the driver that we tested and the ship with the instruments.  the web page http://joule.ni.com/nidu/cds/view/p/id/532/lang/en has not be updated to include PCI-e cards because it's an older driver.

  Thank you

  Rob

  You did not test in 8 years or upgrades? This driver was written before that the PCIe bus even existed.

  What do you ship? I never heard shipping instrument vendors a GPIB card and the driver for it. If your instrument is in accordance with IEEE - 488.2, it will work with a GPIB of any provider.

• How can I clear an error code CANbus (NOR-9853)?

  I use successfully the two ports of a NOR-9853 of cRIO backplane 9104, unity a port is disconnected.  The disconnected port gives me error 65538 (Op failed) while him remains functionally connected port error 65539 (entry missed 1 or several data points).  I can detect the switch using these error codes, but I don't know what are the best measures for:

  (1) continue to use the connected port

  While

  (2) voting the disconnected port to see when it is reconnected

  Looks like you have every port IO nodes in the same loop FPGA.

  If one node of IO is a failure, he'll at least have a timeout 4 seconds before it fails, and the default time is 14 seconds (configured in the properties). There are two time-outs: one is the output
  Timeout, configured by the user in the 'Advanced Options' dialog box of the dialog box properties module and the other is a second timeout 4 fixed in
  LV-FPGA pending a response from the CAN module.

  If the nodes are in the same loop, the disconnected port will block the loop again and again causing the port always connected to sample to a crawl. Try moving them to their own lines.

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

• Uninstall the NOR 488.2

  How can I uninstall the 488.2 OR...?, I do not find it on remove/uninstall program in WIN7.

  IT IS TOO EASY... JUST GO TO CONTROL PANEL / UNINSTALL A PROGRAM / NATIONAL INSTRUMENTS PROGRAMMS / DOUBLE CLICK AND CHOOSE OR 488 TO REMOVE... RESTART AND COMPETE WITH THE UNSTALLATION... TOO EASY

  Thank you