Posted on

Reva Poddar’s Status Report for 10/21

Accomplishments This Week:
This week, I focused on setting up the Bluetooth communication framework and managing data transfer. I made progress in preparing the Bluetooth package for Flutter to detect nearby devices and started evaluating different data handling techniques to ensure smooth real-time data transmission. I also looked at flutters existing graphical representation libraries.

Progress Status:
I am currently a bit behind schedule, and anticipate that I will encounter issues with maintaining a stable connection and organizing the data flow within the app, so I am planning to dedicate more time throughout the upcoming weeks to catch up. The delay primarily involves establishing the initial Bluetooth connection and finalizing the file system structure. I am confident that with a concentrated effort, I can get back on track and complete the planned milestones.

Deliverables for Next Week:

  1. Complete the initial Bluetooth connection setup to receive data on the app.
  2. Finalize the file system design for managing Bluetooth-transmitted data from ESP32.
  3. Begin integrating the data visualization features using data from the Bluetooth connection.

Updated Schedule:

  • By End of the Week: Continue working on making the initial Bluetooth connection and refining the file system for Bluetooth communication.
  • Upcoming Weeks: Dedicate extra effort to finalize the Bluetooth integration with Vansh and start implementing the graphical representation components.

The focus will be on managing any remaining connectivity or data flow issues and ensuring that progress aligns with the project goals.

Posted on

Team Status Report for 10/21

Accomplishments This Week:

  • System Architecture: Completed a detailed design for the insole, integrating the IMU, pressure pad, BLE module, and LIPO battery. Outlined data flow and real-time transmission via ESP32.
  • Data Collection and Processing: Documented data handling methods, including preprocessing and filtering using MATLAB to minimize noise.
  • Bluetooth: communication in Flutter, and explored graphical representation libraries.
  • Validation Plan: Developed a testing strategy to assess system accuracy, response time, and battery efficiency.

Progress Status:

  • Behind Schedule: Delays in Bluetooth connectivity and data flow organization. Additional effort planned to catch up.

Significant Risks:

  • Bluetooth Stability: Addressing communication issues with tests and alternative BLE options.
  • Data Handling: Optimizing real-time processing methods to avoid latency.

Updated Schedule:

  • This Week: Complete Bluetooth setup and file system design.
  • Upcoming Weeks: Finalize integration and start implementing data visualization.

Part A: Global Factors (Written by Reva Poddar)

The motion-tracking insole addresses a global need for improved gait analysis as well as injury prevention across various demographics. The solution caters to athletes and individuals undergoing physical therapy, as well as everyday users looking to monitor and enhance their movement patterns. With the rise in remote health monitoring and wearable technology adoption worldwide, the insole offers a universally accessible tool that supports different regions and user groups, even those who are not technologically inclined. The app’s compatibility with both iOS and Android devices ensures it can be used across diverse device ecosystems, making it suitable for a broad audience outside academic and local communities.

Part B: Cultural Factors (Written by Vansh Mantri)

Cultural considerations are crucial in designing the insole, as attitudes towards exercise, rehabilitation, and technology use vary widely. In communities that prioritize fitness and sports, the insole can be a tool for optimizing athletic performance. In cultures where traditional medicine or low-tech rehabilitation is preferred, the app’s user-friendly interface can help introduce the benefits of modern gait analysis without overwhelming users.

Part C: Environmental Factors (Written by Vansh mantri)

The insole is designed with sustainability in mind, promoting environmental considerations in multiple ways. By helping users prevent injuries, the need for prolonged physical therapy or medical treatments, which have environmental impacts due to resource and energy use, is reduced. The hardware components are selected for durability, minimizing electronic waste through fewer replacements.

 

Posted on

Team Status Report for 10/5

This week, we made substantial progress on both the hardware and software components of the motion-sensing shoe sole project. The hardware team focused on finalizing component selections, while the software team concentrated on developing a functional app prototype. The goal is to ensure that both the hardware and software align with our design specifications and operational requirements.

Progress Summary:

