Database Users

USB Host Controller - Looking into android controlled robotic projects

Hello everyone. I have been searching for threads all day and have not found much information about being able to hook up devices into some kinda of USB interface or serial interface on Android devices. The closest thing I can find is this: http://forum.xda-developers.com/showthread.php?t=1202082
There has to be a host controller on these phones right? I would think that if there is a micro SD read reader on the phone, there would be one. Am I the only one thinking this? What is the best way to find out?
My inspiration comes from the ArduPilot project . I think this is pretty sweet but I think it could be way more powerful with a full operating system versus a limited micro controller. An additional fun link of, what most can imagine, my final goal: http://www.wimp.com/helmetcam/
I am posting this on the Evo 4G general thread due to owning it and it would be easy to disassemble, if there is something I need to look into.
I want to look finding (or creating) a robotics application for the android OS to map *connected* servo controllers (not bluetooth connected, Arduino powered, etc..) that will also allow remote users to control the phone multiple threads to control the UV or UAV. Examples: 1: Flying the RC Plane while viewing the video stream on the phone's multiple cameras (integrated or attached). 2: Executing autopilot application and monitoring it's progress through two-way communication from a controlling "base" station (PC, Server, Tablet, etc..). Maybe executing multiple RC vehicles at once.
I have a feeling that this would help many others with other types of monitoring projects (What comes to mind: Home security, Car Security, garden monitoring, etc..) This could also help the creation of other commercial products.
Any input and direction you can give would be appreciated.

Google ADK vs Arduino ADK vs Sparkfun IOIO vs ADK Shield vs ?????

Alright, so I'm kinda up in the air. The ADK is very interesting to me and from my understanding it is total mobile device side processing with the Arduino/ADK/IOIO acting as a slave. I'd like to play with this feature which was introduced at Google IO and first included in Android 2.3.4 but I don't know where to start.
So, let me explain what I'd like.. I'd like to build a robot powered by my phone. I want to plug in my phone and drive it around the house. I can work out most of the details on this project myself, however, I'd like to get the most bang-for-buck as possible. I don't want this to be a strictly ADK or IOIO device. I'd like to be able to repurpose it later.
The Open Hardware Acessory Development Kit
Aka Google ADK or Google's IOIO (Pronounced Yo-Yo). At a cost of $400, i imediately said screw that.. I'm not paying $400 for what is practically a finished project and not really a development board. No way, no how... I'm looking for the same functionality without paying the same amount as a new Android device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am looking at 3 different devices. The Sparkfun IOIO, The Google ADK or the ADK Shield for Arduino. I already own an Arduino Mega 1280 so I'm up in the air as to upgrade with a shield or go with a dedicated device.
The IOIO from Sparkfun
http://www.sparkfun.com/products/10748
This IOIO seems to be the cheapest, full device available. Costing only $50. It would seem that it is strictly designed to plug in to USB-OTG on a device and there is no USB for the computer meaning it can only be used as a slave device?
The Arduino ADK
http://www.google.com/products?q=Arduino+adk&hl=en
This device is based on the Arduino Mega 2650 platform. This would be an upgrade from my current MEGA 1280. Costing $75, it seems to be a fairly decent development board with the additional benefeit of ADK/ioio functionality.
USB Host Shield for Arduinohttp://robosavvy.com/store/product_info.php/products_id/1859/currency/USD
The USB Host Shield for Arduino seems to be a pretty good bet. At only $32, it will add the proper USB interface to an Arduino and allow ADK functionality. I'm worried about incompatibility on this Arduino Shield as I only have an Arduino Mega 1280 and not the faster 2650 platform.
I want to make a good choice here.. I'd like some help. I've never worked with ADK/ioio. AT&T has not even officially upgraded my device to 2.3.4 yet.
So, here's my questions:
Will the ADK work properly with a 1280 and a shield?
My understanding, correct me if I'm wrong, the ADK uses server and client side processing and is more for communication between the two devices, while the ioio method is direct slave-only control of the device?
Is there any advantage to buying the official Google ADK other than receiving a pre-fabricated shield with lights and buzzers?
Which one would you go with and why? Do you know of any better options for interfacing Android?

I'm not a programmer, and quite a noob in arduino. I've thought about connecting Android to my Arduino UNO and the method with most freedom seems to be via bluetooth. Was planning to follow the stuff on this site: http://amarino-toolkit.net/
I have yet to start that project though.

The Arduino ADK
I just picked up a Arduino ADK. Spent a few hours messing around with a RGB LED. My Motorola Photon would never connect due to the 2.6.32 Kernel. The 2.3.4 was right but the Kernel needs to be 2.6.35 to be an accessory.
Great board just not for the Photon. Will be getting the UNO and a WI-FI shield. And pick up a handfull of RGB LED Matrix, for a wifi driven LED message board.
I used three resistors with a RGB LED.
The Green LED is using the built in resistor. It flashes in time with the SMT LED on the board.

cellfreak said:
I just picked up a Arduino ADK. Spent a few hours messing around with a RGB LED. My Motorola Photon would never connect due to the 2.6.32 Kernel. The 2.3.4 was right but the Kernel needs to be 2.6.35 to be an accessory.
Great board just not for the Photon. Will be getting the UNO and a WI-FI shield. And pick up a handfull of RGB LED Matrix, for a wifi driven LED message board.
Click to expand...
Click to collapse
You won't need an Arduino UNO. The MEGA form factor is compatible with the smaller UNO form factor and the pins are totally compatible. Just get the wifi shield. My understanding is that the Uno would only be a reduction in size and features.

IOIO seems great. From their site, it seems like it has plenty of potential

Return
I returned the ADK. And will be getting an UNO or MEGA. If it comes down to size I'll get a nano with a shield.
AdamOutler said:
You won't need an Arduino UNO. The MEGA form factor is compatible with the smaller UNO form factor and the pins are totally compatible. Just get the wifi shield. My understanding is that the Uno would only be a reduction in size and features.
Click to expand...
Click to collapse

cellfreak said:
I returned the ADK. And will be getting an UNO or MEGA. If it comes down to size I'll get a nano with a shield.
Click to expand...
Click to collapse
Why did you return it? The ADK does more than Uno right? As far as I understand, you just downgraded?

I'm the developer of IOIO, so I won't pretend to be objective
First, there's no such thing as "Google IOIO". Google's board is called ADK. Although the original board cost $400, there have been since many other compatible boards, with the cheapest ones costing about $80 I believe.
There's also IOIO, which I developed and is sold by SparkFun for about $50.
The two most significant differences between the two are:
ADK and its clones would only work on very specific Android devices, while IOIO would work on almost any Android device since Android 1.5.
With ADK you'd have to write both the Android-side (Java) and the Arduino-side (C++) software, and establish a communication protocol between them. You'd have to know both languages and two different IDEs and unless you're doing something very trivial, it will take a significant amount of time to get something working reliably. With IOIO, you just write the Android side. You include a library called IOIOLib in your application, which provides an API that lets you control the IOIO pins and functions as if they were physically connected to your Android. You don't need to care about the fact that there's a separate processor here, communication protocols, etc.
Some possibly less important differences:
ADK boards are compatible with Arduino shields. If you want to use one in your application, IOIO will not be a good choice.
If you stick a Bluetooth dongle into IOIO instead of a USB cable to the Android, it will communicate wirelessly with the Android. The nice thing is that your application doesn't need to care about it, and you can even switch back and forth while your app is running.
If you want more info, see my blog post. Since I can't seem to be allowed to post links, just Google "IOIO over OpenAcessory" (without quotes).

