Quantcast
Channel: Instrument Control (GPIB, Serial, VISA, IVI) topics
Viewing all 5670 articles
Browse latest View live
↧

Problem with VISA Reads in TCPIP socket interface, VISA configuration?

February 8, 2016, 1:34 am
$
0
0

Hi there,

  I have encountered a problem with different drivers if these make use of VISA READS. In case a Visa Read follows a Visa Write, in a first run the read buffer never outputs the right data but a “DCL” (Device Clear?) or line feed or the result of another previous Write command, but the next times the same VI runs the Visa Read outputs the expected data, although maybe not the complete string. There is not timeout error. It seems like the VISA Reads have a triggering problem. I am using NI-VISA 14.0 in labview 2014 to control my keithley 6221 instrument as a TCPIP socket. The MAX software successfully opens the instrument and a VISA Test Panel can be used. Here, the parameters are

 

Hostname: 192.168.001.003

Address: 192.168.1.3

Port 1394

No packet delay

Send End on Writes

Suppress End on Reads

Enable Termination Character (LF)

Advanced settings:

Acquire Exclusive Lock

Events Enable

Trigger Protocol Default

 

With this Test Panel I check the instrument “ID query?” that gives “No error”, however the “Read STB” command does not work and other attempts to change settings or “Assert trigger” give error VI_ERROR_INV_SETUP

 

What parameters could avoid the triggering/reading problem? Can anyone advice on this? How to fix it?

 

Jose M. Colino

 

↧
Search

visa read timeout error -1073807339

February 8, 2016, 3:06 am
$
0
0

Hi All

 

I'm trying to do an autoscale command on a Agilent (Keysight) DSO-A4034A connected over ethernet.

But for some reason I get a timeout error. when cheking for system errors.

 

I have set up the visa session in "MAX" and use the name of the instrument session to call it in the VI.

 

I have based these VIs on the instrument driver from Agilent. and I can do all the other stuff I need to do without errors. EI. setup measurements Aqusition type read data and so on without error.

 

The error is generated by the read command just after the ": SYST:ERR?" command in the error query VI.

 

I have updated the firmware of the scope and upgrated to VISA 15.0.1 but so far without luck.

 

When I turn on "execution highlight" there is no problem...

 

Is there anybody that can give me some pointers as to where to look for this fault? All help would be gratefully recived.

 

/Regards Rasmus

↧
↧

dynamic time delay between wright and read.

February 8, 2016, 6:52 am
$
0
0

Hi All

 

I'm woring on expanding my instrument sriver for my Agilent DSO-X4043A Oscilloscope.

I have made a VI that sets up a VPP measument and it works fine. Until I set the aqusition type to "Average" and ask it to do this over 128 measurements.

 

I suspect that this is due to the fact that it takes to long to do this averaging. So that I try to read before the data is ready.

Since I'm running this over ethernet, I dont have the otion of monitoring the amount of data ready to be read.

 

My question is therefore: Is there a way to determin when the scope is ready to "unload" the data?

 

I know I could set up a time delay, but I'm duing quite a lot of measurements. So I would like to have this VI running as fast as posible.

 

Help is much areciated

 

Regards Rasmus

↧

Using both NI GPIB-USB-HS and Keithley KUSB

February 8, 2016, 6:32 pm
$
0
0

I am trying to use two different GPIB-USB connecters on one computer-(1 Keithley KUSB and 1 NI GPIB-USB-HS) to communicate in LABVIEW.

 

To use NI's GPIB to USB, you need to install NI's 488.2 and need to make sure no other GPIB communication software is installed.

To use Keithley GPIB to USB, you need to uninstall NI's 488.2 software and use the Keithley Specific Driver, GPIB-488 ver 9.2. (This has been covered by a few posts on the forum)

 

My problem is that I can get both devices to work individually with their respective softwares but not togather.

 

 

I am wondering, has anyone found a work around for a similar type of problem?

Are two different 488 software protocols not allowed on the same computer?

 

 

↧

NI MAX Freezes

February 9, 2016, 10:53 am
$
0
0

Hi,

Every time I start the NI MAX it freezes. At first it shows the splash screen and then attempts to establish a network connection (?).

