Difference between revisions of "F16: Thunderbolt"

• Master Controller
  • Abhishek Singh
  • Saurabh Ravindra Deshmukh
  • Neha Biradar
• Motor Controller
  • Krishank Mehta
  • Neha Biradar
  • Saurabh Ravindra Deshmukh
• GPS/Compass Module
  • Samiksha Ambekar
  • Virginia Menezes
• Sensors
  • Arthur Nguyen
  • Rajeev Sawant
  • Samiksha Ambekar
• Bluetooth
  • Abhishek Singh
  • Nikhil Namjoshi
• Android Application
  • Nikhil Namjoshi
  • Saurabh Ravindra Deshmukh

Parts List & Cost

CAN Communication

DBC File

The DBC file implementation can be accessed at the following link:

https://gitlab.com/singh.abhishek21/Thunderbolt_CMPE243/blob/master/243.dbc

CAN Communication Table

PCAN Dongle and BusMaster

We have used BusMaster to monitor the CAN messages between the various controllers. The GUI is useful to log all the information and is very helpful in debugging various messages and conditions in real-time. The CAN bus USB adapter (PCAN Dongle) connects the CAN bus to the USB port of a computer, which also supplies the power to the adapter (no power supply needed) and Bus Master is used to display and debug the messages between the controllers.

PCAN Dongle

BusMaster screenshot with all messages

Master Controller

Schedule

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 Design

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

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.

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

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Sensor Controller

Group Members

• Arthur Nguyen
• Rajeev Sawant

Schedule

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.

This section goes over the design and implementation of the sensor controller. The sensor controller is the main controller for everything dealing with sensors. For this project, the sensor controller's main task deals with the ultrasonic sensors, which are used to show the distance of the closest objects around the car. Knowing the proximity of objects around the car helps it navigate and maneuver around them in order to get to the destination without crashing. For this task, the car must be able to know what is to the right, middle, and left of the car in order to adjust accordingly. In rare, cases, the car must be able to know the distance behind it for reversing out of certain situations. For this methodology, four sensors were used and positioned to get the right, middle, and left distances for the front, as well as one sensor for the back of the car.

Hardware Design

The main components of the sensor board consisted of four ultrasonic sensors. Three sensors (left, middle, and right) are placed in the front of the car and one sensor is placed in the back. The sensors are MB1010 LV-MaxSonar-EZ21 Ultrasonic Rangefinder sonar sensors, which can range from 0-inches to 254-inches with 1-inch resolution. They all share the same supply voltage and ground, which are supplied by the SJOne board's 3v3 and ground pins. The left sensor's RX pin

The stands for holding the sensors are curved such that the sensors are aimed toward the sky and not horizontally. This decision is made in order to avoid interference with the ground due to the wide range of detection by the sensors.

MaxSonar MB1010 Sensor

Timing Diagram

MaxSonar MB1010 Sensor

Mounting of Sensors

We have 3D printed the supports for mounting the sensors as seen below. The software used is 123D Design.

3D Design for mounting the sensors

Hardware Interface

Hardware Interface between SJOne board and Sensors

Software Design

Flow Diagram

The idea behind implementing algorithm for sensor was to make sure that beam from the sensors do not collide with each other. Thus we trigger front and back at one time, and right and left separately. This technique saves our 100 ms of time. Every sensor takes a calibration cycle of 49 ms. Also we considered the initial power up delay of 250 ms. The sensor task scheduling is implemented using semaphore which can be seen in sensor.cpp file.

For getting values from sensor we keep the PWM pin high for 40ms (as per datasheet), this is the time for the sensor to send the beam and get the reflected beam back.
To inform the master that sensor is in working state , we send a Heartbeat signal to master which is implemented in 1HZ task.

We have implemented the following in the 100 Hz periodic task, which executes every 10 ms. The sensor function composes of three triggering (RX) sensors.
The triggering sensors are for the left sensor, middle and back sensors, and the right sensor, in that order. Each triggering occurs 60 ms between each other to avoid interference between sensors.

• When the count is zero (0 ms has passed from the beginning of ranging), the left sensor is first triggered for 20 microseconds.
  
