Difference between revisions of "F17: Optimus"

Revision as of 02:32, 8 December 2017

Project Title

Optimus - Self Navigating R/C Car powered by SJOne(LPC1758) micro controller

Abstract

This section should be a couple lines to describe what your project does.

Objectives & Introduction

Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

Team Members & Responsibilities

Master controller, QA
- Revathy
- Kripanand Jha

GPS Controller
- Sneha
- Sarvesh

Sensor Controller
- Sushma
- Harshitha
- Supradeep

Android App, Bluetooth/App Interface
- Parimal

Motor Controller
- Rajul
- Unnikrishnan

PCB Design
- Rajul

Schedule

Legend:

Major Feature milestone , CAN Master Controller , Sensor & IO Controller , Android Controller, Motor Controller , Geo , Testing, Ble controller, Team Goal

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.

Week#	Date	Planned Task	Actual	Status
1	9/23/2017	Decide roles for each team member Read FY16 project reports and understand requirements Setup Gitlab project readme Ordered CAN Tranceivers and get R/C car	Team roles are decided and module owners are assigned Gitlab project is set Ordered CAN tranceivers and got R/C Car	Complete.
2	9/30/2017	Design software architecture for each module and design signal interfaces between modules Setup Wiki Project Report template Design Hardware layout of system components Create component checklist and order required components for individual modules. Setup Gitlab project code for each modules	Overall project requirements are understood Wiki Project report setup is done Odered components for Geo controller module Initial commit of project base is done	Complete
3	10/14/2017	Major Feature: Implement Free run mode Implement heartbeat messages and initial system bootup sync between modules Interface the RPLidar to SJOne board via UART Achieve basic communication such as obtaining the device and health info. Study of Android Toolkit for Bluetooth Adapter connections and APIs Study of HC-05 Bluetooth Module Creating APIs for Start/ STOP button requests to write to output-Stream buffers Creating RFComm SPP Connection socket and the rest of UI for basic operation of Pairing, Connection Checking the AT Command sequence for Bluetooth Operation and Pairing Automating the AT Command sequence for Bluetooth HC-05 operation and Android App Run Motors via commands from SJOne Automatically Order the RPM sensor module for the Drive Controller Design and Order PCB	Major Feature: Implemented Free run mode Added hearbeat messages from all controllers to master in can_db and implemented the handling functions in master controller Implemented speed steer command CAN msg transmission and handling in Master controller. Master-Drive integration phase-I Interfaced RPLidar to SJOne board and achieved basic communication via UART. Started obtaining data as well. Android:Android API for Bluetooth Adapter connections studied. Android:Learning of AT Command sequence for Bluetooth Operation and Pairing done. Android:Created Start/Stop API's for button requests to be Sent to HC-05 IC. Android:Basic Pairing Operation Working. Motor: ESC Traxxas XL-5 (Electronic Speed Control) interfaced to SJOne board Tested and identified duty cycles for different speeds required; Callibration and testing of ESC is over exteral switch at P0.1 Ordered RPM sensor	Complete
4	10/21/2017	Major Feature: Implement Basic Obstacle Avoidance in Free-run mode Add all modules CAN messages to DBC file Test steer and speed CAN commands between Master and Motor Implement Obstacle avoidance algorithm Obtain data from the lidar and process the data i.e. decide on the format in which the data has to be sent to the master Write unit test cases for the lidar. Interface compass module to SJOne board and calibrate the errors find the heading and bearing angle based on mocked checkpoint Test and verify GPS module outdoor to receive valid data and check for errors Calibrate the GPS module error Design and implement the DRIVE_CONTROLLER STEER/SPEED interface with Master (TDD) Install the new RPM sensor module for the Drive Controller Operating motors based on the CAN messages from the Master	Major Feature: Implemented Free-run mode w/o obstacle avoidance Added all modules basic CAN messages in can_db Implemented interface files in master controller to handle CAN messages from all nodes to master Implemented Master-Drive controller Integration Implemented Master-Bluetooth controller integration Added all modules basic CAN messages in can_db GPS integrated to SJONE board Added all modules basic CAN messages in can_db Wrote unit test cases for the LIDAR. Wrote logic for dividing the information obtained from the lidar into sectors and tracks. MASTER_SPEED_STEER_CMD was defined to use 8-bits for speed control (neutral, forward, and reverse); 9-bits for steer control (straight, left, and right) Designed glue code: DriveManager and hardware interface code: DriveController using TDD (test code in _MOTOR/_cgreen_test/) Got the Traxxas #6520 RPM sensor; installed the same with the slipper clutch; Observed the RPM sensor trigger over an oscilloscope and found the minimum distance of magnet to RPM sensor is not achievable with the stock slipper clutch. Ordered Traxxas #6878 new slipper clutch and ball-bearings Master - Drive Controller Interface implemented and tested over CAN; Check "drive" terminal command on Master controller	complete
5	10/28/2017	Major Feature: Implement maneuvering in Master controller Implement maneuvering algorithm to drive steering angle of the servo Implement maneuvering algorithm to control ESC speed Test and validate the information obtained from the sensor. Send the Lidar data and heartbeat over CAN. LIDAR should be fully working. Identify the basic speed(s) at which the car shall move; the min, max and normal forward speeds, and the min and normal reverse speeds Interface the RPM sensor over ADC and validate the readings Writing PID Algorithm for Motor Control Calibrating PID constants according to the Motors Testing the Bluetooth Range and multiple pairing option to establish security of the Master device Testing the accuracy of GPS while moving Made the code modular and added the wrapper function for all the important modules Worked on android app which will dump the lattitude and longitude information for checkpoints Test the accuracy of GPS while moving Get the code review done and do the testing after that Worked on the Android app that will dump the checkpoints into a file Finish PCB design and place order	Major Feature: Implemented maneuvering in Master-Geo controller Major Feature: Implemented Basic Obstacle Avoidance in Free-run mode Implement maneuvering algorithm in android app is moved to next week schedule Implemented maneuvering algorithm in Master to drive steering angle of the servo Implement maneuvering algorithm in Master to control ESC speed Unit Testing obstacle avoidance algorithm Tested and validated the sensor data by plotting graphs in an EXCEL sheet. Sending the obstacle information and heartbeat over CAN. LIDAR fully working and sending obstacle information. Identified basic speeds, slow, normal, and turbo for forward and reverse Interfaced the RPM sensor over GPIO and validated; but the clutch gear with magnet was far apart from the RPM Sensor Wrote the PID code keeping future integration in mind; Have pushed the code Failed to use RPM sensor - new clutch gear also did not work (magnet is too far away - validated with Oscilloscope); Have to consider using IR sensor for feedback Android:Tested successfully individual and multiple Device pairing. Android:Android app updated with Navigation and Drawer Modules with Detecting NAV points. Tested the accuracy of GPS while moving Made the GPS and compass code modular and checked the functionaity after the changes Worked on the Android app that will dump the checkpoints into a file Completed PCB Design	Complete
6	11/07/2017	Major Feature: Implement maneuvering with mocked GEO checkpoints Collect mock checkpoints using the Android Data Collector application Collect mock checkpoints using the GEO module and compare for any discrepancies Identify I/O on-board Display information; Currenly identified are documented below: Health status like GPS Lock status, etc. Identify hardware to check battery-status and procure the same; update PCB as well Display bluetooth pairing status Test on-board I/O module for bluetooth pairing status In case RPM installation/usage fail, Identify new mechanism for feedback and order components; Update PCB as well to include new hardware Implement simple feature additions on steer control to handle reverse; basically steering rear-left and rear-right has to be practically implemented on motor/drive controller Receive GEO Controller's Turning-angle message and compute target steer Use GEO Controller's distance to next-checkpoint information to compute target speed Mock checkpoint navigation testing using different possible obstacle heights and forms possible Identify advertisement messages on the DBC file and add documentation in Wiki; Currently identified advertisements: a) current GEO location, b) SENSOR radar map Shall define the BLE Controller to android message structure and message generation-intervals (classify on-demand advertisements and periodic advertisements) Implement marker for current location display - which is an on-demand advertisement Implement feature for the user to enter destination - a Google Map View shall be shown to the user to confirm route from source(current car location) to destination Android app (once on the new device) shall download the entire offline map information of the SJSU campus and store it on a SQLite database	Major Feature: Implemented maneuvering with mocked GEO checkpoints Provided Mock checkpoints and used the heading and bearing angle logic to get the turning angle Collected mock checkpoints and check for the error with different places Interfaced the Sparkfun Seven segment display with the SJOne Board. Implemented interface method to receive GEO Controller's Turning-angle message and set target steer Target speed is not changed between checkpoints.So geo feedback for distance to destination is not used in design Destination Reached flag is tracked to stop the car on reaching destination Checkpoint Id CAN signal is processed by Master to start the car once destination is selected Android:Implemented Marker for current position Display. Android:User entry for setting up destination on MAP done. RPM Installation failed, but could get auxiliary hardware (motor pinion) from local shop and get it working Implemented basic motor feedback using hall sensor (RPM sensor); tested working on ramps Steer left and right on reverse now follows natural order; Could not finish literal reverse-left and reverse-right implementation; Moved this task forward; Had to test and implement motor feedback this week Defined the BLE Controller messages to android in JSON message structure and message generation-intervals (classify on-demand advertisements and periodic advertisements) On Demand Advertisement- Current Marker Location Draggable Destination Marker for final destination and intermittent checkpoint transmission to GEO from Android via BLE Marking the checkpoints with HUE_BLUE color to do better tracking of the navigation. Added multi state BT options and Added restrictions on buttons like NAV usage dependency on BT Connection, Powerup button dependency on NAV setup before actually powering the car.	Complete
7	11/14/2017	Major Feature: Implementing maneuvering with Android app supplied GEO checkpoints with on-board I/O Use mock data from file to compute: a) Heading b) Bearing -> use Haversine's algorithm to compute turning angle Advertise distance to the next checkpoint (again using Haversine's algorithm) Save the proper checkpoints for one route (Clark's to SU) to SDCARD on GEO Controller Implement system start/stop triggers from different use cases Turning angle offset of -10,10 is added to take right / left turn Implement the battery-status DBC Message advertisement Indicate checkpoint proximity using backlight indicators Create 2 CAN messages for Disgnostic and I/O data to transmit it to BLE module Receive the diagnostic CAN message and decode to transmit it to Android App [Android I/O:] Design Android app views for visualizing Diagnostic and I/O data Test and validate success/fail cases for on-board I/O display information(as defined above) Update PWM pulses to match MASTER's target speed with proper feedback from the identified feedback-mechanism Identify PID constants kp, ki, kd and evaluate performance against the basic feedback implementation Finalize feedback algorithm and fine-tuning	Major Feature: Implemented maneuvering with Android app supplied GEO checkpoints with on-board I/O [Geo:] Implemented mock data from file to compute: a) Heading b) Bearing -> used Haversine's algorithm to compute turning angle [Geo:] Advertised distance to the next checkpoint (again using Haversine's algorithm) [Geo:] Saving the checkpoints in SDCARD on GEO Controller battery-status is optional feature. Planning for later Indicate checkpoint proximity using backlight indicators [BLE:] Created CAN messages for Telemetry data from all modules to BLe to send to Android [BLE:] Received Telemetry messages are transmitted to Android App [Android I/O:] Android app views created for visualizing Telemetry data Test and validate success/fail cases for on-board I/O display information Update PWM pulses to match MASTER's target speed with proper feedback from the identified feedback-mechanism Finalize feedback algorithm and fine-tuning	Complete.
8	11/21/2017	Major Feature: Complete maneuvering implementation with Android app and Android I/O [Android I/O:] Implement display of Sensor Obstacle Information on a RADAR map [Android I/O:] Dynamically update car's Current location on the map's route path [Android I/O:] BT Auto Connection and Pairing implemented [Android I/O:] Health information from BLE Controller, namely battery, GPS lock status, and motor speed shall be updated [Android I/O:] BT Auto connect implementation and re-connection on disconnection. Test achievable target speeds with different possible obstacle heights and forms possible, and ground conditions	Major Feature: Completed maneuvering implementation with Android app [Android I/O:] Sensor obstacle LIDAR information has been updated on the app [Android I/O:] Dynamic update of Car's current location and intermittent checkpoints implemented. [Android I/O:] Health information from BLE Controller, namely GPS lock status, and motor speed has been updated on the Dashboard of the app. [Android I/O:] Completed BT Auto connect implementation and re-connection on disconnection.	Complete.
9	11/28/2017	Major Feature: Full feature integration test Execute the test plan created above [Planned for 11/14] (check Testing documentation in Wiki) Execute the test plan created above [Planned for 11/14]; Phase 1: Test all identified cases for ground-conditions (grass, inclines, etc) Execute the test plan created above [Planned for 11/14]; Phase 2: Test all identified cases for GPS routes and obstacle forms	Major Feature: Full feature integration test Integration testing with all controllers and Android App to select routes and send checkpoints from App to Ble.	Complete.
10	12/5/2017	Major Feature: Full feature integration test Execute the test plan created above [Planned for 11/14]; Phase 3: Test all identified cases for speed levels and on-board I/O validation Execute the test plan created above [Planned for 11/14]; Phase 4: Test all identified cases for [Android I/O] validation	Major Feature: Full feature integration test Integration testing with Android App with Debug view/Dash board with sensor and GPS data	Complete
11	12/12/2017	Major Feature: Full feature integration test Execute the test plan created above [Planned for 11/14]; Phase 5: Test all identified cases for desired Turbo mode(s) Update Wiki Complete Report	Major Feature: Full feature integration test		On Track

