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
{{ message }}
This repository has been archived by the owner on Jan 31, 2022. It is now read-only.
Based on a discussing that @evka85 and I had we should increase the time between when a link reset is performed and when VFAT sync error counters are checked. These counters are checked once per orbit so we should allow one or more orbits to occur by before checking those counters after a link reset.
An orbit is 9.09091E-05 seconds.
Types of issue
Bug report (report an issue with the code)
Feature request (request for change which adds functionality)
we should insert a sleep statement for at least N orbits (N=1?).
We could consider also inserting a sleep statement in between each OH (e.g. between lines 806 & 807 but I'm not sure that's necessary (as 24 register reads should take at least some 200 micro-seconds?).
Current Behavior
Right after a link reset is sent we immediately start checking the SYNC_ERR_CNT registers.
Context (for feature requests)
Returned results by monitoring getmonVFATLinkLocal may not be accurate because we aren't waiting enough time for the sync error counters to increment.
Brief summary of issue
Based on a discussing that @evka85 and I had we should increase the time between when a link reset is performed and when VFAT sync error counters are checked. These counters are checked once per orbit so we should allow one or more orbits to occur by before checking those counters after a link reset.
An orbit is 9.09091E-05 seconds.
Types of issue
Expected Behavior
After line 801:
ctp7_modules/src/daq_monitor.cpp
Lines 798 to 802 in 187a945
we should insert a sleep statement for at least N orbits (N=1?).
We could consider also inserting a sleep statement in between each OH (e.g. between lines 806 & 807 but I'm not sure that's necessary (as 24 register reads should take at least some 200 micro-seconds?).
Current Behavior
Right after a link reset is sent we immediately start checking the
SYNC_ERR_CNT
registers.Context (for feature requests)
Returned results by monitoring getmonVFATLinkLocal may not be accurate because we aren't waiting enough time for the sync error counters to increment.
Your Environment
The text was updated successfully, but these errors were encountered: