Kyle Kozlowski Status Update 11/30

Capstone Status Update

Hardware Design

  • Bicycle sensor system heavily damaged, repairs underway
  • In process of repairing or replacing the phone for the bicycle sensor system
  • Bicycle system progress currently halted

Schedule

  • Sensor system schedule harmed by loss of phone
  • Integration delayed until phone recovered
  • Calibration will be continuing until the end

To Do

  • Still continuing with car sensor system, needs integrated with Android system
  • Need repairs to bike phone ASAP

Kyle Kozlowski Update Post 11/2/19

Capstone Status Update

Hardware Design

  • Evaluated various sensor options needed to obtain necessary data for algorithm
  • Bicycle sensor system designed for demo
  • All necessary parts have been ordered and are ready in lab
  • Assembly on bicycle finishing tomorrow for demo

Schedule

  • A delay in obtaining parts has forced a delay in independent parts and testing bluetooth
  • This has been simplified by switching to bluetooth-enabled parts and removing the need for the RPi

To Do

  • Confirm bluetooth connectivity
  • Preliminary hardware integration

Weekly Status Report – Week of 10/6 from Kyle

  • This week I have begun work on potential designs of sensor systems to compliment the data collected by the MDEK.  The MDEK provides relative position fairly reliably, but additional sensors to collect absolute velocity and information on steering are being selected.
  • It became abundantly clear this week that the MDEK alone does not provide enough information to support a machine learning collision prediction algorithm.  Without such an algorithm, we do not believe we can reliably and quickly predict collisions. This risk is being mitigated with the design of the additional sensor system.
  • My progress is behind schedule.  We have the batteries for testing, but are not yet certain if we need additional MDEK sensors.  To compensate, I am working on competing designs, on of which uses extra MDEK sensors. and another which does not.
  • Our main deliverable this week is finishing the Design Review Report.

Weekly Status Report – Week of 9/29 from Kyle

  • This week I investigated the capabilities of our core sensing system, the Decawave MDEK1001 by reviewing the available documentation and manuals, and papers on other relevant projects using the same system.  Additionally, I looked into methods of powering and testing our system, and ordered  batteries and assembled a chassis for a simple robot car.  Any additional design into the sensor system is heavily dependent on the decision of purchasing more MDEK nodes.
  • This level of focus is being given to the MDEK because its capability is the most significant risk to the project.  The pairing behavior of sensors in its network could limit its range and potential.  We are prepared to add sensors of a different type to compensate for this if it happens, or to add 12 additional MDEK nodes to our existing 4.
  • My progress is behind schedule.  We are hoping to get the batteries we need this week to more conclusively test the MDEK.  Our parts list is heavily dependent on this testing because if our tests show that we need more sensor modules, it will take half of our budget to get more, limiting the other sensors we can incorporate.
  • I intend to have two competing designs this week that differ based upon whether or not we need the additional sensor package.