After fixing wiring issues with encoders, we tried to deploy code again, only to not be able to connect to the roborio through Ethernet or wireless. We’ve tried
The pdh status is magenta, so it’s in keep alive timeout, but nothings working
The deploy console says you are deploying as team 2714, but your ChiefDelphi account says you are on team 691. I think you need to change the teamNumber field in the .wpilib/wpilib_preferences.json so that it can find the roboRIO correctly through Ethernet.
FWIW - Rev’s MaxSwerve Java Template is also hardcoded against Team BBQ’s number - https://github.com/REVrobotics/MAXSwerve-Java-Template/blob/main/.wpilib/wpilib_preferences.json#L5
If this file got copied in as part of the debugging, it could explain the sudden onset of the symptom.
@OP - another debugging step that could possibly have revealed this - make a temporary, brand new, blank robot project. If that deploys, it implies the issue is project specific, which narrows down some of the debugging steps you tried.
What does the Driver Station status tab show?
That’s where we usually start with testing PC to rio connections.
Also, basic connectivity tasks like ping should be used to diagnose before you go nuclear and start swapping components.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
