LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Agilent MXA N9020A change Avg/hold num

I have created the attached vi using the Agilent MXA series instrument driver's.

 

If I change the configure trace from "Clear Write" to "Average" the MXA then sets an Avg/Hold num of 100... by the time it reaches 100 my vi has finished execution and captures no data, with the trace set to "Clear Write" it captures the data, but with no averaging. So a couple of questions, 1) how do I make the vi wait until the 100 averages to capture data? I did try inserting a "Wait for acquisition" but that did not work, 2) how do I change the number of averages "Avg/hold num"? I don't seem to be able to find a driver for this.

 

TIA

LABOR OMNIA VINCIT
0 Kudos
Message 1 of 4
(2,612 Views)

Hi Jimbo,

 

by the time it reaches 100 my vi has finished execution and captures no data,

But you should get an error instead, most probably something like TimeOut…

 

1) how do I make the vi wait until the 100 averages to capture data?

Have you tried to increase the timeout?

 

2) how do I change the number of averages "Avg/hold num"? I don't seem to be able to find a driver for this.

Have you read the (programming) manual for your device to look for the needed SCPI commands? Did you verify your driver VIs use the correct command with correct parameter formatting?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 4
(2,594 Views)

Hi GerdW tanks for your response.

 

I was in fact receiving the following error message "Maximum Time has been exceeded.", so I have increased the timeout as you suggest which has resolved issue 1, just to work out have to change the number of averages now 🙂

LABOR OMNIA VINCIT
0 Kudos
Message 3 of 4
(2,575 Views)

Also resolved the issue with number of averages "Avg/hold num"... had to move the Configure Averaging vi earlier in my sequence.

 

Attached final vi

LABOR OMNIA VINCIT
0 Kudos
Message 4 of 4
(2,560 Views)