Information
- Participants: Heitor, João Lucas, Thiago, Waine
- Duration: ~1h
Agenda/Minute
- Discuss approach towards projects
- What project we prefer? Luggage?
- Wait for response? Develop both? Develop only luggage carrier?
- Discuss questions raised about the projects
- Luggage use cases
- What if the luggage gets lost?
- Absolute position/location; notify user and airport staff; sound
- What if the user wants to get away from luggage? (example, bathroom or leave it with a friend for sometime)
- User may deactivate the luggage following him/her
- How the payment will be?
- Simulate the payment through Google Pay/Apple Pay (SIMULATION)
- Luggage technical questions
- Number of wheels and how to turn
- Change it to three wheels, ask Fabro
- How to know the absolute position of the luggage to know where it is?
- Separate absolute and relative location
- UW, Bluetooth, Wifi? Decide later
- Distance measurement from the user and its localization (RF)
- IT’S A LOT HARDER THAN WE THOUGHT
- May be handle a controller for the user so that it can control luggage? Unconvenient, but it would make our work a lot easier
- Research and define a technology, stablish limitations, and propose a solution
- Do we worry about connection being lost?
- Bluetooth user/luggage: notifies the user and buzz one time, changes communication to wifi (led to represent communication)
- WiFi luggage: notify the user and buzzes (keeps buzzing), (led to represent communiation)
- Do we let user control the system through cell phone or beacon? For example, manually moving or resetting the alarm?
- Uses cell phone for control
- Aquarium care taker use cases
- What it will measure and control upon? Is it worth to use pH?
- How it will control the metrics? How it will notify the user for these metrics?
- Is the system going to be self powered?
- Aquarium technical questions
- How we will control pH?
- How the system will drop food and control its storage?
- Do we use local or cloud storage?
- Updates for next week:
- Document problem (Thiago)
- Document functional/non-functional planned to be covered (João)
- Document proposed solution
- Structure (Heitor)
- Embedded (Waine-Heitor)
- App (Thiago)
- Main Central (Waine)
- Integration (later)
- ALL components with specs (ex. range of working for RF sensor; force/torque of motor, etc.)
- Risks
- Build diagrams for full system and its subsystems
Tasks
-
Heitor
- João Lucas
- Document functional/non-functional planned to be covered
- Thiago
- Document the problem
- Specify the app screens
-
Waine
Observations