ytai said:
I'm the developer of IOIO, so I won't pretend to be objective
First, there's no such thing as "Google IOIO". Google's board is called ADK. Although the original board cost $400, there have been since many other compatible boards, with the cheapest ones costing about $80 I believe.
There's also IOIO, which I developed and is sold by SparkFun for about $50.
The two most significant differences between the two are:
ADK and its clones would only work on very specific Android devices, while IOIO would work on almost any Android device since Android 1.5.
With ADK you'd have to write both the Android-side (Java) and the Arduino-side (C++) software, and establish a communication protocol between them. You'd have to know both languages and two different IDEs and unless you're doing something very trivial, it will take a significant amount of time to get something working reliably. With IOIO, you just write the Android side. You include a library called IOIOLib in your application, which provides an API that lets you control the IOIO pins and functions as if they were physically connected to your Android. You don't need to care about the fact that there's a separate processor here, communication protocols, etc.
Some possibly less important differences:
ADK boards are compatible with Arduino shields. If you want to use one in your application, IOIO will not be a good choice.
If you stick a Bluetooth dongle into IOIO instead of a USB cable to the Android, it will communicate wirelessly with the Android. The nice thing is that your application doesn't need to care about it, and you can even switch back and forth while your app is running.
If you want more info, see my blog post. Since I can't seem to be allowed to post links, just Google "IOIO over OpenAcessory" (without quotes).
Click to expand...
Click to collapse
I found your blog. I changed the title as there is no Google IOIO.
Ok. So, from what I'm seeing, the differences:
IOIO is a total slave unit that accepts direct inputs over usb from a running application. It's compatible with more devices out-of-the-box. The ADK allows a custom program to be launched for whatever code is running on the AT processor on the device... EMF Reader will launch your EMF app, Robot will launch your Robot app... I think this is a limitation of IOIO right?
Can the ADK emulate the same IOIO functionality where pins are commanded high and low?

ADK
I posted the ADK will not work with the Sprint Motorola Photon. The phone has the wrong has the 2.6.32.9 kernel. For it to be seen by the ADk board it needs the 2.6.35.9 kernel.
AdamOutler said:
Why did you return it? The ADK does more than Uno right? As far as I understand, you just downgraded?
Click to expand...
Click to collapse

cellfreak said:
I posted the ADK will not work with the Sprint Motorola Photon. The phone has the wrong has the 2.6.32.9 kernel. For it to be seen by the ADk board it needs the 2.6.35.9 kernel.
Click to expand...
Click to collapse
Well, yeah, but that's just a kernel upgrade right?
http://forum.xda-developers.com/showthread.php?t=1262123
If you grab an ICS build, you can get 3.0 kernel.

Honestly, I don't have much experience with this since I don't even have an Arduino board yet.
However, if you want to get a board locally, go with the Arduino. They sell them now at Radio Shack.
I intend to get one as soon as I can and experiment with it on my Kindle Fire.

I was also interested in this. I think it would cool to fly a rc plane with a phone hooked up, using the camera for live video feed and a laptop to send flight controls through 3g link.. Heck, you could even use the accelerometer as a gyro, the magnetic sensor for orientation, and gps for coordinates. If 3g were to drop, the plane would switch to gps guided autopilot until it gets reception.
I've since scrapped the idea, since it would probably be easier for me to get a HAM license and do all that with my own rX/tX stuff.

kindlefirexda said:
Honestly, I don't have much experience with this since I don't even have an Arduino board yet.
However, if you want to get a board locally, go with the Arduino. They sell them now at Radio Shack.
I intend to get one as soon as I can and experiment with it on my Kindle Fire.
Click to expand...
Click to collapse
Arduinos at radioshack are Duemillenova style. They are the basic modeland wont do anything with Android. You need the ADK. It can be obtained online for $80.
I have one, but i havnt had time to play with it.

Great～！I want to get IOIO now~
ytai said:
I'm the developer of IOIO, so I won't pretend to be objective
First, there's no such thing as "Google IOIO". Google's board is called ADK. Although the original board cost $400, there have been since many other compatible boards, with the cheapest ones costing about $80 I believe.
There's also IOIO, which I developed and is sold by SparkFun for about $50.
The two most significant differences between the two are:
ADK and its clones would only work on very specific Android devices, while IOIO would work on almost any Android device since Android 1.5.
With ADK you'd have to write both the Android-side (Java) and the Arduino-side (C++) software, and establish a communication protocol between them. You'd have to know both languages and two different IDEs and unless you're doing something very trivial, it will take a significant amount of time to get something working reliably. With IOIO, you just write the Android side. You include a library called IOIOLib in your application, which provides an API that lets you control the IOIO pins and functions as if they were physically connected to your Android. You don't need to care about the fact that there's a separate processor here, communication protocols, etc.
Some possibly less important differences:
ADK boards are compatible with Arduino shields. If you want to use one in your application, IOIO will not be a good choice.
If you stick a Bluetooth dongle into IOIO instead of a USB cable to the Android, it will communicate wirelessly with the Android. The nice thing is that your application doesn't need to care about it, and you can even switch back and forth while your app is running.
If you want more info, see my blog post. Since I can't seem to be allowed to post links, just Google "IOIO over OpenAcessory" (without quotes).
Click to expand...
Click to collapse

