When the robot is enabled the drive station loses communication to the
robot and the RSL turns off entirely or goes to solid on. The RoboRio remains
on and the mode light remains green, indicating that the robot is still enabled.
We are seeing this consistently but not every time.
Sometimes it happens immediately upon enabling and other times it takes
several minutes. There is no specific time period.
roboRIO Firmware: 6.0.0f1 image is: FRC_roboRIO_2020_v10
Radio Firmware: On latest firmware as of 3/3/2020, version 20.0.0
Talon Firmware: 20.1
Spark Firmware: 1.5.2
Things we have tried with the same result
Replaced the roboRIO
Replaced the radio
Replaced the radio to roboRIO ethernet cable.
Replaced the drive station
Things we have tried that did not cause a disconnect
Connected directly to the roboRIO with a usb cable
Connected directly to the roboRIO with an ethernet cable
Coming up to our first event, and have no idea
Any help would be appreciated.
RSL off, for how long? There is a ~30 second full roborio reboot where the RSL turns off, and then comes back on.
There is also an 8-12 second “soft reboot” the roborio does where the RSL stays on solid, but comms will go away and come back.
When you lose comms, for how long?
Most of these things by the way are related to power fluctations. So the first things I would start checking are power related. Someone here on CD posted this a day or two ago, I shared it with my team that was having similar problems leading up to our week 1 competition: Common hardware problems for dead robots.
We were also having this soft reboot where a motor stall caused it. Never saw it before so I posted on CD, saw the motor voltage and our idle voltage was something like 11.5V
During our tests today we did not touch the robot.
We enabled it, waited 1 - 7 minutes and the phenomena would happen.
We have performed 5 tests today with the same result.
Last Test: 1 min after enable
roboRIO Lights: All lights listed are solid
Power light: Green, Status light: Blank, Radio light: Blank
Comm light: Green, Mode light: Green, RSL: Solid orange
Radio Lights: Power: Solid Blue, Wireless Status: Solid orange; Comm: Blinking Blue
Wired Light: Blank
Drivestation: “No Robot Communications” with no erros
We waited 5:22 after event, no reboot, no reenable
Please take a look at this thread (Robot Keeps Losing Com and Code). Particularly look at the list of items that Peter Johnson asked for information about. There are quite a few teams that are suffering similar problems – so if upon looking at that thread you think the behavior you’re seeing is the same please post there the information requested.
Thanks. Carl
Check in your log to be sure there are no loop overrun messages. Some of us have run into trouble with I2C devices causing loop overrun, and there’s a theory that this eventually causes the program to hang.
Try setting everything on your robot’s network to use a static IP.
Connect to your roboRIO at 10.TE.AM.2, go to network settings, and set the IP to static. Set the IP to 10.TE.AM.2, your subnet mask to 255.255.255.0, and your default gateway to 10.TE.AM.1. If you have a Limelight, JeVois, Raspberry Pi, or anything else that communicates on your robot’s network, make sure you do the same - connect to them, give them an IP of 10.TE.AM.X (where X is a number 1-255 that isn’t taken by anything else on the network), and the same subnet mask and default gateway as above.
Once that’s done, if you’re on Windows go to Control Panel -> Network and Internet -> Network and Sharing Center -> Change Adapter Settings -> Right click on Wireless Network Connection (if connecting wireless) and click Properties. From there, double click on “Internet Protocol Version 4” and click “Use the following IP address.” Set an IP 10.75.28.X, and the same subnet mask and default gateway as above. Then click OK On the two windows that should be open.
A heads up - if you’re running this setup on the field, you should use a subnet mask of 255.0.0.0 (not 255.255.255.0) for your driver station. The WPILib docs have more information.