Final Report Project Title Design and Development of

  • Slides: 21
Download presentation
Final Report Project Title: Design and Development of a Continuous Monitoring System based on

Final Report Project Title: Design and Development of a Continuous Monitoring System based on Wearable Devices Yijie Xiao Page 1

Project Objective Design and Develop a Medical Monitoring System that can: Connect and control

Project Objective Design and Develop a Medical Monitoring System that can: Connect and control various types of sensor Store data and user information Read and present data from sensor Page 2

Project description 1) Hardware integration 5 types of Wearable sensors 2) Software Design System

Project description 1) Hardware integration 5 types of Wearable sensors 2) Software Design System Architecture Database 3) System Implementation Desktop Application Android Application Pebble Smart Watch Application Keywords: Wearable sensors, Software architectures, Bluetooth, Database , Android Page 3

Video Demonstration Page 4

Video Demonstration Page 4

I. Hardware Integration Hardware Selection e-Health Sensor Platform V 2. 0 for Arduino and

I. Hardware Integration Hardware Selection e-Health Sensor Platform V 2. 0 for Arduino and Raspberry Pi § § § Based on Arduino: Easy to develop Various Types of Sensors Completed Library and Hardware Connection Page 5

I. Hardware Integration Sensor Description Sensor Figure Sensor Name galvanic skin response (GSR) Pulse

I. Hardware Integration Sensor Description Sensor Figure Sensor Name galvanic skin response (GSR) Pulse and Oxygen in Blood (SPO 2) Description Skin conductance, also known as galvanic skin response (GSR) is a method of measuring the electrical conductance of the skin, which varies with its moisture level. Pulse oximetry a noninvasive method of indicating the arterial oxygen saturation of functional hemoglobin. Body Position The Patient Position Sensor (Accelerometer) monitors five different patient positions (standing/sitting, supine, prone, left and right. ) Glucometer is a medical device for determining the approximate concentration of glucose in the blood. The meter displays the level in mg/dl or mmol/l. Body temperature depends upon the place in the body at which the measurement is made, and the time of day and level of activity of the person. Different parts of the body have different temperatures Page 6

I. Hardware Integration Way of Communication Request Char Sensor used to be Functions to

I. Hardware Integration Way of Communication Request Char Sensor used to be Functions to be called ‘A’ GSR ‘B’ Body temperature ‘C’ Body Position ‘D’ SPO 2 ‘E’ Glucometer float conductance = e. Health. get. Skin. Conductance(); float resistance = e. Health. get. Skin. Resistance(); float conductance. Vol = e. Health. get. Skin. Conductance. Voltage(); float temperature = e. Health. get. Temperature(); uint 8_t position = e. Health. get. Body. Position(); e. Health. print. Position(position); e. Health. get. BPM() e. Health. get. Oxygen. Saturation() uint 8_t number. Of. Data = e. Health. get. Glucometer. Length(); Page 7

I. Hardware Integration Result Page 8

I. Hardware Integration Result Page 8

II. Software Design System Architecture Focus part Page 9

II. Software Design System Architecture Focus part Page 9

II. Software Design Database Design Purpose: Storage of following information: • User Information •

II. Software Design Database Design Purpose: Storage of following information: • User Information • Sensor Status • Read Value and Time Page 10

III. System Implementation Desktop Application Serial Connection 1) serial. Port = (Serial. Port) port.

III. System Implementation Desktop Application Serial Connection 1) serial. Port = (Serial. Port) port. Id. open("Ardunio", 2000); 2) Ardunio. Control reader = new Ardunio. Control(); 3) public void serial. Event(Serial. Port. Event event) Connection and Query of Database Class. for. Name("sun. jdbc. odbc. Jdbc. Odbc. Driver"); Connection con=Driver. Manager. get. Connection(url, user, password); Statement stmt=con. create. Statement(); Result. Set result=stmt. execute. Query(ls); 1) Java GUI Page 11

III. System Implementation Desktop Application 1)Main Page 12

III. System Implementation Desktop Application 1)Main Page 12

III. System Implementation Desktop Application 2)Read and Query Data Page 13

III. System Implementation Desktop Application 2)Read and Query Data Page 13

III. System Implementation Android Application 1)Main Page 2)Searching Device 3)Read Data Page 14

III. System Implementation Android Application 1)Main Page 2)Searching Device 3)Read Data Page 14

III. System Implementation Pebble Smart Watch Android Arduino Pebble Original Plan: Two Slave devices

III. System Implementation Pebble Smart Watch Android Arduino Pebble Original Plan: Two Slave devices cannot be paired Implementation: Using Android as a bridge for transmission Page 15

III. System Implementation Pebble Smart Watch Message format Example: //content of message: “connected” const

III. System Implementation Pebble Smart Watch Message format Example: //content of message: “connected” const uint 8_t connected. Msg[30]={0 x 00, 0 x 1 a, 0 x 0 b, 0 x. B 8, 0 x 01, 0 x 00, 0 x 09, 0 x 43, 0 x 6 f, 0 x 6 e, 0 x 6 e , 0 x 65, 0 x 63, 0 x 74, 0 x 65, 0 x 64 , 0 x 0 d , 0 x. FF, 0 x. FF , 0 x. FF, 0 x. FF}; Yellow part: These 6 numbers are fixed for every message. Green part: This hex number is the number of the char included in this message. Blue part: The sequence of hex number is obtained by transform the content of the message into hex format. Red part: The rest of the message packet is filled with “ 0 x. FF”, in order to reach 30 hex numbers in each message packet. Page 16

III. System Implementation Pebble Smart watch 1)Function in Android 2) Display on Pebble Page

III. System Implementation Pebble Smart watch 1)Function in Android 2) Display on Pebble Page 17

Conclusion 1) Arduino: Excellent choice for conducting this project. § Completed Library and easy

Conclusion 1) Arduino: Excellent choice for conducting this project. § Completed Library and easy language § Plug and play Feature Great potential for development of medical system § Low cost § Good extensibility Page 18

Conclusion 2) Bluetooth: Meet the system requirement § Communication range § Low cost Convenient

Conclusion 2) Bluetooth: Meet the system requirement § Communication range § Low cost Convenient for future development § compatibility Page 19

3) Java: Conclusion not an appropriate language for serial communication § Input stream reading:

3) Java: Conclusion not an appropriate language for serial communication § Input stream reading: Number of read byte: 5 Number of read byte: 25 Number of read byte: 30 Number of read byte: 13 Number of read byte: 17 Number of read byte: 22 Number of read byte: 8 § Byte hex Better to combine with other language such as C. § Good in development of interface and multimedia Page 20

END Gracias! Page 21

END Gracias! Page 21