AnsweredAssumed Answered

vrf AW: File transfer over GPIB == * as READ BINARY until

Question asked by VRFuser on Jan 13, 2003

after getting this response (thanks to Bruno) I read the manual again, and
here it is mentioned as you described
(* is only working for some special read (e. g. read from file), but not for
Read from GPIB).

So the only solution I found so far is to read byte by byte until an error
occurs. This works fine,
but it takes a long time until the sequence is finished.

Any better idea how to utilze the binblock read ?



Infineon Technologies
Hermann Ruckerbauer
MP TI PD DES 5 / MchB / Room 3448
Balanstrasse 73
D-81541 Munich
Phone:          +49 (89) 234 25041
Fax.:           +49 (89) 234 715757

-----Ursprngliche Nachricht-----
Von: Beliveau, Bruno []
Gesendet am: Montag, 13. Januar 2003 22:49
An: VEE vrf
Cc: VEE vrf
Betreff: [vrf] Re: File transfer over GPIB ==> * as READ BINARY until EOF
not possible ????

With a file I/O transaction, you click on the "Size:" button and it changes
to "To End" (and the quantity to "*").  With a GPIB I/O transaction, the EOF
is not defined (not to my knowledge), so the same trick does not work.

-----Message d'origine-----
De: [
<> ]
Date: 13 janvier 2003 08:19

I have tried the program send by Phil (thanks a lot, see his mail below),
but my VEE (v6) is reporting an error, when it detects a # sign in the
data flow. So I tried the pure binary transfer.
This works fine, if I do know, how much data is transfered, as I can give
the size of the 1dim array I'm going to transfer.
unfortinally I do not know how big the file is I would like to transfer.

Therefore I took a look to the advanced programming guide which says on page

526 that a * will do a read binary until EOF. But when trying to write a
into the corresponding "NumElements" field of the direct IO object VEE is
reporting a syntax error, when pressing OK to accept the command!

Is this a bug OR something wrong in the handbook OR am I just to stupid do
use it correct ????

-----Ursprngliche Nachricht-----
Von: Phil McRevis [
<> ]
Gesendet am: Dienstag, 10. Dezember 2002 15:48

Perhaps this will help, but PLEASE excuse me if this attachment is not
appropriate.  Even though my days of code development are largely over, I
can't break away from looking at this group every now and then.  Is this
group similar to crack?  Maybe.  Gotta get a fix!

Anyway, I used to use this program to transfer scope images via gpib.  While

I don't have a licensed copy of VEE at my disposal right now to verify this
attachment (I suppose I could look at it in notepad), I recall using a
binblock transfer to accomplish this task.

Obviously, some customization will be necessary based on the potential
unique commands of your individual scope(s), but that should be a simple
investigation.  First issue the command in an I/O transaction object to send

the scope image, then perform a binblock read of byte array format.

I also recall preferring this simple little program because I didn't like
the dependence of IntuiLink.  Hey, if I can get the job done with one or two

simple VEE objects, why bog myself down with IntuiLink?

>From: "Jay Nemeth-Johannes" <>
>Reply-To: "Jay Nemeth-Johannes" <>
>I think you will need to be more specific in order to get an answer.
>IntuiLink for the scope uses a set of documented scope commands for
>transferring a bitmap screen image.  The spectrum analyzers use a similar
>capability for a printer dump and then interpret the pcl codes to recreate
>the image.  In both cases, the commands to get the screen image exist in
>the instrument.
>If you want the same thing for a non-Agilent instrument, you are going to
>have to read the programming manual and see if the capability exists.  If
>it doesn't, which is often the case, your only option is to pull the trace
>data and manually create the rest of the screen with an external graphics
>pack and then re-import.
>-----Original Message-----
>From: Dale Hauck [
<> ]
>Sent: Wednesday, December 04, 2002 1:32 PM
> Specifically image files, screen capture from an instrument.
>Agilent uses Intuilink to overcome this. What can we do for non- Agilent
>instruments? I am unable to get source code for Intuilinks screen capture.
> The key seems to be in editing the header information to reflect the
>appropriate file format.

You are currently subscribed to vrf as:
To subscribe send a blank email to "".
To unsubscribe send a blank email to "".
To send messages to this mailing list, email "".
If you need help with the mailing list send a message to

You are currently subscribed to vrf as:
To subscribe send a blank email to "".
To unsubscribe send a blank email to "".
To send messages to this mailing list,  email "". 
If you need help with the mailing list send a message to "".