12:30 - 5:30 pm
1. Completed ADC Test Report
2. Research possible ADCs
3. Summarized ADC features for best options
-----------------------------------------------------------
1. Entered remaining ADC test data and completed report with procedure, data, conclusions, and discussion sections.
2. Looked up potential ADCs with the following criteria:
- resolution >12 bits
- multi-channel or multiplexed input
- data rate > 400 SPS
- programmable input gain
- sigma-delta
- low power: <~ 50 mW
3. Selected best ADC options and listed their features to compare. Narrowed choices down to 3 options.
March 7, 2008
3/07/08 Leticia Rojas
12:15-2:30
1. worked on Matlab Data analysis program
2. worked on matlab video acquisition
3. Reseached video acquisition in LabView
--------------------------------------------
1. worked on details of a function that allows the user to plot several parameters on a same graph. Worked on other details of the program, like closing prompt windows after use.
2.I'm testing the limits of matlab for this video acquisition.
3. I'm reseaching examples to see if it is better to get our video acquisition using Labview.
1. worked on Matlab Data analysis program
2. worked on matlab video acquisition
3. Reseached video acquisition in LabView
--------------------------------------------
1. worked on details of a function that allows the user to plot several parameters on a same graph. Worked on other details of the program, like closing prompt windows after use.
2.I'm testing the limits of matlab for this video acquisition.
3. I'm reseaching examples to see if it is better to get our video acquisition using Labview.
March 6, 2008
March 3, 2008
3/03/08 Leticia Rojas
3:30-6:15
1. worked on Matlab Data analysis program
2. met with Bram about the Matlab program
----------------------------------------------------
1. Implemented a function that allows the user to plot 2 parameters against each other.
2. Spoke with Bram about what the ranger team needs to get from the program and we established a priority list of things to work on.
1. worked on Matlab Data analysis program
2. met with Bram about the Matlab program
----------------------------------------------------
1. Implemented a function that allows the user to plot 2 parameters against each other.
2. Spoke with Bram about what the ranger team needs to get from the program and we established a priority list of things to work on.
03/03/08 Nicole Rodia
3:45 - 5:45 pm
1. A/D Converter Test Report
2. Future Robotics Team Meeting
3. Researched potential Sigma-Delta ADCs
---------------------------------------------------------
1. Created data tables and began writing report on A/D Converter testing from past two weeks.
2. Meeting: Discussed possible use of Sigma-Delta ADCs, with multiple inputs, high sampling rate. Necessity of filtering high frequencies on ADC input to prevent aliasing.
3. Looked up Sigma-Delta ADCs from Maxim, Analog Devices, and TI. Looking for at least 16-bits of resolution, multiple analog inputs, and sampling rate > 1kSPS.
1. A/D Converter Test Report
2. Future Robotics Team Meeting
3. Researched potential Sigma-Delta ADCs
---------------------------------------------------------
1. Created data tables and began writing report on A/D Converter testing from past two weeks.
2. Meeting: Discussed possible use of Sigma-Delta ADCs, with multiple inputs, high sampling rate. Necessity of filtering high frequencies on ADC input to prevent aliasing.
3. Looked up Sigma-Delta ADCs from Maxim, Analog Devices, and TI. Looking for at least 16-bits of resolution, multiple analog inputs, and sampling rate > 1kSPS.
March 2, 2008
3/1, Rohit Hippalgaonkar
Hours (from Tuesday 2/26 through 1/3):
Tuesday - 3 pm to 4 pm (Upson CIT Computing lab) ;10.30 pm to 11.30 pm (from home)
Wednesday - 11 am to 12.30 pm; 3 pm to 6 pm (from CIT)
Saturday - 5.30 pm to 7.00pm; 8.30 pm to 12.30 pm (from CIT)
------------------------------------------------------------------
1. Hyperworks 8.0 (MotionView, HyperGraph, HyperView, etc)
* Compared Hyperworks plots to results from MATLAB simulation of double pendulum. The Matlab simulation itself WAS accurate to a good degree, and showed conservation of energy (3 hours).
* Implemented double pendulum while learning various plotting and animation features of the software - such as plotting user defined expressions, getting new outputs and so on. These small things ended taking a lot of time, but finally these helped in doing an energy conservation check of the double pendulum model. (7 hours)
* Implemented a simple model involving collisions (bouncing ball dropped from a height onto a floor) - did an energy check and so on. The software somehow only plots one collision cycle- looking into this. (2 hours). Once I work this out, will move on to the simplest walker.
Implemented double pendulum with energy conservation - learnt more plotting features.
Tuesday - 3 pm to 4 pm (Upson CIT Computing lab) ;10.30 pm to 11.30 pm (from home)
Wednesday - 11 am to 12.30 pm; 3 pm to 6 pm (from CIT)
Saturday - 5.30 pm to 7.00pm; 8.30 pm to 12.30 pm (from CIT)
------------------------------------------------------------------
1. Hyperworks 8.0 (MotionView, HyperGraph, HyperView, etc)
* Compared Hyperworks plots to results from MATLAB simulation of double pendulum. The Matlab simulation itself WAS accurate to a good degree, and showed conservation of energy (3 hours).
* Implemented double pendulum while learning various plotting and animation features of the software - such as plotting user defined expressions, getting new outputs and so on. These small things ended taking a lot of time, but finally these helped in doing an energy conservation check of the double pendulum model. (7 hours)
* Implemented a simple model involving collisions (bouncing ball dropped from a height onto a floor) - did an energy check and so on. The software somehow only plots one collision cycle- looking into this. (2 hours). Once I work this out, will move on to the simplest walker.
Implemented double pendulum with energy conservation - learnt more plotting features.
Subscribe to:
Posts (Atom)
