DSO-X 2014A ReadDelayMeasurement

[Charles.Tac]

Hi,

When looking into your trace log, it is obvious that the agx2k3k_WaitForOPC function raise a time-out error. 

This is a common issue for driver. There might be three reasons to cause this error.

1. There is no physical signal or data in channel, so no matter how long the driver wait, the instrument will not return any data.

2. There is a software bug in driver. To verified this, you could invoke agx2k3k_WaitForOPC after InitializeWithOption. If no error occur, the driver is OK.

3. The acquisition operation will take a long time. We could increase the WaitTime to ensure the data is acquired before driver fetch it.

Please check the signal and have a try on 2 and 3.

Thanks,

Charles

[YGraphPopup]

Hi Charles,

Signal is exist and also increasing time does not help.

When adding error = agx2k3k_WaitForOPC (agx2k3k, 5000) after agx2k3k_InitWithOptions, than error == 0.

The DSO-X-2014A instrument has been purchesed in order to eplace the DSO1012A which have only 2 channels.

The DSO1012A is working fine with the ag1000ni drivers, this is the reason I assume the agx2k3k drivers are not match with the 2014A

Do you know other person that is using the 2014A in a remote?

Thanks 

[nyc_(is_out_of_here)]

---

@YGraphPopup wrote:

When adding error = agx2k3k_WaitForOPC (agx2k3k, 5000) after agx2k3k_InitWithOptions, than error == 0.

---

Do you understand even what this means???

It means that your Init is taking too long and that you need WaitForOPC to allow the Init to finish.

[Charles.Tac]

---

@YGraphPopup wrote:

When adding error = agx2k3k_WaitForOPC (agx2k3k, 5000) after agx2k3k_InitWithOptions, than error == 0.

---

This result proves that the WaitForOPC function of this driver is compatible with your model...

[Charles.Tac]

Actually, the way of acquiring data remotely need 5 steps:

1. Configure Parameter >>
2. Configure Trigger (In which condition will the instrument acquire data) >>
3. Init (begin to wait for the trigger condition) >>
4. WaitForOPC (Even the instrument itself does not know when the signal will match trigger condition... so we have to wait) >>
5. Read Data (if the operation is complete, then we could get the data from instrument)

I check the trace log file again and seems you are using the edge trigger mode and set the trigger level to 0.0 V. So the trigger condition will only match if the signal across the 0.0V level. Would you please check that?

Thanks,

Charles