Week 1
Our main
focus was on doing research, collecting statistics and drawing out
a blue print for the project. We prepared and submitted an official project proposal to the course instructor as well as the Technical Advisor for the
project. We felt slightly more confident about our project at this point with respect to the usage.
Week 1
Through our research, we learned that we would require different RFID tags so that we could test them. Hence, we requested our adviser to order an assortment of RFID tags. The link to the product we ordered can be found here.
Our plan was to understand existing ways through which hospitals ensure the security of the baby. Through research, we learned that the current system uses active tags. Active tags are bulkier and more expensive than passive tags. Active tags have a higher range than passive tags but once their batteries die, they are useless - hence, posing a threat to the security. Passive tags would solve the problem of having to replace batteries but have a shorter range. Weighing the pros and cons, we decided to use passive tags, the Impinj XArray RFID reader and multiple antenna. This would let us use passive tags, antennas would help us reduce tags and the XArray would give us data in terms of x and y locations which can be directly used for our indoor positioning system.
The lab already had the XArray and antennae and hence, we did not need to order it. However, the XArray system is not setup yet. Using RFID technology for indoor positioning is a relatively new technology. The XArray is expected to be set up by the time we require the data.
Week 2
This week
was about getting acquainted with the Android Studio in order to get started
with the app development and programming on Java. We followed the below given tutorials to learn how to build an app. Mannika and Mridul are familiar with basic Java and MATLAB. Jui is only familiar with basic MATLAB. We hope to come out of this project learning a new language and hopefully learning on how to build an app.
Tutorial
link: Android Studio App development
We soon realized that it was quite hard to make an app. Upon conversing with some of our peers in Computer Science, it hit us that maybe ten weeks is a really short time to build an app.
We then decided to have a meeting with the
programmers in the Drexel App Lab at 3401 Science Center to get more
information and a head start towards the preparation of the wire-frame of the
app. They confirmed with us that ten weeks was indeed a short time for us to build the kind of app we wanted to. By the end of the week, through discussions and brainstorming sessions,
the basic layout including the wire-frame and the general features of the app
had been finalized. However, we were still worried about the time constraint.
Week 3
In week 3, we had a meeting with Dr. Kurzweg, our adviser and updated him about our situation regarding the time constraint. He agreed with us that this app would probably take a longer time. We decided to build a prototype of the program on MATLAB. All three of us are familiar with MATLAB and building a program is less time consuming than the app. It was also decided that we would first start working on a sample data file because the XArray was not working yet.
We received the data in the form of a .json file from the RFID readers. The data we received was not from the XArray but we are using this data to learn how to parse .json files and to plot it. Later, we will receive the relevant data which we can pass through the program.
We started working on the code. We started learning how to make a Graphic User Interface (GUI) on MATLAB. We built a code to parse the .json files. Due to midterms, our work slowed down and hence, that's all we were able to do.
Week 4
A plot was
created on MATLAB which complements the sample data received through the .json
file. The plotted point changes its position as a new sample entry data is
updated.
We visited the Hahnemann Hospital for a
scheduled meeting with Dr. Owen Montgomery. Dr. Kurzweg works closely with Dr. Montgomery to define what the needs of the hospital are and to find solutions that are commercially viable. Dr. Owen claimed that our project might not be the best idea. This is because, the baby really doesn't move around in the hospital. After birth, the baby is cleaned, tested and immediately given to the mother. Very rarely does the baby leave the mother's side. Therefore, it was determined that making a baby tracking system would be worthless as compared to the cost because the baby really doesn't move inside the hospital.
Some other things we learned at the hospital were:
1. The current system uses an active tag system. The tags are bulky and if the batteries die, the tag is inactive. A reader is placed near the exit of the floor and if a tag is detected by the reader, the hospital is immediately put on a shutdown and an alarm goes off. This is because no tagged baby is supposed to be near the exit. Also, if someone tries to cut the tag, the circuit breaks and an alarm goes off.
2. Some ways that this system could fail:
i) The batteries die and the tag becomes inactive
ii) The baby is stolen from the windows; this is especially possible in lower floors. This information came from researching baby theft cases.
iii) A fire alarm is set off then the fire alarm shuts off the Anti-theft system and a baby could be stolen. This is the way that a child was stolen from Hahnemann Hospital.
iv) A well planned scheme of stealing the baby is performed where the person has a fake id which gives them access to the floor, they know how to deactivate the tag and hence, would be successful in stealing the baby. This is highly unlikely because deactivating the tag is something only nurses and the tag makers are familiar with.
3. We learnt that the biggest need of the hospital in this certain area would be to make the tags less bulky, battery-less and cheaper - all of which could be achieved by using passive tags.
The meeting proved
to be really fruitful in terms of getting the right direction and the required
first hand information. However, it also threw us off from our original project of making a baby tracking device. Dr. Montgomery did mention that RFID systems were being used in the Psych ward.
Week 5
With the information gained from Dr. Montgomery, we met with our adviser and it was decided that we could continue building the tracking system except that the application of the system would be towards Psych ward patients, geriatric patients, for tracking tools and devices within the hospital and various other platforms where indoor positioning is necessary.
We also decided to work on making the tag tamper proof but this idea is put on hold till the time the program comes through.
To make the program, we want to include real time data reception from the RFID reader. We learned that MATLAB does not have a facility to send and receive real time data. Hence, we have to switch languages again and now we're building the program on Python.
The disadvantage that comes with Python is that none of this are familiar with this language. Hence, we're doing this from scratch; learning the language and then building the program.
The XArray has still not been setup in the lab. It's taking longer than expected because this is a new technology and it takes time to configure it and install it. We're still working on the sample set data and will build our program based on that. In the future, when the XArray is set up, we shall calibrate it with our program.
Week 6
Week 6 was the toughest week for our project. The XArray was not set up yet and it probably wouldn't be before Week 10 so we had to scrap out that plan. We taught ourselves Python by watching YouTube videos and started building the GUI for our program.
After talking to our adviser, we came up with a plan to use RSSI values to determine distance. RSSI gives us the signal strength and that could help us determine the distance. However, RSSI is not a reliable source because the signal strength varies with the environment - in the presence of other objects, the wave bounce off of the surfaces and the signal varies.
Calibration of RSSI versus distance
Week 7
During Week 7, our group continued to work on learning Python and making the GUI for the program. We made the buttons and windows, added alarm sounds. Since all of the data this system will collect is confidential, we added a username and password feature. If the two did not match, the person would receive an error message.
The user enters their assigned username and password
If credentials are incorrect, an error message is sent
Week 8
During Week 8, we started working on finding a relationship between RSSI and distance. We ordered an assortment of tags and then found out the RSSI value for each tag kept at a distance of 1 foot from the reader. We tried to keep all environmental conditions as constant as possible. After selecting the best tag i.e. the one with the highest RSSI value, we performed calibrations. We kept the tag at known distances, noted down the RSSI values for those distances and tried to build a relation.
While performing the calibration, we got the same RSSI values for multiple distances and this was due to the wave reflection effect. After consulting with our adviser, we figured out some ways we can improve the situation. We removed all surfaces that were in the way between the reader and the tag, we kept the tag and the reader at the same height and we only kept the tag directly away from the reader instead of diagonally or in some other direction.
After doing the above, we were able to find a relationship between RSSI and distance using a regression tool and the equation was to the power of 6.
At the end of Week 8, the program had all windows and buttons, it was able to receive and print real time data from the server and it was kind of able to plot the data as well. Plotting the data is the challenge currently as we want to plot it in real time. Learning Python and simultaneously building a GUI application in it has posed a lot of challenges for us.
Week 9
In Week 9, majority of our time was put into finalizing our code, cleaning up the prototype of the application, writing the Final Report and making our Final Presentation.
Finally, the prototype looked like this;
Log In Window
In case the user enters the incorrect username and password
Current location of tag
Alert notification if target is out of premises.
Plot of where the target has been in the past 15 minutes
Plot of where the target has been in the past 30 minutes
Plot of where the target has been in the past hour
Week 10
In Week 10, we had our Final Presentation during which we explained our project to an audience including our entire section, our course coordinator, other interested students and our advisor. These past 10 weeks have been great, we learned a lot and all our work paid off.
We'd like to especially thank Dr. Timothy Kurzweg, our advisor who supported us throughout this project. Dr. Shrenik Vora and Ilhaan Rasheed, the graduate students who helped us with brainstorming ideas and taught us how to use the RFID system. We'd also like to thank Dr. Montgomery, the Chairman of the OB/GYN department of Hahnemann Hospital who took out time from his busy schedule to talk to us and work on effective applications of this project.
Week 2
Tutorial link: Android Studio App development
We soon realized that it was quite hard to make an app. Upon conversing with some of our peers in Computer Science, it hit us that maybe ten weeks is a really short time to build an app.
Week 3
We received the data in the form of a .json file from the RFID readers. The data we received was not from the XArray but we are using this data to learn how to parse .json files and to plot it. Later, we will receive the relevant data which we can pass through the program.
We started working on the code. We started learning how to make a Graphic User Interface (GUI) on MATLAB. We built a code to parse the .json files. Due to midterms, our work slowed down and hence, that's all we were able to do.
Week 4
We visited the Hahnemann Hospital for a scheduled meeting with Dr. Owen Montgomery. Dr. Kurzweg works closely with Dr. Montgomery to define what the needs of the hospital are and to find solutions that are commercially viable. Dr. Owen claimed that our project might not be the best idea. This is because, the baby really doesn't move around in the hospital. After birth, the baby is cleaned, tested and immediately given to the mother. Very rarely does the baby leave the mother's side. Therefore, it was determined that making a baby tracking system would be worthless as compared to the cost because the baby really doesn't move inside the hospital.
Some other things we learned at the hospital were:
1. The current system uses an active tag system. The tags are bulky and if the batteries die, the tag is inactive. A reader is placed near the exit of the floor and if a tag is detected by the reader, the hospital is immediately put on a shutdown and an alarm goes off. This is because no tagged baby is supposed to be near the exit. Also, if someone tries to cut the tag, the circuit breaks and an alarm goes off.
2. Some ways that this system could fail:
i) The batteries die and the tag becomes inactive
ii) The baby is stolen from the windows; this is especially possible in lower floors. This information came from researching baby theft cases.
iii) A fire alarm is set off then the fire alarm shuts off the Anti-theft system and a baby could be stolen. This is the way that a child was stolen from Hahnemann Hospital.
iv) A well planned scheme of stealing the baby is performed where the person has a fake id which gives them access to the floor, they know how to deactivate the tag and hence, would be successful in stealing the baby. This is highly unlikely because deactivating the tag is something only nurses and the tag makers are familiar with.
3. We learnt that the biggest need of the hospital in this certain area would be to make the tags less bulky, battery-less and cheaper - all of which could be achieved by using passive tags.
The meeting proved to be really fruitful in terms of getting the right direction and the required first hand information. However, it also threw us off from our original project of making a baby tracking device. Dr. Montgomery did mention that RFID systems were being used in the Psych ward.
Week 5
With the information gained from Dr. Montgomery, we met with our adviser and it was decided that we could continue building the tracking system except that the application of the system would be towards Psych ward patients, geriatric patients, for tracking tools and devices within the hospital and various other platforms where indoor positioning is necessary.
We also decided to work on making the tag tamper proof but this idea is put on hold till the time the program comes through.
To make the program, we want to include real time data reception from the RFID reader. We learned that MATLAB does not have a facility to send and receive real time data. Hence, we have to switch languages again and now we're building the program on Python.
The disadvantage that comes with Python is that none of this are familiar with this language. Hence, we're doing this from scratch; learning the language and then building the program.
The XArray has still not been setup in the lab. It's taking longer than expected because this is a new technology and it takes time to configure it and install it. We're still working on the sample set data and will build our program based on that. In the future, when the XArray is set up, we shall calibrate it with our program.
Week 6
Week 6 was the toughest week for our project. The XArray was not set up yet and it probably wouldn't be before Week 10 so we had to scrap out that plan. We taught ourselves Python by watching YouTube videos and started building the GUI for our program.
After talking to our adviser, we came up with a plan to use RSSI values to determine distance. RSSI gives us the signal strength and that could help us determine the distance. However, RSSI is not a reliable source because the signal strength varies with the environment - in the presence of other objects, the wave bounce off of the surfaces and the signal varies.
Calibration of RSSI versus distance
Week 7
During Week 7, our group continued to work on learning Python and making the GUI for the program. We made the buttons and windows, added alarm sounds. Since all of the data this system will collect is confidential, we added a username and password feature. If the two did not match, the person would receive an error message.
The user enters their assigned username and password
If credentials are incorrect, an error message is sent
Week 8
During Week 8, we started working on finding a relationship between RSSI and distance. We ordered an assortment of tags and then found out the RSSI value for each tag kept at a distance of 1 foot from the reader. We tried to keep all environmental conditions as constant as possible. After selecting the best tag i.e. the one with the highest RSSI value, we performed calibrations. We kept the tag at known distances, noted down the RSSI values for those distances and tried to build a relation.
While performing the calibration, we got the same RSSI values for multiple distances and this was due to the wave reflection effect. After consulting with our adviser, we figured out some ways we can improve the situation. We removed all surfaces that were in the way between the reader and the tag, we kept the tag and the reader at the same height and we only kept the tag directly away from the reader instead of diagonally or in some other direction.
After doing the above, we were able to find a relationship between RSSI and distance using a regression tool and the equation was to the power of 6.
At the end of Week 8, the program had all windows and buttons, it was able to receive and print real time data from the server and it was kind of able to plot the data as well. Plotting the data is the challenge currently as we want to plot it in real time. Learning Python and simultaneously building a GUI application in it has posed a lot of challenges for us.
Week 9
In Week 9, majority of our time was put into finalizing our code, cleaning up the prototype of the application, writing the Final Report and making our Final Presentation.
Finally, the prototype looked like this;
Log In Window
In case the user enters the incorrect username and password
Current location of tag
Alert notification if target is out of premises.
Plot of where the target has been in the past 15 minutes
Plot of where the target has been in the past 30 minutes
Plot of where the target has been in the past hour
Week 10
In Week 10, we had our Final Presentation during which we explained our project to an audience including our entire section, our course coordinator, other interested students and our advisor. These past 10 weeks have been great, we learned a lot and all our work paid off.
We'd like to especially thank Dr. Timothy Kurzweg, our advisor who supported us throughout this project. Dr. Shrenik Vora and Ilhaan Rasheed, the graduate students who helped us with brainstorming ideas and taught us how to use the RFID system. We'd also like to thank Dr. Montgomery, the Chairman of the OB/GYN department of Hahnemann Hospital who took out time from his busy schedule to talk to us and work on effective applications of this project.
No comments:
Post a Comment