I've been working with the Mega ADK for a while, and it is true, there is SOOO much stuff you have to wade through on the Eclipse/Android side, and the Arduino/C++ side before you can get the thing to do basic stuff (like control a servo without the official demokit sheild)
So to recap (and correct me if I am wrong) here are the pro's and cons of the IOIO and the ADK
IOIO
Pro's - Just code in android! Quick simple access to all the pins available on the board.
Accepted by more devices?
Con's - no division of processing power
ADK
Pro's - just send commands to arduino, and have the arduino's processor take on extra tasks, (maybe if you are doing a bunch of High end computer vision stuff, and fancy motor control, you would want to split the task load?) Full control over how you program the board itself.
Con's- byzantine sample code to wade through. Fewer Android devices support this?
So it seems like, unless you need really high end performance, the IOIO is the way to go!

blorgggg said:
I've been working with the Mega ADK for a while, and it is true, there is SOOO much stuff you have to wade through on the Eclipse/Android side, and the Arduino/C++ side before you can get the thing to do basic stuff (like control a servo without the official demokit sheild)
So to recap (and correct me if I am wrong) here are the pro's and cons of the IOIO and the ADK
IOIO
Pro's - Just code in android! Quick simple access to all the pins available on the board.
Accepted by more devices?
Con's - no division of processing power
ADK
Pro's - just send commands to arduino, and have the arduino's processor take on extra tasks, (maybe if you are doing a bunch of High end computer vision stuff, and fancy motor control, you would want to split the task load?) Full control over how you program the board itself.
Con's- byzantine sample code to wade through. Fewer Android devices support this?
So it seems like, unless you need really high end performance, the IOIO is the way to go!
Click to expand...
Click to collapse
You forgot a few. There's more cons to the ioio and pros to the ADK.
ioio cannot function on its own. ioio is simply an output device.
adk is easier to program than android, the device can function on its own and then pass data to the Android. ADK can function as a stand-alone USB device that can be plugged into a computer as well.

ytai said:
Some possibly less important differences:
ADK boards are compatible with Arduino shields. If you want to use one in your application, IOIO will not be a good choice.
If you stick a Bluetooth dongle into IOIO instead of a USB cable to the Android, it will communicate wirelessly with the Android. The nice thing is that your application doesn't need to care about it, and you can even switch back and forth while your app is running.
If you want more info, see my blog post. Since I can't seem to be allowed to post links, just Google "IOIO over OpenAcessory" (without quotes).
Click to expand...
Click to collapse
hi i wonder if i can stick a bluetooth dongle on my Arduino Mega Adk and comunicate wirelessly with android..
have anyone try to do this? thanks! i have my motorola Xoom Working with Arduino Mega ADK via USB

AdamOutler said:
You forgot a few. There's more cons to the ioio and pros to the ADK.
ioio cannot function on its own. ioio is simply an output device.
adk is easier to program than android, the device can function on its own and then pass data to the Android. ADK can function as a stand-alone USB device that can be plugged into a computer as well.
Click to expand...
Click to collapse
i prefer the ioio over the adk cause of all the extra junk needed to get the adk working and if you need complex functions just do them android side. the adk is standalone which is a plus but most applications need to be send data back. but the adk has more liberies available but most of them are easy to write in java if needed. all the adk is is a serial bridge so you would need to write an interface to send data back and forth so as long as your project needs constant communication and you can do basic c and java for the liberies the ioio is a better choice provided your not using crazy shields like gprs
---------- Post added at 12:47 PM ---------- Previous post was at 12:47 PM ----------
jams90 said:
hi i wonder if i can stick a bluetooth dongle on my Arduino Mega Adk and comunicate wirelessly with android..
have anyone try to do this? thanks! i have my motorola Xoom Working with Arduino Mega ADK via USB
Click to expand...
Click to collapse
the ioio lets you do this with a 2 bt module

ASK
can you explained about USB Host Shield for Arduino n how to work this??
soryy bad english

