<>
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"
Submission of FYP Documents

Assalamualaikum and hi! 🌸

Week : 19
Date  : 1 Dec 2019 - 7 Dec 2019

Activities :


 1.  Submission of FYP documents

πŸ“†  5 December 2019
πŸ“¬  Level 1

πŸ“Œ  FYP coordinator has checked all the thesis report format and there is no problem with it. Alhamdulillah. FYP technical paper has been submitted successfully to the FYP coordinator.
πŸ“Œ  The thesis report has been signed by the supervisor before being submitted to the library.



 2.  Submission of FYP thesis report & FYP technical paper


πŸ“†  6 December 2019
πŸ“¬  Library, Level 7

πŸ“Œ  Alhamdulillah, FYP thesis report and CD have been submitted to the library successfully. Thank you to supervisor, Sir Shah Rizailli bin Mukhtar for all the guidance and blessing since FYP1 until FYP2.  





"It isn't the mountains ahead to climb that wear you out; it's the pebble in your shoe" 
Muhammad Ali

Checking Plagiarism

Assalamualaikum and hi! πŸ’¬

Week : 18
Date  : 24 Nov 2019 - 30 Nov 2019

Activities :

 1.  Submitting Draft FYP2 Final Report and Technical Paper

πŸ“Œ Draft of FYP2 final report has been submitted on 25 Nov 2019 for checking of plagiarism meanwhile the draft of technical paper has been submitted on 26 Nov 2019 for checking of the contents.
  

2.  Tenth Meeting with FYP2 Supervisor - Sir Shah Rizailli Mukhtar 

πŸ“†  29 November 2019

πŸ“¬  Office, Level 5

πŸ“Œ  Supervisor checked the updated progress on the new collection of data and asked to insert graphs for each testing to see the trends of the frequency's value for the oscilloscope during one cycle and positive width and the frequency's value for the serial monitor during one cycle. Supervisor also asked to insert the graph of the frequency value for the positive width of the waveform in the discussion in Chapter 4 of the FYP2 thesis report. The average, maximum and minimum value also need to be stated in the discussion of the thesis report.
πŸ“Œ  Checking of plagiarism has been done by supervisor using TurnItIn software for draft FYP2 thesis report and draft technical paper. For draft FYP2 thesis report, the percentage of plagiarism is 2% meanwhile for the draft technical paper, the percentage of plagiarism is 5%. Both of the thesis report and technical paper achieved the requirements needed by the FYP coordinator which is percentage of plagiarism must be less than 20%.
πŸ“Œ  The last submission date of FYP2 thesis report, technical paper and CD is on 6 December 2019.



"It does not matter how slowly you go, so long as you do not stop" 
Confucius

Week 17

Assalamualaikum and hi! πŸ’¬

Week : 17
Date  : 17 Nov 2019 - 23 Nov 2019

Activities :


 1.  Collection of Data - Waveform


πŸ“†  19 November 2019
πŸ“¬  SPS 215, Level 2


πŸ“Œ For this project, there are two alarms that must be collecting the data of the sound waveform which are the NIBP sound alarm and battery failure sound alarm. The data of the battery failure sound alarm is collected by conducting 16 tests. Each test is observed by reading the frequency of the waveform for the full cycle and the positive width of the cycle. The serial monitor data calculated by the coding is also recorded. All of the data taken is captured using camera, the value of the reading is written in the Microsoft Excel to calculate the average value of the waveform's frequency, average value of the serial monitor's frequency, the difference between waveform's frequency and serial monitor's frequency and the percentage error of the differences between both value.
  

2.  Updating FYP2 Thesis Report and Writing Technical Paper

πŸ“Œ  Due to all of the data has been collected, the thesis report of FYP2 and the technical paper can be continued to be finished. All the data in Chapter 4 : Results & Discussion has been changed with the new collection of data for both condition; battery failure and NIBP cuff failure. The results were recorded and tabulated using Microsoft Excel to observe the average value of the data and the percentage error between the oscilloscope's value and the serial monitor's value. After finished updating FYP2 thesis report from Chapter 1 until Chapter 5, the technical paper is written. The technical paper is the summarize of the full FYP2 thesis report.



