S15: Patient Buddy System (PBS) - Revision history

Proj user7: /* Project Video */

2015-05-25T09:17:01Z

‎Project Video

2015-05-25T06:42:53Z

‎Acknowledgement

2015-05-25T06:42:17Z

‎References Used

2015-05-25T06:41:24Z

‎Conclusion

2015-05-25T06:38:52Z

‎Testing & Technical Challenges

2015-05-25T06:37:41Z

‎Testing & Technical Challenges

2015-05-25T06:36:08Z

‎Testing & Technical Challenges

2015-05-25T06:35:35Z

‎Implementation

2015-05-25T06:35:07Z

‎Software Design

2015-05-25T06:34:46Z

‎Hardware Interface

@@ Line 293: / Line 293: @@
 === Project Video ===
-Upload a video of your project and post the link here.
+https://www.youtube.com/watch?v=nBGfwDIN63E&feature=youtu.be&app=desktop
 === Project Source Code ===

@@ Line 300: / Line 300: @@
 == References ==
 === Acknowledgement ===
-Any acknowledgement that you may wish to provide can be included here.
+Thanks to Preet and all the ISAs for their help in the project!
 === References Used ===

@@ Line 303: / Line 303: @@
 === References Used ===
-List any references used in project.
+*http://www.computer.org/csdl/proceedings/icisa/2013/0602/00/06579332.pdf
 === Appendix ===
 You can list the references you used.

← Older revision		Revision as of 06:41, 25 May 2015
Line 272:		Line 272:

	== Conclusion ==		== Conclusion ==
−	Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

	*Things we learned:		*Things we learned:

@@ Line 251: / Line 251: @@
 *STEP COUNT:
 **Step count was tested on two subjects, Subject 1 and Subject 2, and in two different modes, fast and normal mode. On each test 100 steps were made. The table below show the results:
-*End to End Communication:
 [[File: S15_PBS_StepTestResults.jpg|400px|thumb|center|Results]]
 Include sub-sections that list out a problem and solution, such as:

@@ Line 246: / Line 246: @@
 == Testing & Technical Challenges ==
-Describe the challenges of your project.  What advise would you give yourself or someone else if your project can be started from scratch again?
 The main modules for the system were tested on different subjects to check for subject to subject consistency. These tests include:====

← Older revision		Revision as of 06:35, 25 May 2015
Line 208:		Line 208:
	=== Implementation ===		=== Implementation ===

−
−	This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

	=====Analyzing the Sensor Signals=====		=====Analyzing the Sensor Signals=====

@@ Line 154: / Line 154: @@
 === Software Design ===
-Show your software design.  For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level.  Do not show the details of the code.  For example, do not show exact code, but you may show psuedocode and fragments of code.  Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
 *Firmware of the SJ One Board is designed using FreeRTOS. C++ language is used to write the firmware. The drivers provided by the SJ One Board manufacturer are used for low level application. Each task is assigned to collect a measurement, process an algorithm on it and compute the result. To maintain the high accuracy sampling frequency of the pulse sensor, the RIT- repetitive timers, interrupt service routine and binary semaphore are used. To maintain the sampling frequency of the accelerometer and the temperature sensor vTaskDelay is used. Since the clock cycles spent on the tasks are low, using the vTaskDelay was accurate enough to get a reasonably constant sampling frequency of the accelerometer and the temperature sensors.

@@ Line 143: / Line 143: @@
 === Hardware Interface ===
-In this section, you can describe how your hardware communicates, such as which BUSes used.  You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high level workings rather than inner working of your project.
 *Pulse sensor:
 **Sends the raw photoplethysmograph signal to the on-board ADC and the signal is sampled every 2ms.