I have a PXIe system with three daisy-chained NI-PXI 5673E generators. My code configures frequency, power, IQRate, phase offset for each. Then it tries to commit the changes using niRFSG_Commit for all three instruments. The first one runs fine the second dumps this error:
-1074118136, The AWG reported the following error:
PLL could not phase-lock to the external reference clock.
Make sure your reference clock is connected and that it is within the jitter and voltage specifications. Also, make sure the reference clock rate is correctly specified.
Status Code: -200245
Any ideas why this might be happening?
Thanks so much.
In order for us to narrow the source of this issue down, it's important to try some basic tests:
The PXI-5673E is made up of three modules: 5622, 5601 and 5652. I need to determine if the source of this issue is the 5450 (which the error message is referencing).
My first thought would be to double check all the cables used to pass the LO signal and 10 MHz reference signals to the slave NI 5673s.
You can see a picture of what your setup should look like here: http://zone.ni.com/devzone/cda/tut/p/id/9127
This page is a subset of the MIMO Test page, which has a lot of info on setting up the modules in a phase coherent system.
Also, If you still have an issue, this topic would best be posted on the RF Measurement Devices
RF Systems Engineer - National Instruments
Ok, I'll post it to RF Measurement Devices forume then.
Thanks a lot,
The problem was resolved.
Thanks all for help.
This error has come back. What is strange about it is that now it is generated from niRFSG_WriteArbWaveformComplexI16.
I'd like to confirm that the hardware is in fact working correctly at this point, and the best way to do that is with some basic initial troublehsooting steps.
Does the device pass self test in MAX?
Can you open up the NI-FGEN Soft Front Panel and generate waveforms?
The error doesn't seem like it should be related to that function. I would expect to see it returned when configuring the sample clock or committing the task to hardware. Also, are you exporting any signals? It may be a longshot, but not knowing too much about your code you could also check out this KB to see if it's relevant. The error message is different, but the code is the same