Quote:
Originally Posted by Sixis
IR/ ultrasonic sensors, additional touch sensors, pressure sensors, bluetooth modules (or other forms of wireless communication in addition to the gaming adapter to give the driver more feedback on the robot), Servos/ different motors, and other microcontrollers/ controllers in general. Originally i wanted to set up a circuit running in parallel with the CRIO that could micromanage different aspects of the cometition. For instance ball placement/ detection, aiming, detecting/ avoiding other robots, anything that would make the robot (since it is supposed to be a robot) "smarter".
As for what you said about AM, i didn't necessarily mean that FIRST designed the restrictions around the parts AM already made however, i think AM is the only site that sells a majority of chassis parts and whatnot (aren't the pieces from the KOP all from andymark?). Additionally i think the only place where you can buy a lot of the electrical components is AM. I would just like to see the rules expanded so that different parts can be used. I just feel like FIRST has a lot of room to improve in terms of the robots. I feel that by allowing people to bring in knowledge from different fields they can greatly improve the overall quality of the game and robot.
|
I guess I don't understand your post.
IR sensors are legal. Ultrasonic sensors are legal. Touch sensors are legal. Pressure sensors are legal. Other microcontrollers used in conjunction with the Crio are legal (the crio and wireless requirements are there for safety reasons - FIRST needs to be able to KNOW they can kill your robot). Off-crio processors are legal. Custom circuits are legal.
Different motors? Why? Were the fisher prices and cims not powerful or fast enough? Your circuit would have been perfectly legal - as long as it fed in to the Crio.
The only thing I see in your post is the servo / motor changes and wireless.
The wireless is that way for very specific reasons: interference, troubleshooting..... what single component gave FRC the biggest issue this year? 1 guess.
Did you fully saturate the data feedback to the driver? Considering that the basic dashboard feeds back every input and output on crio, plus streaming video at the same time, I'm not sure exactly what you would want that you couldn't add in.
Can you be more specific on the shortcomings of the dashboard feedback, and the wireless data connection? Can you be more specific as to why you couldn't feed your circuit back through the Crio?