Home Automation [Ard vs Rasp vs IOIO]

Hello,
I would like to hear some opinions about my personal want-sth-to-do project. I want to use NFC to open my house doors, including the front door, garage and bedrooms door. In addition, I want to be able to control my air-conditioning system, TV and audio system. I want to integrate some sort of IP/CCTV cameras into my personal system. Just to improve the system, I will develop a Android App to control it via an API.
So, to make this project possible, come to my mind three ways:
1. [Arduino]
- Using the Arduino and its shields to develop the entire system. It will take a while and be hard in some points such as IPCAM recording.
2. [RaspberryPi + Arduino]
- Using the RaspberryPi connected to some Arduino shields using the GertDuino (GPIO expansion boards that make RaspberryPi compatible with Arduino Shields).
- This options seems to be the best option for now, but I dont know if RaspberryPi is able to handle the entire system.
3. [IOIO-OTG]
- IOIO-OTG is a board that make any android device as the heart of the system, making you just program in Java and control the GPIO and UART.
- The benefit is that I can develop it using some Android Stick, however, I need to search about available shields for it.
In addition, I need to think how to separate the core of the system from the sensors such as nfc readers. I do not think that wiring over the entire house is the best way... but I didn't found any wireless sensors...
Someone want to give some opinion? I will update the thread with the sensors I'm looking around and so...

I'd go the arduino (maybe more than one) + raspberry-pi (maybe more than one) way.
the ioio seems to be some µc that runs a firmware that connects to android and provides all i/o pins to android... so nothing you couldn't do yourself with an arduino or something similar.
I'd start with the devices you want to connect. Air conditioning might be controlled using Infrared emitters - would that work?
NFC Readers can be built from an arduino AFAIK, but you'll need some sort of field bus or wireless connection between all the parts...

SkzBR said:
Hello,
I would like to hear some opinions about my personal want-sth-to-do project. I want to use NFC to open my house doors, including the front door, garage and bedrooms door. In addition, I want to be able to control my air-conditioning system, TV and audio system. I want to integrate some sort of IP/CCTV cameras into my personal system. Just to improve the system, I will develop a Android App to control it via an API.
So, to make this project possible, come to my mind three ways:
1. [Arduino]
- Using the Arduino and its shields to develop the entire system. It will take a while and be hard in some points such as IPCAM recording.
2. [RaspberryPi + Arduino]
- Using the RaspberryPi connected to some Arduino shields using the GertDuino (GPIO expansion boards that make RaspberryPi compatible with Arduino Shields).
- This options seems to be the best option for now, but I dont know if RaspberryPi is able to handle the entire system.
3. [IOIO-OTG]
- IOIO-OTG is a board that make any android device as the heart of the system, making you just program in Java and control the GPIO and UART.
- The benefit is that I can develop it using some Android Stick, however, I need to search about available shields for it.
In addition, I need to think how to separate the core of the system from the sensors such as nfc readers. I do not think that wiring over the entire house is the best way... but I didn't found any wireless sensors...
Someone want to give some opinion? I will update the thread with the sensors I'm looking around and so...
Click to expand...
Click to collapse
I find your ambition high. But as someone running an Insteon Smart Home with an ISY994i, I can't help but feel you are trying to make a fairly cost effective and secure option more expensive and less secure. Mobilinc integrates with tasker, so you could set it up to unlock doors and stuff pretty easy with NFC.
Best of luck with your search.

me likes

DThought said:
I'd go the arduino (maybe more than one) + raspberry-pi (maybe more than one) way.
the ioio seems to be some µc that runs a firmware that connects to android and provides all i/o pins to android... so nothing you couldn't do yourself with an arduino or something similar.
I'd start with the devices you want to connect. Air conditioning might be controlled using Infrared emitters - would that work?
NFC Readers can be built from an arduino AFAIK, but you'll need some sort of field bus or wireless connection between all the parts...
Click to expand...
Click to collapse
I agree with DThought. Including a Raspberry Pi would allow some pretty intense processing power.
If you want to limit the amount of wiring you do, you could actually use a USB wifi dongle on the Raspberry Pi. You could then make some simple protoboards/PCBs with an Arduino with a wireless shield for each thing you want to control. This would likely be a more expensive solution than plain wiring but it would allow a lot of flexibility. Especially if you had each of the Arduino clients very similar so that they are interchangeable.
You could also try using Xbee Arduino wireless shields in case you don't want to use regular wifi.
This sounds like a very good project. I hope it works out for you. :laugh:

