SignalExpress

cancel
Showing results for 
Search instead for 
Did you mean: 

SignalExpress: change IVI power supply setting during test

How do I change the IVI power supply setting in the middele of a test?  I want to have the power supply switch from 20 Vdc to 30 Vdc after about 10 minutes of the run.
0 Kudos
Message 1 of 5
(6,698 Views)
This should be possible using the Sweep step and the Execution Control tab on the IVI Power Supply. The idea being:
Drop the Sweep and Add the condition to sweep the Voltage level from 20 to 30 in 2 points.
Then on the IVI Power Supply step, go to the Execution Control tab and add a Post-execution delay. Since it's in ms, to do 10 mins would be 600000.
 
Let us know if that works for you, we'd never tried such a slow sweep.
0 Kudos
Message 2 of 5
(6,689 Views)

It's working but I had to do things just a little different. I set the SWEEP to a start of 20 Vdc and a stop of 20 Vdc with 2 points.  It didn't seem to make any difference what the stop value was set to.  I tired several stop values.   For the IVI Power Supply I set the Configuration tab to 30 Vdc.  On the Trigger Tab I set the voltage to 30 Vdc and Immediate trigger.  On the Execution Tab I set the pre-execution delay to 10,000 (10 second delay for just testing setup).  I had to leave the post-execution delay set to 0.

The power supply is a Agilent E3645A.  The driver is hpe364xa.  I'm using SignalExpress 2.0

0 Kudos
Message 3 of 5
(6,680 Views)

I just made a change.  I set the SWEEP to: Type: "List of Points" and set the value to 20.00.  The IVI Power Supply was left the same as before. See above.  It still works fine.

0 Kudos
Message 4 of 5
(6,675 Views)
Thanks for pointing this out. After finding an Agilent power supply to test with I noticed that SignalExpress is not working correctly with this instrument due to setup of the triggering. As you noticed, the voltage level is always being pulled from the setting on the Trigger page, instead of the intended control on the Configuration page. We will investigate this and ensure that it is fixed in an upcoming version. For the time being, your solution sounds like the right workaround.
0 Kudos
Message 5 of 5
(6,667 Views)