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.

CCS/CC1312R: 'config-tx-power' in collector.cfg seems not work

Part Number: CC1312R
Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

Dear Sir,

We implemented a subg coordinator(gateway) by CC1312R.

S/W SDK profile:

collector: based on 'ti154stack_linux_x64_4_30_00_06'

coprocessor: based on 'simplelink_cc13x2_26x2_sdk_4_30_00_54' coprocessor project

Issue:

Basically, it works well against sensors that are also implemented by CC1312R. (in long range mode)

But, yesterday, we used an Agilent spectrum to measure the RF transmit power of the collector module,

it shows only 2.6 dBm.

However, the option 'config-tx-power' in collector.cfg is set 14.

How can we debug this issue?

(PS)

1. The transmit power measured upon sensor side is 11 dBm which seems reasonable.

2. We also have a collector module implemented by CC1310. The measurement result

    is normal. But, we run the same linux gateway software on both CC1312R1 collector module and 

   CC1310 collector module.

Thank you

  • Hi Adam, 

    Are you using a LaunchPad or a custom board? 

    Do you see this issue on multiple devices? 

    Do you see this issue when testing on another example? 

    Thanks, 
    Elin

  • Hi Elin,

    The problem happens on our custom board (the collector board used in a gateway device).

    I ever replaced it with CC1312R1 launchpad (connect to the gateway device via USB) and

    ran the same CoP f/w and Host collector process, it looked much more normal.

    The measured power is 8.6 dBm.

    Up to now, we had two pieces of collector module got the problem out from

    two produced samples.

    Adam

    Thank you

  • BTW, we tried to read back the transmit power value by below api

    ApiMac_mlmeGetReqUint8(ApiMac_attribute_phyTransmitPowerSigned, &value),

    and it showed '14' which is exactly what we set.

    We noticed that we did not set CCFG_FORCE_VDDR_HH as 1 in CoP f/w,

    but, it should still had 12.5 dBm capability.

  • Hi,

    We compared the h/w designs between sensors and coordinators and found the root cause.

    Close the request as the result.

    Thank you for your time.