2015 Driver Station Frozen?

[RufflesRidge]

I'm not sure why you started a new thread instead of posting in that one, but I would check the things Greg asked for in that thread and post back there with the additional info. He wrote it so he's the best person to help figure out what's going on.

[nighterfighter]

Originally Posted by RufflesRidge

I'm not sure why you started a new thread instead of posting in that one, but I would check the things Greg asked for in that thread and post back there with the additional info. He wrote it so he's the best person to help figure out what's going on.

I made a new thread because it is a slightly different issue (unless I understood the original thread wrong). This computer can't connect to the robot, as I can't even change the team number. It doesn't get ANY communication from the robot. The PC battery % fluctuates, but in the other thread, I am assuming that the robot battery % was fluctuating? From what I understand in the other thread, they can connect to the robot with the Driver Station, then they encounter these errors.

But as for the answers to Greg's questions:

Robot Communication's Light: Red
Robot Code Light: Red
Even the Joysticks light is Red, even if they are plugged in.

I can't open the charts tab, because none of the buttons work.

CPU usage stays normal, (checked it at 51,960K), and doesn't change much. (After 30 seconds it went to 52,000K).

I can check the roboRIO-team.local tomorrow.

[Joe Ross]

Is this the same computer that gets stuck at [echo] Trying Target: roboRIO-1771.local in your other thread?. It sounds like mDNS issues could cause both.

Early in beta, you could type in an IP address to the driver station team number. Not sure if that functionality still exists, but you can try that to try to work around mDNS issues.

[nighterfighter]

Originally Posted by Joe Ross

Is this the same computer that gets stuck at [echo] Trying Target: roboRIO-1771.local in your other thread?. It sounds like mDNS issues could cause both.

Early in beta, you could type in an IP address to the driver station team number. Not sure if that functionality still exists, but you can try that to try to work around mDNS issues.

Yes, this is the same computer.

I'm not 100% sure what you mean by typing in an IP address for the driver station. I know in the previous years, the driver station would automatically assign your computer's IP address for you, after you input a team #.

However, with the driver station frozen, I can't access the settings page (of the Driver Station), to input anything.

I am going to reinstall the Driver Station on my laptop tonight, hopefully that fixes it.

Update: After uninstalling and reinstaling the entire Update Suite, the driver station appears to be working. (Not connected to a robot though). Hope I don't get the problem the original thread described, once I connect to the robot.