Thread: motors enabled while cRIO reboots (Safety hazard)
View Single Post
  #1   Spotlight this post!  
Unread 16-03-2012, 15:55
byteit101's Avatar
byteit101 byteit101 is offline
WPILib maintainer (WPI)
AKA: Patrick Plenefisch
no team (The Cat Attack (Formerly))
Team Role: Programmer
  
Join Date: Jan 2009
Rookie Year: 2009
Location: Worcester
Posts: 699
byteit101 is a glorious beacon of lightbyteit101 is a glorious beacon of lightbyteit101 is a glorious beacon of lightbyteit101 is a glorious beacon of lightbyteit101 is a glorious beacon of lightbyteit101 is a glorious beacon of light
motors enabled while cRIO reboots (Safety hazard)
When we reboot our robot via the "Reboot cRIO" button on the DS, motors (relays) revert to pre-disable state.
for example, we have a compressor and a harvester that are on the relay modules, and while testing, may disable the robot while not turning them off. when we hit reboot, if the harvester was on before we disabled it, it will turn on again, and stay on until the cRIO loads (not sure if it stops at FRC_NetworkCommunication.out or FRC_UserProgram.out, but its one of the two). unplugging ethernet cable, flipping switches does nothing (as expected).
This is a real safety hazard, and we have duplicated it on two seperate robots, with different cRIOs, different Sidecars, different modules, and different cables.
The relay lights on the sidecar are on.
Any idea how to fix this?
__________________
Bubble Wrap: programmers rewards
Watchdog.Kill();
printf("Watchdog is Dead, Celebrate!");
How to make a self aware robot: while (∞) cout<<(sqrt(-∞)/-0);
Previously FRC 451 (The Cat Attack)
Now part of the class of 2016 at WPI & helping on WPILib
Reply With Quote