Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timestamp for configuration messages #36

Open
153957 opened this issue Nov 21, 2015 · 0 comments
Open

Timestamp for configuration messages #36

153957 opened this issue Nov 21, 2015 · 0 comments

Comments

@153957
Copy link
Member

153957 commented Nov 21, 2015

How is the timestamp for configuration messages determined?
A couple of years ago I ran some tests where I started one of the tests on 2011-11-27 14:26 (GPS time).
Since I started the HiSPARC DAQ at that time a configuration message was generated and sent to the datastore. It can be seen here:
http://data.hisparc.nl/api/station/94/config/2011/11/27/
The problem is the timestamp in the configuration is "2011-11-27 15:25" Which is offset by an hour.
The HiSPARC electronics does send a GPS timestamp with the configuration message (ID 42).
Perhaps the HiSPARC DAQ does not use that timestamp and simply adds its own using the local PC time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant