Ideas Test

9 VOTE

Display trigger time

I need to know the trigger time to be able to relate events to outside events such as log entries and the like. I would like to be able to see the trigger time in the UI as well as in exported data.

While we're at it, why not have the option to display all times as absolute time rather than time relative to the trigger time. Again, both in the UI as well as exported data.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 26 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    We've added this to our architecture design that we're working on now. However we're not ready to make public commitments on timeline yet.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    Hello
    It is still very important for me. Does it not matter high accuracy. When i start application and wait all the night for trigger when some errors occurs in my application then one second is quite enough.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    I'd also really like to see absolute time. Otherwise it becomes really difficult if not impossible to collate the Saleae capture with other logs.

    Millisecond accuracy would be fine. Enough to match up the Saleae logs with other data.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    Hello,
    There is a need for this feature here too:
    we would like to know the delay between the start of the trigger and when the trigger actually happened.
    For the test we do here, 1 ms to several hour of timestamp would be nice.
    Regards.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    Hi, new Logic user here, looking for exactly this using the latest beta. Was this ever implemented, and if so, where do I find it?

    For my current project, any timing at all is a plus, even if microsecond (or tenths of it) would be nice.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    Millisecond accuracy would be great, but even second accuracy would deal with my use case. I have long-term alarms that I need to validate, and a small fleet of logics is a cheap test tool.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    I have the exact same use case as RobertB and I agree that millisecond precision should be sufficient for matching up with most logs.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    Millisecond or better would be nice but I'll take whatever accuracy that you can get. My main need for this is to relate log entries to events in Logic and even a thirtieth second accuracy would be very useful.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 26, 2018 19:37

    I think we'll try to record the absolute start time of the data stream as accurately as possible. Our devices stream in real time and the trigger operation is performed purely in software, so we could calculate the trigger time based on the start time, the trigger sample number and the sample rate.

    If anyone else would like this feature, please commend on what timing accuracy you would like to see, as well as what the minimum timing accuracy you would consider usable.

    Worst case, we could easily record the system time within one thirtieth of a second. Best case, if we can get the time stamp of the first single USB packet of the stream, we might be able to get 10's of micro seconds of accuracy. - however I don't think we could beat that without some kind of device side hardware support.