"If I had eight hours to chop down a tree, I'd spend six hours sharpening my ax." 
Abraham Lincoln

0 love(s)
Week 16

Assalamualaikum and hi! ⚽

Week : 16
Date  : 10 Nov 2019 - 16 Nov 2019

Activities :


 1.  Collection of Data - Waveform


πŸ“†  14 November 2019
πŸ“¬  FYP Room, Level 2


πŸ“Œ For this project, there are two alarms that must be collecting the data of the sound waveform which are the NIBP sound alarm and battery failure sound alarm. The data of NIBP sound alarm is collected by conducting 20 tests. Each test is observed by reading the frequency of the waveform for the full cycle and the positive width of the cycle. The serial monitor data calculated by the coding is also recorded. All of the data taken is captured using camera, the value of the reading is written in the Microsoft Excel to calculate the average value of the waveform's frequency, average value of the serial monitor's frequency, the difference between waveform's frequency and serial monitor's frequency and the percentage error of the differences between both value.
  

2.  Soldering New Sound Sensor

πŸ“Œ  Due to the microphone of the sound sensor is broken, the microphone is soldered back to the sensor but it still cannot be used. Thus, a new FC-04 sound sensor module is bought and soldered to complete the hardware of the project. So, the collection of data can be continued done. 



"The future depends on what you do today." 
Mahatma Gandhi

0 love(s)
Week 15

Assalamualaikum and hi! ⚽

Week : 15
Date  : 3 Nov 2019 - 9 Nov 2019

Activities :


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

πŸ“†  7 November 2019
⌚  11.00 am - 12.00 pm
πŸ“¬  FYP Room, Level 2


πŸ“Œ Supervisor asked to see the progress of the project. The collection of data by matching the data from the serial monitor of Arduino IDE software with the data from the oscilloscope is shown to observe the accuracy of the results. 
πŸ“Œ  Supervisor asked to explain the coding for the project. Supervisor asked to search the meaning of 38462 in the formula frequency = 38462/period in the coding. 38462 is the timer rate for a 16-bit integer. Supervisor asked to recollect the waveform data due to the waveform is not in inverted form.  

2.  Updating FYP2 Thesis Report

πŸ“Œ  FYP2 thesis report is actually the continuing of the FYP1 proposal report which consists of five chapters; Chapter 1 (Introduction), Chapter 2 (Literature Review), Chapter 3 (Methodology), Chapter 4 (Results & Discussion) and Chapter 5 (Conclusions). All five chapters must be updated and completed according to the project that has been done. This thesis also consists of a declaration of project, approval page, abstract, table of content, list of figures, list of tables, list of abbreviations, list of references and appendices.
πŸ“Œ Chapter 3 is still in progress of updating. Chapter 3 consists of the methodology of work. Flow chart, block diagram and basic circuit of the project have been inserted in this chapter with a full explanation. The explanation for the main components used also been written in this chapter. In this chapter, the analysis of the survey is put to show the significance of this project.
πŸ“Œ Every sentence needs to be created and written without plagiarism from any other publication. Each of the sentences that been taken from other journals or publication must be cited by using APA 6th edition style. Plagiarism for FYP2 thesis report must not exceed 20%.



"Just one small positive thought in the morning can change your whole day." 
Dalai Lama

0 love(s)
Week 14

Assalamualaikum and hi! ⚽

Week : 14
Date  : 27 Oct 2019 - 2 Nov 2019

Activities :


 1.  Final Year Project 2 Workshop

πŸ“†  1 November 2019
⌚  3.00 pm - 5.00 pm
πŸ“¬  TTL 1


