TLDR: I finished most of the theory to the design, power on is done, device recognition is done for this phase and will be revisited regularly, power control is done, touch communication is done-ish (i still need to order the touch screens from the chinese site, but the theoretical theory is there).

The first challenge that I need to overcome is developing a bridge.  The bridge controls the communication between the main system and the the different peripherals.  I have reviewed the power system theory for the Aura project today, and I have decided against that theory in favor of one that I had made a while ago.  They had an adjustable power source that floated and automatically adjusted to the conditions to prevent loss.  I am sticking with a fixed system to step up the voltage and regulate it from there.  This is because I am working with USB for my mainstay communication on the peripherals.  I am happier taking the losses with a double conversion if the majority of devices are 5v USB compliant.  This opens up backwards compatibility that stretches 20+ years without much more design input.  It also opens up the possiblity of other legacy devices that run at the 5v power standard (if I am feeling up to it can anybody say ISA slot?).

This is all controlled by a singular microcontroller that decides who and what has or gives power.  Right now I am using a series of timers to control this method.  Each peripheral will cause a noticeable change to the µC, and depending on which way voltage appears to be flowing to it tells it what it is and how it should be treated. While at the same time all the data about the device gets reported to the mainboard via USB.  My original consideration was to use I2C to communicate between the devices and the µC, but it is much easier just to simplify it down to a series of comparisons and let the main board take care of the labor intensive things.  

I am also doing the same thing with the power button. Depending on what state the µC is in it will cause a different response depending on time. If it's in an extremely low power mode (aka off) when pressed it will activate a programmed timing that says to turn on or not bother with the message, and if it's on it will tell the µC to send a lock message to the main board or send a "wanna power down" message.

Now, who is my champion for a µC?  Out of circuit an arduino (I had it lying about collecting dust), but in circuit it's a... hang on I have to grab it.  IT'S GONE... no, it's under the antistatic foam. It's a Texas Instruments M430F5529 (because I also had one lying about). This is a choice one because how little power it draws when I demand it to.  It is also capable of I2C and I need that for communicating with the main board, touch sensors, and controlling the display.  I also need it to turn on and off display communications to the wrong port, but I will get into explaining that later.  

Right now I need a schematic that will organize the power system in a kinda neat fashion that has a fair bit of loss built into it that meets my requirements.  I also need to prime my µC to interpret the signals so it knows what to do when a charging cable is attached.  For now I will rely on C as my base programming language.  I also need to order the parts that will help me solidify what size of tablet I will focus on first.  I say this because I will eventually try to access more than one size.

BUT OF EVERYTHING ELSE I AM TRYING TO MAKE THIS SIMPLE ENOUGH ANYBODY WITH A SOLDERING IRON COULD DO IT.