Hardware Component Finalization:

  1. Inertial Measurement Unit (IMU): We selected an IMU that includes both an accelerometer and gyroscope, crucial for real-time motion tracking.
  2. Pressure Pad: Chosen for accurate foot pressure detection to enhance user feedback.
  3. Bluetooth Low Energy (BLE) Module: We opted for a BLE module to ensure low-power wireless communication between the insole and external devices.
  4. Battery: After calculating the power requirements, we confirmed the use of a rechargeable LIPO battery. This will support extended use, and the calculations have been documented in the design report.
  5. ESP32 Microcontroller: Following a meeting with the CLIMB team (working on a similar project), we decided to use the ESP32 microcontroller for its low power consumption, integrated BLE, and ease of interfacing with sensors and the battery.

IMU Testing and Simulation:

  • We connected an Arduino to the Bosch IMU sensor and began collecting data.
  • A preliminary simulation in MATLAB helped us identify issues such as sensor drift and saturation, which will be addressed during future sensor calibration and firmware development.

Software Development (App Prototype):

  • We developed a functioning prototype of the mobile app with the three key sections outlined in our design presentation:
    • A main page showing real-time stats from the IMU.
    • A history and trends page displaying past performance.
    • A settings page allowing users to set customizable thresholds and receive alerts when metrics fall below specified limits.
  • We encountered issues with the iOS simulator due to dependency conflicts, which delayed testing. The app is now functional on iOS, but further testing on Android is needed to ensure smooth operation across both platforms.

Risks:

  1. Sensor Calibration: The IMU data may have issues with drift and saturation, identified through our simulation. We are working to address these issues through calibration in the next phase.
  2. Power Optimization: Battery life could be impacted by sensor performance, and optimizing the balance between power consumption and functionality remains a key focus.
  3. Cross-Platform Testing: Although the app runs on iOS, the Android version needs more attention to ensure functionality on both platforms.

Changes to the Design:

  • After discussions with the CLIMB team, we made the decision to use the ESP32 microcontroller. This change improves power efficiency and integration simplicity at the cost of some initial setup challenges, but we believe the benefits outweigh these costs.

Next Steps:

  1. Hardware:
    • Continue sensor calibration and integrate the IMU with the ESP32.
    • Finalize the communication protocol between the insole and external devices.
    • Refine the simulation model to reduce sensor drift.
  2. Software:
    • Collaborate with Vansh to receive IMU data via Bluetooth and integrate it into the app.
    • Work on presenting the IMU data graphically within the app.
    • Address remaining Android testing issues to ensure smooth cross-platform functionality.

Updated Schedule:

With the hardware components finalized and the app prototype functioning on iOS, we remain on schedule. The next major milestone will involve testing the integration of real-time IMU data with the app and addressing any power or sensor-related challenges.

Conclusion:

We are progressing well on both the hardware and software fronts. The finalized hardware components—Bosch IMU, ESP32, and BLE module—are ready for integration, and the software app is functioning on iOS with pending improvements for Android. The upcoming focus will be on sensor calibration, app refinement, and Bluetooth integration to complete the motion-sensing system.

Posted on

Reva Poddar’s Status Report for 10/5

This week, I made significant progress by developing a functioning prototype of our app based on the design presentation specifications. The app now has three key sections:

  • A main page that displays real-time statistics collected from the IMU, providing users with immediate feedback on their movement data.
  • A history and trends page that shows past performance, allowing users to review historical data and track improvements over time.
  • A settings page, where users can set customizable thresholds for specific metrics (e.g., speed or stride efficiency) and receive alerts if they fall below the set limits.

I faced some challenges setting up the iOS simulator for testing, mainly due to issues with dependencies in my development environment, which delayed the testing by a few days. Despite these challenges, I was able to get the prototype working on an IOS simulator however android testing will require a little bit more time to ensure the app runs smoothly on both platforms.

Next Steps:

Going forward, my focus will shift toward data integration:

  1. I plan to work closely with Vansh to receive the IMU data values via Bluetooth. This will involve using Flutter’s Bluetooth package to establish the connection and ensure smooth data transmission from the IMU to the app.
  2. Once I receive the data, I will begin integrating it into the app, developing a system to analyse + present the information graphically to users in real-time.
  3. I will also continue addressing the iOS simulator issues and aim to get the app running on both iOS and Android devices for a more robust testing process.