πŸ“Œ Speaker : Dr. Mohd Noor Nordin 
πŸ“Œ Workshop on Art of Writing A Technical Paper from FYP report.
πŸ“Œ Aim of technical paper : As a contribution to society especially engineering society.
πŸ“Œ Submission on : 29 November 2019
πŸ“Œ Structure format of the technical paper : 


IMRaD
(Introduction, Method/Material, Results and Discussion)

πŸ“Œ Technical paper must be done in past tense, short and precise.
πŸ“Œ Technical paper consists of the title of the project, abstract, the introduction of the project, the material used, the methodology used, the results that been obtained and the discussion on the results. Usually, the material and methodology are written in the same heading meanwhile for results and discussion cannot be written in the same heading in the technical paper.

πŸ“Œ Abstract : This section needs to state the principle, objectives and scope of investigation, describe the methods used, summarize the results and state the principal conclusions. It is written only in 1 paragraph, in past tense and not more than 250 words.
πŸ“ŒIntroduction : This section includes the study of the project, the problem statements, the objectives, the reason why it is significant to do the project and the approach take on the study. It is advisable to do in 3 paragraphs; first paragraph is about the general part of study, the second paragraph is to state other research information and in the third paragraph is to tell what have been done in the project. 50% of references are cited here. Must be written in present tense to refer work that been publish and past tense for my own work and not more than 450 words.
πŸ“Œ Materials & Methodology : In this section, need to tell people/reader on how this project is carried out. The example of the subheading are materials, experimental procedure, analysis, calculation or computational procedure. 10% of references are cited here. Do not put the results of the project in this section.
πŸ“Œ Results : It is easier to put the results in table or graph form and figures. 10% of references are cited here. It must be written in past tense.
πŸ“Œ Discussion : This section must discuss the results obtained and used references as proof. In the paragraph, it is needed to state the major finding of the project and also summarise all the findings. The discussion can be referred to the table and figure of the results. 20% of references are cited here due to comparing with other studies.
πŸ“Œ Conclusion : It must be written in the simplest way and tell how significant the project is. (As example, I think this study shows how important ......)
πŸ“Œ References in IEEE format. Maximum of 20 references.


2.  Updating FYP2 Thesis Report

πŸ“Œ  FYP2 thesis report is actually the continuing of the FYP1 proposal report which consists of five chapters; Chapter 1 (Introduction), Chapter 2 (Literature Review), Chapter 3 (Methodology), Chapter 4 (Results & Discussion) and Chapter 5 (Conclusions). All five chapters must be updated and completed according to the project that has been done. This thesis also consists of a declaration of project, approval page, abstract, table of content, list of figures, list of tables, list of abbreviations, list of references and appendices.
πŸ“Œ Chapters 1 and 2 have been updated and completed this week. Chapter 1 consists of the background of the project, objectives, problem statements, scope and limitation of work and the significance of the project. Chapter 2 consists of the literature review. Some of the journals that closely related to the project are reviewed in this chapter and an overall view of the comparison of the journals also has been done in this chapter. 
πŸ“Œ Chapter 3 is still in progress of updating. Chapter 3 consists of the methodology of work. Flow chart, block diagram and basic circuit of the project have been inserted in this chapter with a full explanation. The explanation for the main components used also been written in this chapter. In this chapter, the analysis of the survey is put to show the significance of this project.
πŸ“Œ Every sentence needs to be created and written without plagiarism from any other publication. Each of the sentences that been taken from other journals or publication must be cited by using APA 6th edition style. Plagiarism for FYP2 thesis report must not exceed 20%.



"Failure will never overtake me if my determination to succeed is strong enough." 
Og Mandino

0 love(s)
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

0 love(s)
Week 12

Assalamualaikum and hi! β˜•

Week : 12
Date  : 13 Oct 2019 - 19 Oct 2019

Activities :

 1.  Suggestion on improvements