Item#	Part Description	Vendor	Qty	Cost
1	SJ One Board (LPC 1758)	From Preet	6	$480
2	[1]	Prof. Kaikai Liu provided	1	$0
3	Accelerometer/Magnetometer LSM303	Adafruit	2	$40.00
4	Bluetooth Module	Sparkfun	1	$34.95
5	CAN Transceivers	From ebay.	15	$51
6	Battery Pack	From Sheldon Hobbist	1	$49.99
7	RP Lidar		5	$400
8	LED $ Digit Display	From Preet	1	$0
9	GPS Module	From Adafruit	1	$43.34
10	General Components	From Amazon	-	$
11	RPM Sensor	From traxxas	1	$20
12	PCB		1	$10.66
13	Acrylic Board	From Amazon	1	$12.53
14	PCAN dongle	From Preet	1	$0
15	Power Bank	From Amazon	1	$41.50
16	PCB Manufacturing	From PCB Way	5	$70

CAN Communication

System Nodes : MASTER , MOTOR , BLE , SENSOR , GEO

SNo.	Message ID	Message from Source Node	Receivers
Master Controller Message
1	2	System Start command to start motor	Motor
2	17	Target Speed-Steer Signal to Motor	Motor
3	194	Telemetry Message to Display it on Android	BLE
Sensor Controller Message
4	3	Lidar Detections of obstacles in 360 degree grouped as sectors	Master,BLE
5	36	Heartbeat	Master
Geo Controller Message
4	195	Compass, Destination Reached flag, Checkpoint id signals	Master,BLE
5	4	Turning Angle	Master,BLE
5	4	Heartbeat	Master
Bluetooth Bridge Controller Message
4	38	Heartbeat	Master
5	213	Checkpoint Count from AndroidApp	Geo
5	214	Checkpoints(Lat,Long) from Android App	Geo

