F13: Garage Parking Assistant - Revision history

Preet: /* Project Source Code */

2013-12-08T03:54:22Z

‎Project Source Code

Preet: /* Project Source Code */

2013-12-08T03:53:44Z

‎Project Source Code

Proj user1: /* Vehicle Module */

2013-12-08T01:55:46Z

‎Vehicle Module

Proj user1: /* Vehicle Module */

2013-12-08T01:54:50Z

‎Vehicle Module

Proj user1: /* Parts List & Cost */

2013-12-08T01:52:28Z

‎Parts List & Cost

Proj user1: /* Vehicle Module Testing */

2013-12-08T01:48:40Z

‎Vehicle Module Testing

Proj user1: /* Vehicle Module */

2013-12-08T01:47:23Z

‎Vehicle Module

Proj user1: /* My Issue #2: PWM and Piezo buzzer */

2013-12-08T01:44:00Z

‎My Issue #2: PWM and Piezo buzzer

Proj user1: /* Vehicle Module Testing */

2013-12-08T01:31:18Z

‎Vehicle Module Testing

Proj user1: /* Implementation */

2013-12-08T01:18:42Z

‎Implementation

@@ Line 431: / Line 431: @@
 === Project Source Code ===
-* [https://sourceforge.net/projects/sjsu/upload/CmpE240_LM_F2013/ Project Source Code]
+* [https://sourceforge.net/projects/sjsu/files/CmpE240_LM_F2013/ Project Source Code]
 == References ==

@@ Line 431: / Line 431: @@
 === Project Source Code ===
-Send me your zipped source code and I will upload this to SourceForge and link it for you.
+* [https://sourceforge.net/projects/sjsu/upload/CmpE240_LM_F2013/ Project Source Code]
 == References ==

@@ Line 206: / Line 206: @@
 ''Vehicle Module Hardware - Front side''
-[[File:GarageParkingAssistantCarBack.PNG|400px]]
+[[File:GarageParkingAssistantCarBack.PNG|350px]]
 ''Vehicle Module Hardware - Back side''

@@ Line 202: / Line 202: @@
 Below are photos of the front and back side of the Vehicle Module Hardware. <br/>
-[[File:GarageParkingAssistantCarFront.PNG]]
+[[File:GarageParkingAssistantCarFront.PNG|480px]]
 ''Vehicle Module Hardware - Front side''
-[[File:GarageParkingAssistantCarBack.PNG]]
+[[File:GarageParkingAssistantCarBack.PNG|400px]]
 ''Vehicle Module Hardware - Back side''

@@ Line 132: / Line 132: @@
 |-
 | scope="row"| 15
-|| [http://www.newegg.com/Product/Product.aspx?Item=9SIA27C12M7437 Mini USB Type-B Male socket connectors] ||Newegg  || 1 || $4.34 || $4.34
+|| [http://www.newegg.com/Product/Product.aspx?Item=9SIA27C12M7437 Mini USB Type-B Male socket connectors (includes 10)] ||Newegg  || 1 || $4.34 || $4.34
 |-
 | scope="row"|
-|| Total||  ||  || || $257.88
+|| Total||  ||  || || $261.87
 |}

@@ Line 397: / Line 397: @@
 . Tested the distance data is being sent from Garage module to Vehicle module.  We used printfs and displayed on the 7 segment LED on both modules.
-. Tested the garage remote control will activate only on the first package received from garage controller
+. Tested the garage remote control will activate only on the first package received from garage microcontroller
 . Tested piezo buzzer will turn off at less than per-determined stop distance.  However, we also discovered piezo buzzer needs to stop when it stops receiving wireless signal from Garage Module.

@@ Line 178: / Line 178: @@
 ====Vehicle Module====
-The SJ One board, piezo buzzer, and garage door remote controller are contained in a compact transparent plastic enclosure. The SJ One board is mounted on lid of the enclosure with the on-board LED display visible to the user using standoffs. The piezo and remote controller are resting at the bottom of the enclosure facing the bottom. All parts of the Vehicle module are powered either by 4-battery pack modified to connect to mini USB or USB car charger and cable.
+The SJ One board, piezo buzzer, and garage door remote control are contained in a compact transparent plastic enclosure. The SJ One board is mounted on lid of the enclosure with the on-board LED display visible to the user using standoffs. The piezo and remote control are resting at the bottom of the enclosure facing the bottom. All parts of the Vehicle module are powered either by 4-battery pack modified to connect to mini USB or USB car charger and cable.
 '''Garage Door Remote Control'''
-The Vehicle module opens the garage door by sending GPIO signal from the microcontroller (pin P1.28) to the garage door remote controller.  The GPIO is signal is wired to the back of the pushbutton switch on the remote controller. The garage door remote control is universal garage door remote and needs to be pre-programmed to communicate with the garage door prior to installation in the enclosure. In addition, a LED on the SJ OneBoard will be lit up for the time duration when GPIO signal is sent.
+The Vehicle module opens the garage door by sending GPIO signal from the microcontroller (pin P1.28) to the garage door remote control.  The GPIO is signal is wired to the back of the pushbutton switch on the remote control. The garage door remote control is universal garage door remote and needs to be pre-programmed to communicate with the garage door prior to installation in the enclosure. In addition, a LED on the SJ OneBoard will be lit up for the time duration when GPIO signal is sent.
 The photo of the Vehicle module back side shows a rectangular garage door opener with the pushbutton cover removed.  The photo of the Vehicle module front side show the LED that will light up when GPIO signal is sent.

@@ Line 410: / Line 410: @@
 === My Issue #2: PWM and Piezo buzzer ===
-The PWM outputs a continuous pulse of varying duty cycle.  However, there was an issue with my computer in which no sound was produced after the initial click. Once the new SourceForge was used, the PWM signal worked. However, during the time I was troubleshooting to ensure the piezo buzzer was not damaged, GPIO output was used to generate PWM.  A PWM signal was generated when implementing delays and loop and setting GPIO signal high or low.
+The SJ One Board has capability to output PWM signal to create a sound from the piezo buzzer.  However, there was an issue with my computer in which no sound was produced after the initial click. Once the new SourceForge was used, the PWM signal worked. However, during the time I was troubleshooting to ensure the piezo buzzer was not damaged, GPIO output was used to generate PWM.  A PWM signal was generated when implementing delays, a for loop and setting GPIO signal high or low.
 === My Issue #3: Daisy-chain SPI and Nordic wireless ===

@@ Line 386: / Line 386: @@
 The Vehicle Module individual testing consisted of:
-. GPIO was initially placed into a separate function, in which a pushbutton on the SJ OneBoard sends GPIO signal to the garage remote controller.  The garage remote controller LED light was monitored to ensure it lit up when GPIO signal was sent.
+. GPIO was initially placed into a separate function, in which a pushbutton on the SJ OneBoard sends GPIO signal to the garage remote control.  The garage remote control LED light was monitored to ensure it lit up when GPIO signal was sent.
 . Piezo Buzzer was tested for different frequencies to determine the frequency with the loudest noise. The piezo buzzer was tested at the following frequencies:  2kHz, 4kHz, 4.5kHz, 6kHz, and 10kHz. It was determined the loudest sound was from the piezo buzzer's datasheet resonant frequency of 4.5kHz at 85dB.

@@ Line 347: / Line 347: @@
 '''Microcontroller to Piezo Buzzer''' <br/>
 The microcontroller to piezo buzzer communication was implemented using PWM.  The microcontroller outputs PWM signal of approximately 3.3V.  The piezo buzzer operates nominally at 5V.  The volume of the alarm can be adjusted by the duty cycle and different sounds can be produced based upon different frequencies.
-In the alarm application, the frequency was set to within the human hearing frequency range and duty cycle is set at 50% for maximum volume. The software initializes the PWM output and the frequency.  Using  set(duty cycle) functon from the pwm class, 50% is used to turn on alarm and 0% is used to turn OFF alarm.
+In the alarm application, the frequency was set to within the human hearing frequency range and duty cycle is set at 50% for maximum volume. The software initializes the PWM output and the frequency.  Using  set(duty cycle) function from the PWM class, 50% is used to turn on alarm and 0% is used to turn OFF alarm.
 '''Microcontroller to Garage Door Remote Control''' <br/>
-The microcontroller to garage door remote control communication was implemented using GPIO. To open the garage door, a pulse equivalent to pushing down on a pushbutton switch is sent. First, the GPIO pin is  initialized by setting the pin corresponding to FIODIR to output. In order to simulate 500 millisecond pulse, microcontroller sends high (3.3V) GPIO signal for 500 milliseconds and then sets it low using FIOSET and FIOCLR.
+The microcontroller to garage door remote control communication was implemented using GPIO. To open the garage door, a pulse equivalent to pushing down on a push button switch is sent. First, the GPIO pin is  initialized by setting the pin corresponding to FIODIR to output. In order to simulate 500 millisecond pulse, microcontroller sends high (3.3V) GPIO signal for 500 milliseconds and then sets it low using FIOSET and FIOCLR.
 '''Microcontroller to 7-segment LED display''' <br/>
-The microcontroller to 7-segment LED display communication was implemented using I2C.  However, LED classs and its functions have already been created to display digits to LED display so LED display code development was not needed.  The set(char num) function was called to display distance on LED.  If the distance exceeds 99 inches, the LED display will be set to 99.  After not receiving data from Garage module for 1000 mesh packets, the clear() function was used to clear LED display.
+The microcontroller to 7-segment LED display communication was implemented using I2C.  However, LED class and its functions have already been created to display digits to LED display so LED display code development was not needed.  The set(char num) function was called to display distance on LED.  If the distance exceeds 99 inches, the LED display will be set to 99.  After not receiving data from Garage module for 1000 mesh packets, the clear() function was used to clear LED display.
 == Testing & Technical Challenges ==