After those changes, the NI MAX window freezes. It won't respond. I've been waiting for an hour or so and I had to kill the process.

 

I'm using the v15, two GPIBs (one of them brand new) and a PXI with the cards PXI-4070 and the 6341.

The same happens when I try to use VISA on LabVIEW, I select the "Open VISA" VI and when I try to add the "port" it freezes as well.

 

What is going on? I'm getting real dissapointed due to the value of the products that I have and none of them seem to work just fine.

I have Windows 7 Professional SP1. One of the GPIBs is attached to a Power Supply and the other one is attached to a multimeter Agilent 34401A.

 

I didn't mean to be rude, but it's getting really frustrating.

↧
↧

Turn off outputs when computer crashes or communication loss

February 10, 2016, 4:27 am
$
0
0

Hi!

 

I am working on a monitoring and control system for a gas turbine for educational purposes.

I need to have some sort of safety system in case of communication loss between the computer and the cDAQ-9178.

As soon as something happens to the computer connected to the daq, all outputs needs to be set to 0.

 

Any ideas how i can manage that?

/Gideon

↧

Instrument Driver for Keysight 34461A DMM works with GPIB, errors with USB

February 10, 2016, 11:15 am
$
0
0

I'm trying to remotely control a Keysight 34461A DMM using the instrument driver located here:

http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=21589

 

 

This instrument driver works like a charm when the DMM is connected via GPIB, but it errors out when it is connected via USB.  I've isolated the problem to "Default Instrument Setup.vi".  When this VI is called in the USB case, the instrument is left in a state that results in a timeout of any subsequent call to VISA Read.  The only way I've found to get the instrument talking again after this error condition occurs is a power cycle.  I have another 34461A exhibiting the same behavior, so it is unlikely to be a hardware issue.  I can run the example "Agilent 3446X Series Acquire Single.vi" successfully over USB if I remove any calls to "Default Instrument Setup.vi".

 

Has anyone else experienced this or a similar issue?

 

I'm using Windows 7, LabVIEW 2014 SP1, NI-VISA 14.0.1, and the GPIB-USB-HS+ (NI-488.2 14.0) when operating over GPIB.

↧

Serial Query and USB-Serial Adapters

February 11, 2016, 10:54 am
$
0
0

Transferring serial device from old (functioning) computer to new. 

(Old) Computer A:  

Labview V14.0.1f3 (Service Pack 1)

NI-VISA 1401 full

 

(New) Computer B:  

Labview V14.0f1

NI-VISA 5.20

NI-SERIAL 15.00

 

1) Computer A can control device motion and obtain position readout with established labview code.

2) Both computers can control device motion and query position through a non-labview command terminal.

3) Neither computer can control device motion through Measurement & Automation Explorer

4) Computer B crashes when running VISA Configure Serial Port 

5) All settings for VISA Configure Serial Port are the same on both computers.

6) The only discrepancy is communication through COM1 on Computer A and COM10 on Computer B. 

7) Via a USB-Serial converter, both computers can send commands through established Labview code, but cannot query the device position. 

 

Can you help me determine the source of this problem? 

↧
Search

In serial communication, upon request it sends 2 responses which is correct but i need to separate them in 2 different lines.

February 11, 2016, 11:12 pm
$
0
0

Hi,

 

I need to know how to seperate the 2 or 3 responses upon a single request, for eg:

 

Request: 3B 16 XX XX XX XX XX

Respoonse i am getting as :  3B16 XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX

 XX3B 16XX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX  3B16 XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX 

 

I want to separate these 3 response which starts from 3B 16, is there any simple way to do that beacuse i can use the offset and separate them but it will become too messy.

 

Thanks 

Aniket

↧
↧

NI-MAX with empty Logical name list

February 12, 2016, 2:24 am
$
0
0

Hi all, I am new to this forum & NI so please be patient with my questions.

I have recently installed several programs & IVI drivers.

 

However, something went wrong in MAX where all the IVI drivers went missing.

All the tabs under the Logical names & Driver sessions are now empty.

 

What could have happened or did I do something wrong along the way?

 

Thank you.

KangJonathan

↧

