A new forward array was modeled for the tagger. This looks more complex and should fit the aesthetic of the project better. Functionally, it adds more room for the forward components which should make it easier to assemble and trouble-shoot. An accessory riser was added to the top to ensure alignment with the rest of the tagger.
Aligning all the components on the pipe has been difficult and led to wonky looking taggers. It wasn't a problem since they were not game-ready anyway but it seemed logical to make good looking taggers. The models below go into the ends of the pipe and provide a spot for a straightedge to make sure everything lines up.
Describing how the tools should work was difficult so pictures were taken and instructions were written on how to use them. Also, I found black ABS pipe with the same dimensions as PVC. It was considerably more expensive and lighter but it won't need paint so scuffing won't show as the taggers get worn.
Infrared emitters and receivers were attached to the serial pins of some TTL 232 ↔ USB adapters. Colloquially known as an "FTDI adapter" or, "the thingy I program my Arduino Pro with." I got garbled output.
When I noticed that the emitter would glow constantly I assumed it only went low while transmitting but I think this was due to the transmitter. A couple of resistors and a transistor (2N3904) were used to make a NOT gate, also called an inverter. After that, the emitter would only glow when it was transmitting.
A NOT gate was also constructed for the receiver and all the combinations were tried. Despite everything, no data could be reliably transmitted and garbled data was the best that could be received.
Rotating view of forward array
Aligning all the components on the pipe has been difficult and led to wonky looking taggers. It wasn't a problem since they were not game-ready anyway but it seemed logical to make good looking taggers. The models below go into the ends of the pipe and provide a spot for a straightedge to make sure everything lines up.
Model of pipe alignment tools
Describing how the tools should work was difficult so pictures were taken and instructions were written on how to use them. Also, I found black ABS pipe with the same dimensions as PVC. It was considerably more expensive and lighter but it won't need paint so scuffing won't show as the taggers get worn.
Marking the centers of ABS pipe
Infrared emitters and receivers were attached to the serial pins of some TTL 232 ↔ USB adapters. Colloquially known as an "FTDI adapter" or, "the thingy I program my Arduino Pro with." I got garbled output.
The emitter shines purple though a digital camera
When I noticed that the emitter would glow constantly I assumed it only went low while transmitting but I think this was due to the transmitter. A couple of resistors and a transistor (2N3904) were used to make a NOT gate, also called an inverter. After that, the emitter would only glow when it was transmitting.
NOT gate controlling an infrared LED
A NOT gate was also constructed for the receiver and all the combinations were tried. Despite everything, no data could be reliably transmitted and garbled data was the best that could be received.
Garbled data
The rest of the weekly summaries have been arranged by date.
Disclaimer for http://24hourengineer.blogspot.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, are 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.
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, are 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.
Comments
Post a Comment