AnsweredAssumed Answered

vrf Dynamic I/O configuration of new type instrument (TCPIP, USB) in

Question asked by VRFuser on Mar 24, 2004
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"><TITLE>.NET in VEE7</TITLE><META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD><BODY><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004>Hi, all.</SPAN></FONT></DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004></SPAN></FONT> </DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004>I would like to offer my point of view on new VEE7.</SPAN></FONT></DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004></SPAN></FONT> </DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004>In my humble opinion the major disadvantage of VEE7 is impossibility to use all available VISA type address for one I/O object. There are TCPIP direct I/O object that allows using only TCPIP type addresses as well as USB direct I/O that allows using only USB type addresses. GPIB direct I/O object allows use only SICL type addresses. In is the reason that end user has got big trouble with dynamic I/O configuration. Some additional headache is using Agilent LAN-GPIB gateway since VISA resource manager returns instrument address in VISA  LAN client interface format (like GPIB1::3::INSTR)  however in VEE in is possible to use SICL format (for using SICL format it is necessary to know TCPIP address of Agilent LAN-GPIB gateway) or VXI11.2  format (like TCPIP::host address::gpib0,5::INSTR).</SPAN></FONT></DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004></SPAN></FONT> </DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004>Concerning discussion about .NET. I am agree that .NET is very powerful but developing any complicated .NET code in VEE is very difficult task since there is no debugger as well as for finding any help information it is necessary to visit Microsoft web site. In my humble opinion developing .NET code in Microsoft Visual studio is the best approach. Present VEE7 is fit very well only for testing some communication algorithm with instruments.</SPAN></FONT></DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004></SPAN></FONT> </DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004>Unfortunately T&M toolkit forum on Agilent web site is not a place where it is possible to get answer for some questions.</SPAN></FONT></DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004></SPAN></FONT> </DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004>With best regards,</SPAN></FONT></DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004></SPAN></FONT> </DIV><DIV><FONT face=Arial color=#0000ff size=2><SPAN class=125304314-24032004>Mikhail Kozlov </SPAN></FONT></DIV><FONT face=Arial color=#0000ff><SPAN class=125304314-24032004></SPAN></FONT><FONT face=Tahoma><DIV><FONT face=Arial color=#0000ff size=2></FONT><FONT face=Arial color=#0000ff size=2></FONT><BR> </DIV></FONT>---<BR>You are currently subscribed to vrf as: rsb@soco.agilent.com<BR>To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".<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 "owner-vrf@it.lists.it.agilent.com".</BODY></HTML>  

Outcomes