Difference between revisions of "S19: Run D.B.C"
Proj user10 (talk | contribs) (→WIRING HARNESS) |
Proj user10 (talk | contribs) (→SCHEDULE) |
||
(10 intermediate revisions by the same user not shown) | |||
Line 314: | Line 314: | ||
! scope="row"| 3/17/19 | ! scope="row"| 3/17/19 | ||
| | | | ||
+ | * <span style="color:#000000">Establish Git Repository Structure</span> | ||
+ | * <span style="color:#FF8C00">Completed high-level system block diagram </span> <br /> | ||
+ | * <span style="color:#000000">Completed PCB design requirements</span> | ||
+ | * <span style="color:#000000">Selected PCB manufacturer</span> | ||
+ | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
| | | | ||
* | * | ||
− | + | * | |
+ | * | ||
* | * | ||
Line 324: | Line 333: | ||
! scope="row"| 3/24/19 | ! scope="row"| 3/24/19 | ||
| | | | ||
+ | * <span style="color:#008000">Successfully unit test a JAVA module with J-UNIT (JAVA unit test framework)</span> | ||
+ | * <span style="color:#008000">Choose Android mobile phone/OS to load app onto</span> | ||
* <span style="color:#EE82EE">Interface with with speed controller and servo controller</span> <br /> | * <span style="color:#EE82EE">Interface with with speed controller and servo controller</span> <br /> | ||
* <span style="color:#FF8C00">Finalize high-level system block diagram and control scheme</span> <br /> | * <span style="color:#FF8C00">Finalize high-level system block diagram and control scheme</span> <br /> | ||
+ | * <span style="color:#36c">Interface with GPS and compass modules</span> | ||
+ | * <span style="color:#EE82EE">Record how servo and DC motors react to RC Transmitter and Receiver feedback</span> <br /> | ||
+ | * <span style="color:#000000">Ordered PCB</span> | ||
| | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
* | * | ||
| | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
* | * | ||
Line 338: | Line 362: | ||
| | | | ||
* <span style="color:#000000">'''All parts have been ordered'''</span> | * <span style="color:#000000">'''All parts have been ordered'''</span> | ||
− | * <span style="color:# | + | * <span style="color:#008000">Create button to launch mobile application</span> |
− | * <span style="color:# | + | * <span style="color:#008000">Integrate Google Maps into mobile application</span> |
− | * <span style="color:# | + | * <span style="color:#d33">LPC 1758 responds to feedback from bump sensor</span> |
+ | * <span style="color:#d33">LPC 1758 responds to feedback from Ultrasonic sensors (reports distance of objects in their detection radius)</span> | ||
+ | * <span style="color:#d33">Complete DBC CAN message format</span> | ||
+ | * <span style="color:#36c">Use feedback from GPS and compass to calculate bearing angle</span> | ||
* <span style="color:#EE82EE">LPC 1758 responds to feedback from motor speed sensor (reports RPM of wheels, when a PWM signal is applied) | * <span style="color:#EE82EE">LPC 1758 responds to feedback from motor speed sensor (reports RPM of wheels, when a PWM signal is applied) | ||
* <span style="color:#EE82EE">Complete DBC CAN message format</span> | * <span style="color:#EE82EE">Complete DBC CAN message format</span> | ||
| | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
* | * | ||
Line 351: | Line 381: | ||
* | * | ||
| | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
* | * | ||
Line 362: | Line 395: | ||
! scope="row"| 4/7/19 | ! scope="row"| 4/7/19 | ||
| | | | ||
− | * <span style="color:# | + | * <span style="color:#008000">Successfully get starting and destination coordinates </span> |
+ | * <span style="color:#d33">Complete sensor module code and push final revision to GitLab</span> | ||
+ | * <span style="color:#FF8C00"> Master controller can send/receive CAN messages to/from all other controllers on CANbus</span> | ||
+ | * <span style="color:#36c">Transmit latitude and longitude coordinates as CAN messages to master controller </span> | ||
+ | * <span style="color:#EE82EE">Angle wheels left/right/straight based on CAN feedback from master controller</span> <br /> | ||
| | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
| | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
Line 373: | Line 418: | ||
| | | | ||
* <span style="color:#000000">'''All modules have been fully assembled'''</span> | * <span style="color:#000000">'''All modules have been fully assembled'''</span> | ||
+ | * <span style="color:#008000">Successfully integrate checkpoints into mobile app </span> | ||
+ | * <span style="color:#FF8C00">Completed implementation of speed control algorithm</span> | ||
+ | * <span style="color:#36c">Transmit heading and bearing angle as CAN messages to master controller </span> | ||
+ | * <span style="color:#EE82EE">Implement obstacle avoidance algorithm</span> <br /> | ||
| | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
| | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
Line 382: | Line 439: | ||
! scope="row"| 4/21/19 | ! scope="row"| 4/21/19 | ||
| | | | ||
+ | * <span style="color:#000000"> Complete first vehicle test drive</span> | ||
+ | * <span style="color:#008000"> Send starting/destination coordinates to bridge controller </span> | ||
+ | * <span style="color:#008000"> Send starting/destination coordinates as CAN messages from bridge controller to master controller</span> | ||
+ | * <span style="color:#EE82EE">Design a feed back mechanism to adjust speed of DC motor using RPM sensor values for vehicular movement on the slope</span> <br /> | ||
+ | | | ||
+ | * | ||
+ | * | ||
+ | * | ||
* | * | ||
| | | | ||
* | * | ||
− | + | * | |
+ | * | ||
* | * | ||
Line 392: | Line 458: | ||
! scope="row"| 4/28/19 | ! scope="row"| 4/28/19 | ||
| | | | ||
+ | * <span style="color:#000000"> Achieve full communication between all subsystems on the CANbus</span> | ||
+ | * <span style="color:#EE82EE">Use GPS feedback to govern (motor behavior) car movement</span> <br /> | ||
+ | | | ||
+ | * | ||
* | * | ||
| | | | ||
* | * | ||
− | |||
* | * | ||
Line 403: | Line 472: | ||
| | | | ||
* <span style="color:#000000">'''RC car has been fully assembled and modules have been integrated'''</span> | * <span style="color:#000000">'''RC car has been fully assembled and modules have been integrated'''</span> | ||
+ | * <span style="color:#000000"> Complete integration of PCB and wiring harness </span> | ||
| | | | ||
+ | * | ||
* | * | ||
| | | | ||
+ | * | ||
* | * | ||
Line 412: | Line 484: | ||
! scope="row"| 5/12/19 | ! scope="row"| 5/12/19 | ||
| | | | ||
− | * | + | * <span style="color:#000000"> Resolve any remaining bugs or concerns </span> |
| | | | ||
* | * |
Revision as of 23:41, 19 March 2019
Contents
- 1 ABSTRACT
- 2 INTRODUCTION & OBJECTIVES
- 3 SCHEDULE
- 4 BILL OF MATERIALS
- 5 HARDWARE INTEGRATION PCB
- 6 WIRING HARNESS
- 7 CAN NETWORK
- 8 ANDROID MOBILE APPLICATION
- 9 BRIDGE CONTROLLER & LCD MODULE
- 10 GEOGRAPHIC CONTROLLER
- 11 MASTER CONTROLLER
- 12 MOTOR CONTROLLER
- 13 SENSOR CONTROLLER
- 14 CONCLUSION
- 15 Grading Criteria
ABSTRACT
The RUN-D.B.C project, involves the design and construction of an autonomously navigating RC car. Development of the R.C car's subsystem modules will be divided amongst and performed by seven team members. Each team member will lead or significantly contribute to the development of at least one subsystem.
INTRODUCTION & OBJECTIVES
RC CAR OBJECTIVES | ||||
---|---|---|---|---|
|
TEAM OBJECTIVES | ||||
---|---|---|---|---|
|
CORE MODULES OF RC CAR | ||||
---|---|---|---|---|
|
PROJECT MANAGEMENT ADMINISTRATION ROLES | ||||
---|---|---|---|---|
|
TEAM MEMBERS & RESPONSIBILITIES | ||||
---|---|---|---|---|
Team Members |
Administrative Roles |
Technical Roles | ||
|
|
| ||
|
| |||
|
|
| ||
|
|
| ||
|
| |||
|
| |||
|
|
SCHEDULE
TEAM MEETING DATES & DELIVERABLES | ||||
---|---|---|---|---|
Week# |
Date Assigned |
Deliverables |
Status |
Date Completed |
1 | 2/16/19 |
|
|
|
2 | 2/24/19 |
|
|
|
3 | 3/3/19 |
|
|
|
4 | 3/10/19 |
|
|
|
5 | 3/17/19 |
|
|
|
6 | 3/24/19 |
|
|
|
7 | 3/31/19 |
|
|
|
8 | 4/7/19 |
|
|
|
9 | 4/14/19 |
|
|
|
10 | 4/21/19 |
|
|
|
11 | 4/28/19 |
|
|
|
12 | 5/5/19 |
|
|
|
13 | 5/12/19 |
|
|
|
14 | 5/22/19 |
|
|
|
BILL OF MATERIALS
MICRO-CONTROLLERS | ||||
---|---|---|---|---|
PART NAME |
PART MODEL & SOURCE |
QUANTITY |
COST PER UNIT (USD) | |
|
|
|
|
RC CAR | ||||
---|---|---|---|---|
PART NAME |
PART MODEL & SOURCE |
QUANTITY |
COST PER UNIT (USD) | |
|
|
| ||
|
|
| ||
|
|
|
ANDROID MOBILE APPLICATION & BRIDGE CONTROLLER | ||||
---|---|---|---|---|
PART NAME |
PART MODEL |
QUANTITY |
COST PER UNIT (USD) | |
|
|
|
GEOGRAPHIC CONTROLLER | ||||
---|---|---|---|---|
PART NAME |
PART MODEL |
QUANTITY |
COST PER UNIT (USD) | |
|
|
|
|
MASTER CONTROLLER | ||||
---|---|---|---|---|
PART NAME |
PART MODEL |
QUANTITY |
COST PER UNIT (USD) | |
|
|
|
|
MOTOR CONTROLLER | ||||
---|---|---|---|---|
PART NAME |
PART MODEL |
QUANTITY |
COST PER UNIT (USD) | |
|
|
|
|
HARDWARE INTEGRATION PCB & WIRING HARNESS | ||||
---|---|---|---|---|
PART NAME |
PART MODEL |
QUANTITY |
COST PER UNIT (USD) | |
|
|
|
|
SENSOR CONTROLLER | ||||
---|---|---|---|---|
PART NAME |
PART MODEL |
QUANTITY |
COST PER UNIT (USD) | |
|
|
| ||
|
|
|
HARDWARE INTEGRATION PCB
Hardware Design
<Picture and information, including links to your PCB
WIRING HARNESS
Hardware Design
<Picture and information, including links to your PCB
CAN NETWORK
<Talk about your message IDs or communication strategy, such as periodic transmission, MIA management etc.>
Hardware Design
<Show your CAN bus hardware design>
DBC File
<Gitlab link to your DBC file> <You can optionally use an inline image>
ANDROID MOBILE APPLICATION
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
<Bullet or Headings of a module>
Bug Tracking
<Problem Summary> <Problem Resolution>
BRIDGE CONTROLLER & LCD MODULE
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
<Bullet or Headings of a module>
Bug Tracking
<Problem Summary> <Problem Resolution>
GEOGRAPHIC CONTROLLER
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
<Bullet or Headings of a module>
Bug Tracking
<Problem Summary> <Problem Resolution>
MASTER CONTROLLER
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
<Bullet or Headings of a module>
Bug Tracking
<Problem Summary> <Problem Resolution>
MOTOR CONTROLLER
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
<Bullet or Headings of a module>
Bug Tracking
<Problem Summary> <Problem Resolution>
SENSOR CONTROLLER
<Picture and link to Gitlab>
Hardware Design
Software Design
<List the code modules that are being called periodically.>
Technical Challenges
<Bullet or Headings of a module>
Bug Tracking
<Problem Summary> <Problem Resolution>
CONCLUSION
<Organized summary of the project>
<What did you learn?>
Project Video
Project Source Code
Advice for Future Students
<Bullet points and discussion>
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.