"Ibrahim OZKAN <iozkan@aselsan.com.tr> wrote:
> Hi all,
> I'm working with Agilent 6012A oscilloscope. I'm trying to develop
> panel drivers for this oscilloscope. Can anyone help me about how to
> create .id files? Is there any documentation that may help? Thank you.
The programming manual for ITG drivers should be available as a download on Agilent.com. At least it used to be there.
Also there's a Driver Writing Tool which is very useful for learning the language and was included with older versions of VEE.
This is a compiled language, so after you write the driver compile it using "idc.exe" which should be extent in your VEE install.
That will create the ".cid" that VEE can use.
rgeards
Stan
--------------------------------------------------------------------------
Stan Bischof Agilent Technologies 707-577-3994 stan_bischof@agilent.com
--------------------------------------------------------------------------
---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
> Hi all,
> I'm working with Agilent 6012A oscilloscope. I'm trying to develop
> panel drivers for this oscilloscope. Can anyone help me about how to
> create .id files? Is there any documentation that may help? Thank you.
The programming manual for ITG drivers should be available as a download on Agilent.com. At least it used to be there.
Also there's a Driver Writing Tool which is very useful for learning the language and was included with older versions of VEE.
This is a compiled language, so after you write the driver compile it using "idc.exe" which should be extent in your VEE install.
That will create the ".cid" that VEE can use.
rgeards
Stan
--------------------------------------------------------------------------
Stan Bischof Agilent Technologies 707-577-3994 stan_bischof@agilent.com
--------------------------------------------------------------------------
---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
generating a new file at some periodic interval (i.e. midnight). I have
settled on a method that combines suggestions and appears to meet my
needs. I'm generating a number of data files simultaneously and I didn't
want the application spending more time than necessary determining if it
was time for initializing new files. Clearly, every new file needs a
new name so using the time to generate the names on each file entry pass
does the trick but including "Build_Filename" as part of each file
generation thread seemed excessive.
Alternatively, in independent thread could generate the time dependent
part of each file name and the individual file threads could each simply
add their unique portion. This would seem to save some time but this new
thread would need to run frequently in order to catch the time interval
transition.
The solution I'm experimenting with adds a simplified version of the
concept Shawn suggested; it calculates the number of seconds until the
next file initialization time and uses this value to set a delay. When
the delay time expires, the variable part of the file names is generated
and, when used by each file thread, new files are started automatically.
This approach appears to work perfectly, at least for my incoming data
rates. Also, I've noticed that when looking at the CPU loading, I can't
see any difference between using this method and simply allowing
individual files to grow indefinitely.
The attached example shows the method for hourly initializations but
only deals with one data file and therefore uses a simple
"BuildFileName" method.
One final point - for my purposes, I seem to be able to get away with
closing each file after each entry. If I didn't do this, old files would
remain open unless a "new file name" test corrected this situation (see
Mike Asbery's "New File at Midnight" response).
Barrie
whoi
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Â
I now built up a small program which just sends MEAS:CURR:DC? to the 34401a on address 22.
As the built-in instrument manager of VEE told me (*checked it* by *IDN?) that I have two interfaces GPIB14 with 1422 and GPIB32 with 3222 -although I have only one interface built in, I'm quite sure about that!- , I took this all into the attached program. On both interfaces, the 34401a (after power on) went to DC-Current as ordered and took a measurement. The IO stopped after the talker-addresing of 22 (TALK 22) and a timeout-message came.
The instrument went into ERROR -410 when I started the program a new, because the outputbuffer was not emptied yet. This understandable. So I had to turn off power of the instrument and start allover again.
Â
I cannot understand, why there are two different interfaces present, with only one built in and why does only the sending work and not the receiving of data.
Â
Maybe somewhere in the *VEE-World* there is someone who may help me.
Please don't tell me to throw the computer into my dustbin, it is only 6 months old!
Â
Peter Weber
HYPERLINK "http://www.pcmess.com"www.pcmess.com
Birkenweg 8, D-87677 Stoettwang
Tel: +49(0)8345-482
Wir halten unseren Internetzugang sauber mit Symantec-Produkten in der jeweils neuesten Version. Dies auch bei allen E-Mails.
We keep our internet connection clean using Symantec products of the latest version. This applies also to all e-mailing.
---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Â
The first interface (1422) is built into the functionality of VEE to call the NI 488.2 GPIB drivers directly. The select code 14 corresponds to board 0, 15 to board 1, 17 to board 2, 18 to board 3. This was implemented back in the original versions of VEE-PC to be able to use the NI GPIB cards to talk to instruments.
Â
The second interface (3222) is a new function of the I/O Libraries to allow Agilent VISA/SICL to pass-through commands to the NI 488.2 libraries. At around the same time the NI libraries also contained a pass-through feature to allow the NI drivers to call Agilent GPIB cards.
Â
It appears from the GPIBREP.txt file that you are using a GPIB card that emulates the NI software by supplying it's own GPIB-32.dll. What may be occurring is that the supplied DLL is not implemented exactly the same as the NI version of the DLL, or at least requires some functionality that VEE does not call and is not required by the NI driver. But the VISA layer calls work since the supplied visa32.dll (as they list as 32-bit Forwarding VISA DLL) must comply with the industry defined VISA function calls/parameters.
Â
One thing I have found over the years is that some instruments will respond to *IDN?, *STB?, and other standard function calls when not in remote mode, but will not respond to all other commands. Is the voltmeter going into remote operation mode? If not try performing a execute remote to the instrument first, or check if the supplied GPIB software has a setting to assert REN when SC (this is a software setting NI supplied software ahs available to set).
Â
Thanks,
Â
Lyle
Â
Â
Â
Â
Lyle Carnahan
Aerospace and Defense Sector
M/A-COMÂ Inc.
1011 Pawtucket Boulevard
Lowell, MAÂ 01853-3295
Phone: (978) 442-4504
Fax:Â Â (978) 442-4409
carnahal@tycoelectronics.com
-----Original Message-----
From: piwi@pcmess [mailto:piwi@pcmess.de]
Sent: Thursday, August 31, 2006 10:02 AM
To: VRF
Subject: [vrf] Again: Problem with GPIB: logical unit (again the third)
Hi folks, this drives me crazy!!!?###@@@
Â
I now built up a small program which just sends MEAS:CURR:DC? to the 34401a on address 22.
As the built-in instrument manager of VEE told me (*checked it* by *IDN?) that I have two interfaces GPIB14 with 1422 and GPIB32 with 3222 -although I have only one interface built in, I'm quite sure about that!- , I took this all into the attached program. On both interfaces, the 34401a (after power on) went to DC-Current as ordered and took a measurement. The IO stopped after the talker-addresing of 22 (TALK 22) and a timeout-message came.
The instrument went into ERROR -410 when I started the program a new, because the outputbuffer was not emptied yet. This understandable. So I had to turn off power of the instrument and start allover again.
Â
I cannot understand, why there are two different interfaces present, with only one built in and why does only the sending work and not the receiving of data.
Â
Maybe somewhere in the *VEE-World* there is someone who may help me.
Please don't tell me to throw the computer into my dustbin, it is only 6 months old!
Â
Peter Weber
HYPERLINK "http://www.pcmess.com"www.pcmess.com
Birkenweg 8, D-87677 Stoettwang
Tel: +49(0)8345-482
Wir halten unseren Internetzugang sauber mit Symantec-Produkten in der jeweils neuesten Version. Dies auch bei allen E-Mails.
We keep our internet connection clean using Symantec products of the latest version. This applies also to all e-mailing.
---
You are currently subscribed to vrf as: carnahal@tycoelectronics.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
</span></font><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;color:navy'>Jon Griggs</span></font><font color=navy><spanstyle='color:navy'> <o:p></o:p></span></font></p><p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:5.0pt;margin-left:0in;text-autospace:none'><font size=3 color=navyface="Times New Roman"><span style='font-size:12.0pt;color:navy'><ahref="mailto:jgriggs@crownintl.com"><font size=2 face=Arial><spanstyle='font-size:10.0pt;font-family:Arial'>mailto:jgriggs@crownintl.com</span></font></a><o:p></o:p></span></font></p><p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:5.0pt;margin-left:0in;text-autospace:none'><font size=2 color=navy face=Arial><spanstyle='font-size:10.0pt;font-family:Arial;color:navy'>Test Engineer </span></font><fontcolor=navy><span style='color:navy'><o:p></o:p></span></font></p><p class=MsoNormal style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:5.0pt;margin-left:0in;text-autospace:none'><font size=2 color=navy face=Arial><spanstyle='font-size:10.0pt;font-family:Arial;color:navy'>Crown International</span></font><fontcolor=navy><span style='color:navy'>
</span></font><st1:address w:st="on"><st1:Street w:st="on"><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial; color:navy'>1718 West Mishawaka Road</span></font></st1:Street><font color=navy><span style='color:navy'>
</span></font><st1:City w:st="on"><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial;color:navy'>Elkhart</span></font></st1:City><font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial; color:navy'>, <st1:State w:st="on">IN</st1:State> <st1:PostalCode w:st="on">46517</st1:PostalCode></span></font></st1:address><fontcolor=navy><span style='color:navy'> <o:p></o:p></span></font></p></div></div><BR>---<BR>You are currently subscribed to vrf as: rsb@soco.agilent.com<BR>To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list, email "vrf@agilent.com". <BR>If you need help with the mailing list send a message to<BR>"owner-vrf@it.lists.it.agilent.com".<BR>Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".</BODY></html>
The vrf archive appears to be down. I remember someone telling how to programmatically edit the field name of a record. Something about converting the record into text and replacing the name. Has anyone tried this?
Â
Regards
Â
David Watling
---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".