Warning with NIRFSG_ATTR_LO_IN_POWER attribute when setting the output of NI5673

[chris_amadasun]

Hey Ilya,

In the code you are initializing the other 5663's.To do this you will need to do the following

1. Open a NI-RFSG session.
2. Configure the frequency and output power level.
3. Configure the generation mode.
4. For this example, the first device in the for loop will be the device that has the LO.
    a. Configure the reference clock source.
    b. Export the LO and reference clock for the other 5663s to use.  Read the LO Out Power.
5. All other devices have an external LO.  The LO from the first device is daisy-chained through each 5611.
    a. Configure the reference clock source.

There are a couple of ways to do this.

You can use the RFSG 5673 Synchronization (TClk, Shared).vi in NI Example Finder (obviously you would need to make some changes to the VI to use an RFSA instead).

Or you can try this RFSA example in the link below

http://zone.ni.com/devzone/cda/epd/p/id/6078

Let me know how this goes.

[JMota]

I've been following this discussion from the sidelines as I'm no RFSA expert. However, I'm  curious to know the cases where the warning happens. Is it just at 5.6GHz and a power level of 0dBm? Does setting the power level to -1dBm gets rid of the warning? Do you see the warning at 6GHz and 0dBm?

[ilyak]

I just ran the same frequency sweep at -1dBm. Same thing.

You can check it in the attached Spy log.

[ilyak]

Hi Christian:

So the general idea is that power and frequency have to be set first before all that configuration of LO and TClk synchronization?

Is this correct?

-Ilya.

[Eric_K]

Ilya,

Yes, the power and frequency will need to be set for each of the cards first.  The then LO and TClk synchronization can be set up.

Thanks,

Eric K

Applications Engineer

National Instruments

[ilyak]

Hi Kyle:

Hm, strange, that's exactly what I do.

The attached is the NI-Spy log with the commands. You can check if if you get a chance.

-Ilya.

[ilyak]

Hi Kyle:

Same error again with a different test. 

SPY log is attached. The error happens only on this frequency. 

-Ilya.

PS: The SPY actually crashes all the time when I try to open the GetError function.