Quote:
Originally Posted by Xenozero
well, we did change the Ethernet cord with a better one that we borrowed and made sure both ends were snaped in, um let me ask you , does it mater which port is being used on the watchdog? because if the ports do have a potential to go would i be able to use the other and have the problem fixed (even though i believe we tried both). but the disconnection is an interesting tid bit and may help to solve this mystery. the motor drives a rod that is surrounded by a cloth belt that spans the width of the robot the cloth is tensioned by another rod at the top of the rod that has a bearing in it to allow it to spin along with the driven rod. something that does not support the disconnection / vibration possibility is that the wheels that shoot the balls out at the top of our robot vibrate alot and do not affect the robot at all, plus the belt does'nt really vibrate at all, it slides
|
Either port on the DS can be used. The watchdog is on the cRIO and will disable all ports if more than 5 packets (~100ms) are missed. This is hard programmed into the FPGA on the cRIO. When the watchdog is tripped (not fed) then ALL outputs are disabled (This would explain ALL of your speed controllers shutting down), this is a safety feature to prevent a runaway robot.
You might want to look for shavings or debris inside the cRIO ethernet ports (or damage to the pins) as that (with vibration) would cause communication corruption.
Daniel Krastev & Creator Mat,
I doubt it's an electrical issue because he states that it works on the playing field but not (Tethered) in the pits. Therefore I suspect the tether system (ethernet ports and cable)