• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 461 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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-CC26X2R1: SYS_SET_TIME Return Code?

Robert Meissner
Prodigy 90 points
Part Number: LAUNCHXL-CC26X2R1


Hello,

I am setting the SYS_SET_TIME as follows:

fe0b2110 00000000 0b 33 37 08 10 e607 cc

- UTC time is all zero, using the values for minute, hour etc. The year I changed MSB/LSB from 07e6 (2002) to e607

Answer is supposed to be "fe016110 + FCS". However, I am getting: fe03600002211050.

Even a SYS_GET_TIME does return: fe03600002211151 (which is fixed for each call, not changing).

Thanks,

Robert

  • 0
    TI__Guru**** 218887 points

    Hi Robert,

    You are most likely receiving a MT_RPC_ERR_COMMAND_ID status in MT_SysCommandProcessing resulting in due to FEATURE_UTC_TIME not being defined in the ZNP project.

    Regards,
    Ryan

  • 0
    Prodigy 90 points

    Thanks. How can I now set the time? :-) I am using this Zigbee2Mqtt FW. Any chance to set the time? My goal is to have a correct timestamp in the messages received from my sensors (set by the ZC once message was received).

    Regards,

    Robert

  • 0 in reply to Robert Meissner
    TI__Guru**** 218887 points

    You would need to rebuild the ZNP project to enable these settings.  You can consult the Zigbee2MQTT forum and/or develop your own host application solution.  The APIs do not change over-the-air packet structure, simply initialize the SimpleLink OSAL UTC which you can read from at any time.  

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 90 points

    Understand. Guess this is too much trouble :) So bottom line with this firmware I am using, I cannot set/read the time as this feature is not enabled. What about those timestamp in AF_INCOMING_MSG:

    fe1b448100000600009e010100cc00 9d460a00 000718540a00001001009e1d88

    The red part is the 4 byte time stamp (000a469d) - 673437? Did I get this right? Is this the seconds since 1970? This stamp is set by the sensor (when sending) or by the ZC when receiving? I am just running a script which is sending/receiving from a TCP socket (which gets converted to the serial on the board). Anything I can send/set to get a correct timestamp into the messages I am receiving?

    Thanks,

    Robert

  • 0 in reply to Robert Meissner
    TI__Guru**** 218887 points

    This is the MAC Timer2 timestamp at Rx, which is in in internal MAC timer units (RAT ticks).  https://e2e.ti.com/f/1/t/850850 

    Only the local device adheres to this timestamp, and it will not affect transmissions.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 90 points

    Thanks Ryan. Understand. I will just set the time when I will receive the messages. The idea was to get the time once the message is received by the ZC (based on the ZC time set, system time) and once I receive the messages via the serial interface (in my case via the TCP socket). This is anyway the same time as I am constantly reading from the socket checking for incoming messages.

    Thanks,

    Robert