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.

LAUNCHXL-CC1352R1: CE and FCC certification

Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: CC1310

Hey guys,

we have just received information from our certification lab. We are planning to get CE based on EN 300 220 and "band L - channels" EN 300 440-2 as well as FCC based on 15.247 (FH).
We have a sensor collector setup in star topology, though there can be more than one collector present to handle all sensor nodes.
For collector we use CC1352R1 launchpad with external antenna with 4dB gain and the sensors are TIDA00489 boards. Note that the sensors are sleepy. For CE, we use non-beacon mode.

I do now have some basic questions, if the thread gets confusing, I will split it.

CE-certification:

1. Is there a function in SmartRF Studio, where I can use LBT.
In example, I use Packet Tx function to transmit to another device having the Packet Rx function running and I add a jamming device blocking on the employed frequency.
Can I use such a setup? If not I use sensor/collector example and add a jamming device.

2. In SmartRF Studio, there is the "Bit Error Rate". The lab is asking if there is some kind of "error correction" implemented in SmartRF Studio having an effect on the BER?

3. Since we want to use 865MHz - 868 MHz (L-band) according to EN 300 440-2 V3.1.1 annex B, there is another requirement regarding the max. output power besides the maximum 25 mW.
The power density limit is 6.2dBm/100kHz. Are we within this spec with our devices using sensor/collector example with PHY_ID: APIMAC_GENERIC_ETSI_LRM_863_PHY_131?

4. The lab wants us to provide the following information regarding LBT according to EN 300 2220-1 V3.1.1 table 48.



Some information from our side:
- the maximum packet length is our data packet with approx. 330 bytes (@5kbps)
- We do not have other messages than data, polling (content of config message is out of box) or association/disassociation
- we have CONFIG_MAX_DATA_FAILURES 2 and CONFIG_MAX_RETRIES 3
- CONFIG_MIN_BE   3 | CONFIG_MAX_BE   5 | CONFIG_MAC_MAX_CSMA_BACKOFFS   4

4.1 Is it possible to set the duration between two retries? I think it has to be higher than 100 ms?
4.2 Could you provide the infos (or give me a link). I assume, Tmax for single transmission or dialogue or the Max Tcum has to be handled by the application and there is no feature in the MAC layer handling it automatically?


FCC Certification:

1. Regarding the active hopping test, is it possible to enable hopping in SmartRF Studio somewhere? But I think there is the certification test mode in the sensor/coll example for this test, right?

2. I think the certification test mode is usefull to test the hopping of the collector, but since our sensors are sleepy, is it enough for the test that the sensor follow the collector or is there a test,
where the sensors are hopping actively to "demonstrate" this ability and the collector is sending messages to it?

Best wishes

