This project has been in the mental works for years. Currently, the ID tags people are implanting have a range measured in centimeters. Long-range RFID can get much further than that but the cost is orders of magnitude higher, and the products haven't been tested for this sort of thing. So, I'm going to test them.
My goal is to create an implant based on the long-range tags and reader already available to hackers/makers but prove that it can be made implantable. The first part will be to get a system working and responding the way I want. The second step will be reading a tag in a simulated implant site. The third step will be to make one of the tags implantable and actually stick it under my skin. All these factors assume the previous steps don't reveal any insurmountable barriers.
My biggest concern is that these tags use a higher frequency, 910±50MHz, than the NFC tags, 13.56MHz, currently being used, and that won't work well through flesh. Feedback from people has been encouraging, and I think it's worth the research, even if it only proves that it's not viable.
Enough background
----------
A UHF reader was purchased and given long pins so it could attach to an Arduino Uno. A clone was readily available, so it was selected for now. The long pins will allow connections to be made on the top and the long pins on the bottom will keep some space between the boards. Additional space between the RFID board and the Arduino will be important when cooling the RFID which reportedly overheats without cooling.
Example programs from Sparkfun were installed into the Arduino IDE according to the tutorial on their site. Getting a reading from the first tags was a rush. The range was not great since only the onboard antenna was being used and it was at a power rating of 5dBm while the max power is 27dBm and the 6dBi antenna was not attached yet.
Two tags were scanned, and their output was printed onto labels so they could be easily identified. One of the tags, the one at the top of the picture, had the antenna trace cut so a switch could be installed. This will be part of the final project. It was shown that the tag would not scan until the gap was bridged. It was easier to cut the trace in this area than next to the IC which was hidden by the label.
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1.
Completed projects from year 2.
Completed projects from year 3.
Completed projects from year 4.
Disclaimer for http://24hourengineer.blogspot.com/ and http://24hourengineer.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2018-06-07
My goal is to create an implant based on the long-range tags and reader already available to hackers/makers but prove that it can be made implantable. The first part will be to get a system working and responding the way I want. The second step will be reading a tag in a simulated implant site. The third step will be to make one of the tags implantable and actually stick it under my skin. All these factors assume the previous steps don't reveal any insurmountable barriers.
My biggest concern is that these tags use a higher frequency, 910±50MHz, than the NFC tags, 13.56MHz, currently being used, and that won't work well through flesh. Feedback from people has been encouraging, and I think it's worth the research, even if it only proves that it's not viable.
Enough background
----------
A UHF reader was purchased and given long pins so it could attach to an Arduino Uno. A clone was readily available, so it was selected for now. The long pins will allow connections to be made on the top and the long pins on the bottom will keep some space between the boards. Additional space between the RFID board and the Arduino will be important when cooling the RFID which reportedly overheats without cooling.
Sparkfun board installed on an Arduino Uno clone
Example programs from Sparkfun were installed into the Arduino IDE according to the tutorial on their site. Getting a reading from the first tags was a rush. The range was not great since only the onboard antenna was being used and it was at a power rating of 5dBm while the max power is 27dBm and the 6dBi antenna was not attached yet.
Scanning at a few inches and 5dB
Two tags were scanned, and their output was printed onto labels so they could be easily identified. One of the tags, the one at the top of the picture, had the antenna trace cut so a switch could be installed. This will be part of the final project. It was shown that the tag would not scan until the gap was bridged. It was easier to cut the trace in this area than next to the IC which was hidden by the label.
Tags with printed labels
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1.
Completed projects from year 2.
Completed projects from year 3.
Completed projects from year 4.
Disclaimer for http://24hourengineer.blogspot.com/ and http://24hourengineer.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2018-06-07
Comments
Post a Comment