This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1352R: CC1352R Not passing FCC certification in Long Range Mode

Part Number: CC1352R

Since we are currently in the test lab we need to find an answer for this quickly.

1.) How is the long range mode intended to be used since it is not meeting 500KHz bandwith and therefore not FCC compliant?

2.) How do we setup the receive mode in the radio command API for certification testing.  It is a Part 15B requirement to pass radiated spurious emissions with the radio receiver ON if the radio operates below 960MHz. 

  • 1) LRM will not comply with FCC 15.247 using "digitally modulated intentional" but you should still be able to pass using Frequency hopping or if you target FCC 15.249. 

    2) Could you link to the exact paragraph? Should you still receive packets under this test? If so I would assume you can use a simplified version of your existing SW for certification testing. We have also used SmartRF Studio for some tests. 

  • 15.101 Equipment authorization of unintentional radiators.

    (a) Except as otherwise exempted in §§ 15.23, 15.103, and 15.113, unintentional radiators shall be authorized prior to the initiation of marketing, pursuant to the procedures for certification or Supplier's Declaration of Conformity (SDoC) given in subpart J of part 2 of this chapter, as follows:

    (b) Only those receivers that operate (tune) within the frequency range of 30-960 MHz, CB receivers and radar detectors are subject to the authorizations shown in paragraph (a) of this section. Receivers operating above 960 MHz or below 30 MHz, except for radar detectors and CB receivers, are exempt from complying with the technical provisions of this part but are subject to § 15.5.

  • Not following you. 15.101 is for "unintentional radiators". Since the original question was about TX you have an intentional radiator and hence you should look under "Subpart C" and not "Subpart B"?

  • Yes, you are correct.  The unintentional radiator testing is also performed during certification and the test lab was questioning if the Receiver was turned on for that test.  In the cert code there is no explicit way to turn on the receiver, so it was assumed that when power was applied to the CC1352R the receiver was on by default.  We have no way to verify that.  From the data sheet our understanding is that when the BLE stack is not in use, it handles the power management through its own power management mechanisms. Whether it's putting the BLE module in an "IDLE" or "OFF" state is unknown. TI suggests to let the BLE stack handle the power management. However, it looks like this can be overridden to give direct power control of this module. The question, is it on by default?  If not then we need to figure out how to explicitly turn it on. 

  • Are you only running BLE on CC1352 or in combination with some sub 1-GHz stack? 

    Which state the RF part of the chip is in depends on your SW implementation. I'm not too familiar with the BLE stack but I believe the stack sets the radio alternating between TX and RX. Look into the HCI commands (https://dev.ti.com/tirex/explore/node?node=AAdGbdkELbDCwzMZfDxBJg__pTTHBmu__LATEST) , it looks like it exist a command to set the chip in cont. RX.