Does anyone have idea why phoenix tuner is doing this? It's not an immediate problem because I can work around it to read the CAN devices, but it's a new error to me. To keep an explanation as simple as possible, I'll explain the process I went through to find this issue. First of all, the software we use to push code and drive our robots are WPILib Visual Studio Code 2023 to write and push the code, FRC Driver station to enable and disable the robot, Phoenix Tuner/Lifeboat to identify our CAN devices and their respective ID numbers, and NI tools. As of late, the only things I have downloaded to the main computer we use for this were the WPILib VS code 2023 updates and the new NI tools downloads. Everything has been working normally, until today when I went to Phoenix to check the CAN devices, which weren't being identified despite the communications being good. This isn't usually a problem, because I can 'Install temporary diagnostics' and this brings up the devices. Today, however, was an exception. The diagnostics weren't doing their job in fixing the missing CAN devices. I tried troubleshooting, but eventually just decided to push my code anyway. Somehow pushing the code caused the CAN devices to come up?? The kicker was when I tried to install the diagnostics afterward. Doing so caused the CAN devices to disappear. Like I stated, this isn't an immediate emergency because I can work around it, but I've never had this problem before. Anyone have experience with this or know what's going on? Cheers.