• When the count is 6 (60 ms has passed from the beginning of ranging), the middle and back sensors are triggered for 20 microseconds.
• When the count is 12 (120 ms has passed from the beginning of ranging), the right sensor is triggered for 20 microseconds.
• Finally, when the count is 18 (180 ms has passed from the beginning of ranging), all sensors have completed ranging and all sensor data is updated, encoded, and sent over the CAN bus.
• The count is also reset to -1. The count is also incremented once at the end of this 100 Hz task.
  
  

Implementation

The hardware implementation was able to follow the design of three (right, middle, and left) front sensors and one back sensor.

Working of Sensor algorithm

Testing & Technical Challenges

1. Delay time of RX

2. Angle of sonar sensors

Motor & I/O Controller

Group Members

• Krishank Mehta
• Saurabh Deshmukh
• Neha Biradar

Schedule

Design & Implementation

The Motor IO controller works as per the commands from the Master controller. The motor module is responsible for the running on the car, its direction and speed. The IO module consists of LCD and backlights.

Hardware Design

Motor Module

The Motor module consists of servo motor, DC motor and speed sensor module. The servo motor is responsible for steering of the car and the DC motor is responsible for speed control.
The Master controller sends signals of drive, speed and steer to the motor controller to navigate the car, based on the information received from Sensors and GPS.

DC Motor
In the car, we have the ARRMA MEGA waterproof 35A ESC, combined with the 15T MEGA Brushed Motor. The MEGA ESC is designed to be used with the supplied NiMh Battery Pack and can easily handle 2S LiPo battery packs or 7 cell 8.4V NiMh battery packs.

ESC

DC Brush Motor cycle

Brushed DC motor

The ESC (Electronic Speed Control) is connected to the SJOne board to generate the PWM as shown in the block diagram below, which is connected to the DC Motor. It is powered by a ARRMA 6 Cell 2000mAh 7.2 volt NiMh Battery.

ESC

DC Motor Interface with SJOne Board

DC Motor with ESC

Servo Motor
The Servo motor in our car is ADS-5 Steering Servo, which will provide fast and consistent steering response on the most demanding surfaces. This servo provides 5kg/cm (70oz/inch) of torque.
The servo motor is connected to the SJOne board and provided PWM signal to control the steering of the car in 5 directions - far left, left, center, right, far right.

Servo motor rotation

Servo Motor Interface with SJOne Board

Steering Servo Motor

Speed Sensor

Traxxas Speed Sensor

5 magnets on wheel

IO Module

The IO Module consists of two LCD Modules - Picaso Integrated Display Module and Serial Liquid Crystal Display Module and backlights based on the direction and movement of the car.

IO Module gen4-uLCD-32PT

IO Module gen4-uLCD-32PT

LCD Display - Picaso Integrated Display Module
We are using two LCD modules in the project. One of them is a gen4 3.2” Picaso Integrated Display Module, which features a TFT LCD Display.
The processor includes a microSD memory storage, 13 customizable GPIO, 2 serial ports and a Master I2C interface, along with multiple millisecond resolution timers, and Audio Generation.
The Model number we are using is gen4-uLCD-32PT.
The data from the Sensor controller, Motor controller and GPS controller is sent to the LCD Module through I2C.

LCD displays the following information:

 Speedometer

LCD Display

LCD Display - Serial Liquid Crystal Display Module
The second LCD is a 4 line * 20 characters Serial Liquid Crystal Display Module. The Model number we are using is NHD-0420D3Z-NSW-BBW-V3.
This display uses a built-in PIC16F690 for serial communication. 100mS delay is required upon power-up for the built-in PIC to initialize the display controller.
The data from the Sensor controller, Motor controller and GPS controller is sent to the LCD Module through I2C.

LCD displays the following information:

 1st Line -  THUNDERBOLT
 2nd Line -  Sensor Controller Data - Left Sensor, Front Sensor, Right Sensor, Back Sensor Readings
 3rd Line -  Motor Controller Data - Direction,  Speed,  Distance 
 4th Line -  GPS Controller Data - Final distance, distance to next checkpoint 