Controlling a Watlow F4

February 15, 2016, 10:22 am
$
0
0

Hello All,

 

I am new to Labview and will be using it to communicate with a Watlow F4 controller. The instrument I am communicating with is a Watlow F4 controller used to control a Associated Enviormental Systems chamber. First, I would like to open a communiation to the controller and have it send data every 20 mins while I conduct my experiments. The chamber sends out information about temperature and humidity. I would like to record this as an excel file. Eventually I would like to set temperature/humidity profiles from labview and record the data.

 

Right now I have not been able to establish a successful communciation. I have been searching through similar threads but I'm still getting a timeout error. I have attached my current VI and appreciate any advice as I continue to troubleshoot my VI. 

 

Best,

Naim876

↧

GPIB timeout after a while using LabVIEW & E4404B Spectrum Analyzer

February 17, 2016, 1:05 am
$
0
0

Hi,

 

I'm using LabVIEW to communicate with Spectrum Analyzer Agilent E4404B/E4402B, with Agilent Driver to read trace and create graph according to that.

 

I get a Timeout error after a random time of operation, it can happen between 5 min to 4 hours and more (I mean that the LabVIEW is running and communicate with SA).

Everytime I get this error the Spectrum Analyzer is not coressponding at all. Can't shift it back to Manual mode and I have to unplug the power socket.

When i plug back the electrical power cable the Spectrum is ready to work again.

 

I know that I should probably post this question in Agilent forum, and I will, but i ask here one question:

Should I Flush the "GPIB Buffer"?

 

Please share with me any thougth you have, that may solve my problem. 

 

Hadar.

 

↧

GPIB-USB-HS Driver Error -- Windows 10 possibly after Feb Windows Update

February 17, 2016, 1:08 pm
$
0
0

As of 2/17/2016, GPIB-USB-HS devices (2) no longer connect on Windows 10 using NI488.2 Rev 15 from 8/15 with the 15.0.1 patch.

 

Using VMWare player 7.1.3, the VM sees the hardware, connects to it, lights turn on and then turn off. The VM shows 'Driver Error' unable to connect to the USB device. This was tested with two USB devices that have been working with the same configuration for some years now on Windows 7, 8, 8.1 and 10 using VMate 7.x and 12.xs 

 

Possibly, this is related to the latest Windows Update, 

 

Neither repair nor a full install of NI488.2 rev 15 fixes this.

 

VISA still works via TCP/IP. 

 

Any thoughts will be greatly appreciated. 

 

 

↧
↧

NI-VISA Crashing after Update

February 17, 2016, 6:11 pm
$
0
0

Hi All,

 

I have been using NI-VISA runtime 4.3 for some time now (as it is a dependency for the Ultrascope DS1000 software I use) and recently installed NI-VISA 15.0 found here. After installing the upgrade I get a crash every time i attampt to connect to my instrument as shown below.

 

This crash is not isolated to that particular program however as I experience the same crashing problem when i attempt to connect to the instrument in my c# code on the connection attempt line below. Has anyone else experienced this problem or have an idea what I can do to fix it? futher more could someone help to explain the difference between NI-VISTA drivers and NI-VISTA runtime Eninge??

 

 mbSession = (MessageBasedSession)ResourceManager.GetLocalManager().Open(strVISARsrc);

 

Capture.PNG

↧

Keithley2400 voltage ramp rate

February 18, 2016, 2:32 am
$
0
0

Hello, 

 

I am using Keithley 2400 and Labview because I need to make a ramp of Voltage from 0-5 V (initially). Although I read it at the graph in Labview, I can not see the same signal at the scope. Thus, I would like to understand what is the rate of increase of the ramp and try to control it. This ramp block is tricky for me to understand, could you please indicate how I can set the rising time and make it slower/faster please? I tried to find an example for ramp but didn't find any. Do you see any error in my code?

 

I have attached the screenshot of the scope and what I see at Labview too. Please help ! 

 

 

Thank you in advance!

↧
Search

Error: property node (arg 5)

February 18, 2016, 3:09 am
$
0
0

Hello,

I am getting this error :

Proprerty node (arg 5) in Initialize PR670.vi->Main.vi. ( see attached pic)