Raspberry Pi USB HUB+Power Supply in one.

Introducing the PiPUB (Powered USB Board).
The all-in-one Raspberry Pi power supply and USB hub.
Hey all,
Just wanted to gather interest for something that I am working on.
See attached photos...
What it is/has:
A x4 Port, Powered USB Hub
A Power supply for the Raspberry Pi with overvoltage protection built in.
A Power Switch that completely removes power from the Raspberry Pi after initiating a safe shutdown
An IR receiver
A Remote On/Off switch for any single IR command "learnt" from a remote of your choosing
And IR extender - Gives you the ability to stick the Pi to the back of your TV and have the IR receiver discreetly mounted to the bottom of the screen.
All of this and the ability to fit within your current Raspberry Pi Case
Let me know what you think. Would any of you be interested in one?
Edit:
Kickstarter campaign started: https://www.kickstarter.com/project...b-and-power-control-for-raspbe?ref=nav_search

So, it's actually just something like this?
Improved schematic:
Sent from my GT-P5210 using Tapatalk

Not really.
Your schematic shows bypassing the raspberry pi protection circuits. Although this is fine if you know 100% that you have a decent power supply. However, I don't consider this ideal.
My board does away with the microUSB port used to power the Raspberry Pi. Instead it has its own standard DC 5V power in (see picture) which has its own protection circuit equal to that of the Raspberry Pi. It then splits the power supply to the hub and Pi, dedicating constant 5V supply to the Pi through the GPIO. This means when you plug in your USB powered HDD into the PiPUB, the sudden current draw does not effect in any way the power supply of your Pi and your Pi is protected from power surges.

Pretty neat stuff! I need this kind of setup!
Sent from my SCH-I545 using XDA Premium 4 mobile app

I am the co developer of the PiPUB and have a few more technical and operational details to add.
The hub controller is a Multiple Transaction Translator type meaning all 4 ports run at their maximum speed regardless of the generation of USB device that is connected. Some hubs are slowed down when earlier generation devices are connected.
The PiPUB plugs into one of the existing USB ports by a small, near flush PCB connector. For the keener DIY’er you can solder the USB data lines to the back of the Pi’s USB connector.
All upstream and downstream USB ports are protected against ESD by high speed, low capacitance TVS diodes.
5V power is inputted via a standard 5.5x2.1mm DC connecter through a 3A poly fuse and large TVS for over-current and voltage protection. Power to the Pi is then split off through a 1.1A poly fuse to the GPIO pins, similar to the existing power distribution on the Pi. We have loaded up all USB ports to 500mA and had the Pi running with negligible voltage drop.
You can use either the on board IR receiver or plug in the IR extension. They both work at 38Khz which is fairly common amongst remotes. These pass IR from your remote to the Pi via GPIO 18 and also to the microcontroller to control the power to the hub and Pi. You can map your particular remote to control XBMC.
There is a power button and LED that sits to the left of the audio jack above the Pi’s status LED’s.
If the Pi is OFF, pushing the power button or the learned IR remote button turns the power ON. If power is ON and the power script is installed or the XBMC addon we have created is installed, our board will initiate a safe shutdown. If neither is installed power will be switched off straight away. GPIO 23 and 24 are used for this.
On board is an open collector transistor that allows you to switch loads up to 250mA from GPIO 25. The intent of this is to allow people to control their own peripheral like a fan if desired.
It fits into the Black Multicomp and ModMyPi Cases without modification. It is then up to you to drill and cut the holes you want. We recommend the Black Multicomp case as it is an easy plastic to work with, it is the cheapest and certainly looks the part! In the future we hope to design a 3D printable case and a laser cut acrylic case similar to the Adafruit version for people to make.
If you have any suggestions on how we could improve the design and function it would be much appreciated.

Great little board, where do I get one?
Sent from my GT-N7105 using XDA Premium 4 mobile app

Thanks! We will be running a little Kickstarter campaign in the next week or two. Will let you know.

