From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
02-27-2018 08:17 AM
Hi everyone,
I have an issue regarding the acquisition from a 5665 spectrum analyser.
As you can see in the picture, the Read IQ brings the following error:
Error -1074118654 occurred at niRFSA Read IQ (Complex Cluster 1Rec 1Chan).vi
Possible reason(s):
Maximum time exceeded before the operation completed.
Status Code: -200221
The acquisition is done for 3 channels through a For Loop.
The main issue is with the third channel (about 90 % acquisition). The acquisition for the first channel is done 99% and for the second one about 95%.
I have another equipment with the same PXI and same .vi. And it is running perfectly.
Can you give me some tips what i can check?
I'm a beginner in RF measurements...
Thank you!
Solved! Go to Solution.
02-28-2018 05:30 PM
Hello,
This usually indicates a timeout. What is the timeout set to? Are you positive that you're receiving the trigger you've specified as well?
Can you explain your other setup which is not showing this behavior further? What is different about the systems?
03-01-2018 11:49 AM
Hi,
It is a timeout error (12 sec --12 times higher than a normal acquisition/channel ).
The difference between the systems is the CPU. The one with problems has an i5 of 2CPUs and the other 2 have i5 and i7 of 4 CPUs.
I guess I need to focus on how to reduce the CPU usage, because only Labview uses somewhere about 70 % while running the RF .vi.
And I think I lose the signal from the DUT meanwhile.
As a fact, while opening the block diagram and putting some probes, the defect starts to occur more often. For example, the system on i7 has this issue extremely rare. But adding probes will cause about 5 % defects.
So I think there is no problem with the acquisition. Probably there is no signal to acquire anymore.
Thank you!
11-06-2018 02:20 AM
Hi,
The root cause for this error was exactly like I thought and it is described in the previous post.
As a solution, I enabled the hyper-threating of the CPUs. The CPUs usage decreased by 50 %. It solved a very expensive and annoying problem with such an easy trick.
Thank you!