VISA or logging GPIB Drivers

Similar Questions

• Can I install Driver Visa and USB-GPIB on LabVIEW7?

  Can I install Driver-NI-VISA and USB-GPIB on LabVIEW7? Or I need to install LabVIEW8?

  Thank you

  Véronique.

  Veronica wrote:

  Can I install Driver-NI-VISA and USB-GPIB on LabVIEW7?

  Yes.

  Or I need to install LabVIEW8?

  Only if you want to program in LabVIEW.

• How to detect if the NI GPIB drivers are not loaded

  Hello

  I use VS2008 c# to control an instrument based GPIB, using .NET

  The software should also work on a PC that does not have the GPIB drivers loaded in spectator mode.

  So, how can I detect this.

  I have NationalInstruments.NI4882 specified as a reference and I distribute this dll with my package.

  The software works fine on a PC that uses drivers loaded, but hangs on a PC without the NI GPIB software installed.

  Specification of a problem with NationalInstruments.common. I tried that copy on a target computer, but is always a mistake.

  All I have to do is detect if it is not there and then run in spectator mode.

  David

  Hi David,

  You should look for the existence of HKEY_LOCAL_MACHINE > SOFTWARE > National Instruments > NOR-488, 2.   If it is, this means that the drivers must be installed.

  Kind regards

  Thomas Clark

• GPIB drivers run simultaneously in a subvi?

  Hi guys, sorry for my dupicated post, but I'm with a short timetable on that.

  I need innitialize and read several data with 4 different instruments. I had 1 electric, 2 Multimeters and 1 temperature regulator. And I need to know if I just like attachment that I send. I know that probably no one these specific drivers are installed, but if someone has already worked with this, give me ideas or advice, please.

  All opinions are welcome.

  Thanks for your time.

  
  

• Impossible to update DirectX, error: please visit DXError.log and DirectX.log in your windows folder to determine the problem

  Original title: Directx problems

  I have a computer of Windows 8 and im trying to run a game on steam. Whenever I do it says that I need a Directx says update when I try to install it. AN internal system error has occurred please see DXError.log and DirectX.log in your windows folder to determine the problem. I watched up I don't have much sense of him here, it is

  --------------------
  [11/10/14 09:20:27] module: DXWSetup (Mar 30 2011), file: dxwsetup.cpp, line: 229, function: CDXWSetup::InitInstallEngine

  Sections are not initialized.

  --------------------
  [11/10/14 09:20:27] module: DXWSetup (Mar 30 2011), file: psheets.cpp, line: 705, function: PreinstDlgProc

  CDXWSetup::InitInstallEngine() failed.

  --------------------
  [11/10/14 09:22:25] module: DXWSetup (Mar 30 2011), file: dxwsetup.cpp, line: 229, function: CDXWSetup::InitInstallEngine

  Sections are not initialized.

  --------------------
  [11/10/14 09:22:25] module: DXWSetup (Mar 30 2011), file: psheets.cpp, line: 705, function: PreinstDlgProc

  CDXWSetup::InitInstallEngine() failed.

  --------------------
  [11/10/14 09:41:52] module: DXWSetup (Mar 30 2011), file: dxwsetup.cpp, line: 229, function: CDXWSetup::InitInstallEngine

  Sections are not initialized.

  --------------------
  [11/10/14 09:41:52] module: DXWSetup (Mar 30 2011), file: psheets.cpp, line: 705, function: PreinstDlgProc

  CDXWSetup::InitInstallEngine() failed.

  --------------------
  [11/10/14 09:49:16] module: DXWSetup (Mar 30 2011), file: dxwsetup.cpp, line: 229, function: CDXWSetup::InitInstallEngine

  Sections are not initialized.

  --------------------
  [11/10/14 09:49:16] module: DXWSetup (Mar 30 2011), file: psheets.cpp, line: 705, function: PreinstDlgProc

  CDXWSetup::InitInstallEngine() failed.

  --------------------
  [11/10/14 10:04:23] module: DXWSetup (Mar 30 2011), file: dxwsetup.cpp, line: 229, function: CDXWSetup::InitInstallEngine

  Sections are not initialized.

  --------------------
  [11/10/14 10:04:23] module: DXWSetup (Mar 30 2011), file: psheets.cpp, line: 705, function: PreinstDlgProc

  CDXWSetup::InitInstallEngine() failed.

  --------------------
  [28-10-14 19:04:26] module: DXWSetup (Mar 30 2011), file: dxwsetup.cpp, line: 229, function: CDXWSetup::InitInstallEngine

  Sections are not initialized.

  --------------------
  [28-10-14 19:04:26] module: DXWSetup (Mar 30 2011), file: psheets.cpp, line: 705, function: PreinstDlgProc

  CDXWSetup::InitInstallEngine() failed.

  --------------------
  [28-10-14 19:59:23] module: DXWSetup (Mar 30 2011), file: dxwsetup.cpp, line: 229, function: CDXWSetup::InitInstallEngine

  Sections are not initialized.

  --------------------
  [28-10-14 19:59:23] module: DXWSetup (Mar 30 2011), file: psheets.cpp, line: 705, function: PreinstDlgProc

  CDXWSetup::InitInstallEngine() failed.

  Thank you

  Hello Peta,

  Thanks for posting your question on the Microsoft Community forum.

  According to the description, I understand that you are not able to install DirectX and get error message: internal system error has occurred please see DXError.log and DirectX.log in your windows folder to determine the problem

  In order to understand the issue more clearly, I would ask that kindly provide me with the following information.

  1. You did changes to the computer before this problem?

  2. Since how long you are having this problem?

  3. The game you are trying to launch in the system?

  I suggest you follow the methods and check if it solves the problem.

  Method 1:

  Click on item below and follow the instructions to install DirectX.

  How to install the latest version of DirectX

  https://support.Microsoft.com/kb/179113?WA=wsignin1.0

  If the problem persists, please follow method 2

  Method 2:

  How to use the tool File Checker system to fix missing or damaged system files, please follow the steps in the link provided below.

  https://support.Microsoft.com/kb/929833?WA=wsignin1.0

  Note: System File Checker is a Windows utility that allows users to find corruptions in Windows system files and restore the damaged files. This article explains how to run the tool (SFC.exe) System File Checkerto scan your system files and to repair the missing system or damaged files from Windows or Windows 8 8.1. If a Protection of resources Windows (WRP) file is missing or is damaged, Windows may not behave as expected.

  You can also check out the link below.

  Diagnosing basic problems with DirectX

  http://Windows.Microsoft.com/en-us/Windows-8/diagnosing-basic-problems-with-DirectX

  Please answer back with an update on if it solves your problem.

  Thank you.

