LO Setting Could Not Be Locked When Used RFmx Limited Configuration Change

Updated Jun 6, 2023

Reported In

Software

  • RFmx

Issue Details

You found LO source setting is not locked sometimes when you use RFmx signal name with Limited Configuration Change. You tried to share LO(LO_In) using RFmx signal name and Limited Configuration Change, but it isn't set to LO_In when they call 'initiate' with the signal name. Why did it not work ?

Solution

Refer the feature specification document , there is some problems with RFmx debug mode. Check the code , disable the debug mode , the LO setting can be locked with LCC.

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.