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.

RTOS/CC1310: Using RF Core signals vs ApiMac_SetReqUint8() to control PA/LNA

Part Number: CC1310
Other Parts Discussed in Thread: CC1190,

Tool/software: TI-RTOS

Hi,

I have a cc1310 with a cc1190 front-end. I'm trying to find identify the differences in controlling the CC1190 PA/LNA through the RF Core signals (i.e. using PINCC26XX_setMux() ) vs setting the RangeExtender and TransmitPowerSigned Pib attribute through ApiMac. 

If I were using RF Core signals, I assume I still have to set the TransmitPowerSigned Pib? Can someone verify this? So my actual RF output over the air is dependent on TransmitPowerSigned value, as well as the CC1190 configuration (LGM vs HGM)?

Also, if I were to set RangeExtender, the documentation said I can set the TransmitPowerSigned up to 27dBm. Does the documentation make an assumption on the fact that the CC1190 is supplied by 3.6V? The CC1190 is not capable of amplifying to 27dBm with a supply voltage lower than 3.6V.

Final question around this, is there an option for me to use HGM for RX, but LGM for TX?

Thanks so much for your time.

  • RF core signals are only used to enable CC1190. The Tx power values are coming from the txpower register of rfc_CMD_PROP_RADIO_DIV_SETUP_t. Please refer to SmartRF Studio and play with Tx power on CC1310 + CC1190 target configuration. These are the values that the TransmitPowerSigned API uses to change the Tx power.

    Yes, the max power is achieved at 3.6V VDD. The output power drops if the voltage drops. The output power is also dependent on the temperature as shown in the graph below.

     Hello,

    HGM and LGM are for Tx and won't affect Rx.

    Regards,

    Prashanth

  • jc0706: I assume you are using the 15.4 stack? In that case the only thing you should need to do is define that you use a range extender and the control signals should be set.
  • Thanks for the help guys.

    I have 2 other questions as well:

    1. If i were to set a custom bitrate, such as 25kbps, do i need new power table values?

    2. This question is not really related to the power aspect, but I've noticed that on SDK version 1.6.0, when a sensor does an orphan scan and it succeeds, the PAN ID doesn't set to the PAN ID of the coordinator which sent the coordinator realignment frame. The other PiB values do (coord short addr, device short addr, coord ext addr, etc.).

    Thanks again for your time.

  • The power tables is not a function of bit rate. If the other question is still relevant, I suggest you start a new thread since it's a different topic than the original question.