Links

P07-Automated Tea Infuser Documentation

Automated Tea Infuser on Wikifactory

P07 - Automated Tea Infuser

As part of a semestral project, we decided to build an automated tea infuser.

The need for a such device stems from the diversity of the different types of tea and, of course, the individual preferences for tea infusing.

One of the possible use cases occurs in a situation where the user forgets to pull out the tea bag after a certain time. This is an unpleasant situation, where in most cases the user is disgusted and unnecessarily wasted, as the user does not like the brewed tea, or the tea is too strong, which is caused by the high degree of brewing.

The second use case is usability and convenience when using an automated infuser. A common scenario is a situation where the user is in time distress. It is necessary not only to pour hot water over the tea, but also to guard the time needed for brewing. This creates an unpleasant situation where the user, most often in the kitchen environment, is dependent on an approximate time tracking via an analogue clock, as the smartphone with a timer may be in another room. At the same time, keep in mind that the time constraint increases every minute. Time tracking thus increases the user's aversion to the activity and reduces the overall enjoyment of the beverage preparation.

Another use case may involve a situation where the user pours the tea but forgets about the tea.

It is also necessary to keep in mind the wide range of tea enthusiasts who need to know the water temperature and set the exact brewing time when preparing tea.

The proposed embedded system would be able to cover all these use cases, while allowing users to set the tea brewing time, after which the tea bag would be automatically removed from the cup. At the same time, after removing the bag, the embedded system would notify the user to end the tea brewing. In addition, during the process, the embedded system would show the cup temperature on the display.

Requirements specification

The requirements specification section summarizes the functional and non-functional requirements for the resulting embedded system.

Functional requirements

• the embedded system should allow the user to set the timer value in 10-second increments,
• the embedded system should allow both the increase and decrease of the timer value during the timer setting process,
• the embedded system should load the cup temperature at regular intervals and display it on the LCD display,
• the embedded system should update the timer value at regular intervals and display the number of minutes and seconds remaining on the LCD.
• the embedded system should ensure that the tea bag is removed from the cup after the timer expires,
• the embedded system should notify the user using an audible notification when the timer expires, and the tea bag is removed from the cup.

Non - functional requirements

• the embedded system should be robust enough to withstand incorrect user input,
• the embedded system should be safe enough so that the user does not suffer any damage to health or property as a result of its use,
• the embedded system should be usable by the user, the individual actions should be sufficiently predictable and easy to use.

Components

The following components will be needed for the project implementation:

• Microcomputer Arduino Uno Rev3

https://www.alza.sk/arduino-uno-rev3-d569244.htm

23,90€

• LCD display 16x2 with yellow backlight and I2C module

https://techfun.sk/produkt/led-display-16x2-zlte-podsvietenie-spajkovany-i2c-modul/

4,90€

• Keypad 4x1

https://techfun.sk/produkt/klavesnica-4x1-avr-4-klavesy/

0,90€

• Non-soldering contact field (breadboard) 400 points

https://techfun.sk/produkt/nepajive-pole-400-bodov/

1,90€

• Servo SG90

https://techfun.sk/produkt/servo-motorcek-sg90/

3,10€

• Servo SG90 - 360° - continuous

https://www.hwkitchen.cz/9g-mikro-servo-motor-sg90-360-kontinualni/

4,71€

• Active buzzer on board

https://techfun.sk/produkt/aktivny-buzzer-na-doske/

1,50€

• LM35 temperature sensor

https://techfun.sk/produkt/teplotny-snimac-lm35-samostatne/

1,80€

The total amount for the components needed to implement a functional prototype is 42.7 € excluding shipping costs and a 9V AC-DC power adapter that we have available.

Besides components, the following material is required for implementation:

• Jumper cables M-F
• Jumper cables M-M
• Insulation material
• Tin solder
• Resistor set

Also, for the implementation of the project, it is advisable to have a soldering iron or a soldering station.

Libraries

Wire.h

The library allows you to communicate with the I2C bus. In firmware, it is only used during I2C bus scanning.

LiquidCrystal_I2C.h

