GPIB and Mercury WinRunner

I want to automate the communication from the pc to the GPIB - Device
(ANT-20 Analyzer). But I have problems calling the external functions in the
gpib-32.dll wit TSL (WinRunner) there comes an error "bad Pointer". There is
no way to use pointer in the TSL language (WinRunner) . Does anybody now
other ways ?

In article <7s8orv$t4p$[email protected]>,
[email protected] wrote:
> Is it possible to control GPIB and read off a serial
> port at the same time ? I need to read off the serial
> port before any GPIB function takes place
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
Hi,
If the serial ports are not connected to the same instrument, it is
possible to.
If the serial port is connected to the instrument where GPIB is
connected, it is possible to ... but not with all gpib instruments: I
use one witch must be configured for serial communication 0R GPIB
communication but not both at the same time.
Laurent.
Sent via Deja.com http://www.deja.com/
Before you buy.

Similar Messages

How can I use a GPIB and AT-MIO-16L with a common NI-DAQ?

I'm using a GPIB card for recording data and a AT-MIO-16L for sending an analog output to my instrument. Earlier, both the devices (GPIB and AT-MIO-16L) were running correctly. Until I reformated my hard disk. Now I'm trying to install NI-DAQ 6.1.1 for AT-MIO-16L but that doesn't detect my GPIB card. On the other hand if I use NI 488.2 along with MAX 1.7 or MAX 2.2, I'm unable to use AT-MIO-16L. Is there a way I could get both my devices running on a common platform?

NI-DAQ is not supposed to detect your GPIB and NI-488 software will not detect your daq board. When you installed MAX, was this from a LabVIEW driver install CD that also put a new version of NI-DAQ on your pc. Open MAX and check your currently installed versions of NI-DAQ and NI-488. They should both be listed. If you have a new version of NI-DAQ than 6.1, you can uninstall the newer version and install 6.1.

GPIB and RS232 communication problems

