[Team230]

Thanks for your input. We tried and fixed a bunch of things today, and now have a different set of problems. The problems seems to possibly have been caused by setting our network password to both the Primary and Secondary slots. The Samantha automatically connected to the Primary (as visible in samostat), and although the Primary and Secondary networks were identical, this seemed to be the problem, because when we overwrote the Primary network with a bogus address, FCS began to recognize the robot.

However, we now have a new problem. This happened to us at past competitions too, even though we've been able to connect successfully there. Randomly, the robot will suddenly cut power to all of the motors and servos. We've diagnosed the problem to determine that the NXT is still receiving signals from the Samantha, and the NXT still recognizes when joysticks are moved around or buttons are pressed (we have it beep). As well, the program is certainly working fine, because all of the controls are in the same loop as the beep, and there is no way that it could not be sending the command to run the motors. We've also ensured that power is not getting cut as all of the lights remain on and don't flicker when the motors stop. The problem can be resolved by restarting the robot and the NXT brick, and the robot will work again for another minute or so before refusing to run.

Do you have any idea why this new problem could by happening? Thank you very much!