The library is used to control the LCD display connected via the I2C bus. The interface is similar to the standard LiquidCrystal library. Working with the library is simple and allows the use of displays of various sizes, the size of which must be set when initializing the library.

Keypad.h

The library allows you to work with the keyboard. As with the LCD library, a keyboard of various sizes can be used with the Keypad.h library.

Servo.h

To work with the servo drive, we decided to use the Servo.h library, which greatly simplifies the work. For proper operation, it is necessary to connect the drives to the PWM outputs of the microcomputer.

 Links

P07-Automated Tea Infuser Documentation

Automated Tea Infuser on Wikifactory

Links:

link EA - link on EA repository

linkEA EN version - link on EA repository EN

good tutorial for ActivePresenter for beginners - 

EA tutorials for beginners using ActivePresenter

Bc. Kamil Macek (S12) , Bc. Jozef Olejník (S16)

SMVIT, Winter term 2020/2021, FIIT STU

Project description

Create a series of short videos (tutorials) on your chosen topics related to working with EA using ActivePresenter tool. Make sure the videos are easy to explain (this will ensure that the videos are easy to understand even for complete beginners).

Motivation

Getting started with EA can be difficult, as it is complex software with many difficult-to-understand features. Therefore, we decided to create an educational tool aimed at understanding working with EA on the subject of SMIT represented by a series of videos in the ActivePresenter tool, which can simplify this initial work with EA and we can avoid discouraging the use of this tool.

We also belong to the category of people who feel stress when working with EA, and by creating this project we have the opportunity to learn to work with EA better, we would also like to get more similar and try working with ActivePresenter tool.

Goal

The goal of the project is to create a series of 8 videos dealing with basic UC executable in EA during the initial work with this tool.

• Create simple videos to support working with EA
• thanks to simple and short videos, we will try to attract followers to work with EA
• motivate followers to expand our idea, in the form of motivation to use the ActivePresenter tool to expand this tutorial and a wider range of topics available to the public
• try to keep one video in the range of 2-10 minutes to ensure full concentration of the viewer

In terms of complexity, these videos will be about the basic functionalities presented in the form of educational videos, as we ourselves are beginners in this area.

Analysis

It will be using as an introduction to the EA tool, the creation of diagrams and the possibilities of EA communication.

What do we need for the implementation of the project:

1) EA tool

2) ActivePresenter tool

3) List of topics of individual tutorials

Characteristics of videos:

• video range will be shorter (range 2-10min)

• simple

• concise

• dealing with some problem with working in EA

• each video consists of an introductory page that describes what the video will be about and then continues the illustrative solution of the problem

• information windows (type click here, write it ..) are also uniform, thanks to the ActivePresenter tool.

Project solution procedure:

1. installation of ActivePresenter and Enterprise Architect tools

2. Familiarize yourself with ActivePresenter

3. Define video themes

4. independent work with EA within the topics, understanding of the problem and its solutions

5. recording individual videos

6. making videos available to public

List of videos

1) Tutorial 1 - How to setup connection to model and create shortcut

available also as video - Tutorial 1 - video

2) Tutorial 2 - How to setup universal workspace

available also as video - Tutorial 2 - video

3) Tutorial 3 - How to communicate in Enterprise Architect

4) Tutorial 4 - How to create new project and generate class diagram from source code

5) Tutorial 5 - How to see latest changes in model & how to see edit history for specific diagram (audit)

6) Tutorial 6 - Generate documentation (pdf)

7) Tutorial 7 - Where to find your actor & creating simple 'about me' diagram

8) Tutorial 8 - How to create simple BPMN diagram

Fotodocumentation

Evaluation

We evaluate this project very positively, as we also had the opportunity to immerse ourselves more in working with EA and try the ActivePresenter, which is very useful tool. We had the opportunity to learn how to work with an active presenter tool, and finally we have a little more motivation to work in EA tool.

Some videos are similar to yours, and we motivated ourselves to try using the active presenter on those similar videos. Later on, we did our tutorial.

We think it's quite useful. Since the situation in the world is as it is, we are glad that we did not go with a hardware project, because it would be quite difficult to harmonize and create something functional and useful. We firmly believe that after the end of the COVID19 pandemic, we will have the opportunity to try out the technologies in FABLAB.