DBC File

https://gitlab.com/optimus_prime/optimus/blob/master/_can_dbc/243.dbc

Design & Implementation

The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

Hardware Interface

In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

Board

Schematic

Discuss your hardware design here. Show detailed schematics, and the interface here.

Software Design

Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

Implementation

This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

Testing & Technical Challenges

Testing the car out on the grounds was the prime responsibility of the team. Individual modules like Sensor (LiDAR), Motor (The ESC and Servo), GPS & Compass, the android application and the Bluetooth bridge were tested by respective team members. But, the most important problems are being found with the Testing we do with the integrated whole.

Include sub-sections that list out a problem and solution, such as:

Unit Test Cases

Discuss the major unit test cases.

Technical Challenges

Drive (Motor) Controller

ESC Calibration

We messed up the callibration on the ESC. "XL 5 had a long press option to calibrate the ESC, where the ESC shall: a) After long press, glow green and start taking PWM signals for neutral (1.5). b) Glow green once again where we shall feed in PWM signals for Forward (2ms). b) Glow green twice again where we shall feed in PWM signals for Reverse (1ms)." -We wrote code to calibrate using EXT-INT (EINT3) over P0.1 - switch to calibrate the ESC this way!

ESC Reverse

"The ESC was not activating reverse if we directly - as in the datasheet (no formal datasheet - only XL 5 forums - talked about 1ms pulse width at 50Hz for reverse). We figured out that Reverse is actually 3 steps: a) goNeutral() b) goReverse() c) goNeutral() d) goReverse()

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

