-
Notifications
You must be signed in to change notification settings - Fork 891
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
Feature/signal real timestamp #969
Conversation
Physical test carried with HackRf One (Native) |
6af7cf8
to
15618c1
Compare
@jopohl Let me know if you need further information. |
15618c1
to
f95cd7e
Compare
@jopohl let me know if further changes are required ;) |
f95cd7e
to
a0eea05
Compare
@jpacov could you please sign the CLA? Probably it wants that again due to the force-push or something. |
e6de77a
to
e563910
Compare
Dne @jopohl . It was a problem with 2 accounts mixed. Signed with both now. |
@jopohl can we merge now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice to add some unit-tests or update existing ones to verify the new timestamps work as expected. I do not have an SDR here to test recording/Protocol Sniffer so if someone from the community could test this would be appreciated.
self.signal.bits_per_symbol, write_bit_sample_pos=False) | ||
self.signal.bits_per_symbol, write_bit_sample_pos=True) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this change needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So that _ppseq_to_bits
populates bit_sample_pos
array and we are able to calculate more accurate timestamps using bit sample position.
e563910
to
714d36b
Compare
@jopohl I tested more extensively the timestamps, and made some changes and small fixes. I also added some small unit tests for the ProtocolSniffer as you requested. Let me know if that is enough. |
714d36b
to
d5494ea
Compare
@jpacov sorry for late reply, could you please pull in latest changes from master? I just updated the CI to support more recent Python versions and like to ensure your changes are compatible. |
d5494ea
to
c78a850
Compare
c78a850
to
bb740c5
Compare
Thank you for your contribution. |
Adding timestamps to Recorded Signals and ProtocolAnalyzer messages
Adding timestamps to messages generated in ProtocolSniffer
Before this PR, signals and messages interpreted by protocol analyzer, had no real timestamps; just some relative time measurements between each messages in signal. Now timestamps are absolute and are saved into proto.xml files correctly for future reference.