AnsweredAssumed Answered

vrf Panel Driver

Question asked by VRFuser on May 26, 2003
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><META http-equiv=Content-Type content="text/html; charset=iso-8859-9"><XETA content="text/html; charset=iso-8859-9" http-equiv="Content-Type"><XETA content="MSHTML 6.00.2600.0" name="GENERATOR"><STYLE></STYLE><META content="MSHTML 6.00.2800.1170" name=GENERATOR></HEAD><BODY style="COLOR: #000000; FONT-FAMILY: " bgColor=#ffffff><DIV><FONT face=Arial><FONT size=2><SPAN class=008223219-27052003> >  </SPAN>From the previous messages,  I have understood that we can create Panel Drivers for VEE.<SPAN class=008223219-27052003> </SPAN></FONT></FONT></DIV><DIV><FONT><FONT face=Arial><FONT size=2><SPAN class=008223219-27052003>>  </SPAN> But noone has ever mentioned how to accomplish this. Does anyone out there know how to<SPAN class=008223219-27052003> </SPAN></FONT></FONT></FONT></DIV><DIV><FONT><FONT face=Arial><FONT size=2><SPAN class=008223219-27052003>>  </SPAN> create Panel Drivers (as far as I remember, the cid files)?</FONT></FONT></FONT></DIV><BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003> Ohhh,   bringing up memories from the old days.  At one time I taught the   "How to write a driver" course.</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>The easiest way to   write a driver is to find one that does something close to what you want to   do,</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>then modify   it/study it for your instrument.</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>(IIRC, the driver   writer tool does fine for simple things, but if there are complex interactions   between</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>controls you will   have a problem.)</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>Get the .id   version of the driver.  The .cid is the compiled version - you can't edit   it.  VEE automatically</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>makes the .cid   from the .id.  The .id version </SPAN></FONT><FONT face=Arial   size=2><SPAN class=008223219-27052003>can be edited in a text editor.    The language is "forth like", </SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>but something all   its own. </SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>There are two main   sections of the driver:</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>   1)   Component section</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003>        A) Tells   the type of each component</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003>        B) Gives   the SET ACTIONS - what to do if the value is changed.</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003>                i) PANEL SET ACTIONS - can give separate actions if the panel is being   displayed - such as update other components</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003>        C) Gives   the GET ACTIONS - how to query the instrument for the value</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>      2) Panel section</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003>         A)   How to display the information</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>That's the first 5   minutes of the course.  The course went on for 2 or 3 days.  A bit   big to discuss here.  </SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>The problems come   in when you have "coupled" actions - such as setting aperture causes   readings/sec to change, or</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>when you have   multiple parameters for a command (when do you send the command - each time a   parameter is</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>changed, or wait   until all have been entered?)  On the other hand, you can use the   language to do some rather</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>trick stuff.    </SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003>"Complete  Test" is available to consult or   to write a driver for you.  It can get a bit expensive though.  A   complicated</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>scope or network   analyser can take 3 months or more to develop.  At $90/hour that adds   up. </SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>(As far as other   posts asking about what revision the Driver Writing Tool was made for,   HP/Agilent abandoned work</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>on the Classic   Panel Drivers in 1995 when things were switched to Plug&Play.  But   the Driver Engine was kept intact.</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>If it worked in   1995, it should be just as good today.)</SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN   class=008223219-27052003></SPAN></FONT> </DIV>  <DIV><FONT face=Arial size=2><SPAN class=008223219-27052003>  <P><FONT size=2>Les Hammer<BR>VP Engineering<BR>Complete Test<BR>720 SW 14th   St.<BR>Loveland, CO.  80537<BR>Les.Hammer@CompleteTest.com   </FONT></P></SPAN></FONT></DIV></BLOCKQUOTE>---<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@it.lists.it.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