Posted on

Team Status Report for 9/28

Task Overview:

This week, the focus was split between software architecture development and hardware component selection and design finalization for the motion-sensing shoe sole. Reva concentrated on the app’s software design, while Vansh worked on selecting the appropriate hardware components and finalizing the insole design. The goal was to ensure that both the technical specifications of the hardware and the software architecture align with the operational requirements outlined in previous discussions.

Progress Summary:

Software Architecture (Reva’s Contributions):
Reva focused on refining the software architecture for the mobile app. After evaluating multiple software platforms, Flutter was chosen for its ability to target both iOS and Android devices from a single codebase, optimizing development time and cost. The app has been structured into three main sections:

  1. History and trends: to display past performance data.
  2. Real-time data: to provide immediate feedback based on sensor readings.
  3. Settings: for user preferences and system configurations.

This architecture will allow for intuitive access to key features and help users monitor and analyze their movement patterns effectively. Reva is on schedule and will begin developing the app in Flutter next week.

Hardware Component Selection and Design Finalization (Vansh’s Contributions):
Vansh focused on selecting and finalizing the hardware components that will make up the motion-sensing sole. Key progress includes:

  1. IMU (Accelerometers & Gyroscopes): The Bosch IMU was selected for its ability to track both linear and angular motion, with a ±16g accelerometer range and ±2000°/s gyroscope range, offering sufficient accuracy for our use case.
  2. Pressure Sensors: High-resolution pressure pads were chosen for precise foot pressure mapping, with sensors placed at the forefoot, midfoot, and heel for detailed movement data.
  3. Microcontroller (ESP32): Selected for its built-in Bluetooth Low Energy (BLE) and Wi-Fi capabilities, which allow efficient data transmission to the mobile app.
  4. Power Supply: A 200mAh rechargeable lithium-polymer battery was selected to support at least 3 hours of continuous use, subject to final testing and optimization.
  5. Connectivity: BLE 5.0 was chosen for low-power, efficient data transmission to mobile devices.

Vansh also made progress in finalizing the insole design, opting for a removable insole for flexibility and comfort, and selecting lightweight, moisture-wicking materials. Minor adjustments to the sensor placement and materials will be made following initial user testing.

Challenges Encountered:

  1. Battery Life Optimization: Ongoing work is needed to optimize the balance between sensor performance and power efficiency to ensure longer battery life.
  2. Sensor Calibration: Efforts continue to refine calibration settings to ensure accurate data collection across diverse environments and use cases.

Next Steps:

  1. Software: Reva will begin developing the app in Flutter, starting with the basic layout and navigation.
  2. Hardware: Vansh will continue working on the design report, finalizing the component selections and specifications, and begin prototyping with the selected components to validate their functionality and performance.
  3. Power Optimization: Ongoing efforts will focus on improving power consumption to extend battery life during use.

Design Review Presentation:

Vansh is preparing a design review presentation to summarize the component selection, design choices, and the rationale behind these decisions. This presentation will serve as a key milestone to finalize the hardware and software integration plan and will be ready by the end of the week.

Conclusion:

The team is progressing well with both the software architecture and hardware design. The combination of Flutter for software development and the selected Bosch IMU, pressure sensors, and ESP32 microcontroller for hardware will help meet the project’s operational requirements. The next phase will involve prototyping and testing to validate the design.

Looking at the project as a whole, in terms of public health, safety, and welfare (Part A), the motion-sensing shoe sole is designed to improve users’ physical well-being by providing real-time feedback on foot strike patterns, stamina, and other metrics during physical activities. By helping users track and optimize their movement, the product can contribute to injury prevention and promote physical health. Additionally, the app’s user-friendly interface will reduce psychological strain, making it easy for users to monitor their progress, thus enhancing overall well-being. Safety considerations include ensuring the accuracy of sensor data to prevent false readings, which could otherwise lead to injury or improper posture adjustments.

