-
Notifications
You must be signed in to change notification settings - Fork 224
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
Time Sync Server #1801
Comments
What do you see here when things are in both the working and not-working configuration? |
Gonna add on to this. I think the root of the issue is that every time you deploy code, the FGPATimestamp resets to 0 but the PhotonVision timestamps do not. Therefore, when you first power cycle the robot, everything works as normal, but after you deploy code, it breaks. In YAGSL, there is this code in double mostRecentTimestamp = resultsList.isEmpty() ? 0.0 : resultsList.get(0).getTimestampSeconds();
double currentTimestamp = Microseconds.of(NetworkTablesJNI.now()).in(Seconds);
double debounceTime = Milliseconds.of(15).in(Seconds);
for (PhotonPipelineResult result : resultsList) {
mostRecentTimestamp = Math.max(mostRecentTimestamp, result.getTimestampSeconds());
}
if ((resultsList.isEmpty() || (currentTimestamp - mostRecentTimestamp >= debounceTime)) &&
(currentTimestamp - lastReadTimestamp) >= debounceTime) { ... } Because mostRecentTimestamp gets set to the PV timestamp (which is much larger than the FGPA timestamps), the condition |
https://github.com/user-attachments/assets/e71858e9-699f-46ad-842f-1c18460aeb6c I was unable to reproduce this behavior here while restarting either my robot code simulation or photonvision at least |
https://github.com/user-attachments/assets/4544949a-126a-49cc-b22a-00d28e06aea3 |
Describe the bug
I get warning messages after deploying code to our robot about the cameras time sync server. When this warning happens, photonvision pose estimator stops working.
To Reproduce
Steps to reproduce the behavior:
Platform:
"""
PhotonVision coprocessor at path /photonvision/flCam2025 is not connected to the TimeSyncServer? It's been 9223372036854.78s since the coprocessor last heard a pong.
Check /photonvision/.timesync/{COPROCESSOR_HOSTNAME} for more information.
PhotonVision coprocessor at path /photonvision/frCam2025 is not connected to the TimeSyncServer? It's been 9223372036854.78s since the coprocessor last heard a pong.
Check /photonvision/.timesync/{COPROCESSOR_HOSTNAME} for more information.
"""
The text was updated successfully, but these errors were encountered: