Difference between revisions of "F16: Titans"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Hardware Interface)
(Hardware Interface)
Line 112: Line 112:
 
<b> GPS Module: Readytosky Ublox NEO-M8N </b>
 
<b> GPS Module: Readytosky Ublox NEO-M8N </b>
  
| [[File:CMPE243 F16 Titans GPS Module.jpg |350px|right|right|thumb]]
+
| [[File:CMPE243 F16 Titans GPS Module.jpg |350px|right]]
  
|This GPS module uses UART serial communication interface. The refresh rate ranges from 1Hz up to 10Hz with a default baud rate of 9600bps. This module is an updated version to the Ublox NEO-M7N which brings improved accuracy of up to 0.9 meters using its build in antenna.
+
This GPS module uses UART serial communication interface. The refresh rate ranges from 1Hz up to 10Hz with a default baud rate of 9600bps. This module is an updated version to the Ublox NEO-M7N which brings improved accuracy of up to 0.9 meters using its build in antenna.
  
 
Specifications:
 
Specifications:

Revision as of 07:45, 24 September 2016

Project Title

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

  • A
  • B
  • Yang Thao
    • Interface and program GPS module
  • D

Schedule

Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

Week# Date Task Actual
1 10/8 Task list Completed? Problems Encountered?

Parts List & Cost

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

Parts List & Cost

Item# Part Desciption Vendor Qty Cost
1 RC Car
2 Ublox NEO-M8N GPS module with HMC5883L Compass Amazon 1 $35.99

Sensor Controller

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.

Motor & I/O Controller

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.

Geographical Controller

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.

GPS Module: Readytosky Ublox NEO-M8N

|
CMPE243 F16 Titans GPS Module.jpg

This GPS module uses UART serial communication interface. The refresh rate ranges from 1Hz up to 10Hz with a default baud rate of 9600bps. This module is an updated version to the Ublox NEO-M7N which brings improved accuracy of up to 0.9 meters using its build in antenna.

Specifications:

  • Power Supply:DC Voltage 2.8V~6.0V
  • Power Consumption: 50mA@5V
  • Support for GPS,GLONASS,Galileo,BeiDou,QZSS and SBAS
  • 72 Searching Channel
  • Receiving Sensitivity:Trace -167dBm, Capture-148dBm
  • Positioning Time:Cold Start:avg26s, Warm Start:avg25s, Hot Start:avg3s
  • positioning accuracy:2m At Open Wind
  • Output Frequency:1Hz-10Hz,Default 1Hz
  • Speed accuracy:0.1 m/s (Without Aid)
  • Acceleration accuracy:0.1 m/s (Without Aid)
  • Dynamic Characteristics:Max Height:18000m, Max Speed:515m/s, Max Acceleration:4G
  • UART Interface:UART Port:TXDA and RXDA
  • Support Rate:4800bps to 115200bps,Default 9600dps
  • Working Temperature:-40℃-+85℃
  • Storage Temperature:-40℃-+85℃
  • Diameter:45mm
  • Height:6mm
  • Weight:10g
  • 6pins 1.25mm port


GPS Connector Definition:

  • GND,
  • TX,data output
  • RX,data intput
  • VCC,2.8V-6V

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.

Communication Bridge Controller

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.


Central Controller

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.


My Issue #1

Discuss the issue and resolution.

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

References

Acknowledgement

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

References Used

List any references used in project.

Appendix

You can list the references you used.