Great board! I was looking for a solution to shutdown the Raspberry Pi with a remote control.
Will this board work with the new Raspberry Pi B+? (Just ordered one to get rid of my hub...)
I've got 2 suggestions:
1. add a radio control-module (receiver and sender), so you will not only be able to shutdown the Raspberry Pi but also devices like an external HDD or the TV pluged in a radio controlled power outlets.
(background: I'm using my RPi as server with an external HDD and a printer as well as a wifi-router and when i'm leaving home, I don't use it, so I'm looking for a convenient way to shutdown all devices.)
2. offer a case suited for the Rpi+PiPUB (perhaps as stretchgoal in your kickstarter-campaign?)

Unfortunately it won't work with the B+ as the power button sits where the new set of USB ports are. We may look at producing a B+ version if our Kickstarter is a success (starting in the next 24hrs).
1. If the other devices you are looking at controlling have IR then the PiPub has AUX pads which you could solder 2-3 IR LED's to in series. It is connected to GPIO25 with a transistor so the LED's can be powered correctly. Using LIRC and a script I can see no reason why you couldn't get it to shutdown/power-up your other devices when the learnt IR button for the PiPub has been received. I haven't tried this but it seems more than plausible.
But it sounds like you are using RF controlled power outlets which I'm unsure how you could interface.
2. Like you suggest we would love to offer a case as a stretch goal. Most likely just a laser cut acrylic or 3D printable design. However it would be awesome if we could get Multicomp to modify their design to suit the PiPub!

Kickstarter up and running...
Hi all,
Kickstarter campaign is up.
https://www.kickstarter.com/projects/22555674/pipub-powered-usb-hub-and-power-control-for-raspbe?ref=nav_search
Please spread the word and help us make this a reality.

Ah, great! Perhaps, shutdown the RPi via IR is enough. I'll see
I got some new questions...
1. As I understand, the PiPuB has an external power supply. Does this power supply power the Raspberry Pi as well, or does the RPi "still" need its own power supply? (could save one power outlet)
2. Is this IR expansion cable anything special, which can only obtained by you? Would be nice to buy it afterwards if neccessary.

Yup. One of best things about the PiPub is that it removes the need for heaps of cables. The single 5V 3A power supply poweres the USB hub and the Raspberry Pi.
The IR extension is nothing special. You can find these on the internet or even a local electronics store. We tested a few and found some to be less ideal than others in terms of practicality. The one we're offering is what we deemed to be the best option but you may very well find something better...

Thanks!
One last question comes to my mind:
How can I use an IR remote with XBMC? In your video, you showed how to program one button of the remote. But what about the rest? I.e. the Flirc USB stick comes with special software to provide this functionality.

phoenix0_4 said:
Thanks!
One last question comes to my mind:
How can I use an IR remote with XBMC? In your video, you showed how to program one button of the remote. But what about the rest? I.e. the Flirc USB stick comes with special software to provide this functionality.
Click to expand...
Click to collapse
XBMC can be configured to receive IR commands through the GPIO port. The PiPub has an on board IR receiver that is connected to GPIO 18 and also an optional external IR receiver that can be connected. You have to run through a bit of configuration to learn your remote and assign the buttons to a function. Some good info about it here.
wiki.openelec.tv/index.php/Guide_To_lirc_rpi_GPIO_Receiver
druss.pp.ua/2012/08/raspbmc-lirc-gpio-xbmc-en/

ah, I see. Thanks again. I also found some how-tos in german.
So, I backed your project by pledging for a PiPub + power supply. Would be a nice "toy".
BTW, I found a similar kickstarter-project (but without IR or a switch). It's called "Raspiado". (because I'm new in this forum, I can't post a link, sorry.)

phoenix0_4 said:
ah, I see. Thanks again. I also found some how-tos in german.
So, I backed your project by pledging for a PiPub + power supply. Would be a nice "toy".
BTW, I found a similar kickstarter-project (but without IR or a switch). It's called "Raspiado". (because I'm new in this forum, I can't post a link, sorry.)
Click to expand...
Click to collapse
Thanks for the support.
Yea, unfortunately the Raspiado beat us to it with the KickStarter. I think the Raspiado is nice, but does not solve many of the Pi's issues. I don't understand the purpose of thes long custom USB cables if you're trying to reduce clutter.
What we wanted to focus on is the main issues faced by users of the Raspberry Pi in MediaCentre applications. This being said, the PiPub is still very useful in other applications. Just the power switch alone is massive capibility addition. See: https://www.modmypi.com/pi-supply. This sells for $23USD. Our PiPub is $33USD and does this while still fitting inside your Raspberry Pi case!
Thanks again for your support. :highfive:
Please repost this elsewhere and help us spread the word.

