We are using a BC660K-GL with firmware BC660KGLAAR01A01_BPJ_BETA20260226.
The non-signaling test document states that when SigType=0xFF, the module transmits in sine-wave mode and “kHz is adjustable.” Please clarify the following for the final nScStart parameter in AT$QCRFNST=0053:
Does it represent a subcarrier index, a frequency offset, or an absolute tone frequency in this mode?
What are its valid range, units, step size, and signed/unsigned encoding?
Does nScStart=0 produce a tone exactly at CarrierFreq, or is an offset still applied?
Which TxMode value should be used for continuous sine-wave transmission?
We want to generate a continuous tone at 885 MHz on Band 8. We tried: AT$QCRFNST=0053080092225C000000FF000000
The module returned MT00000000 and OK, but approximately 10 seconds later emitted RDY and returned to CFUN: 1.
Please confirm the correct command for this firmware and whether any parameter combination above could cause that restart. Our intended experiment is to measure this tone using a second BC660K-GL configured for a Band 5, 885 MHz, no-trigger single-tone SNR test. Is this arrangement supported, and is a specific tone offset required?
i did few more tests and want to improve my problem statement
The non-signaling test document states that when SigType=0xFF, the module operates in sine-wave mode and “kHz is adjustable.” Please clarify the following regarding the final nScStart parameter in AT$QCRFNST=0053:
Does it represent a subcarrier index, frequency offset, or absolute tone frequency?
What are its valid range, units, step size, and signed/unsigned encoding?
Does nScStart=0 generate a tone exactly at CarrierFreq, or is an offset applied?
Which TxMode value enables continuous sine-wave transmission?
Our intended experiment uses Band 8 TX and Band 5 RX at 885 MHz, with no receiver trigger.
Update on the earlier restart: The modem previously emitted RDY and returned to CFUN: 1 approximately 10 seconds after starting TX. After powering the device from an external DC supply, that restart is no longer observed.
However, TX-on measurements continue to return SNR Valid=0 and SNR_Lin=0
We have tried requested TX powers of 23 dBm and 0 dBm, different antenna separations, and nScStart values 0, 1, and 2 without obtaining valid TX-on SNR. TX-off measurements have occasionally been valid.
Please confirm whether this two-module cross-band experiment is supported on our firmware and provide validated TX/RX commands, required tone offset, received-signal level, and measurement timing. What conditions cause the SNR validity flag to be zero in this test?