Backlights

Backlights

The direction and the movement of the car controls the backlight.
When the car is in drive or in reverse mode, the Green LED lights up.
When the car is in stop mode, the Red LED lights up.
When the car is steering to the right, the right indicator is lit, while when it is steering to the left, the left indicator is lit.

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.

Schematic

Motor IO Hardware interface

Software Design

**Drive, Steer and Speed signals from Master to Motor controller

 BO_ 209 MASTER_DRIVING_CAR: 8 MASTER
   SG_ MASTER_DRIVE_ENUM : 0|4@1+ (1,0) [0|0] "" MOTOR,COM_BRIDGE
   SG_ MASTER_STEER_ENUM : 4|4@1+ (1,0) [0|0] "" MOTOR,COM_BRIDGE
   SG_ MASTER_SPEED_ENUM : 8|4@1+ (1,0) [0|0] "" MOTOR,COM_BRIDGE

**Speed and distance travelled data from Motor to Master and Communication bridge controllers

 BO_ 147 MOTOR_CAR_SPEED: 4 MOTOR
   SG_ MOTOR_SPEED_DATA_UNSIGNED : 0|8@1+ (1,0) [0|0] "" MASTER,COM_BRIDGE
   SG_ MOTOR_DISTANCE_FROM_START_POINT_UNSIGNED : 8|8@1+ (1,0) [0|0] "meters" MASTER,COM_BRIDGE

**Heartbeat signal from Motor to Master Controller

 BO_ 339 MOTOR_HEARTBEAT: 2 MOTOR
   SG_ MOTOR_HEARTBEAT_UNSIGNED : 0|11@1+ (1,0) [0|0] "" MASTER

Implementation

Three signals - Drive, Speed and Steer signals are received by the Motor Controller from the Master. Based on the signals received from the Master module, the motor is controlled.

Master-Motor IO Interface

Master Motor Control

Calculation of Speed and Distance

Calculation of Speed and Distance

Testing & Technical Challenges

1. Ideally at 7.5% duty cycle PWM, the servo motor should be aligned to center position, but due to faulty hardware the servo motor is inclined towards right giving us wrong movement.
We solved this problem by setting the PWM to 7.2% duty cycle during initialization, which resulted in accurate center position

2. For D.C motor to start running, we have to initialize the ESC. Hence without providing 1.5ms pulse at the beginning, the motor will start running.

3. As the battery voltage decreases, the motor does not run at the same speed with the same PWM. Hence with the decrease in speed we increased the PWM pulse linearly

4. In order to run the motor in reverse direction (when the motor is currently running in the forward direction), it was required to apply reverse pulse, then a stop pulse and again a reverse pulse, back to back.

Geographical Controller

Group Members

• Samiksha Ambekar
• Virginia Menezes

Schedule

Design & Implementation

The Geographical Controller is used to track the current location of the car and the turn angle to steer to the next checkpoint.

The module comprises of a GPS module and a compass.

Once the user choses the destination point on the Android application, the app will map the shortest path available from the current location to the destination and plot multiple checkpoints based on that. The coordinates of these checkpoints are sent to the GEO controller, which will calculate the distance between the current location of the car and the next checkpoint and the turn angle required to reach the next checkpoint and send this information to the Master controller.

Hardware Design

The GPS module used is SparkFun Venus GPS with SMA Connector [11]. And the Compass is CMPS11 - Tilt Compensated Compass Module [12].

GPS Module

GPS Module

SkyTraq GPS Viewer

GPS with antenna

The GPS Module we use in our project is SparkFun Venus GPS with SMA Connector based on Venus638FLPx IC.

There are three modes of operation based on how it is powered:

1. Cold start: If no external battery (VBAT) of 3V is connected to the module, it will take a longer time to start and get a fix.

2. Hot start: When VBAT is connected to the module, even if the GPS is turned off and turned on within a certain time, it will get its fix from the value stored in memory.

3. Warm start: If the GPS is not turned on within the time frame for hot start (typically 2 hours), it will take sometime to get satellite fix.

GPS Configuration