@@ Line 139: / Line 139: @@
 |
 * <font color="orange"> Major Feature: Implement maneuvering in Master controller  <br></font>
 ** <font color="blue"> Implement maneuvering algorithm to drive steering angle of the servo<br></font>
 ** <font color="blue"> Implement maneuvering algorithm to control ESC speed <br></font>
@@ Line 159: / Line 160: @@
 |
 * <font color="orange"> Major Feature: Implemented maneuvering in Master-Geo controller <br></font>
 * <font color="orange"> Major Feature: Implemented Basic Obstacle Avoidance in Free-run mode <br></font>
 ** <font color="blue"> Implement maneuvering algorithm in android app is moved to next week schedule<br></font>
 ** <font color="blue"> Implemented maneuvering algorithm in Master to drive steering angle of the servo<br></font>
 ** <font color="blue"> Implement maneuvering algorithm in Master to control ESC speed <br></font>
+** <font color="blue"> Unit Testing obstacle avoidance algorithm <br></font>
 ** <font color="clouds">Tested and validated the sensor data by plotting graphs in an EXCEL sheet.<br></font>
 ** <font color="clouds">Sending the obstacle information and heartbeat over CAN.<br></font>
@@ Line 185: / Line 188: @@
 ** <font color="purple">Collect mock checkpoints using the Android Data Collector application<br></font>
 ** <font color="purple">Collect mock checkpoints using the GEO module and compare for any discrepancies<br></font>
 ** <font color="clouds">Identify I/O on-board Display information; Currenly identified are documented below: <br></font>
 ** <font color="clouds">Health status like GPS Lock status, etc. <br></font>
