Hello everyone, after updating our rev power distribution hub the other day we immediately had every light on the hub start blinking red showing sticky faults. This is a new hub so we don’t have much experience with it, does anyone have any tips?
2 Likes
What does the Rev client say the sticky fault is?
1 Like
Try clearing the sticky faults and see if they come back. The blinking light is indicative of a previous tripped breaker condition.
We try to clear the faults in the software and then it comes back after we reboot.
1 Like
On the power hub I get brownout, CAN warning, CAN bus off, and has reset.
On the pneumatic hub I get brownout, and CAN warning
We’ve been having similar issues which require us to re-clear sticky faults every time we boot up the robot. Has anyone identified the root cause of this?
2 Likes
We have the same issue, as apparently do others (see this thread). I’ve got an case open with REV support and have been collecting data for them. Given that it’s only an indicator and doesn’t affect power transfer, we’re not too concerned about it, but it would be nice to see it resolved; if the LEDs work properly it’ll be a valuable feature to have, but as-is they can’t be trusted. They are definitely spurious faults; we’ve never had a breaker trip, much less all of them!
FWIW at least for us, current monitoring appears to work fine despite this.
3 Likes
We have been getting similar issues. They seem to just indicate that the PDH lost power when the robot powered down. They’re not pretty to look at, but they don’t appear to inhibit software/robot function to my knowledge.
edit: It would still nice to see a fix to this so that the LEDs on the PDH/PDP are accurate.
we cannot enable the robot until we clear those sticky faults every time. Then we disable and they come right back
My bad. I haven’t had this happen but I shouldn’t have assumed it wasn’t happening for others.
I haven’t used them myself, but have you tried:
In Java WPILib:
clearStickyFaults()
in the package
edu.wpi.first.wpilibj.PneumaticHub
and
clearStickyFaults()
in the package
edu.wpi.first.wpilibj.PowerDistribution
In C++ WPILib:
frc::PneumaticHub::ClearStickyFaults()
and
frc::PowerDistribution::ClearStickyFaults()
3 Likes
Have not but will do, thanks!
2 Likes
At least as of a month ago, it seemed like this was partly the expected behavior. Its something that could be updated in the firmware, but at least for now most cases shutting off the PDH will cause all the brownout sticky faults to trigger.
1 Like
What do you mean by you can’t enable the robot with the sticky faults. What happens?
1 Like
Until they are cleared, the robot will not enable.
I believe this is our order of operation:
We clear sticky faults, Robot will enable and function as expected.
We disable, PD hub starts flashing red on all channels/ports, will not allow us to re-enable
We clear sticky faults again, 4 High Current Channels remain solid Red, ALL Low Current Channels & Switchable channel remain solid Red, but it allows us to Enable the robot and everything works as expected, despite the solid Red channels.
@ns3517 and @HarrisonKaufman1619, please reach out to us at [email protected]. We have some troubleshooting steps that will help us determine if there is an actual hardware fault or if this is just a bug in our fault reporting.
I’d like to emphasize that these faults will not affect power distribution or robot performance.
Are you able to send us some video of this behavior? There isn’t a mechanism that should be able to prevent the robot from enabling that depends on the fault status of the PDH.
I still don’t understand what you mean can’t enable the robot. What happens when you can’t enable the robot.
I press the enable button on the dashboard/driver station and nothing happens
Does it show “teleop enabled” in the center screen or does it still say disabled?
Do you have any further documentation on this? You post implied (at least to me) that clearStickyFaults() was a static method, but it’s not. I’m a little confused as to where to create the PoweDistribution object.
Edit: Was able to find documentation here.
1 Like
Yes we are currently in contact with your team of reps. Thank you