Contact an Expert

Thread: Problems reading traces in N5242A


Permlink Replies: 2 - Pages: 1 - Last Post: Mar 12, 2012 6:34 PM Last Post By: Dr_joel
keplovic

Posts: 11
Registered: 07/15/09
Problems reading traces in N5242A
Posted: Feb 20, 2012 10:31 AM
Click to report abuse...   Click to reply to this thread Reply
Hi!

I have a TX/RX DUT which can be configured in 64 diferent states of gain and phase. I have to meas diferent phases for each gain state. I have tried different things in order to get all the S21 traces but I have always the same problem: Time out error and this problem appears in different moments but always in the same VI.

I work with Labview 2010, and this is what I do:

- STEP 1: Equipment Configuration: This step configures the instrument (PNA in this case)
- STEP 2: DUT Configuration: This Step configures the DUT (Gain and Phase)
- STEP 3: Read data: I get the trace values (Gain and Phase)

In STEP 1 I configure the PNA with two windows in the same channel. We can find the gain trace (Meas1) in the first window and the phase trace (meas2) in the second window.

Step 2 and 3 are inside a For Loop

In Step 3 I configure th trigger (Continuous), the average (3) and I clear the average. Next, I wait for the three sweeps (average) and I read the meas1 trace and meas2 trace. When I'm reading the data I'm using Read Data.vi from N.I. drivers. In this VI randomly appears the problem. (Time out problem) . I'm reading the data in FDATA format REAL32. Another thing that happens is that when I'm reading the data the PNA always sends something like: Warning: the number of bytes you are reading is equal to the number of bytes in the buffer, there can be more data in the buffer.

Any ideas?

Thanks
odanzy

Posts: 1,543
Registered: 11/16/05
Re: Problems reading traces in N5242A
Posted: Mar 12, 2012 2:33 PM   in response to: keplovic in response to: keplovic
Click to report abuse...   Click to reply to this thread Reply
Which driver are you using and where did you download it?

I would recommend digging into the driver that you are using and seeing where the failure/timeout is occurring. Also are you using Group Triggering or continuous triggering? I would recommend group triggering with the group count set to the averaging factor and then using either *OPC or *OPC? to synchronize the sweeps.
Dr_joel


Posts: 2,744
Registered: 12/01/05
Re: Problems reading traces in N5242A
Posted: Mar 12, 2012 6:34 PM   in response to: odanzy in response to: odanzy
Click to report abuse...   Click to reply to this thread Reply
And I think you may need to restart the averaging for each acquisition, or it will average in old data with new.

Point your RSS reader here for a feed of the latest messages in all forums