Requirements and Verification

Description

Requirements: Requirements provide a technical definition of what each and every subsystem in your design must be able to do. Each subsystem should be associated with a set of requirements. If all requirements have been met for every module, you should have a fully functioning project. A good set of requirements should meet the following criteria.

Verification: Verifications are a set of procedures that you will use to verify that a requirement has been met. Every requirement should have a verification procedure associated with it. Good verification procedures will meet the following criteria.

Remember, a good R&V table should function like a debugging checklist.

Antweight Combat Robot

Ryan Middendorf, Teodor Tchalakov

Antweight Combat Robot

Featured Project

Antweight Combat Robot

Team Members:

Ryan Middendorf (ryanjm8),

Teodor Tchalakov (ttcha2)

Problem

The constraints for Professor Gruev’s competition are as follows:

Must weigh less than 2 lbs

Must be 3D printed in PET(G), ABS, or PLA(+)

Must have controlled movement

Must be controlled over bluetooth or wifi by a PC

Must have a fighting tool to use against other bots

The main challenges involved in this are making a custom control solution and designing a combat robot that will not only survive the 2 minute matches but actually win them by immobilizing the other robot.

Solution

To meet these constraints, we plan to create a custom PCB that contains 3 brushless electronic speed controllers (ESCs) to control the drive and weapon motors and uses a microcontroller to communicate with a PC over bluetooth and control the robot. For the actual robot design we plan to build a vertical spinner which usually performs best in this weight class. The "tool" will be spun by a brushless motor, and so will both sides drive wheels.

Subsystem 1 - Custom PCB and Power

Our first subsystem will be the custom PCB. It has to contain 3 brushless ESCs and interface with a bluetooth enabled microcontroller such as an ESP32 or STM32 that will receive instructions from a PC and turn them into usable PWM signals for the ESCs. It will also have to be powered by a LiPo battery through an XC30 connector and include an integrated screw switch so the robot can be turned on and off simply and safely.

Subsystem 2 - Drive train

Our second subsystem will be the drive train. Our robot will be driven by 2 brushless motors, 1 on each side. Each motor will drive 2 wheels that are connected by a belt so the robot will have a simplified 4 wheel drive in a tank drive configuration.

Subsystem 3 - Weapon/Tool Assembly

Our third subsystem will be the weapon/tool assembly. Our tool will be a robust vertical spinner, most likely a drum/eggbeater style. This type of tool has a lot of success in combat robotics due to its ability to dissipate the force of hitting an opponent into the floor very efficiently. This will be driven by a substantially larger brushless motor than the drive system so it can deliver much more powerful hits.

Subsystem 4 - Chassis

Our fourth subsystem will be the chassis. The chassis has to be very robust and able to withstand all the damage that will be dealt to it throughout a match. It also has to be able to contain all the electronics and prevent them from being damaged. The chassis will be 3D printed out of one of the approved materials listed above but most likely PLA+.

Subsystem 5 - Controlling from PC

Our fifth and final subsystem will be how our robot is controlled by a PC. This will be a program run locally on a PC that takes keyboard inputs and transforms them into instructions that are sent to the microcontroller inside the robot to control it.

Criterion for Success

We would consider our project a success if we are able to communicate with the robot from our computer and successfully drive it around the arena during a match. The commands sent from the pc need to be processed by the microcontroller and the motors need to be powered properly and behave correctly during a match. The robot will also have to be able to shut itself off if the bluetooth gets disconnected for some reason.