Bot Disconnects from RoboRIO and completely disconnects from radio

We’ve been having this issue with our robot where for seemingly no apparent reason, our computer will disconnect from our robot at random times. The computer will completely disconnect from the radio and everything.

At first we thought it was an update so we reflashed the firmware to both the roboRIO and radio. That didn’t solve it. We then assumed a wire issue, but nope. We disassembled and reassembled the robot twice to no avail. We’ve put the robot on a table and propped it up so the wheels didn’t touch the floor and ran the robot then, and even with only the wheels moving it still happens.

We’ve had the robot disconnect immediately after enabling, and had it run for 20+ minutes without it disabling, but eventually it disables. We try doing runs without moving it, and runs where we don’t stop moving the wheels. Both times it disconnects.

We’ve tried different laptops, different firmware, different wires. different radio, different batteries, different roboRIO, different fuses, and all seem to result in the same thing.

We have noticed that the swerve modules will suddenly draw tons of power (160 AMPS) and brownout which cases it sometimes, but other times it wont brownout at all and disconnect.

Some things to note:

  • We’re using swerve drive
  • We’re using Spark Max motor controllers
  • We’ve had the same error occur both connected via WiFi and USB

I’m a coder and have been doing it for 2 years, so I consider myself sort of a newbie but even our most experienced coders have been stumped. Any help would be wonderful. Thank you!

(P.S. I’ve seen other threads with other similar questions but all get locked after a year with no answer.)

Edit: In some runs, it seems to brownout early on but doesn’t disconnect until later.

This is the thing driver station said when it crashed

And sometimes it shows this error:

Have you installed the 24.0.1 version of the driver station? See Known Issues — FIRST Robotics Competition documentation.

Yes

image

Have you deployed a blank robot project and tested it?

This sounds like a possible code crash to me.

If you are browning out, I would expect to see brown dots all over log graph. I am not.

I see two occurrences of brown out on zooming in. Those may be normal my on your current limits. What are your drive current limits?

Are you using I2C by any chance? Anything plugged into that port on the RIO (REV color sensor) or anything plugged into MXP expansion port?

There’s something going on with the CPU utilization, but it might be a data atrifact in the wake of losing connectivity. Any events show up right around the time where the green line drops out? If you can share your logs from maybe a couple of occurrences of the problem and send a couple of pictures of the wiring on your 'bot, there could be clues there…

How long is the disconnect?
Does the DS reconnects with the robot immediately, after around 10 seconds, 1 minute or something else?

There set to 80 amps but they shouldn’t hit that in the code.

If you are only limiting your 4 drivetrain motors to 80 amps, that will brown out the robot. In my previous tests pulling 200 amps or so will drop a newish battery to brown own. You are potentially allowing the motors to pull 320 amps.

I sent this thread to the lead programmer on my team since he knows more about this than I do. Although I mistakenly said 80 amps in total when I meant 80 amps per drivetrain motor.

My team is having a similar issue. Have you figured anything out since?

Yes, we have. It seemed to be a malfunctioning motor controller. We were using Sparkmaxes. There was a leak in our roof and water dripped straight into a box of motor controllers. We bought new ones, but our junior electrical member accidentally put one of the water-damaged ones on our robot. After switching out the faulty one with a new one, it seemed to work out just fine.

To anyone in the future having a similar issue, try switching out your motor controllers individually and see if that fixes the issue. If you are having this issue, it is most likely a hardware issue. I hope this helps :grin:!

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.