Quote:
Originally Posted by tr6scott
We are constantly having issues this year.
Labview, almost everytime we make a change and deploy we lose connection the first time, requires us to send code a second time to enable.
Many times the driver station does not detect comms. We are actually running code from the same laptop, the driver station on the same laptop does not see roborio.
I have also had the webpage up and working and the driver station not have comms.
|
We have the exact same issue as you this year. Last year as well as this year, we have run using a static IP on the roboRIO. We had no trouble last year, but for some reason this year are having trouble deploying code every now and then. Ultimately we found that pinging team-xxxx-FRC.local, would take a while to connect and pinging 10.xx.xx.2 would connect instantly. We attempted to switch our deployment target to our static IP, and it fixed our problems with deploying, but if you choose this route, you cannot tether directly via USB because it will assign the roboRIO a different IP.
Another note, anytime we have this deployment issue, we always have a red or blank comm light. For now we have been resetting the roboRIO to get a green comm light. This is just our fix for now, and it will work for the time being. We are going to work more on it this week and will keep you posted. I'm guessing your team is having a similar problem to us, and I hope I helped to identify the problem more.