I've been having several "interesting" problems with GPIB and RS232 communications in LabVIEW VIs. Some I'll mention at the end for curiosity, but right now I'm facing a rather big problem. I'm essentially self-taught at doing LabVIEW (using 8.5.1 right now), but by now I've had a lot of experience as their either has not been any drivers or pre-made VIs for the instruments I've needed or I've not been able to get the available drivers to work and had to write my own anyway (such as with the HP 3458A), but nothing seems to be working right now. I'm not at work, but we typically find forum sites blocked anyway (I can't even download the NI drivers at work since they house them on a ftp server, go figures) so I can't give the VI itself (it wouldn't be easy to get approval even if I could) so the best I can do right now is in words describe everything I've tried. I will be happy to post follow-ups of specific details if I can if they would be helpful.
I've been working on a routine to read data from an MKS 670 Signal Conditioner/Display with a MKS 274 Multiplexer with 3 connected MKS 690A Baratrons. Previously I've worked on programs using other older displays and the analog outputs which were being read by a DAQ card, but for a new project it was decided to try and just read the data directly. I first worked with a unit with just an RS232 Serial Port which I managed to get to work, but had so much problems with garbage readings and having to add checks and re-reads that by the end no matter what delays I added between each reading and how simplified the command routine down to just 2 sequences and the read that it took at least 10 seconds to get 1 reading from each channel.
Figuring maybe it was a limitation of the serial communications for these instruments I tried to re-work it for a unit with a GPIB port with which I'm actually much more familiar. The problem is that I cannot get anything at all from the unit through GPIB. Everything even the bare-bones built-in GPIB CLR function times out with no response from the instrument no matter how long I set the timeout limit and it also freezes the entire GPIB bus as well. It isn't a waiting issue as it freezes on the very first command. The GPIB initialization function seems to work (I typically find this to be unnecessary), but the instrument itself doesn't even respond with a status code. I've also tried just the basic GPIB write functions with even just passing the <cr> and <lf> characters as well. In Measurement and Automation Explorer most of the time the instrument won't even appear when doing search for instruments and when it does it shows as not responding to the *IDN? command (yes I've messed with the EOI, EOS, etc settings and I've even changed the GPIB address even though when it gets this far it confirms that I have the correct address) and even tried manually doing the *IDN?, *RST, and *CLR commands even with <cr> and <lf> characters which the manual for these units clearly states are compatible commands and NI SPY and everything show no response at all. I've tried 2 different GPIB units, 3 different computers including several that are not online and haven't been updated for a while, and using older LabVIEW versions, extensive re-booting and resetting of computers and devices and still nothing. I'm using an NI GPIB-USB-HS GPIB to USB adaptor which I've used extensively on other systems and even re-connected to those systems and everything worked fine. When I hooked up equipment that I knew was working, it would either freeze the entire GPIB bus until well past whatever timeout setting I set at which point all the instruments would appear, but none responding to *IDN? queries or nothing would appear at all, or if I manually turned it off when frozen the other instruments would work and most even respond to the *IDN? queries. The same goes for both of the GPIB instruments of this type that I tried and again for different versions of LabVIEW, difference computers (all Windows XP though), and every GPIB configuration setting I can find to mess with in every combination.
Any thoughts or suggestions would be greatly appreciated. I've had all sorts of weird problems with equipment and LabVIEW (you've got to love undocumented design features) that have frustrated me before, but I've never had an instrument never respond at all especially a GPIB one. Getting garbage yes, no response at all, no.
The side side issues I'm just mentioning as they may be related, but I'm really interested in the above as I have working solutions for these:
One I've had is with a Hart Scientific (prior to being bought by Fluke) 1560 Black Stack that would continually stop responding to GPIB commands when on a continual read function taking readings just every 4 seconds with 250ms between each GPIB read or write command but for up to hours in total and the times it stops responding are random as far as I can tell. I even started sending the *RST command before and after every read or write command and still it freezes. The only thing is to manually turn it off and then back on or manually go through the menus and manually trigger the GPIB reset routine at which point it immediately starts responding. However, when I got sick of having to babysit it and just decided to try the RS232 serial port (as that is all it has without the extended communications module) it works fine no problem and I can even get readings slightly faster from it. Using a Hart Scientific 1529 Chub-e it could give me data on all 4 channels every second without problems. I just find it a bit odd.
When I couldn't get any of the HP 3458A driver packs to work to even give a single measurement reading and just made my own using basic GPIB read/write commands using the programming manual I still have a few interesting problems in randomly when reading off the full possible 256 bytes on the bus and clearing the bus I often find garbage partial readings on the bus every now and then. I've added a few routines to do some basic checks, but it is annoying. What is really weird is when just doing basic DC Voltage reads the "-" sign will randomly be dropped from some readings (started as about 1 out of every 5, down now to about 1 out of every 10). Fortunately I'm taking several readings and averaging and taking the standard deviation with limits on the deviations and basically added a routine to say if there is even 1 negative number take the absolute value of all then make all negative, but again I find it weird.
Thanks.
-Leif
Leif King
Metrology Engineer
Oak Ridge Metrology Center

Greetings Leif,
I understand you have completed extensive troubleshooting techniques to pin-point the problem with the GPIB communication. To begin, I want to ask you a few questions to help me understand your set-up and the issue at hand.
1) Is the NI GPIB-USB-HS cable the one which cannot communicate with your instrument?
2) When using the GPIB-USB-HS, does the GPIB interface show up in MAX?
3) If yes, does the instrument appear in MAX after scanning for instruments (from what I understand in your issue, it does so in an intermittent manner..)?
4) What driver version of VISA do you have installed in your computer?
5) Are you able to communicate to the same instrument using another GPIB cable?
Thank you for trying out some of these steps again, but we want to make sure we rule out other aspects in the systems which might be affecting the GPIB communication.
As for your other issues, please post seperate threads for each so we can help you accordingly. Thanks!
Sincerely,
Aldo
Aldo A
Applications Engineer
National Instruments

TS1702 Thanks. I had 6 Apps that needed updating on my iPad original. I hit "Update All" and that ruined four Apps. They won't download the updates, nor will they launch and be useable either. I lost Splashtop 2, Bible!, and Mercury Browser! Suggestio

Am I the only fool who clicked on update all when my iPad told me updates were available? Two updates loaded just fine, but the other four never updated and now lie useless and grayed out. I had 6 Apps that needed updating on my iPad original. I hit "Update All" and that ruined four Apps. They won't download the updates, nor will they launch and be useable either. I lost Splashtop 2, Bible!, and Mercury Browser! Suggestions?! I don't want to ruin my access to Splashtop 2 for sure.

I fixed it by going through a few steps using iTunes while hooked to my computer.

White square is shown when on cam using aMsn AND Mercury

Lately i've had some trouble going on webcam to people over aMSN and Mercury Messenger (the only Mac Cam/MSN apps I use). I can see myself just fine, but all the contact can see is a blank, white square in the space where i'm meant to be. I thought that it might just be the one messenger service, but the fact it happens on both pieces of software is making me think that it's to do with iSight.
Could anybody please recommend what I should do?
Thanks a lot.

The60ftOctopus wrote:
Lately i've had some trouble going on webcam to people over aMSN and Mercury Messenger (the only Mac Cam/MSN apps I use). I can see myself just fine, but all the contact can see is a blank, white square in the space where i'm meant to be. I thought that it might just be the one messenger service, but the fact it happens on both pieces of software is making me think that it's to do with iSight.
Could anybody please recommend what I should do?
Thanks a lot.
Welcome to Discussions, The60ftOctopus
You can use the suggestions in http://support.apple.com/kb/HT2090 to see whether iSight is causing your problem. Be sure to try with more than one user account and with some other apps, too:
http://www.ralphjohns.co.uk/EZJim/EZJimpage7.html
If your iSight works properly with any app in any user account you test, iSight is NOT the cause.
If you can eliminate iSight as the source of your trouble, you will need to either switch to other ways of communicating as Defcom suggests or troubleshoot other system elements that might be causing the problem. Here are a couple of things you can consider if you don't get better suggestions here:
(1) Sometimes a restart restores function on internet connected applications. Shut down everything and restart your entire system including modem, router, and Mac in that order. To eliminate possible communication hardware problems, *allow self-test to complete on each device before starting the next*.
(2) If you updated or installed any software immediately before the problem began, check their websites to see if there are known issues with your system configuration or installation. If not, carefully following the developers' instructions, reinstall any possible software cause, repair permissions, and try again.
If you find conflicting software, follow the instructions and uninstall to see if removing it will restore proper function to your favored communications apps.
(3) Check the dedicated aMSN and Mercury Messenger fora to see if your problem has already been solved by other users who post there.
EZ Jim
G5 DP 1.8GHz w/Mac OS X (10.5.8) PowerBook 1.67GHz (10.4.11) iBookSE 366MHz (10.3.9) External iSight

How to synchronize the data acquisition from both GPIB and DAQ card

I want to begin/stop acquiring the data from GPIB and PCI6024E card into Labview at the same time. Since the acquisition from GPIB is quite slow comparing to the one from DAQ card, I can not put both of them in the same loop structure. Is it possible to synchronize them?
Thank you!

