2017-04-08 (Sa) Weekly Summary

Project management sounds like a boring subject. Maybe it is. Maybe listening to a couple cyborgs talk about it in relation to an implantable long-range RFID would spice things up for you. Yeah? Give it a listen.
Brian - Left _____ Tim - Right

Solely using a Raspberry Pi as a controller was not ideal. It was cost-effective to only buy a single board but it did mean that anyone copying this project would HAVE to use a raspberry pi as well. Since the infrared transmission using GPIO and serial ports was a failure, I decided to put all the inputs and outputs, including the infrared stuff, onto an Arduino board.

 Preliminary pin assignment for Arduino Pro Micro

No serious automation would take place on the board. It was simply going to act as an interface between the controlling computer and the real-world devices. All the decisions would be made in the computer.

Working outputs on Arduino

The Arduino would have to recognize data from a USB port and from infrared signals. To demonstrate this an output was controlled with infrared, which is a pretty typical step when creating infrared devices.

 Receiving and recognizing infrared signals

Properly transmitting infrared is also a task in itself. And getting a single device to do this isn't as easy as adding a line of code below existing code. Fortunately, for demonstration purposes, infrared shows faintly in digital photography. The purple light seen below is the transmission bursts of infrared signals.

The purple light is infrared

Eventually, after a lot of forum searching, the transmission and reception was working together. Two units, with identical programming were able to talk to one another and send relevant data to the computers connected to them.

Receptions from the day of work

A protocol for a computer to talk to the Arduino would be necessary. Any connected device capable of talking over a serial com would be able to interface with this project. That should mean that a Linux computer, such as a Pi, or an Android, or Windows machine could all act as the computer for a game. All three should even be able to play in the same game as long as they use the same game protocol. This is something the old version, which used solely Pis, could not do.

Reworking the inputs and outputs and organizing the protocol


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.