Slev1n

  • Hi,

    We will look into it and get back to you ASAP. Please bear with us.

    Thanks,

    PM

  • Hi,

    CE Certification:

    Q1: No, you can't use SmarTRF Studio for testing LBT function. You can use "rfListenBeforeTalk" example. It is under Examples in CC1352 SDK.

    Q2: No Error correction on BER

    Q3: Are you sure about this standard EN 300 440-2 V3.1.1 annex B?? 

    The OCBW should be greater than 600KHz to meet 6.2dBm/100KHz at +14dBm power setting otherwise you need to Back off the Power to meet the spec. We have 200KBPS, 50KHz Dev Mode. You can use this one and adjust the Tx Power to around +11dBm to pass the spec of 6.2dBm/100KHz. You can use SmartRF Studio for this test and Sensor-Collector example with 200KBPS Data rate.

    Q4: Our SDK complies with ETSI spec but please check the documentation in SDK and also under "rfListenBeforeTalk" example

    FCC Certification:

    Q1: No, SmartRF Studio can't be used. Yes, you can use Sensor/Collector example with Freq Hopping

    Q2: Yes, I think Freq Hopping Transmission test should be OK for the Certification testing but please discuss with Certification Lab for details.

    Thanks,

    PM

  • Hi PM;

    PM said:
    Q3: Are you sure about this standard EN 300 440-2 V3.1.1 annex B?? 

    yes, you are right it is EN 300 220. The lab corrected that mistake.

    PM said:
    The OCBW should be greater than 600KHz to meet 6.2dBm/100KHz at +14dBm power setting otherwise you need to Back off the Power to meet the spec. We have 200KBPS, 50KHz Dev Mode. You can use this one and adjust the Tx Power to around +11dBm to pass the spec of 6.2dBm/100KHz. You can use SmartRF Studio for this test and Sensor-Collector example with 200KBPS Data rate.

    We will switch to the "K-Band" where this power distribution is not an issue, but thanks for clarification

    PM said:
    Q4: Our SDK complies with ETSI spec but please check the documentation in SDK and also under "rfListenBeforeTalk" example

    .

    I will try to find some info regarding the applied values.

    Thank you for the fast response. When I have a follow up question, I will reach out.

    Best wishes

    Slev1n

  • Hey PM,

    I do have a follow up question regarding the radio settings in collector sensor example since I need the correct settings for SmartRF Studio.

    TER once said it would be the same settings in Smart RF Studio and in the collector/sensor example, but I am a little bit confused due to the settings visible in the mac_settings.c

    https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/888825?tisearch=e2e-quicksearch&keymatch=RX%20filter%20BW%20sensor%20example

    Collector (CC1352R1):

    In mac_settings.c I found the following:

    // Default parameter summary
    // Address: N/A
    // Frequency: 920.00000 MHz
    // Data Format: Serial mode disable
    // Deviation: 25.000 kHz
    // Packet Length Config: Variable
    // Max Packet Length: 1040
    // Packet Length: Variable
    // RX Filter BW: 110 kHz
    // Symbol Rate: 50.00000 kBaud
    // Sync Word Length: 16 Bits
    // Whitening: Whitening Enabled

    1. RX Filter BW seems not be 110 kHz, since the setting is 0x23 in .rxBw = 0x23, // 88 kHz . According to smartRF Studio, a value of 0x23 in RF_cmdPropRadioDivSetup for rxBW is Unknown for the CC1352R1 board. Is the stack handling all by itsself and overwriting these settings? If not, what are the following settings for APIMAC_GENERIC_ETSI_LRM_863_PHY_131 and APIMAC_STD_US_915_PHY_1 within the collector example?

    • Symbol Rate
    • Deviation
    • RX Filter BW
    • Whitening

    I need to know them for certification as we use SmartRF Studio for some radio tests and I dont find anything else in the code.

    2. Again, if the stack is not setting the same parameters like they are provided by SmartRF Studio: Are these settings the same on the sensor side, which uses a CC1310 chip, if not please list them for both PHY IDs? At least I assume the RX Filter BW differs?!

    EDIT: One further question, what is the channel width within the 868 MHz band? I know that the spacing is 200kHz, but what is the width?

    Best wishes

    Slev1n

  • Slev1n,

    1. Yes, TER was correct. The 15.4 stack uses the default SmartRFStudio settings. Those settings you are looking at will get overwritten inside the source code you do not have access to.

  • Ok, thank you. I was a little bit confused. I guess this answers question 2, too.

    However, it would be great if you could give me the channel width, since I have to provide the information for the questionary in Annex D EN 300 220-2.

    Best wishes

    Slev1n

  • Hi,

    Channel Width would be 100KHz (For 50KBPS, 25KHz Dev).

    Thanks,

    PM

  • Hey PM,

    for ETSI we use APIMAC_GENERIC_ETSI_LRM_863_PHY_131, hence, we have 5kbps and 5 KHz dev. What is the channel width here?

    best wishes

    Slev1n

  • Hi,

    OCBW is around 21KHz. You can declare as 25KHz/30KHz.

    Thanks,

    PM

  • Thank you, than we will declare as 25kHz.