If you search for a Labwindows/CVI driver for the Agilent DSO5032 in IDnet , you will find the ag6000 series driver.
When using that driver i found that it seems to have some basic design problems when used with the DSO5032.
For example you can setup measurement thresholds different for every channel. But the driver seems to use only one instrument wide IVIAttribute for each of these settings. The ag6000_ConfigureRefLevels() function doesn't take a channel as parameter. So you first have to use ag6000_ConfigureMeasSource () to set the channel. And if you want to set the thresholds indentically for both channels you have to do something like that to avoid that the setup for the second channel is being suppressed by the IVI Engine :
status = ag6000_ConfigureMeasSource (Instr_Handle_Scope, "CHAN1",
"CHAN1");
status = ag6000_ConfigureRefLevels (Instr_Handle_Scope, 10.0, 50.0,
90.0);
status = ag6000_ConfigureMeasSource (Instr_Handle_Scope, "CHAN2",
"CHAN2");
status = ag6000_ConfigureRefLevels (Instr_Handle_Scope, 15.0, 50.0,
85.0);
status = ag6000_ConfigureRefLevels (Instr_Handle_Scope, 10.0, 50.0,
90.0);
Another problem seems to be that the driver holds only one global attribute for trigger level. So if you try to set trigger level for both Channel1 and Channel2 to the same value with ag6000_ConfigureTrigger () the setup for the second call will be suppressed. I.e.
status = ag6000_ConfigureEdgeTriggerSource (Instr_Handle_Scope,
"CHAN1", -3.2,
AG6000_VAL_POSITIVE);
status = ag6000_ConfigureEdgeTriggerSource (Instr_Handle_Scope,
"CHAN2", -3.2,
AG6000_VAL_NEGATIVE);
will setup Channel 1 as expected but will omit to set the trigger level for Channel 2 ( Slope will be setup, because it changes)
Are these problems known at NI ?