@@ Line 192: / Line 193: @@
 ** <font color="clouds">Display bluetooth pairing status<br></font>
 ** <font color="teal">Test on-board I/O module for bluetooth pairing status<br></font>
 ** <font color="red">In case RPM installation/usage fail, Identify new mechanism for feedback and order components; Update PCB as well to include new hardware<br></font>
 ** <font color="red">Implement simple feature additions on steer control to handle reverse; basically steering rear-left and rear-right has to be practically implemented on motor/drive controller<br></font>
 ** <font color="blue">Receive GEO Controller's Turning-angle message and compute target steer <br></font>
 ** <font color="blue">Use GEO Controller's distance to next-checkpoint information to compute target speed<br></font>
 ** <font color="teal">Mock checkpoint navigation testing using different possible obstacle heights and forms possible<br></font>
 ** <font color="redbrick">Identify advertisement messages on the DBC file and add documentation in Wiki; Currently identified advertisements: a) current GEO location, b) SENSOR radar map<br></font>
 ** <font color="green">Shall define the BLE Controller to android message structure and message generation-intervals (classify on-demand advertisements and periodic advertisements)<br></font>
 ** <font color="green">Implement marker for current location display - which is an on-demand advertisement<br></font>
@@ Line 214: / Line 211: @@
 ** <font color="blue">Implemented interface method to receive GEO Controller's Turning-angle message and set target steer <br></font>
 ** <font color="blue">Target speed is not changed between checkpoints.So geo feedback for distance to destination is not used in design<br></font>
+** <font color="blue">Destination Reached flag is tracked to stop the car on reaching destination <br></font>
+** <font color="blue">Checkpoint Id CAN signal is processed by Master to start the car once destination is selected <br></font>
 ** <font color="green"> Android:Implemented Marker for current position Display.<br></font>
 ** <font color="green"> Android:User entry for setting up destination on MAP done.<br></font>