Lessons learned

At the beginning, we had weak experience working at EA, but we can say that by creating these videos, we are more motivated and inspired to work with EA now.

We also focused on modeling, not only on setup and work within the subject, as we are also interested in creating diagrams, and for example, EA is often used in the real jobs, so we can use EA tool in the future.

For the first time we tried to create a bpmn diagram and we liked how EA supports all the notations / diagrams, etc. We had the opportunity to see that EA keeps all changes, so we can go back to the changes we made. We also liked how to easily generate a class diagram from the code! :-)

We will definitely use the experience we gained in the future, whether at work or school, for example we can work with EA during the working on our diploma thesis, where we will definitely need to model the software in the analysis or design of the solution. We had the opportunity to see and try modeling with EA tool, it's really not so bad to use EA and it will only bring to you benefits in the future.

Next steps

• extent the tutorial with more videos
• modify of current videos
• continue to inspire future SMVIT students to use these tools

Smart indoor glasshouse 

Team Members: Jakub Mikolaj, Róbert Oros. 

Motivation

We came up with this idea because little babies were born in our families (and we believe that they will be born in the future) and we also think that this project would be suitable for our grandparents, when their monitoring is necessary in some health cases.

Existing solutions

• camera + display
• camera + aplication
• first mobil - camera + second mobile - aplication

System functions

• Image
• Sounds
• Temperature
• Humidity

Solution description

The most important component of baby monitor is control unit which will by drive all other elements. The control unit should be sufficiently powerful and compatible but at the same time small enough. Raspberry Pi best meets these requirements. The primary goal is to create a program that will provide an interface in which the user will be able to view records from the camera and hear sound. He will also be able to talk to the child Gradually, we will expand these basic functions with smart options such as motion and temperature measuring. The user will be notified of unwanted or unusual activities.

Components

Proposal

A camera (that will capture the baby) can be positioned in two ways as needed. Directly on the cover of the device or mount on the bed.

Implementation

 

We need to cut holes for all inputs to Raspberry Pi (USB-C, USB, HDMI, micro HDMI, SD card...). At the bottom we created four pins for ensuring Raspberry Pi 4 against movement.

We split the case in half, to bottom and top part and also we created snap joints to hold the top and bottom parts together.

We realized that we also need holes for connecting the sensor (its cables) to GPIO pins header and also that I need to somehow connect the sensor to the raspberry pi. We did not want to put it inside the package so that the temperature was measured correctly.

Since raspberri pi can overheat, we have created the inscription "Baby Monitor", which can also be used to ventilate hot air. Lastly we created a camera holder (only for our camera type – Microsoft lifecam vx 1000 what we found at home).

 

Links

• Slides: Baby monitor
• EA model: odkaz
• Wikifactory: page

Arduino mini game console

Link to the EA project

Motivation

Our goal was to create smallest posible game console for gamers who want to play their favorite retro games whenever they want. In this project we created PCB design and scheme and and 3d model for Arduino micro based game console. At creating we aimed for small dimensions and good usability.

Design

Users

We aimed for users of all ages who want to play their favorite retro games.

Functional requirements

• ability to run retro games.
• rechargeability.

Non-unctional requirements

• Small dimension.
• Long battery life.

PCB scheme

PCB design

Description

The red lines show the wires connected to the printed circuit board (dps).
The battery is not part of the board and is connected by wires to the board.
The loudspeaker in the lower right corner is actually smaller than designed and therefore does not overlap with the button or the anchor hole.
The display is actually larger than designed and is located at the level of the board and is connected to it by wires.
The dimensions of the board are 38x43x2 mm.

Box design

Disassembled

Assembled

Components

Needed components

• 6 pcs button on the board
• 1 three-position switch
• 1 speaker for a flat board with a cross-section of 10 mm
• 1pc 0.96 “7 PIN SPI display
• 1pc USB C female
• 1pc battery 3-5V with dimensions up to 32x21x5mm
• 1pc Pro Micro Microcontroller
• 4pcs Screw with dimensions 2x15

Cost of components