The GPS module sends out the information in standard NMEA-0183 format or SkyTraq Binary sentence format. The default rate is 9600 bps and is configurable up to 115200 bps. The update rate of this GPS module is up to 20Hz. This indicates how often it recalculates and reports its position.

We have configured the GPS module using the GPS Viewer software provided by Skytraq.

1. The rate of UART is set at 38400bps

2. Update rate of 5Hz

3. Also it is possible to choose which NMEA message format we want the data in. For our car, we are using the GPGGA (Global Positioning System Fix Data) message format.

Apart from configuration, all other information like data received from the GPS, if fix position, no. of satellites, latitude and longitude etc. all can be viewed through this software.

GGA Message Structure : $GPGGA,hhmmss.sss,ddmm.mmmm,a,dddmm.mmmm,a,x,xx,x.x,x.x,M,,,,xxxx*hh<CR><LF> 

Example data: $GPGGA,120218.899,2400.0000,N,12100.0000,E,0,00,0.0,0.0,M,0.0,M,,0000*69

      where,
                $GPGGA   -- Global Positioning System Fix Data (Sentence Identifier)
            120218.899   -- UTC Time of position in hhmmss.sss format
             2400.0000   -- Latitude in ddmm.mmmm format
                     N   -- Latitude hemisphere indicator, ‘N’ = North, ‘S’ = South 
            12100.0000   -- Longitude in dddmm.mmmm format 
                     E   -- E/W Indicator
                     0   -- GPS quality indicator 
                              0: position fix unavailable 
                              1: valid position fix, SPS mode  
                              2: valid position fix, differential GPS mode 
                              3: GPS PPS Mode, fix valid 
                              4: Real Time Kinematic. System used in RTK mode with fixed integers 
                              5: Float RTK. Satellite system used in RTK mode. Floating integers 
                              6: Estimated (dead reckoning) Mode 
                              7: Manual Input Mode 
                              8: Simulator Mode 
                    00   -- Number of satellites in use (00~12)
                   0.0   -- HDOP (Horizontal dilution of precision), (00.0 ~ 99.9) 
                 0.0,M   -- Altitude in Meters - above mean sea level, (-9999.9 ~ 17999.9)
                 0.0,M   -- Height of geoid above WGS84 ellipsoid (mean sea level), (-9999.9 ~ 17999.9)
                  0000   -- DGPS Station ID - Differential reference station ID, 0000 ~ 1023 
                            NULL when DGPS not used  
                   *69   -- Checksum (begins with *)

Compass Module

Compass Module ‎

Modes of operation ‎

The Compass Module we use in our project is CMPS11 - Tilt Compensated Compass Module.
It employs a 3-axis magnetometer, 3-axis gyro and a 3-axis accelerometer. A Kalman filter is used to combine the gyro and accelerometer to remove the errors caused by tilting of the PCB. The output of the three sensors measuring x, y and z components of the magnetic field, together with the pitch and roll are used to calculate the bearing. It requires a power supply of 3.6-5V. The module can be operated in two modes - serial or I2C. We have interfaced the CMPS11 module with SJOne board via I2C for communication.

Compass calibration
The calibration of the compass is very important. We mounted the compass on the car with the motor working to take into account the magnetic deviation caused by its EMI. Calibration mode is entered by sending a 3 byte sequence of 0xF0,0xF5 and 0xF6 to the command register in 3 separate I2C frames with a delay of 20ms between them. Once the CMPS11 is in calibration mode, the LED will start blinking. It should now be rotated in all directions in 3 dimensions. Once calibrated successfully, the calibration mode can be exited with command of 0xF8.

Hardware Interface

Schematic

Hardware interface

Software Design

Algorithm

Distance Calculation

We are using Haversine formula to calculate the great-circle distance between two checkpoints – that is, the shortest distance over the earth’s surface

 Distance = R ⋅ c
 c = 2 ⋅ atan2(√a, √(1−a))
 a = sin²(Δφ/2) + cos φ1 ⋅ cos φ2 ⋅ sin²(Δλ/2)
  
 where,
       φ is latitude,
       λ is longitude,
       R is earth’s radius (mean radius = 6,371km),
  
 Note: Angles need to be in radians to pass to trignometric functions

