Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   FRC Control System (http://www.chiefdelphi.com/forums/forumdisplay.php?f=176)
-   -   Roborio Communication Problems (http://www.chiefdelphi.com/forums/showthread.php?t=143161)

snekiam 04-02-2016 16:05

Roborio Communication Problems
 
Hello All!
We are having trouble maintaining a stable wireless connection to the robot through the OM5P-AN.
Code:

➔ Launching «'/home/lvuser/FRCUserProgram'»
Warning  44003  FRC:  No robot code is currently running.  Driver Station
 [HAL] Starting task FRC_DriverStation...
 NT: server: client CONNECTED: 10.33.22.150 port 57647
 NT: server: client CONNECTED: 10.33.22.150 port 57646
Warning  44002  Ping Results:  link-bad,  DS radio(.4)-bad,  robot radio(.1)-GOOD,  cRIO(.2)-GOOD,  FMS-bad FRC:  Driver Station ping status has changed.  Driver Station
Warning  44004  FRC:  The Driver Station has lost communication with the robot.  Driver Station
Warning  44004  FRC:  The Driver Station has lost communication with the robot.  Driver Station
Warning  44004  FRC:  The Driver Station has lost communication with the robot.  Driver Station
Warning  44004  FRC:  The Driver Station has lost communication with the robot.  Driver Station
Warning  44004  FRC:  The Driver Station has lost communication with the robot.  Driver Station
Warning  44004  FRC:  The Driver Station has lost communication with the robot.  Driver Station

Above is a paste from the driverstation console. Unfortunately, I don't know how to dive deeper into the logs and determine why the communication loss has happened. When we are wired directly to the roborio via ethernet, everything seems to work really well. We are running completely empty robotbuilder code, so nothing should be wrong there. Everything has been updated cleanly to the 2016 software/firmware versions. Can anyone shed any light on this for us?

EDIT: Found this screen in driverstation, seems like we have extremely high packet loss. Any ideas on how to combat this? We are experiencing this at more than one location, but otherwise I would've attributed it to our school's wireless network.

EDIT 2: Appears to be caused by Autodesk Application Manager. Apparently you have to kill it from task manager, not just click exit on the taskbar tray to fully kill it.


All times are GMT -5. The time now is 21:13.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi