AnsweredAssumed Answered

VRf-HPVEE makes my HP4142B shy

Question asked by VRFuser on Jul 24, 1996
Dear everybody,
     I am evaluating HP-VEE with my HP4142B, so I am a
     newbye, the question that I pose is therefore
     simple and I know that by the moment you reach the
     end of this mail you will have the answer.
     Apparently there are some situation in which
     my HP4142B, used with HPVEE, gets shy, i.e. perform the
     measurement and does not show me the data.
     
     Basically I want to use the driver of the HP4142B
     (dated 8/1/94 and ver 2.0) to build up a nice front panel,
     setting the instruments with interactive dialog
     and saving the results to a file.
     
     I am able to do all of this in "Spot Mode" (a single
     point measure) and therefore I could infere that all
     the hardware works correctly.
     
     If I try to do it in "Staircase Sweep" strange phenomena
     occurs (do notice that I measure a resistor with a ramp
     of 3-10 points, so very few data).
     With the following 'program' [see end of the mail]
     I am able to measure the resistor and, by clicking
     on the display which is "built-in" in the driver,
     I am able to see the ramp and reading
     the values with the marker; so the data do exist!
     (*)The first trouble is that when I add the "MEAS_READ" statement
     in the aforementioned 'program' (as I used in the Spot case) then,
     if I click on the display, a "timeout error" appears (do notice:
     sweep of three points).
     (**) If I try to wire something to the output, namely the variable
     "TRACE_Y" what I see, on the Logging A.N. or if I probe the line,
     is a nice Array 1D of "0", do notice that the size of the array
     varies if I vary the number of steps of the Sweep.
     This phenomena appears with or without the "MEAS_READ" statement.
     The only difference is that, WITHOUT it, after having performed
     the measurement and probed a nice set of n-zero, I am able
     to click on the display of the driver and actually see the real
     non zero value of my n-data.
     Apparently this action "pushes" the data so that the next measure
     will show no more "0" in the Log. A.N. but - forever - the results
     obtained before the "push". Mah!?
     
     Probably I am doing such a stupid and huge error that I am not
     able to see it (I have got the evaluation copy, maybe is described
     in the manuals) but before buying this software I'd like to be
     sure that it works correctly and I am really puzzled by its
     behaviour.
     
     Best regards,

Claudio De Diana --- email: sniper@tep.e-technik.tu-muenchen.de ---

voice (+49) 89 2892 3103    TU Muenchen                    
fax   (+49) 89 2892 3134    Lehrstuhl fuer Technische Elektrophysik
                         Arcisstr. 21                    
                        80290 Muenchen                    
                         Germany
                     
                         http://www.tep.e-technik.tu-muenchen.de
-------------------------------------------------------------------
-------                      MIGA BAE !                     -------
-------------------------------------------------------------------
         

     Here is the "program" for us hp4142b fans:
     slot2_enabled (1),channel_numbers(2),
     MM(1),channel_number(2),number_of_steps<inputvariable>,
     start_voltage<i.v.>,stop_voltage<i.v.>,i_compliance(high enough),
     WV(1),BC(1),XE(1),[MEAS_READ(1)],DZ(1).

Outcomes