I've been looking for a OBD1 bluetooth adapter for at least couple years now, but unfortunately, no such thing existed.

Thankfully, that has recently changed!
You can now pipe your ALDL stream to an Android device via bluetooth using a TunerPro definition file. This makes a permanently mounted display much easier and eliminates the mess of cords for a much cleaner look.

Now you can see your BLMs, oxygen sensor voltages, and all kinds of other good stuff wherever you go!


The bluetooth adapter:
http://www.reddevilriver.com/ALDL_Bluetooth.php

Check ebay too, there's probably a listing for it there as well..

The Android app, ALDLdroid:
https://play.google.com/store/apps/d...ldldroid&hl=en

I exchanged a couple emails with the developer already. He's a super guy..

 

Did you need to get a separate adx file for your ECM?

 

I'm not quite sure what you mean. The .bin definition is inherently different from the datastream definition, so you need both files, regardless of make and model. The DA3 .xdf and DA2 .ads file on TunerPro's website are the two I use for a '93. I'm afraid I can't speak much for other years. Going up and down the list though, I see pretty much all the C4 variants listed somewhere.

To be totally honest, I won't have the bluetooth adapter until Wednesday or so, so I won't be able to thoroughly evaluate the thing until then. I can't wait though, and I just wanted to put the word out, because this is something that's been missing from the OBD1 tuning scene for the longest time. We can now, finally, join the OBD2 folks with their cool little ECM feed setups.

I'll provide some impressions once I get my hands on the thing and have had the chance to play around with it a bit.. But for now, I return to the loathsome task of taking the front of my engine off so I can replace my opti-park. Yes.... I said opti-park.

 

Thanks for doing some leg work. I'm sure many will be interested including myself. And yeah, it's about time.

 

Yeah it is nice, I posted on it back in Dec when it first came out

http://forums.corvetteforum.com/c4-s...ta-logger.html

 

I asked about the file because I know very little on how it all works, I had read on the adldroid site to make sure and have the correct files for the ECM. I just want to make sure I get a grasp on it before I take the plunge myself. Sounds like you will get everything you need with it. I am looking forward to your comments after you get it. Thx

 

Sorry Jeff, not trying to step on toes.

I did a search and saw your post prior to posting. For some reason, the only thing I thought you had mentioned in your OP was the USB OTG variant, but I see now that you did briefly mention the Bluetooth one as well. In any case, I'm not trying to dance with you, but for the record, this thread emphasizes the Bluetooth adapter. I personally don't give two hoots about anything constrained by cables right now. It's all about Bluetooth here, baby!

Oh, I forgot to mention earlier, the developer's name is Sébastien. If any of you guys buy his ALDLdroid app or are thinking about buying it, be sure to write him an email (there's an Email Developer link on on the Google Play page) and tell him:
Unfortunately, you're currently stuck with an Android shade of light blue. Obviously, in cars like ours that are decked out in orangish-amber, light blue is most likely not on the color menu. So, the more people request it, the sooner that feature will become available.

 

Oh ok, well that definitely clarifies things. Yea, it appears to piggyback off of TunerPro's .xdf and .ads files, which is a great thing. TunerPro datalogs, and it can edit .bin files offline and in real-time ($39 for RT functionality). The .ads file defines the bit-stream or serial communication parameters for a particular ECM, and the .xdf contains all the switches, constants, tables, and anything else you'd customize in a .bin file. They're kind of like Tunercat's .tdf file, only Tunercat doesn't datalog. It's just a .bin editor and real-time emulator (if you have RT Tuner). TunerPro can be much more versatile in this regard. It's really a combination of TTS Datamaster and Tunercat, only it's totally free. I'm really tempted to go in the $39 for the RT version though, just to show the developer some appreciation. I probably will at some point. To put that all into perspective, TTS will charge you $120 for Datamaster, which doesn't even edit .bin files. For that, you'd also need Tunercat, which would cost $70, or $100 if you want real-time emulation. Free/$40 or $220? It's a no-brainer..

 

Upon further scrutiny, I couldn't seem to find a '90 Corvette or Y-Body on the TunerPro page where it has all the definition files. You'll have to do some looking around for yourself. Check the underside of your ECM, because there's a 7 or 8 digit code which represents which ECM you have. For the '93s, it's 16159278. This code will help you find an ECM on that list which may work for your application..

 

You're asking a lot from a guy who's just trying to get all the pieces working. I've been following his progress and it's a HUGE amount of work to do an app like this.

I just submitted an app to the iTunes app store that I started in May of last year, so I'm VERY familiar with what it takes to get one finished.

 

No worries, it is all good.. makes sense, I should have added Bluetooth to the title.. LOL

 

Ok, so I got my bluetooth adapter from Timm, but it's wired for 12v+ on pins G and L. On the early LT1s, pins G and L of the ALDL connector are both used for other functions. Pins D and E aren't used at all though, so I'm going to send the adapter back and have him rewire it to draw power from pin D.

Be sure to check your ALDL connector by the gas pedal and pick a cavity that has no terminal in it. Timm sends you a metripack pigtail so you can add a terminal to that cavity and wire it to a switched power source. Be sure to message Timm on eBay or his website before you buy it, and tell him that you need to have power wired to that empty cavity. I wish I had known that beforehand, but as it stands, it'll be at least another week before I'm able to get my adapter back from Timm and fire it up.

Note that pin I doesn't exist, it goes from H straight to J, at least on the '93. My guess is that the pinout is the same for all vehicles 91-93, but don't quote me.

 

Here is another one too:

http://www.1320electronics.com/products.html

I'm thinking it might be time to retire the RS-232 ALDL cable I have! Time to get out of the 1990's! LOL!

 

For realz, so true! For the longest time, we didn't have any choice, so this is super cool indeed!

I got my adapter back from Timm a few days ago, but naturally I have to wrap up some front-engine work and get all four wheels back on the ground before I can wire it up. I'm thinking I should have it hooked up by Wednesday next week or so..

 

I took the plunge and ordered from Timm today. Thanks for the tip on letting him know a blank cavity for a power suppply. Looking forward to getting it and trying it out.

 

My Red Devil Bluetooth came in a couple of weeks ago and I had time today to work on getting it connected. Started off well with getting it power through the OBD1, but spent the rest of the day trying to get it to connect and show data in Tuner Pro RT. I am using Tuner Pro RT on my laptop running Win 7. The RD BT unit boots up properly once I turn on power to it and it is plugged in the OBD1 connector, and then the RD BT unit connects with my laptop with Bluetooth no problem. When I try to connect in T/P RT it sticks on DA Connecting and never goes to Connect (blue color) no matter what I try? The RD BT unit changes alternating green/orangish color while T/P attempts to connect. But nothing more happens. T/P just sits on DA Connecting. I double checked the adx file and the baud rate is set to 9600 to match the RD BT unit. I also made sure I have the correct COM set in T/P. I tried a few different adx files than what was listed for my car thinking that might be the problem, but no success. The file I used that appears to be the right one for my year is 1990 - 91 5.7L (L98) - Y Body 1227727 $8D V1.ADX. I have a 1990 L98 with a manual transmission. My ECM has apparently been updated at some point and shows part # SVC16198260 which is a replacement for 1227730 & 1227727. I also tried various methods like starting the car first, not starting, only having the ignition turned to on but not running the car, etc. Any experts with ideas, I am stumped!

 

Interesting.. I am experiencing the same basic problem, only I'm trying to get the adapter to work with the ALDLdroid app. I can pair with the adapter just fine, and ALDLdroid appears to be connected to something.. somehow.. because at the top it says "Connected / RPS 0.0", but at the bottom there's also a red that says "No Response from ECU". RPS must mean replies per second. My adapter is also blinking green and gold, which doesn't make a whole lot of sense because if you read Timm Bacher's documentation on the CD he sent, it says:
It doesn't make any sense because pin E is an empty cavity in my ALDL connector. There's nothing connected to pin E because technically there is no pin E. Do you have a terminal in the pin E cavity, or is yours empty too? I feel as though we're experiencing a very similar issue because our model years aren't that terribly far apart, and our ECMs both talk at 8192 baud.

I captured a debug log and it's basically saying that it's sending information to the ECM, but the ECM isn't responding, not intelligibly anyway..
I'm not sure what the deal is either at this point, but I shot an email off to Timm Bacher and Sébastien Giroux. I'll see what they have to say about it..

 

I noticed the same thing in the documentation - pin E Green with Gold Flashes. Mine is green with what I would describe as orange flashes but I would interpret that would mean E pin. Yes, my E cavity is also empty. I also sent him an email tonight. Maybe he set the units up to read E pin and they should have been set up for M pin, so they are not connecting to the ECM? That would make sense since we are able to connect to the RD BT unit but not get any data connection to the ECM.

On another note I ordered a cheap Android tablet tonight so I can download Adldroid and just leave the tablet in my car when I want to connect to it. I was hoping changing to Adldroid would also be a solution in case I can't get Tuner Pro working, but from the issues you are having it may not be a solution.

Sounds like our issues are very similar and I am starting to suspect it maybe looking at the wrong pin in the OBD1.

 

I just read on his site "Supports both 160 Baud Pin E and 8192 Pin M protocals" so my logic above likely is not the case unless he customized the unit to only read pin E.

 

I saw it too. The way I interpret that is the adapter should be able to operate in any of these environments (160 D, 160 E, or 8192 M). There's a discovery process as soon as the adapter receives power. Another section in the documentation says:
Does yours flash blue before it starts flashing green with gold? Mine does. There's something weird going on...