πŸ“Œ Instead of using two 9V batteries for supply, the prototype can use one 9V battery supply with the implementation of a voltage divider circuit.
πŸ“Œ  Instead of use 9V batteries which are bigger in size, it is advisable to use 5V coin battery to save space.
πŸ“Œ  Improvement in the collection of data can be done by collecting more data to make it more accurate.
πŸ“Œ  The collection of data is also advisable to use various technique such as using LabView software instead of only using the oscilloscope. 

πŸ“Œ  The whole connection of the Arduino NANO board, NodeMCU board, signal conditioning circuit and sound sensor can be further improvised to make it smaller in size by desoldering all the unused pins of Arduino NANO board and NodeMCU board and stack up all together. 


 2.  Technical Paper - draft

πŸ“Œ Technical paper is a document that describes the process, progress, state of technical problem or in a simple wording is a summary of the full report of the prototype. It is advisable to be written for 4 to 5 pages. Technical paper contains abstract, introduction, methodology, result, discussion, conclusion and references. It might also include recommendations and conclusions of the project.



"Even with broken wings, I'll teach myself to fly again." 
Yasmin Ali

0 love(s)
Week 11

Assalamualaikum and hi! 🌸

Week : 11
Date  : 6 Oct 2019 - 12 Oct 2019

Activities :

 1.  Designing FYP2 banner and casing for the prototype.

πŸ“† 6 October 2019


πŸ“ŒFor the FYP2 Exhibition day, every FYP2 student must present by using a banner and demonstrate the prototype. For the banner, I designed it using Adobe Photoshop CS4 software because it is much easier to adjust the size of the banner in the software. The banner is printed at Achik Printing Taman Melawati Sdn Bhd.


The layout of the banner with size (2 x 6 ft).
*click to expand image*

FYP2 banner.
*click to expand image*

πŸ“Œ For the casing of the prototype, I designed it 2 x 5 x 8 cm using Solidwork 3D CAD Design software because this software is a solid modeling computer-aided engineering design. After the design is finished, the design can be set up in the 3D printer to print it. 3D printing is finished around 3 hours for this casing at the Research Lab Level 4 UniKL BMI.


The design of the casing for the prototype.
*click to expand image*

The 3D print casing for the prototype.
*click to expand image*

 2.  Soldering the whole prototype

πŸ“†  7 October 2019


πŸ“Œ The whole circuit of the prototype is soldered together with the Arduino NANO board and the NodeMCU board to save the space for the build of the prototype.


The whole circuit of the prototype combined together.
*click to expand image*

The microphone of the sound sensor is at the center of the front side's prototype.
*click to expand image*

Notification on Telegram for NIBP cuff failure.
*click to expand image*

πŸ“Œ Basically, this project is successful by giving supply from two 9V batteries for Arduino NANO board and NodeMCU board respectively. This prototype may become more effective if there is a presence of switch to on and off the prototype. 

πŸ“Œ The video of the layout can be seen here >> Video of prototype layout.

3.  Testing with the presence of a switch

πŸ“†  8 October 2019

πŸ“Œ After being considered to put a switch to make it more effective, I have soldered the batteries with the switch but due to the batteries are new battery, so the current flow is too high and it makes the NodeMCU became faulty and cannot be used. I tried uploading the coding into the NodeMCU but the code cannot be uploaded into it. I try to connect the circuit with my friend's NodeMCU board and the data can be transmitted successfully. Thus, a new NodeMCU board is bought from the Autobotic Sdn Bhd shop. 


The switch is connected based on this sketching.
*click to expand image*

The switch is connected based on the sketching.
*click to expand image*

πŸ“Œ After the NodeMCU is bought, the whole circuit is constructed back all together and the prototype works but without the switch. A video is taken as proof for the FYP2 exhibition day. Supervisor said to connect a switch must put a voltage regulator so that the current flow is low.

πŸ“Œ The video of the final output can be seen here >> FYP2 prototype


