Study Guide

Objectives (course unit)

After completing the course, student is able to create data transfer from sensors to cloud and vice versa. Student is able to implement an intelligent IoT system combining hardware and software together. Student is aware of IoT architecture from beging to end.

Content (course unit)

Introduction to electronics, A/D- conversion, sensor technologies, broker functionality, IoT- protocols, basics of C and C++ microcontroller programming with IoT interfaces

Location and time

Lectures and laboratory work every week (according to the schedule).

Exam schedules

No exam, the course grade is based on weekly exercises and homework tasks.

Assessment methods and criteria

Course will be evaluated based on weekly exercises and homework tasks. Exercise points are defined in Moodle.

Below table gives equation to exercise points to course grade.
Points = grade
0-35 = 0
36-48 = 1
49-61 = 2
62-74 = 3
75-87 = 4
88-100 = 5

Assessment scale

0-5

Teaching methods

Lectures, exercises and project work in teams to build team’s own embedded weather system

Learning materials

Links and e-material in Moodle.

Optional reading:
https://www.newbiehack.com/MicrocontrollerTutorial.aspx
https://www.renesas.com/en-us/support/technical-resources/engineer-school/mcu-01-basic-structure-operation.html

Student workload

Classroom, lab, project teamwork, individual work

Total size 270h
Contact teaching 135h
students independent own work 120 -180h

Content scheduling

C/ C++ microcontroller programming.
CPU peripherals (binary IO, timers, int service, etc,
Connecting to real life IO (LCD, keyboard, sensors).
Arduino exercises (Processor module + IO)
MQTT
Embedded linux env. (Raspberry or VM)

Completion alternatives

N/A

Practical training and working life cooperation

N/A

International connections

N/A

Assessment criteria - fail (0) (Not in use, Look at the Assessment criteria above)

Weekly exercises don’t full fill minimum requirements (more details in Moodle).
Student has not shown his/her capability for weekly subject.

Assessment criteria - satisfactory (1-2) (Not in use, Look at the Assessment criteria above)

Student can use SDK and other design environments.
Weekly exercises don't contain major failings and are demonstrated on agreed time.
Student is capable to teamworking.

Assessment criteria - good (3-4) (Not in use, Look at the Assessment criteria above)

Student can apply the contest of course and usage of SDK systems. Exercises are done according the given instructions and demonstrated according course time schedule.
Student is capable to use SDK systems and other development systems.
Student is a good team worker.

Assessment criteria - excellent (5) (Not in use, Look at the Assessment criteria above)

Student is self-governing and can apply wide area of course content.
Student has shown deep understanding managing of course content.
Reports are according instructions and returned at agreed time.
Student can utilize SDK and other design tools with efficient way.
Student can debug and fix HW/SW errors. Student is proactive team worker.