@@ Line 233: / Line 232: @@
 ** <font color="purple">Advertise distance to the next checkpoint (again using Haversine's algorithm)<br></font>
 ** <font color="purple">Save the proper checkpoints for one route (Clark's to SU) to SDCARD on GEO Controller<br></font>
+** <font color="blue"> Implement system start/stop triggers from different use cases <br></font>
+** <font color="blue"> Turning angle offset of -10,10 is added to take right / left turn <br></font>
 ** <font color="clouds">Implement the battery-status DBC Message advertisement <br></font>
 ** <font color="clouds">Indicate checkpoint proximity using backlight indicators<br></font>
@@ Line 243: / Line 244: @@
 ** <font color="red">Finalize feedback algorithm and fine-tuning<br></font>
 |
-*<font color="purple">Implemented mock data from file to compute: a) Heading b) Bearing -> used Haversine's algorithm to compute turning angle<br></font>
+* <font color="orange"> Major Feature: Implemented maneuvering with Android app supplied GEO checkpoints with on-board I/O <br></font>
-** <font color="purple">Advertised distance to the next checkpoint (again using Haversine's algorithm)<br></font>
-| Planned.
+** <font color="purple">[Geo:] Implemented mock data from file to compute: a) Heading b) Bearing -> used Haversine's algorithm to compute turning angle<br> </font>
+** <font color="purple">[Geo:] Advertised distance to the next checkpoint (again using Haversine's algorithm)<br></font>
+** <font color="purple">[Geo:] Saving the checkpoints in SDCARD on GEO Controller<br></font>
+** <font color="clouds"> battery-status is optional feature. Planning for later <br></font>
+** <font color="clouds"> Indicate checkpoint proximity using backlight indicators<br></font>
+** <font color="clouds"> [BLE:] Created CAN messages for Telemetry data from all modules to BLe to send to Android <br></font>
+** <font color="clouds"> [BLE:] Received Telemetry messages are transmitted to Android App <br></font>
+** <font color="clouds"> [Android I/O:] Android app views created for visualizing Telemetry data <br></font>
+** <font color="teal"> Test and validate success/fail cases for on-board I/O display information <br></font>
+** <font color="red"> Update PWM pulses to match MASTER's target speed with proper feedback from the identified feedback-mechanism<br></font>
+** <font color="red">Finalize feedback algorithm and fine-tuning<br></font>
+| Complete.
 |-
 ! scope="row"| 8
@@ Line 258: / Line 271: @@
 ** <font color="teal">Test achievable target speeds with different possible obstacle heights and forms possible, and ground conditions<br></font>
 |
-*<font color="green">[Android I/O:] Sensor obstacle LIDAR information has been updated on the app<br></font>
+* <font color="orange"> Major Feature: Completed maneuvering implementation with Android app  <br></font>
+** <font color="green">[Android I/O:] Sensor obstacle LIDAR information has been updated on the app<br></font>
 ** <font color="green">[Android I/O:] Dynamic update of Car's current location and intermittent checkpoints implemented. <br></font>
 ** <font color="green">[Android I/O:] Health information from BLE Controller, namely GPS lock status, and motor speed has been updated on the Dashboard of the app. <br></font>
-| Planned.
+** <font color="green">[Android I/O:] Completed BT Auto connect implementation and re-connection on disconnection.<br></font>
+| Complete.
 |-
 ! scope="row"| 9
@@ Line 271: / Line 286: @@
 ** <font color="teal">Execute the test plan created above [Planned for 11/14]; Phase 2: Test all identified cases for GPS routes and obstacle forms<br></font>
 |
-*
+* <font color="orange"> Major Feature: Full feature integration test <br></font>
-| Planned.
+** Integration testing with all controllers and Android App to select routes and send checkpoints from App to Ble.
+| Complete.
 |-
 ! scope="row"| 10
@@ Line 281: / Line 297: @@
 ** <font color="teal">Execute the test plan created above [Planned for 11/14]; Phase 4: Test all identified cases for [Android I/O] validation<br></font>
 |
-*
+* <font color="orange"> Major Feature: Full feature integration test <br></font>
-| Planned
+** Integration testing with Android App with Debug view/Dash board with sensor and GPS data
+| Complete
 |-
 ! scope="row"| 11
@@ Line 290: / Line 307: @@
 ** <font color="teal">Execute the test plan created above [Planned for 11/14]; Phase 5: Test all identified cases for desired Turbo mode(s)<br></font>
 * <font color="black"> Update Wiki Complete Report <br></font>
+|
+* <font color="orange"> Major Feature: Full feature integration test <br></font>
 |
 *
-|
+| On Track
 |-}

Difference between revisions of "F17: Optimus"

Revision as of 02:32, 8 December 2017

Contents

Project Title

Abstract

Objectives & Introduction

Team Members & Responsibilities

Schedule

Parts List & Cost

CAN Communication

DBC File

Design & Implementation

Hardware Interface

Software Design

Implementation

Testing & Technical Challenges

Unit Test Cases

Technical Challenges

Drive (Motor) Controller

ESC Calibration

ESC Reverse

Conclusion

Project Video

Project Source Code

References

Acknowledgement

References Used

Appendix

Navigation menu

Views

Personal tools

Navigation

Search

Tools

Google AdSense