Simulated Car Control in Proteus

Objectives

The objective is to use Systems Engineering practices to design the various subsystems (steering, motor controls, etc.) work correctly together.

Guidelines

The project begins with the identification of required part in Proteus. The microcontroller, DC Motors, sensors, H - Bridges, Joy Sticks (Potentiometers as voltage divider). A detailed study of unfamiliar components will take place after. Additional resources are available in the Files section of the Course Menu. You must integrate the subsystems and program the microcontroller to operate the car.

A Project Manual is also required. The Project Manual requires the following information:

1. An Analysis of Alternatives showing the alternatives considered and a justification for the chosen alternative;
2. A Bill of Materials that includes the eventual cost of building the simulated car;
3. A System Description that shows the data flow between the system and the subsystems, and between the subsystems;
4. An Operators Section, which describes how to operate the system; and
5. A Testing Section, which shows the Test Plan and results of the testing.

Milestones

Week 1: Review the requirements for the Project Manual. The testing procedures that you develop as you build the subsystems will be included in the Project Manual.

Develop software to control DC motor speed. Develop software to control stepper motor. Use H-Bridge to control motors.

Week 2: Develop software to steer the servo motor.

Program the interface between the potentiometer (voltage divider) and the microcontroller.

Week 3: Perform overview of the Systems Engineering approach. Identify subsystems to meet system requirements.

Week 4: Use voltage and current monitoring to assess the power requirements for each subsystem. Monitor subsystem power voltages while the system is operating to measure the amount of feed through and determine if interference is present.

Week 5: Determine the timing requirements for data to and from the subsystems. Choose the appropriate (interrupt or polling) techniques.

Week 6: Determine the requirement for a networking capability. Consider software routines to allow communication between systems and subsystems. Evaluate subsystem communications to ensure that requirements are met.

Week 7: Perform final testing of the project.

Grading Rubrics

Category	Points	Description
First Deliverable	10	For full credit, the project must be presented before the beginning of the Final Exam.
Visual Sensor Subsystem	10	The student must present documentation that the joysticks have been tested in the simulator and meet the system requirements.
Motor Subsystem	10	The student must present documentation that the Motor Subsystem has been tested and meet the system requirements.
Power Subsystem	10	The student must present documentation that the Power Subsystem has been tested and meet the system requirements.
Software Subsystem	10	The student must present documentation that the Software Subsystem has been tested and meet the system requirements.
System Operation	10	The student must present documentation that the entire System operates in accordance with the system requirements.
Total	60	A quality project will meet or exceed all of the above requirements.

Category	Points	Description
First Deliverable	10	For full credit, the Project Manual must accompany the presentation of the Simulated Car system at the beginning of the Final Exam.
Documentation and Formatting	10	The Project Manual must be typed and contained in a cover. Handwritten text or drawings are not acceptable.
Organization and Cohesiveness	10	The order of the subsections shall be as given in the Project Manual requirements above.
Content	10	The content shall be as given in the Project Manual requirements above.
Total	40	A quality paper will meet or exceed all of the above requirements.