GaryDoug

Nope, there is already a good app for Android. It's ALDLDroid. Takes a bit of work to set it up with a Tunerpro-compatible data file but it gives you the exact data you want, the way you want it displayed.

GaryDoug

I upgraded one of my pc's to Windows 10 and this app works fine on it. No differences from a Win 7 setup for the app or cable.

Injuneer

Thank you!!

ENRKyle20

This program rocks my world. Thank you!!

KYWes

I use SCAN94/95 on my 1995 Z28. I've got a friend who has a 1994 Corvette which has the OBDII 16 pin port but is OBDI like my Camaro.

Does anyone know if I can read his car's information correctly? I know it will physically hook up but will the data coincide, specifically on error codes?

GaryDoug

Re 94/95 Vette coverage: The short answer is yes, it will work (sorta) as-is. The y-car and f-car pcms are almost identical. But for the best version for a 94/95 Vette, get the one(s) in the Trials vette folder. Use either "...exe" file in the folder. It isn't perfect, but it works well enough to read trouble codes and engine data. It just isn't too stable (intermittent operation). I never got the hang of syncing with the pcm and getting around the CCM module, mostly because I don't have a sample Vette PCM or CCM to use.

Injuneer

Post by Novo have been moved to this new thread:

https://www.camaroz28.com/forums/lt1...review-883191/

They turned into complex analysis of data logs for his new LT1, and seemed like it would be better to start a new thread in LT1 Based Engine Tech.

Temo

I know this is CamaroZ28 forum, but i wanna make this adapter for my 1993 GMC C1500 Sierra. V8 5.0L 305 TBI...

Will it work for my truck?

GaryDoug

I don't think the cable will work for you. Your engine, if an L03, uses a different pin# (E) for communication. It is a 160 baud, unidirectional signal (read only). You should look for an ALDL cable with the signal on pin E. A definition file at TunerPro.net may work. It is number $E6.

Temo

Happy Thanksgiving.


John Wales
Nov 13 (13 days ago)

to me
Hi Mr. Mirola-

If the light did not blink with just the adapter connected, that means your vehicle is 8192 baud, not 160 baud. That's a good thing. 160 baud trucks communicate all the time and very slowly. Your truck requires ALDLDroid to send a command, then it responds. So you will want to use the A201 file with ALDLDroid. You will want to configure the switches on the front of the unit as follows:

1-up, 2-down, 3-up, 4-up

After configuring the switches, recycle power to the adapter.

Here are links to the User's guide and ALDLDroid quickstart guide:

http://www.1320electronics.com/downloads/User_Guide.pdf

1320 Electronics LLC

Temo

I got this from the developer of ALDLDroid.

Sébastien Giroux
Nov 22 (4 days ago)

to me
Hi,

That ADX file seems totally wrong, where did you got it from ?

16168625 PCM Information $E6 seems to have the right file

Looking at the information I have so far, there is most likely nothing wrong with the app or the adapter, but the ADX file definitely isn't right. The wrong command is being sent in the monitor macro of the adx file you sent.

Will everything be fine after that ? That's impossible to say but at least one of your problem for sure.

Thanks

Date: Sat, 21 Nov 2015 21:35:58 -0800

GaryDoug

Manual or automatic transmission? 8192 baud with A201 for automatic 4L60E, 160 baud with A179 for manual.

Also, having the light NOT blink does not necessarily mean it's 8192 since the 160 baud version is not connected to the same pin in the DLC.

Temo

its an automatic transmission.

GaryDoug

Then it is the A201 definition file and 8192 baud (bi-directional). The cable should work as described. My apps are only for the LT1 or L32 engines, will not work correctly for L03. The app will send the correct L03 engine data request and receive the L03 data, but you would only be able to view the raw data string in the Comms tab of my app. Nothing would match up in the real time data displays and an error would occur.

I am very familiar with Sebastien's work. I helped him add the 160 baud feature to ALDLDroid.

Temo

Thanks for the clarification.

I am waiting for the cable I will use Tuner Pro when I set up my cable.