πŸ“Œ After the video is taken, I tried to solder the new NodeMCU together with the circuit but it failed. The data does not transmit to the Telegram. The serial monitor also does not print any output. After several troubleshoot, the pin of Tx Rx of the Arduino NANO board cannot be used. That is why the NodeMCU board does not receive any data from Arduino NANO board. 

 4.  Troubleshoot prototype.

πŸ“†  9 October 2019
⌚  7.45 am to 8.30 am
πŸ“¬  Research Lab, Level 4, UniKL BMI

πŸ“Œ  Due to the Tx Rx pin of the Arduino NANO board are faulty, so it is replaced by a new Arduino NANO board and been soldered again the whole circuit and put it in the casing. The whole prototype can function well and is prepared to be demonstrated on FYP2 Exhibition Day at 9.00 am on the same day. 

 5.  FYP2 Exhibition Day


πŸ“†  9 October 2019
⌚  9.00 am to 2.00 pm
πŸ“¬  Gemilang Hall, UniKL BMI

πŸ“Œ For FYP2 Exhibition Day, there are two parts of presentation which are demonstration of the project and the presentation of the technical part.
πŸ“Œ There are two assessors; Madam Siti Afifah binti Mohshim (UniKL BMI's lecturer) and Mr. Syukran Che Pa (Sales & Services Engineer of EASMED Sdn Bhd).
πŸ“Œ The recommendation from Mr. Syukran Che Pa are the device can be smaller by desolder all the unused pin on Arduino NANO board and the NodeMCU board and by put voltage divider circuit so that the supply only needs to use one battery instead of two. But he said, if this prototype is used for imaging equipment, it is breaking the ACT 737 law because it involves the Wi-Fi networking. 



Supervisor, FYP2 coordinator and supervisees.

*click to expand image*

6.  Seventh meeting with FYP2 supervisor - Sir Shah Rizailli Mukhtar

πŸ“†  9 October 2019
⌚  3.45 pm
πŸ“¬  SPS 209

πŸ“Œ After presented on FYP2 exhibition day, supervisor asked to see him. Supervisor encourages to make improvement on the prototype and collect more data.



Supervisor and supervisee.
*click to expand image*


"If you're not failing every now and again, it's a sign you're not doing anything very innovative." 
Woody Allen

0 love(s)
Week 10

Assalamualaikum and hi! 🌸

Week : 10
Date  : 29 Sept 2019 - 5 Oct 2019

Activities :

 1.  Coding - TelegramBot

πŸ“† 30 September 2019


πŸ“Œ For this project, the final output must be sent to the end-users social media specifically to the Telegram application. Telegram is cloud-based storage, so end-users do not need to back up or restore the data receives and send. I am having a problem with the coding which is the Arduino WeMos board cannot transmit the data received from Arduino UNO board to the Telegram via Wi-Fi connection. Arduino WeMos only succeed to connect to the Wi-Fi network but not transmitting any data to the Telegram. 
πŸ“Œ I only managed to create a TelegramBot for the project which is named alarmpmBot. This bot is created using BotFather in the Telegram application. BotFather gives the token of the alarmpmBot to access the HTTP API. By declaring this token in the coding, Arduino WeMos can transmit the data directly to the Telegram.
πŸ“Œ Unfortunately, Telegram still cannot be connected to the Arduino WeMos board and this problem needs to be troubleshoot. 


alarmpmBot is created using BotFather.
*click to expand image*


 2.  Improvement Advice by Supervisor.

πŸ“† 1 October 2019


πŸ“Œ Due to the signal conditioning circuit is a bit bigger, supervisor asked to desolder it back and construct it into a much compact circuit and if possible the same size of 50 cent. Even though the circuit is the same size as the Arduino UNO board and Arduino WeMos board, the advice by supervisor is being considered. 


Size of the signal conditioning circuit.
*click to expand image*


3.  Desoldering signal conditioning circuit

πŸ“†  2 October 2019
⌚  2.00 pm to 3.00 pm
πŸ“¬  Research Lab, Level 4, UniKL BMI


πŸ“Œ After being considered with the advice by supervisor, the signal conditioning circuit is desoldered and soldered back with a new circuit which is more smaller and compact. Even though it is a little bit bigger than 50 cents, but it is much compact and better than the previous one.
πŸ“Œ A technician who in charge of the research lab in Level 4 suggested to use Arduino NANO board instead of Arduino UNO board and NodeMCU board instead of Arduino WeMos board. The suggestion is made because the project if possible is develop as small as possible. The suggestion is being considered.

Size of the new signal conditioning circuit.
*click to expand image*


 5.  Final Year Project 2 Workshop

πŸ“†  2 October 2019
⌚  3.00 pm to 5.00 pm
πŸ“¬  TTL 2

πŸ“Œ Speaker : Dr Imran Mohd Sofi
πŸ“Œ Workshop on FYP2 Exhibition Day (Tips & Tricks) and submission of progress report, final report and technical paper.
πŸ“Œ Submission date for the progress report, final report and technical paper : 29 November 2019

 6.  Buy components for the development of hardware.

πŸ“†  3 October 2019
πŸ“¬  Autobotic Sdn Bhd, 4th floor, Jalan Semarak Api 3

πŸ“Œ After being considered with the suggestion by the technician and further reading of the component datasheet, the Arduino NANO board and NodeMcu board were bought from the Autobotic Sdn Bhd. 
πŸ“Œ  Arduino NANO board is a small, complete, breadboard-friendly board compare to the Arduino UNO board which is much bigger in size. Even though the Arduino UNO board can use to do lots of things due to its input and output pin is more compared to the Arduino NANO board but because the sound sensor only required one analog pin, it is better to use Arduino NANO board to save space. Arduino NANO board can also be programmed in it and the hardware will be simpler easier to bring everywhere. This is convenient for this project as the prototype needs to be as tiny as possible and the Arduino NANO board is the cheapest Arduino board option available making it cost-effective for this project.
πŸ“Œ  NodeMCU board is the best ESP platform available if look from the hardware perspective. NodeMCU can be programmed the same as the Arduino board and it can stand alone. It is used as Wi-Fi module in this project. Even though Arduino WeMos board has the same function as NodeMCU board but due to it has bigger dimension, NodeMCU is much more convenient to be used.

 
Arduino NANO board and NodeMCU board connection
*click to expand image*

7.  Coding - TelegramBot

πŸ“†  5 October 2019

πŸ“Œ This coding is actually the continuing of the previous TelegramBot coding. The previous problem is because the Telegram still cannot be connected to the Arduino WeMos board. 
πŸ“Œ After being troubleshooting for several days, the problem with the coding is because the library of Arduino JSON that been installed is version 6.12.0. This version is the latest of Arduino JSON thus, it is still not stable and not compatible with the Telegram. That is why Arduino WeMos cannot connect to the Telegram via the Wi-Fi network. After downgraded the version Arduino JSON from 6.12.0 to 5.13.4, Arduino WeMos successfully transmit the data from Arduino UNO board to the Telegram via Wi-Fi connection.

Arduino JSON version 5.13.4
*click to expand image*

Telegram alarmpmBot notification on battery failure and NIBP cuff failure
*click to expand image*

πŸ“Œ Due to the hardware is advised to be as small as possible, the coding for interpreting data is uploaded in the Arduino NANO board as a replacement for the Arduino UNO board meanwhile the coding for TelegramBot is uploaded into the NodeMCU as a replacement for the Arduino WeMos board. At first, I want to use only NodeMCU to function as the interpreter data and the receiver and transmitter of the output because NodeMCU can stand alone with the Arduino program but because of NodeMCU cannot read interrupt function, the prototype must use Arduino NANO board and NodeMCU together to make it function well.


"Many of life's failures are people who did not realize how close they were to success 
when the gave up." 
Thomas Edison

0 love(s)
FINAL YEAR PROJECT 2
Development of a Characteristics Error False Alarm Detection