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.

CC1310: Data cannot be received at low temperature.

Part Number: CC1310

Hi team,

Here's the request from the customer:

There are 5 hosts and each one has 10 end devices. At first, they work fine at normal temperature,  but when cool down to -15 degrees, there are 2 hosts that cannot

send and receive data. However there is no crash happen and the button and LCD is normal. The data transmitted by the terminal is normal, and it is judged that the host did not receive the data and did not respond. The other 3 are normal, what may be the problem?

Customer thinks that timing calibration frequency offset may solve the problem, is it possible?

If he want to add a step of timing calibration frequency offset in the main program and do not reset the device.

(*(PowerCC26XX_config.calibrateFxn))(PowerCC26XX_SETUP_CALIBRATE)

Is it possible to add this? Where is the calibration mentioned in the above connection about waking up from sleep implemented, and what is the relevant description?

Could you help check this case? Thanks.

Best Regards,                                                        

Nick

  • Have you checked the frequency offset between the host and end devices? Typically the frequency will change as a function to temperature. See "12.5.2 No Link: Frequency Offset" in swra640. 

  • Hi,

    Here is customer's solution about the post:

    Added an execution every minute to the timer:

    PowerCC26XX_injectCalibration();     //frequency offset calibration

    The test has no effect. 4 of the 5 machines still cannot receive data at -15 degrees. At this time, manually press the key to execute SysCtrlSystemReset(); after the machine is all reset, it can send and receive data normally at -15 degrees. After reset, the machine will execute Power_init(), where the calibration is done here.

    Can you please help analyze this idea, and how to do it correctly?

    Best Regards,                                                        

    Nick

  • It looks like the definition of the fuction is the following is:

    /*
    * ======== PowerCC26X2_injectCalibration ========
    * Explicitly trigger RCOSC calibration
    */
    bool PowerCC26XX_injectCalibration(void)

    which has nothing to do with the radio.