<>
follow




DISCLAIMER POSTS HIT IT
Nur Farhana binti Shahrul Azhar
51215116027
Bachelor of Engineering Technology in Medical Electronics

This blog is created for updating progress of Final Year Project 2 S2 2019 under supervision of Mr Shah Rizailli Mukhtar

Final Year Project 2 :
Development of a Characteristics Error False Alarm Detection

P/S : For newest post, click Home icon on the lower part, right side of the blog.

"Even with broken wings,
I'll teach myself to fly again"
Week 13

Assalamualaikum and hi! 🌸

Week : 13
Date  : 20 Oct 2019 - 26 Oct 2019

Activities :


 1.  Eighth meeting with FYP2 Supervisor - Sir Shah Rizailli Mukhtar

πŸ“†  23 October 2019
⌚  10.00 am - 12.15 pm
πŸ“¬  SPS 209, Level 2


πŸ“Œ Supervisor asked to see the progress of the project. The prototype is shown to the supervisor and how it works for battery failure and NIBP cuff failure.
πŸ“Œ During the testing of the prototype, supervisor did some hard loud sound which indicates the construction sound in real life to see if the prototype able to avoid capturing those noise or not. Even though the prototype is good enough because it capable to avoid the noises that supervisor has created, yet it still needs to improvise in the coding section due to during the battery failure, sometimes the output in Telegram is NIBP cuff failure instead of battery failure. The coding must improvise by putting the range of frequency more specific.
πŸ“Œ Supervisor also asked to improve in the collection of data by matching the data from the serial monitor of Arduino IDE software with the data from the oscilloscope to observe the accuracy of the results. 


 2.  Literature review

πŸ“Œ Another problem with the coding of the prototype is because the coding does not have any delay. Thus, when the prototype captured the alarm, the output will be sent to the Telegram repetitively. 1ms 1 notification and this situation kind of irritating because the notification will still notify in the smartphone even though the alarm has been turned off. It is advisable to get at least 1 notification for 5 seconds of the alarm.    
πŸ“Œ This situation maybe can be avoided by using the delay function in the coding but the problem with delay function is it will delay the program instead of only give 1 notification for 5 seconds because delay function only pauses the program flow.   
πŸ“Œ Instead of using delay function, millis() function is preferable to configure this problem because millis() function returns the amount of milliseconds that have passed since the program start. It also would not prevent running the coding while waiting the data to be processed. It is better to use this function for sampling instead of using the delay function.  

πŸ“Œ More information can be read here >> Using millis() instead of delay()



"Today's accomplishments were yesterday's impossibilities." 
Robert H. Schuller

Post a Comment



<< home >>

FINAL YEAR PROJECT 2
Development of a Characteristics Error False Alarm Detection