Revision as of 20:07, 27 November 2011

Kin Chin Chua - Design Notebook

Week of Sept. 05, 2011

Sept. 07 (Wed):

• attended kick-off meeting
  

Week of Sept. 12, 2011

Sept. 16 (Fri):

• attended weekly meeting
  

Week of Sept. 19, 2011

Sept. 21 (Wed) ~1.5 hour :

• participated in teleconference with HKUST
  

Sept. 23 (Fri):

• attended weekly-meeting
  

Week of Sept. 26, 2011

Sept. 28 (Wed) ~1 hour:

• attended group meeting:
  

1. Designed and drew a block diagram for the control system.
   
2. Discussed about some processors and TI microcontroller.
   

Sept 29 (Thurs) ~1.5 hour:

• Looked over the TI microcontrollers with Arm cortex M3 processor suggested by Scott and Jason
  
• Searched online for other microcontroller board such as Arduino Fio.
  
• Found a webpage introducing a similar project (WIFI Robot) and thought it might be a good reference
  

    ~ Instead of internet, the robot was controlled by the user by connecting a laptop to the router mounted on the robot wirelessly.

    ~ It also has video feed, so that the robot can be controlled even it is out of sight.

    ~ http://www.jbprojects.net/projects/wifirobot/

Sept. 30 (Fri):

• attended weekly-meeting

Week of Oct. 3, 2011

Oct. 6 (Thurs) ~2 hours:

• attended group meeting

1. Designed a draft of poster for VIP poster session

Oct. 7 (Fri):

• attended weekly-meeting

Week of Oct. 10, 2011

Oct. 14 (Fri):

• Search for some network cameras that might be useful such as: (~1.5 hours)
  

~ http://www2.panasonic.com/consumer-electronics/shop/Computers-Networking/Network-Cameras/Residential-IP-Network-Cameras/model.BL-C1A_11002_7000000000000005702
~ http://www.brickhousesecurity.com/vivotek-pt7137.html
~ I found that some cameras are not bad but too expensive.

• attended weekly-meeting

Week of Oct. 17, 2011

Oct. 18 (Tues) ~3 hours:

• attended group meeting

1. decided to take a tank as the vehicle platform as it has more space for us to put things on
2. decided on wireless transceiver
   
3. decided to use push buttons and IR sensors to counter the situation might happen when there is a delay on receiving video.
   
4. some difficulties are encounterred while deciding to use an IP or network camera such as:
   

         ~ it is difficult to feed the video to our server since specific software or webpage is required for most of the IP cameras

         ~ ip address of an IP camera has to be assigned manually

• We also tried to program the microcontroller board and we managed to print our names on it.

Oct. 19 (Wed) ~2 hours:

• met with the group to set up a lab bench in EE63

• attended VIP poster session
  

Oct. 20 (Thurs) ~ 1.5 hours:

• Read the reference manual of the microcontroller board we are using
  
• Read more about the terms like A/D, PMW, SPI, UART, etc.
  

Oct 21 (Fri):

• attended weekly-meeting

Week of Oct. 24, 2011

Oct. 25 (Tues) ~3.5 hours:

• attended group meeting

1. tried to search for some useful cmos cameras
2. realized that the transfer rate of a cmos camera is too high (about a few Megabytes/s)
3. task: try to find for cmos camera that would output M-JPEG or M-PEG
4. wrote a list for all possible peripherals and interfaces which would be needed for the project

Oct. 28 (Fri):

• tried to search for cmos camera that would output M-PEG or M-JPEG but didn't find anything useful. There are quite a few IP cameras that output M-JPEG though. (~1 hour)
• attended weekly-meeting

Week of Oct. 31, 2011

Nov. 2 (Wed) ~ 45 minutes:

• continue working on the draft of the list for design review made by Scott and Chris

Nov. 3 (Thurs) ~ 4 hours:

• attended group meeting.

1. designed a cicuit to drive the motor by PWM output, only problem was the microcontroller board is not providing stable output voltage (4.4V or 0.7V)
2. Chris and I finalized the list of the topics for design review.

Nov.4 (Fri):

• attanded weekly-meeting
  

Week of Nov. 7, 2011

Nov. 8 (Tues) ~ 3 hours:

• attended group meeting to work on the powerpoint slides for design review.
  
• I personally worked on the slides for remote controller and sensors.
  

Nov. 10 (Thurs) ~ 2 hours:

• participated in tele-conference with HKUST
  

Nov. 11 (Fri) ~ 2 hours:

• practised design review presentation with group
  
• attended design review.
  

Week of Nov. 14, 2011

Nov. 15 (Tues) ~ 1.5 hours:

• attended group meeting
  

1. Scoot, Chris and I worked on and improved the protocol proposed by HKUST.
   
2. We felt that the proposed protocol doesn't have any combination for any additional peripheral so we decided to have have 16 bit instructions where every combination has different instruction
   
3. However, we realized that this design does not help when the user wants to have different instruction at 1 time, eg move forward and turning at the same time.
4. Hence, we came out with the protocol as the picture below:

Back to Design Notebooks