I just made the announcement in a german Raspberry Pi-forum and in the OpenELEC-forum. Perhaps it will help...

phoenix0_4 said:
I just made the announcement in a german Raspberry Pi-forum and in the OpenELEC-forum. Perhaps it will help...
Click to expand...
Click to collapse
Thanks for that.

Josh.5 said:
Thanks for that.
Click to expand...
Click to collapse
you're welcome.
Do you know any htpc-forum, which could be another good address?

Alternative
Now that this project did not happen, there is an alternative add-on board available, called RemotePi Board (msldigital.com), it has similar functionality, the IR receiver and power controller but no additional USB ports. Because they have a version for the Raspberry B+ which has 4 USB port this may be a non-issue.

[R&D] HandheldPi - Open Source Handheld Console

Hey there!
I am looking to start an open-source, non-profit project geared towards creating a handheld gaming/PDA device powered by the Raspberry Pi Compute Module. This device should be able to run emulators and games with input from an onboard controller, and should be customizable with different button configurations and different chassis with different screen sizes, battery capacities, and extended functionality. I am hoping that throughout this project I will be able to expand my knowledge of how electronics wor.
The main purpose of the project is to go over the basic design principles of a handheld device, along with engineering that goes into it. This includes PCB design, power management, engineering of components, etc.
As a basic idea, I am looking to design a base model with the following configuration:
- 3.2" or larger LCD
- Built-in speakers & headphone output
- HDMI and/or Composite Output
- 4000 to 6000 MaH Rechargeable Battery (Li-Ion/Li-Po)
- Ethernet connectivity and/or 802.11n Wireless
- Multiple controller inputs (for if it is connected to a TV for those looking to play multiplayer)
- (eventually) a Dock for hooking it up to a TV.
Obviously, I would like to keep everything absolutely open source. This includes the schematics, any customized source code for user interfaces, parts lists, etc. I am hoping to create a guide as to how the device was designed. This will go over the use of a PMIC, designing connectors for modular buttons and screens, placement of internal components, avoiding noise from power sources and signals, etc.
So far I've only realistically researched power management for the unit. The reason behind this is because overall, we only have to provide proper power outputs for the Raspberry Pi Compute module while still having features that would be required in a handheld device. Below, I will be compiling a list of components along with a list of their features that I believe is beneficial to the device.
This list will be updated as I continue to do more research.
Power Management: Texas Instruments TPS65800 PMIC (Single unit cost: $12 & $5.78 for 1Ku)
- 6x LDOs adjustable between 1.25V and 3.3V
- 2x Buck regulators fixed at 3.3V (one will be used to power VBAT, other to power 3V3)
- I2C interface (will allow for voltage adjustments and battery level indication)
- 3 GPIO ports (not sure what we'd use 'em for, but they're there!)
- Li-Ion and Li-Po charging up to 1.5A
Any help, ideas, or suggestions would be greatly appreciated. I'd like to note that I am fairly new to electronics design and am hoping this project will help to further my knowledge in the field.

So you want someone else to design and build it so you can collect money from a kick start for yourself?

5ft24 said:
So you want someone else to design and build it so you can collect money from a kick start for yourself?
Click to expand...
Click to collapse
Quite the contrary! I was looking for help in learning how to design such a device, not for someone to design it for me. If I did get a Kickstarter going eventually, I'd personally rather have the proceeds go to the Raspberry Pi Foundation so that others can learn how to do this themselves. As I stated, everything (including parts lists, schematics, etc) would be completely open source.
As a sidenote, I think a device like this would be very interesting for kids learning how to design their own games.

Great idea, I'd love a device like this running a well integrated retropie(Raspbian) operating system ! Unfortunately I can't help you with this stuff, but I'll spread the word