Week1

 Week1

Feb 3rd


We found our lab time was in a clash and asked teacher for the solution. The result is we were decided to had our lab on Friday afternoon because all of us are free. In the first group lab, we picked up ordered parts from the lab technician.

The ordered parts included:

· Arduino nano

· USB-Type A to Type A plug

· 150mm (about 5.91 in) Male to Female jumper wires

· Breadboard

· LED’s

· Two microphone sensor Modules

· Jumper cables

· Arduino display

· Through hole resistors

The only parts that were picked were the Arduino nano, its display, the USB connector, and the sound sensors. The rest of the parts were available from the lab.

The methodology of the first lab is ensure every part we ordered worked as intended.

However, we found two problems stopped our lab:

· USB Type A to Type A too large

· Arduino not turning on

The solution of the first problem is request a smaller USB from the lab. Then we attempt to connect the Arduino to the lab PC using the new USB and the Arduino IDE, the Arduino goes on, indicated by the blinking light.

Next we Integrated the Arduino on to the breadboard with an LED to test simple blinking program. After program compilation and injection, the LED does not go on, with error code: avrdude: stk500_getsync(): not in sync: resp=0x00.

We tried to check pin connections with LED with the help of a diagram referencing the individual pins as well as restarting the Arduino using the rest button, yet the Arduino still refuses to upload the code. After further research, the error prompt means the Arduino cannot talk with the computer because of a multitude of issues:

· USB broken

· Arduino broken

· Wrong port and Board selected on the IDE.

· There a connection to pins TX and RX.

· Wrong processor selected on the IDE.

To resolve the first issue, we ordered a new USB. We connected the new USB for a trail but did nothing, the error prompt sill showed up.

After that, we re-checked Arduino ports as well as software settings showed the original setup is correct.

Therefore, we concluded the issue is the Arduino and ordered a new Arduino in hopes it arrives in time.

Comments

Post a Comment

Popular posts from this blog

Week 5

  Week 5 Mar 2 nd We h ad a meeting before our presentation   to  discuss our presentation order and content . We s et up   our  poster with  poster board from lab as well as set up   the  circuit for presentation . We p resented poser and circuit to   our  Assessor and Academic supervisor.   After our  presentations, we noted down important points made, such as: •Adding feedback to the system using the sound sensor, whereby certain noise levels determine the level of amplification for the user’s voice. •Making the project more presentable. •Fixing notable code bugs such as some text not refreshing upon calling a new command.
Read more

Week4

Image
  Week 4 Feb 25 th In this lab, we added more functions to code. We also add sound sensor as well as configured it to adjust to certain noise in the room. At first, we tried the code we wrote before and successfully done all the command. However, after we added the new code, the LEDs began to flash randomly. We thought it might be the problem of delay, so we modified our code and called the command again. Then we found another problem that all lights going on when the commanded hadn ’ t be called. To solve this problem, we modified the code again and tried for times. We had a brief meeting about expectations concerning bench inspection after we solved the problem. We found the screen cannot show all the words clearly, so we adjusted the sensitivity and try to record the response and command. However, that ’ s not so successful and we had to leave the room because of the time limit. We discussed and decided to take this project after class. Next week will be bench inspection, so our...
Read more

Week3

Image
  Week 3 Feb 17 th Our o rdered part arrived and we retrieved it from the lab technician. After attended to lab, we h ad a small brief about the expectations with the poster, blog, and the ethics report.   Then we b egan finding pin connections for the grove sensor. At first, we i ntegrated grove speech recognizer to breadboard with Arduino.   T he grove speech recognizer Arduino successfully powers on after connecting USB.   Secondly, we i ntegrated LED with grove speech recognizer and Arduino.   After that, we m odified the code to turn on the LED with the grove speech recognizer.   The LED turns on with the given functions in the documentation . We can call HICELL command   to  turn on the LED.   We a ttempted to add new voice functions by training grove speech recognizer , however, we realized we can no t   achieve the desired affect after all . We d ecided to use the pre   given functions to complete t as ks as ordering a ...
Read more