• I can't install VISA driver and driver USB GPIB on my PC with VISTA... help me...

  I have LabVIEW7 and VISTA, it's ok, but I can't install the driver VISA and USB GPIB driver on my pc... it is necessary to connect my pc with instruments? Or LabVIEW7 have this files? Thank you

  Véronique.

  LabVIEW 7 is not supported on Vista and the version of NI-VISA supplied with LabVIEW 7 is not supported. You can download the latest version of NI-VISA - I ALREADY GAVE the link for you.

• GPIB and VISA support

  I need help to understand how VISA reads from GPIB. By using LabView 8.6, I'm applying to communicate with a customized by using GPIB controller. He is currently working, but I'm not sure of how to use the Enable property of termination.

  I read of GPIB using VISA Read. I use 1000 for the number of bytes. VISA expiration time is set to 30 seconds. The controllers stop character is a ' > ' (ascii 62).

  1 how VISA knows when to stop reading if there are less than 1000 bytes to be read, the stop character is disabled, and it is during the period? VISA stops when more no byte is coming in? It works for me with endpoints off, but with an ending to this topic is much slower and I don't understand why.

  2. I also use the GPIB-RS232 converter for certain situations. The PC has the GPIB and RS232 controller. Using the converter, I need to activate the stop character so that it works correctly.

  A GPIB read should end when EOI is detected. It is one of the management interface, and is a requirement for the GPIB. A stop character of > is very strange. If any type of stop character for a GPIB instrument designed over the past 20 years or more, is, to put it politely, unusual. Your calling a controller raises another question. There is usually only a single controller in a GPIB system and it would be a device as the NI PCI-GPIB or GPIB-USB-HS. You are trying to design your own controller?

  RS - 232 with none of the lines of management GPIB, you need another mechanism to put an end to a reading.

• Communication with the niVisa (GPIB) do not work next to a serial interface

  Hello

  I programmed an application in C++ (Visual C++ with MFC, running on XP). On the one hand, I control devices of different measure (also from different suppliers). All communication is done with niVisa (Version 4.6). On the other side, I send remote commands to a generator via the serial interface. To do this, I use CSerialPort, it's a Wrapper MFC of the Windows API. Thus, niVisa is not used for the serial connection.

  It works without any problem until I connect the measurement equipment (any type of) via Ethernet.

  When I now connect the scope via GPIB (I use a NI PCI-GPIB), communication works without any problem as long as I wouldn't send anything on RS232. After I send something to my generator (and close the com-port), the next Commander of VISA will give me an error (VI_ERROR_ABORT). Now, I can log in again and everything works normally again (until I have again send something on the com-port).

  For me, it's a really strange question. Any ideas? Any help?

  Best regards

  Michael

  OK, I finally found the problem.

  When you use the serial port, you can write data with normal writing (WriteFile()) function or with the tip (WriteFileEx()). Do not now ask me for more details on the difference, it's something with the mode "" overlap...

  After I send all the data with WriteFileEx, VISA-connection via GPIB produces an error. So I went to the basis of WriteFile() and everything works. Don't ask my consistency betwenn VISA (with GPIB and just GBIB) and the connection series. I'm just happy right now...

  Michael

• GPIB / series substitution pilot

  Hello. I'm trying to control my first instrument inherited using LabVIEW. It is a Tektronix TDS 320 (scope). I talk to him through series (not GPIB). The only drivers I can find for her to LabVIEW are GPIB. Would it be possible bring these GPIB drivers to serial or would I need to write my own drivers.

  Cheers, Alec

  Hi Alec,.

  you need to replace all the calls-GPIB with VISA-functions.

  Then, it is rather easy to choose the right bus for communication, as VISA supports both of them (and more)...

• Error reading misaligned GPIB

  Under Instrumeent i / o-> GPIB, are read are writing functions.  The error inside and out for these functions are not aligned.  Why is this?

  Should I still use the GPIB functions?  Can I use the VISA fucnctions instead?  I like the features of GPIB, because I only need to enter a number of GPIB address to a string for the address, and I think that it is convenient.

  Using GPIB functions has not recommended for quite a few years and certified instrument drivers need VISA. Using GPIB is, in my opinion, being short-sighted. They rope you up materials and you belay GPIB. With VISA, you can use other providers GPIB controller and you can easily use VISA with USB, Ethernet, RS-232, etc. with little or no code changes. The extent of comfort and control of resources VISA, you just select the correct resource from the drop - no need to try to remember addresses and you have support for aliases (i.e. "DMM"). I also have the VISA Resource Name Out makes for a neater wiring.

• Good use VISA

  I'm still kind of new with LabVIEW, and I fell on the functions of opening and closing VISA (they were hidden under the Advanced tab so I never saw them before).

  My question is if I'm supposed to be using the functions of opening and closing VISA when I do gpib drivers for hardware that I use.  For example: attached is a simple code that will set up my Keithley 181 and a measurement (really just for demonstration purposes).  I've highlighted the functions of opening and closing, I've never really used before and normally if I wanted to write the same code I would have just skipped them and went directly to the entry VISA (which still works).  I didn't know all the problems with the drivers, I did, although I have not used these functions in the past, but maybe there's a chance that some unexpected results can occur, I'm not really sure.

  Thank you!

  Once upon a time, the use of the Open VISA was necessary. A session has not created unless you call it explicitly. Then the VISA got a little smarter and if a VISA function is called, if the session does not already exist, it is created automatically. Calling the Visa Open is therefore Optional a bit even though I still prefer to use in my code. With the VISA close, there is a setting (Tools > Options > environment) which will automatically close VISA sessions when you leave the highest level, but especially with the series VI, I prefer to have more control.

• Problem with LabVIEW 9.0f2 and VISA 5.0 on Mac OS x 10.6

  Hello

  I'm using MacOSX 10.6 and Labview 9.0f2. I installed the lates VISA (5.0.0) drivers, as they are the only support OSX 10.6.

  Now, I try to run the "basic series write and read" example and get the following error:

  Error 1073807343 has occurred to the property node (arg 1) visa set up a Serial Port (Instr) .vi-> basic series writing and Read.vi

  Possible reasons: VISA: information about insufficient localization (Hex 0xBFFF0011) or the device or resource is not present in the system.

  As I am a newbie to Labview, I'd appreciate any help on this...

  Thank you

  Daniel

  Hello

  You do not have a device series on behalf of resource, you use to write and read and take?

  Did you check with Max OR and log on to this device.

• MAX Dosen´t detects my PCI GPIB

  Hi guys, I am currently using Windows xp sp2 and labview 8.6 adcademic there must be and interface for an instrument for school and my problem is:

  In MAX dosen't appear my PCI (keiithley provider) of KPCI - 488 A card, until my computer hardware, it seems I have alreadry installed the latest driver from keithley page and still does not appear = /, I tried refreshing, fresh installation etc... nothing worked... could someone help me please... tnx guys... xD!

  As mentioned, this device will not appear in NOR-MAX because it is NOT material. And no, you NEITHER-488. 2 driver will not work either. You must use the GPIB-488 driver (version 9.0 or 9.1 should work for you). Once installed, use the tools of 488 GPIB software on your system, as follows:

  To see if the device works properly first confirm the presence of the jury and then to test its ability to comminicate with an instrument the driver alone and then with NI-VISA:

  1. first check that the KPCI - 488 A is detected by the driver. Run the program Start-> all programs-> GPIB - 488-> diagnosis GPIB. This should confirm if the IPP is recognized or not. If this isn't the case, reinstall the pilot or the pcb.

  2. then, connect an instrument with gpib and attempt to communicate with the driver: Start-> all programs-> GPIB - 488-> TRTEST.exe (use the buttons send and Enter to test writing and reading respectively). If this fails, check your cable connection and make sure that you use the correct address for the instrument number.

  3. If it works, then you can you can try to communicate with the instrument using NI Visa Interactive Control on your system (start-> all programs-> National Instruments-> VISA-> Visa Interactive Control), you can also open it and check if your instrument is listed under the VISA i/o tab. If your device is not listed, then recheck your connections and also your passports VISA.

  To check the VISA Paassports, open the utility OR Measurement & Automation (NI Max) and click on software-> NI-VISA, go to VISA-Options tab, click on passports and ensure that the passport of NI-VISA for the GPIB is marked on.

  4. now you are ready to use LabVIEW. You can start with a simple reading GPIB and GPIB write or read visa and Visa write before moving on to complex things.

  Best regards.

• Why I get this: VISA: (Hex 0xBFFF00A5) interface type is valid, but the number of specified interface is not configured.

  I searched the knowledge base NOT found Document ID: 5389BHR7. I went through the 'solution', but I already had NiVi488.dll - NI-VISA passport to the GPIB controlled. I can't find anything else on the matter. Any help would be appreciated.

  Note: this deployment has worked in the past. I upgraded from LV2009 to LV2013 last year and this is the first run my Installer on a new PC since the upgrade. I have all my VI migrated to the format of 2013. A PC running all my previous VI has been upgraded, but I did was install the runtime in 2013 and then copied all the new .exe. They all work. I imported my hardware configuration as part of the installation process.

  I found the solution. I had taken off my VISA Alias names and had the GPIB::6:INST because I had problems with a version of the VISA. This has been resolved once I got an appropriate VISA version installed. Now, this VISA was installed proplerly, I actually had to give a 'name' for each piece of equipment. This is why the error "interface number specified is not configured" message. Once I reassigned all instruments VISA on my GPIB bus with a name, everything started working again.

• GPIB file transfer

  I have an Agilent E5052A that use Windows 2000, and I'm saving the screenshot in the c: local in scope. When I try to copy this image in my PC (via GPIB) the file passes through without problem but I can't open the file, please see the attached files Original.png and Test.png.

  I use ReadToFile.vi Visa to transfer files. I already tried with straight 'Visa read' and "GPIB read" vi and get the same results.

  I compared the two files using a file comparison program, in text mode looks like equal to or similar (except for the beginning and end), but if compare two files in binary files, am I gatting of many differences.

  any body have any idea?

  Hi lmontoya,

  There are two problems:

  -first of all, you have 8 extra bytes at the beginning, some counter or the length of the file or similar...

  -then (almost) all end of LIFE characters are replaced by the 0x0D0A, what happens when you do not set a correct transmission or file in save mode. Need a transmission "binary" instead of the transmission of the text (with the inherent EOL conversion). Probably you have used 'Save the text file' with enabled EOL conversion... Please attach your VI to identify the section of your code problem...