Hi,
I wanted to save data acquired from NI-DAQ (for example, NI 9234) in a file using the DAQ-mx ANSI C Code. The response I got was as follows:-
One way to do it is with TDMS logging. DAQmx comes with functions designed to log to a TDMS file. This is a special file type that is used for collecting data in a logical format. It can be displayed in a TDMS viewer where data is separated into groups and channels. NI-DAQmx provides examples for how to log to TDMS. Look at the TDMS examples in the C:\Users\Public\Documents\National Instruments\NI-DAQ\Examples\DAQmx ANSI C\Analog In\Measure Voltage directory.
However, now I want to know is there a way that using that same C code, can we save the data in a .txt file format (Text File) instead of a TDMS file? We actually want to access that file through MATLAB (that's why we want to save it in text format).
Also on an other note, is there a way we can access & open TDMS files by MATLAB?
Thanks,
Sauvik Das Gupta

Solaris driver for PCI-GPIB and GPIB/ENET

We have written a Java wrapper to communicate with the Solaris PCI-GPIB driver. Now we need to support the GPIB/ENET device. According to ibconf we are running the following driver (NI-488.2 Sol2 2.2). Is there a driver to support both? Our current wrapper supports the following commands: ibConfig, ibFind, SendIFC, Send & Receive.
Thanks in advance,
Paul

Hey Paul,
Unfortunately, we do not offer a driver that will support the PCI-GPIB and the ENET at the same time. In order to use the ENET you will need to use NI-488.2 Version 1.4 (http://digital.ni.com/softlib.nsf/websearch/67f3a445bc3b87c3862569f2005855d9?opendocument).
We recommend you do not install both of these drivers at the same time, because each driver was designed to run independently and some of the files would be overwritten.
However, the functions will be the same for both drivers, so the code you�re developing should be interchangeable. There are a few additional functions the ENET supports, but they are just used to get information about the ENET and do not need to be in your application. The only difference is that you will need to link t
he code to a different library when it is compiled. This information is located inside of the getting started guide.
http://www.ni.com/pdf/manuals/322989a.pdf
I hope this helps out.
JoshuaP
National Instruments

GPIB and serial port communication errors via an executalbe file.

I have a data acquisition program that communicates with instruments via the serial port and GPIB bus. When I create an executable file and run it on another PC I get GPIB and serial port errors when the program tries to initialize these ports. Are there additional vi's I need to include when I build the executable?

When you installed the GPIB board on the other pc, did you install just NI-GPIB? Did you configure the GPIB board? You also need NI-VISA if your're using VISA calls in your program. You can either install the full NI-VISA or just the run-time version.

GPIB and K1944A

Hi,
I'm actually using a GPIB and a voltmeter ( KETHELEY). I generate a signal (sine for instance) thanks to a frequency generator and I want to acquire it with the voltmeter and send measures through the GPIB to plot them on a graph.
I want to give you an extract of the code where I have troubles to understand :
short k1944a_device (void) { return bd; }
short k1944a_ready (void)
short i;
do { ibwait (bd, 0x4800); ibrsp (bd, &sp); i++; }
while ((!(sp & 16))&&(i<10));
if (i==10)
MessagePopup ("", "Le volmËtre ne rÈpond plus");
return 0;
return 1;
short k1944a_ecrire (char *texte)
short ok;
ibwrt (bd, texte,(long)strlen(texte));
ok=k1944a_ready ();
if (ok==0) return 0;
return 1;
When I run the code and click and the button acquire the programm freezes and I can read in RUN TIME window the following error:
NON-FATAL RUN-TIME ERROR : "K1944lab.c",line38,col5,trhead id 0x0000234: Function ibwrt(iberr == 6(0x6))
Moreover, when I try to run the code I get this message : NON-FATAL RUN-TIME ERROR..... Local 'i' was referenced before being initialized. Should I absolutely initialize it?

Hi,
Thanks for posting on NI Forum.
You can find at this link a possible solution to your problem.
Best regards,
Nicolas M.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées Techniques LabVIEW 2012 : du 27 septembre au 22 novembre
2 sessions en parallèle : Débuter a...

GPIB and Serial together

Is it possible to control GPIB and read off a serial
port at the same time ? I need to read off the serial
port before any GPIB function takes place
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

In article <7s8orv$t4p$[email protected]>,
[email protected] wrote:
> Is it possible to control GPIB and read off a serial
> port at the same time ? I need to read off the serial
> port before any GPIB function takes place
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
Hi,
If the serial ports are not connected to the same instrument, it is
possible to.
If the serial port is connected to the instrument where GPIB is
connected, it is possible to ... but not with all gpib instruments: I
use one witch must be configured for serial communication 0R GPIB
communication but not both at the same time.
Laurent.
Sent via Deja.com http://www.deja.com/
Before you buy.

ECATT and Mercury QTP integration.

Hi All,
We are evaluating the SAP eCATT and Mercury integration part for one of our project. So we have downloaded the following:
1. Mercury QTP version 9.1 (14 day trial version)
2. Mercury SAP Addin.
The SAP status is as follows:
1. SAP 4.7 Versions.
(a)SAP BASIS at patch level 48
(a)SAP ABAP at patch level 45
(a)SAP APPL at patch level 20
2. SAP Logon For Windows ( 640 Final Release ) ,Patch level - 23.
We have done the entire configuration at the SAP level like
1. Making "sapgui/user_scripting" value TRUE.
2. Creation of entry in ECCUST_ET table.
3. Also created the user ECATT_ET_USR with the necessary Roles.
After doing all this, when the ECATT is created with the "External Tool" option as "Mercury Quicktest Professional" it gives an error that
"Quicktest Professional is Not installed or Does not have license"
Please let us know whether we are missing any component which needs to be installed or if any other config is missing.
Regards,
Rupesh.

Hi Kalyan,
SAP eCATT is a automation tool meant for functional testing in SAP. It comes with WAS. Latest version is WAS 6.40. It is made in ABAP.
QTP is Mercury's tool, which is a third party tool for automation testing. The language used here is VB Script.
Both the tools are good. But the only drawback with eCATT as of now is that it can execute web based SAP transactions except web dynpro. So if the testing of SRM, CRM etc is involved, one is forced to use QTP.
QTP takes the wrapping of eCATT and executes in SAP.
If only SAPGUI based transactions are involved in testing than eCATT is the best tool to be used. And if web based transactions are also involved, forced to go for QTP.
Hope this clears your query.
PS If the answer solves your query, plz close the thread by rewarding each reply.
Regards
Sapna Modi

GPIB and vfp

Anybody out there used vfp to communicate with a GPIB card. I need to get
started and am having trouble with viOpenDefaultRM(). I know I need to use
the declare dll command but thats about it. What is &defaultRM is this a
pointer to a string? or is it somethig I need to define.
Thanks for any help or suggestions.
Denis

In article <7s8orv$t4p$[email protected]>,
[email protected] wrote:
> Is it possible to control GPIB and read off a serial
> port at the same time ? I need to read off the serial
> port before any GPIB function takes place
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
Hi,
If the serial ports are not connected to the same instrument, it is
possible to.
If the serial port is connected to the instrument where GPIB is
connected, it is possible to ... but not with all gpib instruments: I
use one witch must be configured for serial communication 0R GPIB
communication but not both at the same time.
Laurent.
Sent via Deja.com http://www.deja.com/
Before you buy.

Lc8901a(Gpib) and 3512(ADC) fast polling repost. Labwindows CVI(on a win98 machine)

Okies I made a this lowlevel try to get a controlled
poll. I only pull 2 bytes but still its slow(around
60 polls per second). I also made some attempts with the IVI driver, which isn't workin that good either.
mabe i'm doing things in the wrong order, any poiters would be welcome.
---------8<------------- code
#include
#include
* This program initalizes and accesses the buffer data in the ADC 3512 by *
* CAMAC access. *
*Switch settings are equal to 4.1.2.2 in ADC manual with internal switch * *
* set for internal buffer mode. Rear jumper set LAM active with * *
* 2 bytes in buffer. *
#include
#include
#include
char GetSerialPollResponse(int);
int initalizeboard(void);
int initalizedevice(void);
void SetupADC(int);
short GetSRQ(int);
static int MyDev;
static int Myboard;
unsigned int MyRead[1] = {0};
unsigned int MyRetn[1] = {0};
int main()
int r, c,k=0,g,h;
short srqq;
unsigned int a;
double volts;
Myboard = initalizeboard();
MyDev = initalizedevice();
SetupADC(MyDev);
//srqq gets status of SRQ wait either 1 or 0
srqq = GetSRQ(MyDev);
g=time(0)+5;
//if srqq is not 1 there is no data to be read the program will end
if (srqq == 1)
do{
h=time(0);
if (srqq==1)
//if(1)
//initiates destructive read of 3512 buffer.
ibwrt (MyDev, "\x02\x00\x11", 3);
ibrd (MyDev, MyRead, 2);
k++;
//initializes LAM for 3512
// ibwrt (MyDev, "\x1a", 1);
// ibrd (MyDev, MyRetn, 2);
//gets status of SRQ signifing data is ready to be read.
srqq = GetSRQ(MyDev);
//If srqq is not 1 again the program will end
}while (h }
a = MyRead[0] & 8191;
// a = MyRead[1] & 8191;
printf("%d :: %8.3f\n",k,a*.0009884);
scanf("%d",&r);
return 0;
int initalizeboard()
//Initalizes the gpib board (not 8901a)
Myboard = ibfind ("gpib0");
ibpad (Myboard, 0);
ibrsc (Myboard, 1);
ibsic (Myboard);
ibsre (Myboard, 1);
//disables autoserial polling so the status of SRQ can be utilized.
ibconfig (Myboard, IbcAUTOPOLL, 1);
return Myboard;
int initalizedevice()
MyDev = ibdev (0, 2, NO_SAD, T10s, 1, 0);
//clear CAMAC
ibwrt (MyDev, "\x22", 1);
ibrd (MyDev, MyRetn, 2);
//assert inhibit (no data collection)
ibwrt (MyDev, "\x48", 1);
ibrd (MyDev, MyRetn, 2);
//set up for high speed block read 16bit
ibwrt (MyDev, "\x6A", 1);
ibrd (MyDev, MyRetn, 2);
//initalized CAMAC
ibwrt (MyDev, "\x21", 1);
ibrd (MyDev, MyRetn, 2);
return MyDev;
void SetupADC (int MyDev)
//clears LAM and buffer
ibwrt (MyDev, "\x0a\x00\x11", 3);
ibrd (MyDev, MyRetn, 2);
//enables LAM
ibwrt (MyDev, "\x1a\x00\x11", 3);
ibrd (MyDev, MyRetn, 2);
//writes control register settings (current 2120h)(least signif 1st)
ibwrt (MyDev, "\x10\x00\x11\x20\x21", 5);
ibrd (MyDev, MyRetn, 2);
short GetSRQ (int MyDev)
short e, f;
char d = 0;
//enables SRQ on occurance of LAM
ibwrt (MyDev, "\x41", 1);
//waits for SRQ (data is available)
WaitSRQ (0, &e);
//runs serial poll
//ibrsp (MyDev, &d);
//disables SRQ and clears Inhibit
ibwrt (MyDev, "\x40", 1);
//sends interface clear
ibsic (Myboard);
return e;
okies this polls, and works with SRQ/LAM but slow, very slow.
Ibspy log.
---------------------8<-------------
1. ibfind(gpib0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:15.810 Call Duration: 00:00:00.170
ibsta: 0x100 iberr: 0 ibcntl: 0(0x0)
2. ibpad(GPIB0, 0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:15.980 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 0(0x0)
3. ibrsc(GPIB0, 1)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:15.980 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 1 ibcntl: 0(0x0)
4. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:15.980 Call Duration: 00:00:00.050
ibsta: 0x130 iberr: 0 ibcntl: 0(0x0)
5. ibsre(GPIB0, 1)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.030 Call Duration: 00:00:00.000
ibsta: 0x130 iberr: 0 ibcntl: 0(0x0)
6. ibconfig(GPIB0, IbcAUTOPOLL (0x0007), 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.030 Call Duration: 00:00:00.000
ibsta: 0x130 iberr: 1 ibcntl: 0(0x0)
7. ibdev(0, 2, 0 (0x0), T10s (13), 1, 0x0000)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.030 Call Duration: 00:00:00.060
ibsta: 0x100 iberr: 0 ibcntl: 0(0x0)
8. ibwrt(UD0, """, 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.090 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
9. ibrd(UD0, "#%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.090 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
10. ibwrt(UD0, "H", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.090 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
11. ibrd(UD0, "'%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.090 Call Duration: 00:00:00.050
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
12. ibwrt(UD0, "j", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.140 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
13. ibrd(UD0, "'%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.140 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
14. ibwrt(UD0, "!", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.140 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
15. ibrd(UD0, "#%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.140 Call Duration: 00:00:00.060
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
16. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.200 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 3(0x3)
17. ibrd(UD0, "..", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.200 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
18. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.250 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 3(0x3)
19. ibrd(UD0, "..", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.250 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
20. ibwrt(UD0, "... !", 5 (0x5))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.250 Call Duration: 00:00:00.060
ibsta: 0x100 iberr: 0 ibcntl: 5(0x5)
21. ibrd(UD0, "..", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.310 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
22. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.310 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
23. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.360 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 1(0x1)
24. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.470 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
25. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.470 Call Duration: 00:00:00.060
ibsta: 0x170 iberr: 0 ibcntl: 5(0x5)
26. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.530 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
27. ibrd(UD0, "#%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.530 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
28. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.580 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
29. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.580 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
30. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.640 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
31. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.640 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
32. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.690 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
33. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.750 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
34. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.750 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
35. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.800 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
36. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.800 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
37. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.860 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
38. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.860 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
39. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.910 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
40. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.910 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
41. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.970 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
42. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.020 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
43. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.020 Call Duration: 00:00:00.060
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
44. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.080 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
45. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.080 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
46. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.130 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
47. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.190 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
48. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.190 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
49. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.190 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
50. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.240 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
51. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.300 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
52. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.300 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
53. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.350 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
54. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.350 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
55. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.400 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
56. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.460 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
57. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.460 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
58. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.510 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
59. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.570 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
60. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.570 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
61. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.620 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
62. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.620 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
63. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.680 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
64. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.680 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
65. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.730 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
66. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.790 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
67. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.840 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
68. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.840 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
69. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.900 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
70. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.900 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
71. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.950 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
72. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.950 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
73. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.010 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
74. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.060 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
75. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.120 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
76. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.120 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
77. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.170 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
78. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.170 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
79. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.230 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
80. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.280 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
81. ibrd(UD0, "%%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.340 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
82. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.340 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
83. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.390 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
84. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.390 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
85. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.450 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
86. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.500 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
87. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.560 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
88. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.560 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
89. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.610 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
90. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.670 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
91. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.670 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
92. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.720 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
93. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.780 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
94. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.830 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
95. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.890 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
96. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.890 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
97. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.940 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
98. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.000 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
99. ibrd(UD0, "%%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.000 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
100. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.050 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
101. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.110 Call Duration: 00:00:00.050
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
102. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.160 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
103. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.220 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
104. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.270 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
105. ibrd(UD0, "%%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.270 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
106. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.330 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
107. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.380 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
108. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.440 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
109. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.440 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
110. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.490 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
111. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.550 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
112. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.600 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
113. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.600 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
114. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.660 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
115. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.710 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
116. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.770 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
117. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.770 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
118. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.820 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
119. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.880 Call Duration: 00:00:00.050
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
120. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.930 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
121. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.990 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
122. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.040 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
123. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.040 Call Duration: 00:00:00.170
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
124. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.210 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
125. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.260 Call Duration: 00:00:00.110
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
126. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.370 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
127. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.430 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
128. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.540 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
129. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.590 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
130. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.700 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
131. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.810 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
132. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.870 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
133. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.920 Call Duration: 00:00:00.060
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
134. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.980 Call Duration: 00:00:00.100
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
135. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.080 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
136. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.190 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
137. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.250 Call Duration: 00:00:00.050
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
138. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.360 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
139. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.410 Call Duration: 00:00:00.060
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
140. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.520 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
141. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.580 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
142. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.690 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
143. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.800 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
144. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.850 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
145. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.910 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
Well thats about it. I'm going nowhere in getting this crate working controlled and fast, so any help woul be
appriciated.
/Anders

It's to slow, I was expecting an output of atleast 20-50kHz, shure this code performance will increase somewhat if i pull the maximum of 1024 words but still the code is too slow. Is there any shortcuts you can make? What I want is to get data as fast as possible.
/Anders

Why do error comes when trying to use NI ISA GPIb and NI DAQ card (both PnP)together while they work well when one at a time?

we configured gpib pnp and at-mio-64e3 cards (isa) in the same pc.gpib function was invoked to take the device to remote and listen mode.now when daq function getDeviceInfo is called the remote mode of the device is removed and after this it always shows no gpib board until pc is rebooted

Hi,
I have some questions:
What OS are you using?
What driver versions?. You can find the driver versions in the Windows Add/Remove programs utility. DAQ driver is NI-DAQ anmd GPIB driver is NI-488.2.
Is there any error code?
I haven't found any known issues between these two drivers. How are the board's resources configured? Base address, IRQ, DMA.
Let see if with this information we can clear out what is going on.
DiegoF.

GPIB and Desktop RT

I am running the following:
Desktop Labview Real Time 11.0
NI-VISA Server 5.1
and am using an NI PCI-GPIB card to connect to a couple of different pieces of lab equipment.
When I connect to this remote system from another workstation using MAX, I do see GPIB0 (PCI-GPIB) under devices and Interfaces on the RT machine, but I cannot figure out how to see the GPIB instruments that are connected to the bus.
I don't think it is a electrical problem on the bus because when I boot the workstation into windows instead of RT, I can see the instruments just fine using Max on that machine.
Rick
PS: The workstation I use to connect to the RT machine remotely runs a current version of Labview
Rick Foster
MIT Kavli Institute for Astrophysics and Space Research
Solved!
Go to Solution.

The current VISA Interactive Control layout is a bit differenent from the tutorial.
I do see the instruments now, but they are listed under localhost and I get an error when I try to list them on the remote machine that the GPIB controller is installed in.
I can now access the instruments in my code, but this Localhost versus Remote machine bit is confusing.
Rick
Rick Foster
MIT Kavli Institute for Astrophysics and Space Research

GPIB and Mercury WinRunner

Similar Messages

Maybe you are looking for