• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 505 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.

Timestamps in Z-Tool

Pascal10205
Prodigy 100 points
Other Parts Discussed in Thread: Z-STACK

Hi,

I have a problem with Z-Tool. I'm working with ZigBee-Stack 2.1.0-1.3.0 and Z-Tool 2.0. I send some debugging messages to Z-Tool and besides the information in the message I also need the timestamp. Everything works fine expect the timestamp itself. Here are some example timestamps I obtain from Z-Tool:

19:36.069

19:36.708

19:36.631

It seems that the seconds are missing. 19:36 are the hours and the minutes and 069, 708, 631 seem to be the milliseconds. Is there a way to change the displayed format or do I have a wrong understanding of the format? Or is it possible that this is a bug of Z-Tool 2.0 for  ZigBee-Stack 2.1.0-1.3.0?

Thank you very much.

Regards,

Pascal

  • 0
    TI__Expert 5255 points

    Hi Pascal,

    We just ran ZTool 2.0 and did a SYS_PING to get ZStack to send something back so that we'd see a timestamp. Here's what we saw in the Log window:

    <RX> 12:23:21.350 COM1 SYS_PING_RESPONSE (0x6101)

    Then, we were moving stuff around, and accidentally slid the Log window to the left and we saw:

    23:21.350 COM1 SYS_PING_RESPONSE (0x6101)

    I know this is a long-shot, but is it possible that the left edge of your log window was also cut off?

  • 0 in reply to xyzzy
    Prodigy 100 points

    Hi xyzzy,

    thank you for your quick reply. I think this is not the problem. Here is a complete sample output of my application:

     

    <RX>15:29.609 COM4 DEBUG_STRING (0x4880)
            DebugString: |7.250|51.000|89.045|1.677|-77.688| (0x7C, 0x37, 0x2E, 0x32, 0x35, 0x30, 0x7C, 0x35, 0x31, 0x2E, 0x30, 0x30, 0x30, 0x7C, 0x38, 0x39, 0x2E, 0x30, 0x34, 0x35, 0x7C, 0x31, 0x2E, 0x36, 0x37, 0x37, 0x7C, 0x2D, 0x37, 0x37, 0x2E, 0x36, 0x38, 0x38, 0x7C)

    I am pretty sure that the 15 and the 29 are the hours and the minutes, respectively, since this was the time the output was generated.

    Are you using the same version of Z-Stack? I tried a reinstallation but that did not solve my problem.

    Regards,

    Pascal

  • 0
    TI__Expert 5255 points

    Well, actually we were testing with ZStack-2.2.0 and the same version of Z-Tool that you're using. The timestamp is generated by Z-Tool so the version of Z-Stack should not matter. To answer your original question, we are not aware of a way to change the displayed format. Can you try some other commands (like SYS_PING) and see if you get the same results? It's possible that DEBUG_STRING is acting differently...

  • 0 in reply to xyzzy
    Prodigy 100 points

    Ok, I tried SYS_PING and here is what I got:

    <TX>22:21.240 COM1 SYS_PING (0x2101)

    <RX>22:21.240 COM1 SYS_PING_RESPONSE (0x6101)
        Capabilities: MT_CAP_SYS, MT_CAP_ZDO (0x11)

    The problem remains, the seconds are not displayed.

    Regards,

    Pascal

  • 0 in reply to Pascal10205
    Prodigy 100 points

    Hi,

    it seems that the difficulties arise with the german windows time format. I set the time format to english (USA) and now the seconds are displayed.

    Regards,

    Pascal

  • 0 in reply to Pascal10205
    Intellectual 320 points

    Hi Pascal,

    Im getting the same problem than u. Where exactly  do you change from german to english format? I cant see any option related to that in the Z-Tool settings...

    Thanks

  • 0 in reply to Gonzalo5745
    Prodigy 100 points

    Hi Gonzalo,

    I changed to the english format in the control panel of windows, not in Z-Tool. I hope this answers your question.

    Regards, Pascal

  • 0 in reply to Pascal10205
    Intellectual 320 points

    Pascal u were right.

    I had to change from spanish to english. And now it works fine.

    Thanks a lot! It solved a big problem for me :)