You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is imperative to have a timestamp for each message. Exact world time is not required, exact time between messages is required. It is enough to start the log at 0 milliseconds.
Can you add this functionality to the upcoming release as soon as possible?
The text was updated successfully, but these errors were encountered:
How about adding support for a DS3234 module attached to the SPI pins at the front to get real-time timestamping.
What is a "message"? Is it a LF/CR-LF terminated run of bytes? Is a a chunk of bytes until a pause of N milliseconds? -- I guess the former is the typical situation, but it is totally dependent on what you're logging. There needs to be some new settings to control the insertion of timestamps.
It is imperative to have a timestamp for each message. Exact world time is not required, exact time between messages is required. It is enough to start the log at 0 milliseconds.
Can you add this functionality to the upcoming release as soon as possible?
The text was updated successfully, but these errors were encountered: