Open glopesdev opened 1 month ago
To be able to understand better the problem a procedure as been agreed. Whenever this happens again we need to replace the timestamp generator on the rig with the problem while keeping the old one connected to the computer. There is a timestamp generator in the desk to be used has a replacement.
The procedure is:
Further actions may be needed to support @filcarv in remote debugging.
Over the weekend we noticed a generalized drift across all Harp devices of both AEON3 and AEON4 rigs. Upon further monitoring it seems like all devices continued operation, but were not being synchronized by the timestamp generator / clock synchronizer devices.
We are currently unsure of the reason for the failure, or whether there is any relationship between the almost simultaneous occurrence of the issue on both machines with different synchronizer devices. We are not sure also if this could be related to the update to the Harp 1.13 core which was done at the beginning of the experiments.
Complementary debugging strategies to try next: