[Gmecm] ALDL for Android?

[Avery Nisbet]

Just bit bang the 8192 baud and then hook the hardware serial port to
a blue tooth adaptor running at a standard rate.

I think bluetooth pretty much ignores the baud rate altogether anyway.
It just moved bits when they are present or fit into some buffer.
Think Unix pseudo terminals. The serial port on the bluetooth chip may
have to be configured for the baud you want though.  There maybe some
non-standard baud rates available depending on the chip you use.

In fact the blue smurf available at sparkfun.com can be configured for
non-standard baud rates above 1200baud.
datasheet here -->http://www.rovingnetworks.com/documents/RN-41.pdf
sparkfun project board here --> http://www.sparkfun.com/products/158

Hope that gets you started. This project board is expensive but there
should be others out there.
-Avery

On Tue, Mar 8, 2011 at 5:30 PM, Ant <ant at symons.net.au> wrote:
> Do you know of one that supports 8192 baud? Are non standard rates part
> of the blutooth standard? Wifi negates issues with the non-standard baud
> rate and non-purpose specific hardware.
>
> I'd be keen for an atmel based device, which could easily do the 8192
> baud part but I still want my wireless which then becomes the harder
> side of the problem.
>
> Ant
>
> On Tue, 2011-03-08 at 17:24 -0800, Avery Nisbet wrote:
>> I don't think there is access to a Serial port through the Android
>> API. ?But there are bluetooth to serial adaptors that will work with a
>> non-power stealing ALDL cables. ?Then you would just need to write the
>> android app as if the ALDL cable is over a virtual bluetooth console.
>>
>> I think thats how the bluetooth dongle the current app uses works
>> (serial to bluetooth then a sear
>> -Avery
>>
>> On Tue, Mar 8, 2011 at 5:01 PM, Jay Vessels <jay at vessels-clan.com> wrote:
>> > Hi there!
>> >
>> >> Agreed. Im interested in this too, and this seems to be the hardest part
>> >> part of the problem. The fact we need 8192 baud does not help either.
>> >> Its surprising the elm chips cant do it, but I guess they were not built
>> >> for that purpose.
>> >
>> >
>> > Assuming (!) the Android device (phone, tablet, whatever) has a USB host
>> > port, *and* you can add a driver for it that will enumerate a specific
>> > USB device, one may be able to homebrew an ALDL adapter. ?Various micros
>> > (i.e. PIC) implement a USB device port, and a serial port, so a custom
>> > bridge that speaks the right bitrate over serial (and possibly knows a
>> > bit of the protocol) shouldn't be too bad.
>> >
>> > Anyone have any Atmel or PIC micro stuff laying around that talks 8192
>> > or 160bps ALDL?
>> >
>> >> Im considering this also. Im wondering if the best interface would be a
>> >> 12v wireless AP, one that runs linux that we can get into, and which has
>> >> an on board serial port that supports 8192baud which can be adapted to
>> >> talk aldl.
>> >
>> > Sounds complex but may be the easiest to implement because it uses
>> > off-the-shelf hardware rather than homebrew hardware.
>> >
>> > This screams for a dev. board of some small micro. ?Beagle Board comes
>> > to mind but I don't have one so I don't know if it has everything one
>> > would need.
>> >
>> > Jay Vessels
>> > 1982 Chevrolet S-10 Sport, 2.8V6 TBI
>> > 2006 Pontiac Solstice
>> > _______________________________________________
>> > Gmecm mailing list
>> > Gmecm at diy-efi.org
>> > http://lists.diy-efi.org/mailman/listinfo/gmecm
>> >
>> _______________________________________________
>> Gmecm mailing list
>> Gmecm at diy-efi.org
>> http://lists.diy-efi.org/mailman/listinfo/gmecm
>
>
>