01-23-2013 12:47 PM - edited 01-23-2013 01:35 PM
I have been searching for specific information on how to programatically connect to external devices using the USB port of the Playbook. It appears that the QNX Neutrino system level options don't work, I have tried using system() with some of the usb commands from the utilities (io-usb, usb, ...) with no success. I am attempting to construct an App which would use the USB port of the Playbook to connect to an industrial network such as devicenet or profi-bus as example. Does anyone know if this is possible? If this is related to another post here, admin please relocate it.
Edit Note: Thank you for responding, and the result is pretty much as I had found. I have no contact that I can name for RIM, off of the top of my head. I think that for now I will focus my efforts elsewhere for the Playbook development.
Solved! Go to Solution.
01-23-2013 12:54 PM
01-23-2013 01:07 PM
01-23-2013 01:22 PM
01-23-2013 03:55 PM
Our USB story is growing.
PlayBook OS 2 and BlackBerry 10 offer an implementation of the Android Accessory Protocol.
For experimenting, when you plug a (correctly configured) Arduino ADK into your Dev Alpha or PlayBook, /dev/aap0 will appear, and can be used to send serial data between the two devices.
At this time though - there is no way to find WHAT you are talking to - just to talk to it.
01-23-2013 04:31 PM
01-23-2013 05:14 PM - edited 01-23-2013 05:15 PM
I know that PB and BB10 are capable of handling almost everything - even a microwave oven with proper connection but till then, we can only speculate
01-24-2013 02:25 AM
BB10 firmware on Playbook correctly handles most USB devices including: keyboard, mouse, usb flash drives, arduino devices and many more.
This is tested on BB10.0.9 (the one that works on Playbook).
The reason it doesn't work on Dev Alpha devices is because they don't have a USB OTG port. It's just a regular port.
01-24-2013 03:25 PM
Thanks for the prompt response. Is the Android Accessory Protocol available in Playbook OS version 2.1 SDK? So is this more or less a "dumb terminal" type of connection, just exposing the serial protocol layer?