From a social perspective (Part B), the product can cater to a broad and diverse user base across different cultural and social groups. By enabling users to track their health and fitness data and potentially share it within their communities or social groups, the product encourages social interaction and wellness. It could also contribute to creating a health-conscious community that motivates individuals to engage in physical activities, enhancing collective social welfare.

In terms of economic factors (Part C), the project aims to be cost-efficient by focusing on using an IMU sensor and avoiding more expensive hardware like pressure pads. The choice of Flutter for app development ensures the app can be built for both iOS and Android from a single codebase, significantly reducing development and maintenance costs. This will help in making the product more affordable for users while still delivering robust health-monitoring capabilities, contributing to the sustainability and accessibility of the product in the market.

Posted on

Reva Poddar’s Status Report for 9/28

This week, I focused on the software architecture for our project’s app, carefully evaluating various software platforms in terms of usability, flexibility, and development efficiency. After considering the trade-offs between different technologies, I decided to use Flutter, a cross-platform framework, to build the app. This decision allows us to target both iOS and Android devices simultaneously, ensuring a wider user reach and optimizing the development process in terms of cost and time. Additionally, I laid out the structure of the app into three primary sections: one for viewing historical data and trends, another for displaying real-time data collected from the motion-sensing shoe sole, and a settings section for customizing user preferences. This architecture is designed to provide users with seamless access to essential features, improving their experience by offering an intuitive interface. With the software choice and structure finalized, I’m confident we are on schedule. My next step is to begin implementing the app in Flutter, setting up the basic layout and navigation between these sections.

No significant risks have been identified at this stage, but I will continue to monitor the development process for potential issues, particularly around cross-platform performance and ensuring the app remains intuitive and accessible to a broad audience.

Posted on

Team Status Report for 9/21

This week, we focused on finalizing and presenting our project proposal for the motion-sensing shoe sole. The proposal presentation highlighted the feasibility and design considerations of the project, however as we had changed ideas after the abstract submission, we were not able to meet with professors to fully discuss the feasibility of the project. The presentation was successfully delivered, and feedback was received to guide the next phase of the project – including aspect reevaluating the use of pressure sensors in the shoe sole in regards to durability and data collection for our desired use case. We had an insightful meeting with Tamal to discuss the technical feasibility of our project. During the discussion, we discussed issues like bandwidth, selecting a suitable IMU, and perhaps pivoting away from using pressure pads. and decided to focus more on making the IMU work effectively to meet our data-processing requirements, as well as using it externally in the shoe rather than in the shoe sole which could hinder performance. The lack of pressure pad may lead to unexpected technical challenges in measuring certain foot metrics. However, this trade-off will simplify the design and reduce complexity. So we need to spend some time to make key decisions this weekend to further progress with our project. In regard to the upcoming week, we have decided to meet very early on to look look into our use case requirements in detail, and look at specific hardware components and current studies to revaluate our product and create a more detailed systems and UML design, in order to ensure our design is feasible.

Posted on

Vansh Mantri’s Status Report for 9/21

I delivered the project proposal presentation after preparing with Reva’s help. We also had a meeting with Tamal where we decided to focus on the IMU sensor, and looking at using it externally on the shoe rather than in the sole and move away from using a pressure pad. By the end of next week, I will begin IMU sensor integration and testing to ensure it meets our requirements, and look at reading initial data. I will conduct tests to ensure the data is reliable. Ensuring the IMU sensor’s accuracy, and durability for our current use case which is running is the main risk, so I want to look at pivoting on that, and further exploring this in detail by reading about existing products and studies.

Posted on

Reva Poddar’s Status Report for 9/21

This week, I helped Vansh rehearse for the project proposal presentation, which was successfully delivered. I also focused on the software architecture looking at how I can build an app to take data from our BLE module, and researching how to process IMU data for analyzing metrics like foot strike and stamina some of our use case metrics. The project proposal presentation was completed on time, and I’ve begun planning the software design for data processing. Next week, I will focus on data processing for the IMU sensor and begin initial test scripts, as well as support Vansh in selecting suitable hardware components. The main risk is ensuring the accuracy and frequency of IMU data. I plan to conduct testing and calibration to mitigate this.