Bearing

The final heading will differ from the initial heading by varying degrees according to distance and latitude. This can be calculated as follows:

   Bearing (θ)(radians) = atan2(sin Δλ ⋅ cos φ2 , cos φ1 ⋅ sin φ2 − sin φ1 ⋅ cos φ2 ⋅ cos Δλ)
      
      where,
             φ1,λ1 is the start point, 
             φ2,λ2 the end point 
             Δλ is the difference in longitude

CAN Communication

Following table lists the signals sent by GPS to other controllers via CAN.

-

Msg : 30 bits : GPS_latitude
Msg : 30 bits : GPS_longitude

-

Msg : 16 bits : turn angle 
Msg : 1 bit   : isFinal
Msg : 16 bits : distance to final destination
Msg : 16 bits : distance to next checkpoint

-

The following are the signals that are received or sent by the GEO Controller.

 **Receive Checkpoints from Communication Bridge (Total number of checkpoints, current checkpoint number, latitude and longitude

   BO_ 148 COM_BRIDGE_CHECK_POINT: 8 COM_BRIDGE
     SG_ COM_BRIDGE_MUX M : 0|2@1+ (1,0) [0|0] "" GPS
     SG_ COM_BRIDGE_TOTAL_COUNT_UNSIGNED : 2|8@1+ (1,0) [0|0] "" GPS
     SG_ COM_BRIDGE_CURRENT_COUNT_UNSIGNED : 10|8@1+ (1,0) [0|0] "count" GPS
     SG_ COM_BRIDGE_LATTITUDE_SIGNED m0 : 18|40@1+ (0.000001,-90) [-90|90] "degrees" GPS
     SG_ COM_BRIDGE_LONGITUDE_SIGNED m1 : 18|40@1+ (0.000001,-180) [-180|180] "degrees" GPS
   
 **Receive RESET signal from Com Bridge (Android device)

   BO_ 10 COM_BRIDGE_RESET: 2 COM_BRIDGE
     SG_ COM_BRIDGE_RESET_UNSIGNED : 0|11@1+ (1,0) [0|0] "" MASTER,GPS,MOTOR,SENSOR
   
 **Receive START signal from Com Bridge (Android device)

   BO_ 84 COM_BRIDGE_CLICKED_START: 2 COM_BRIDGE
     SG_ COM_BRIDGE_CLICKED_START_UNSIGNED : 0|11@1+ (1,0) [0|0] "" MASTER,GPS
   
 **Send acknowledgement to Com Bridge if all checkpoints have been received
      
   BO_ 290 GPS_ACKNOWLEDGEMENT: 2 GPS
     SG_ GPS_ACKNOWLEDGEMENT_UNSIGNED : 0|11@1+ (1,0) [0|0] "" COM_BRIDGE
   
 **Send current location coordinates (latitude and longitude in decimal degrees) to Com Bridge
    
   BO_ 162 GPS_CURRENT_LOCATION: 8 GPS
     SG_ GPS_LATTITUDE_SIGNED : 0|30@1+ (0.000001,-90) [-90|90] "degrees" COM_BRIDGE
     SG_ GPS_LONGITUDE_SIGNED : 30|30@1+ (0.000001,-180) [-180|180] "degrees" COM_BRIDGE
   
 **Send Heartbeat signal to Master

   BO_ 338 GPS_HEARTBEAT: 2 GPS
     SG_ GPS_HEARTBEAT_UNSIGNED : 0|11@1+ (1,0) [0|0] "" MASTER
   
 **Send calculated data to Master and motor (Turn angle, Is final, distance to final destination, distance to next checkpoint

   BO_ 146 GPS_MASTER_DATA: 7 GPS
      SG_ GEO_DATA_TURNANGLE_SIGNED : 0|16@1+ (0.1,-180) [-180|180] "degrees" MASTER,MOTOR
      SG_ GEO_DATA_ISFINAL_SIGNED : 16|1@1+ (1,0) [0|0] "" MASTER,MOTOR
      SG_ GEO_DATA_DISTANCE_TO_FINAL_DESTINATION_SIGNED : 17|16@1+ (0.1,0) [0|0] "meters" MASTER,MOTOR
      SG_ GEO_DATA_DISTANCE_TO_NEXT_CHECKPOINT_SIGNED : 33|16@1+ (0.01,0) [0|0] "meters" MASTER,MOTOR
   
 **Send Compass reading to Com Bridge

   BO_ 300 GPS_COMPASS_HEADING: 3 GPS
      SG_ GEO_DATA_COMPASS_HEADING_UNSIGNED : 0|16@1+ (0.1,0) [0|359] "degrees" COM_BRIDGE
   
 **Receive Acknowledgement from Master when data is received successfully

   BO_ 281 MASTER_ACKNOWLEDGEMENT: 2 MASTER
      SG_ ACKNOWLEDGEMENT_DATA_REACHED_UNSIGNED : 0|11@1+ (1,0) [0|0] "" GPS

Implementation

Geographical Controller Flow Diagram

Testing & Technical Challenges

GPS gives imprecise current location

1. Unable to get a satellite fix on GPS module:
The first GPS module we received would not get a satellite fix. We spent a considerable amount of time outdoors to get a fix but it never did.
Finally we returned the product and ordered a new one. We got a feedback from the vendor Sparkfun that the GPS module was defective and so the issue.
The new module got a fix the first time within the first 20 minutes.

2. GPS gives imprecise current location:
There was a small yet noticeable difference between the location provided by the GPS module and the exact current location. The adjacent image shows a plot of the current location vs the route plotted.
We tried to fix this by increasing the update rate from 5Hz to 10Hz, but this failed the parsing of the data and we sometimes ended up getting incorrect latitude and longitude values.
Finally we configured the GPS module to pedestrian mode which gave precise current location.

3. Car not stopping at final destination:
As per our algorithm, once the car reaches the destination, the IS_FINAL flag should be set and the Master controller should send the STOP command to the motor controller.
But it is not possible that the car reaches the exact location i.e. achieves the exact coordinates in precision and so the IS_FINAL flag was never set, resulting the car never stopping even on reaching the final destination.
To fix this issue, we modified the algorithm that when the distance between the car and the final destination is between 3 meters, the IS_FINAL flag would be set, and thus the Master controller will send out STOP command, bringing the car to a halt.

Android and Communication Bridge Controller

Group Members

• Nikhil Namjoshi
• Saurabh Deshmukh

Schedule

Design & Implementation

The Communication Bridge Controller is responsible to connect the RC car to the Android application via Bluetooth. It provides the route information between source and destination chosen on the Android application. Once the source and destination is chosen, checkpoints between the two are fixed on the Google Maps and sent to the geographical controller. The checkpoints and destination information is then used by the Geographical controller to calculate the distance and turn angle the car has to travel for based on the current location and sent to the Master controller. HC-06 Bluetooth Module[edit]

Hardware Design

Bluetooth Module

Bluetooth HC-05 Module

We are using Bluetooth module HC-05 to establish wireless communication between the car and the Android device.
This module is based on the Cambridge Silicon Radio BC417 2.4 GHz BlueTooth Radio chip. This is a complex chip which uses an external 8 Mbit flash memory
It includes the Radio and Memory chips, 26 MHz crystal, antenna and RF matching network.
The right section of the Bluetooth Board has connection pins for power and signals as well as a 5V to 3.3V Regulator, LED, and level shifting.

HC-05 PinOut :

- KEY: If brought HIGH before power is applied, forces AT Command Setup Mode. LED blinks slowly (2 seconds)
- VCC: +5V Power
- GND: Ground
- TXD: Transmit Serial Data from HC-05 to SJOne board UART RXD
- RXD: Receive Serial Data from SJOne board UART TXD
- STATE: Tells if connected or not

Hardware Interface

Bluetooth Controller Pin Connections

Communication Bridge Hardware Interface

Software Design

Workflow

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

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

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?

Project Video

Upload a video of your project and post the link here.

Project Source Code

• Gitlab Code Link

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix