Fixed inconsistent hardware clock timestamp. #12430
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Camera Model: D455
SDK Version: 2.54.2
Firmware Version: 5.15.1
Apply the attached patch to watch measurements of mean, minimum, maximum and
standard deviation of the interval between the hardware clock timestamp and
current time for every 2000 frames.
measure.patch
By the result, the hardware clock timestamp is inconsistent, and it may even
be a future time when the hardware clock (2^32) restarts from zero (on update_samples_base()).
error.log
About this line of current code, the author thinks the hardware clock timer is retrieved and
is immediately sent back. That means the most duration (delay) of getting a hw clock
is spent before retrieving. Having this design is due to varying delay. I assume
the varying delay is caused by firmware design.
I tried the code that refers the delay happening after retrieving the hw clock.
This means the firmware receives the request and immediately processes it.
From the result, we have a consistent hardware clock timestamp.
fixed.log
This line of commit is because _last_request_time is also connected with the hw clock.
It should be modified like _prev_time.
The future timestamp could also be fixed.
Thanks.