I am using a virtual com port.

Can anyone help me please?

Thanks

F

↧

VISA: (Hex 0xBFFF001D) The specified attribute is not defined or supported by the referenced resource.

February 18, 2016, 12:17 pm
$
0
0

I've been recieving this error when attempting to run my VI: Error -1073807331 occurred at Property Node (arg 1) in Agilent 34401.lvlib:Initialize.vi->Sample Measurement.vi

 

I have all the proper drivers installed and the I/O Agilient Library. I also have the Tulip passport selected.

 

Anyone knwo what the issue is?

 

Thanks!

↧
↧

Connecting to a TCP/IP VISA Resource Requires Registration - Why?

February 18, 2016, 7:03 pm
$
0
0

Using the ICS-9065 interface requires registering a VISA resource for each instrument using NI-MAX.  Apparently, this manual procedure just adds entries such as these to the visa configuration file:

 

[TCPIP-RSRCS]
SynchronizeAllSocket=0
SynchronizeAllVxi11=1
NumOfResources=3
Name0="TCPIP0::192.168.1.140::gpib0,15::INSTR"
Enabled0=1
Static0=1
Name1="TCPIP0::192.168.1.140::gpib0,22::INSTR"
Enabled1=1
Static1=1
Name2="TCPIP0::192.168.1.140::gpib0,24::INSTR"
Enabled2=1
Static2=1

[ALIASES]
NumAliases=4
Alias0="'COM1','ASRL1::INSTR'"
Alias1="'7001','TCPIP0::192.168.1.140::gpib0,15::INSTR'"
Alias2="'2002','TCPIP0::192.168.1.140::gpib0,22::INSTR'"
Alias3="'2410','TCPIP0::192.168.1.140::gpib0,24::INSTR' "

In fact, rather than going through NI-MAX, the resources could be added directly by editing this file. It seems, therefore, that adding resources is rather unnecessary making it harder to deploying applications. Doing away with the manual step clearly will facilitate deployment.  In fact, rather than having to add these resources manually, the VISA environment could add said resources automatically upon a successful creation of a VISA session.  

 

My questions:

(1) is this analysis correct?

(2) could this automatic resource registration feature be added to a future release of VISA?

 

 

 

 

↧

Instrument driver location

February 19, 2016, 5:08 am
$
0
0

Hi all

 

I'm well aware that labview wil by default instal driver en the "Labview\instr.lib" folder but is it posible to install drivers on a network location so it can be shared?

 

I'm asking this since I like to code my applications on my desktop computer. But if they need to run for an extended period of time, I like to run the aplication on my laptop. witch means that I have to copy the instrument driver to my laptop, and any "small" fixes needs to be copyed back to my desktop.

 

I gues a similar situation would arise if there was more than one man using, and "improving" the driver.

 

/Regards Rasmus

↧

Trigger type for PXI-5922 not setting correctly

February 19, 2016, 1:03 pm
$
0
0

I'm writing up a front panel for PXI-5922 (a high-resolution digitizer). I've encountered a minor but annoying issue - it seems that at startup, when the instrument is being initialized, the trigger does not get set up correctly.

 

The trigger type options are Edge and Immediate, and the trigger source options are Ch 0, Ch 1, and External.

 

If at startup the Edge type is selected, everything is fine. If Immediate and External are selected, everything is fine. But if Immediate and either Ch 0 or Ch 1 are set, then the instrument defaults to Edge.

 

If I update these settings while the front panel VI is running, everything works correclty. The problem appears only at VI startup.

 

Also, I've noticed that if this the first run of the VI, and the Immediate trigger is selected, then the instrument is stuck in a measurement loop, where it never registeres a completed measurement.

 

A screen cap of the initialization VI is attached. Can post the rest of the VIs if that would help.

 

Any idea why the trigger type sometimes reverts to edge? And why this depends on the trigger source selection? This shouldn't even matter if the type is set to immediate.

 

Hardware: PXI-5922 digitizer in a PXI-1036DC 6-slot chassis. Software: LabView 2015 x64 running on Windows 7 x64, using the IVI Scope library to interface with the scope.

↧
Viewing all 5670 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>