
Progress
Log
Week 13
4/11 - 4/17
The final draft of the completed proposal report was presented to Professor Ejaz. The last comments were taken and applied. The due date of the report is the 4/16. The draft proposal presentation was shown after the report and it was critiqued. Website updates were made to change verbiage, add success criteria, update timeline & budget. The final report was uploaded to website at 6:39pm 4/16.
Week 12
4/04 - 4/10
All existing chapters of the proposal report were combined into the format in which the report needs to be. The overall draft of the proposal report was reviewed and commented on. The proposal presentation draft was started. The website was not available within the week so updates was not made as consistently.
Week 11
3/28 - 4/03
Edits to the drafts of chapters 2,3, and 4 were made before being presented to be reviewed and critiqued. Edits were made and for more bigger corrections or suggestions notes were taken to implement later.
Week 10
3/21 - 3/27
The draft of the abstract and chapter 1 of the proposal report was presented and critiqued. Small edits were made on the spot of the review and and notes were taken for other edits. Chapters 3 and 4 drafts were also completed but were not reviewed at the time. The draft of chapter 2 was started.
Week 9
3/14 - 3/20
Both Team members began working on the draft of the proposal report. Mark decided to work on the abstract and Chapter 1's Introduction, Kyle decided to work on Chapters 3 Non-Technical issues and 4 Conclusion. Chapter 2 was decided that both handle in its completion. A visual representation of the system was created by Kyle and will be added to the website to the block diagram section. The decision to use a different a Lidar was made. Budgetary reasons was the main reason for the change. The new Lidar, YDLIDAR X2 360 was priced at $69.99 in comparison to the $129.00, Garmin LIDAR-Lite v3. The YDLIDAR X2 360 has a lower a range at 8m, but this is still acceptable with added benefit that it is also has 360 degree view.
​
​
Week 8
3/07 - 3/13
Both team members research implementing a image recognition system to add to the overall project. This camera system will potential solve the issue confirming the entering and exiting of the intersection that the laser system would not be able to solve. Two possible cameras were discussed as the main hardware. These two varied in megapixels 0.3 and 2, so a consideration of minimum requirements was made to to maximize potential cost. In the midst of camera research the Pixy2, a device design for object and image recognition was decided on for the project.
Week 7
2/28 - 3/06
Discussion of exact parts to use and finalization of proposed budgets were made. Also with the power budget it was suggested to make two different budgets in reference to the primary and secondary microcontroller.
The idea of a laser to be used to monitor a vehicle entering and exiting the intersection needed more research, as well as a proper way to signal pedestrians.
The proposed beginning of a working timeline is in the works for April.
Revised timeline:
• Changed Week 3 to development of the secondary module and initial RF communication
• Changed Week 4 to testing of communication between master and multiple slave units
• Changed Week 6 to design of power module
• Changed Week 7 to case enclosure design
• Changed Week 8 to small scale testing
• Changed Week 9 to begin draft of report
• Changed Week 10 to app creation and integration
• Changed Week 11 to continued testing in various conditions
• Changed Week 12 to final testing
Discussed necessary engineering specifications for project: Lidar, proximity sensor, LEDs,
Discussed addition of proximity sensor and function, vehicle to be sensed by proximity sensor producing a 1 when the vehicle leaves the stop sign proximity sensor reading will go to 0 and a timer will begin, timer will be adjustable depending on size of intersection to reflect an average crossing time, once timer has reached 0 the next vehicle/pedestrian in the queue will be prompted to cross the intersection
Mark to research data on historic/low traffic areas where the system would be best suited. Mark to also research Lidar usage at stop signs/intersections.
Kyle to research and work on Engineering Specifications and fix Project Requirements
Kyle researched MyOpenLab software, Mark looking into using access to open lab to build simulation in LabView.
Set up in person weekly meetings on Tuesdays and Fridays to work on project.
Week 6
2/21 - 2/27
Discussion of exact parts to use and finalization of proposed budgets were made. Also with the power budget it was suggested to make two different budgets in reference to the primary and secondary microcontroller.
The idea of a laser to be used to monitor a vehicle entering and exiting the intersection needed more research, as well as a proper way to signal pedestrians.
Week 5
2/14 - 2/20
The potential reducing of 3 secondary microcontrollers by having the lidar communicate directly to the primary controller was researched. With investigation it was found that the lidar communicate through pulse width modulation (PWM), because of this the potential of reducing the total number of microcontrollers to one does not seem plausible. The communication between primary controller and android application was decided on a Bluetooth module. Numerous plans of funding budget, engineering requirements and addition of communication module to block diagram were discussed and made. These initial plans were updated to the website.
Week 4
2/07 - 2/13
Team members decided on the smart 4-way intersection as design project. With this decision more intense research was made on intersection statistics i.e. accidents at a state level and wireless communication between lidar, RF transceiver and microcontroller. The National Highway Safety Administration was a immediate resource.
Week 3
1/31 - 2/06
Added research for a smart 4-way intersection system was conducted and block diagram was made. Lidar component of the potential system was discussed and the specifications were analyzed. The Garmin LIDAR-Lite v3 meet the initial requirements.
Garmin LIDAR-Lite v3 Specification
Unit size (HxWxD): 40 x 48 x 20 mm (1.6" x 1.9" x 0.8")
Weight: 22 g (0.77 oz)
Resolution: 1 cm
Accuracy: +/- 2.5 cm at distances greater than 1 meter. Refer to operating manual for complete operating specifications.
Range: 5 cm to 40 meters
Update rate: up to 500 Hz
Interface: I2C or PWM
Power (operating voltage): 4.75-5 VDC; 6 V Max
Current consumption: 105ma, idle; 130ma, continuous
Operating temperature: -20 to 60° C
Laser wave length/Peak power: 905 nm/1.3 watts
Beam divergence: 8 m Radian
Optical aperture: 12.5 mm
Regulatory approvals: CLASS 1 LASER PRODUCT CLASSIFIED EN/EIC 60825-1 2014.
Website updates and maintenance.
Week 2
1/24 -1/30
A team meeting was held to discuss two more potential projects as two of the projects were turn because of difficulty (3-D Mapping Drone) or not feasible (Smart Symptom Detector). A piano trainer and a hard of hearing captioning device. Another rough idea was discussed, vehicle height detection for overpasses. Website updates that consist of adding relevant links and descriptions to new proposal Ideas and team members
Week 1
1/17-1/23
Three ideas were developed and research for the first senior proposal meeting. A V2X Crosswalk, Smart Symptom Detector (Covid inspired) and a 3-D Mapping Drone. A senior design website was created with only the bare minimum details available. The design of the website took inspiration from previous senior design websites.


