Tweet
Summary
The Car
Problem
I built the 2transistor converter, but the $1FA.ads file wouldn't work. I then learned that mine is a different protocol (A263), so I rewrote the ADS file. Still no connection. I threw together a C# program to read from the serial port, log the information, and allow me to send a few commands (mode 08, and a message request). Hooking it up while off, the program saw a few null bytes (the number varied each time). Turning the key to on, and the screen flooded with data. For my chatty ECM, that is perfectly normal. I tried sending a few Mode 8 requests, but it ignored it. I turned the key off and saved the captured data. Either the connection was out of sync, or my EBCM (ABS is device $F9) is ranting with weird messages of 1 to 137 bytes in length.
I didn't process the log with a PERL script yet to see if they are valid messages (checking the stated length and then calculating a checksum to see if they match), so it may be jibberish. Also, I logged at 9600 as some sources say you can use 9600 in place 8192. I will try again later today at 8192 baud.
Some people say that the 2 transistor circuit is crap, and it fails to connect more than it works. So perhaps when the max232s arrive everything will be ok. Has anyone had any experiences with the A263 protocol -- regardless of success?
The ALDL files listed protocols for airbag and ABS computers too. Once I can talk to the PCM, I'm eventually going to see if I can get information from them too.
I'm trying to connect (for maintenance not tuning) to my 1995 Olds Cutlass Ciera, 3.1 v6 (L82) with MAF, likely the A263 protocol. I have the ALDL documents, a laptop, Tunercat Pro (the nagware version), a $1FA.ads file for A261 protocol, several line converter schematics, max232s in the mail, a self built 2-transistor converter, and computer programming experience. I've run into some problems, has anyone had experience with the A263 protocol? Skip down to "Problem".
Greeting/IntroHello to the community. I'm not into tuning, and because of my strained finances, I probably never will. I am just a broke geek (computer geek) with an internet connection, who used the net to fix their car and now to find and fix all the other problems with the car. After all repairs are done (months from now?) I may do some "modding" such as timers to roll with windows, a lowend car-puter, custom alarm system (apparently Atmel sells chips).
Last week I broke etiquette and PM'd 'pocket rocket' about their post of making an aldl cable. He seemed knowledgeable and talkative, so I broke etiquette this one time, and asked via PM what color the wires from the car were. Sorry, pocket. His response was quick and useful, and he suggested I post here about the car, since someone may have already had success with the A263.
Last week I broke etiquette and PM'd 'pocket rocket' about their post of making an aldl cable. He seemed knowledgeable and talkative, so I broke etiquette this one time, and asked via PM what color the wires from the car were. Sorry, pocket. His response was quick and useful, and he suggested I post here about the car, since someone may have already had success with the A263.
The Car
My car is one of those "Bastard cars" from 1995. Its a 1995 Oldsmobile Cutlass Ciera, 3.1L v6 (L82) with MAF sensor. Its ODB, and apparently it uses the A263 protocol. Up until May, I didn't know much about cars other than how a generic engine ran from when I did a middle school project ~1993. I studied up and replaced the gaskets (head, LIM, UIM, Throttle Body, etc) on the car when yellow "snot" appeared in the oil. I then found that the mechanic of the previous owner did a lot of hack jobs on the car, and I also found many broken/damaged things. Broken vacuum lines, radiator fan wired to battery, camshaft position sensor wires damaged at the sensor, exhaust manifold bolts broken below the line, and many more problems. Some were beyond me and I had to leave as they were (drilling out the broken bolts), others I did fix or will as soon as I have more cash (cam sensor). To help isolate any other problems, I wanted to ask the computer what it saw wrong, and that brings me to why I am here...
Problem
I built the 2transistor converter, but the $1FA.ads file wouldn't work. I then learned that mine is a different protocol (A263), so I rewrote the ADS file. Still no connection. I threw together a C# program to read from the serial port, log the information, and allow me to send a few commands (mode 08, and a message request). Hooking it up while off, the program saw a few null bytes (the number varied each time). Turning the key to on, and the screen flooded with data. For my chatty ECM, that is perfectly normal. I tried sending a few Mode 8 requests, but it ignored it. I turned the key off and saved the captured data. Either the connection was out of sync, or my EBCM (ABS is device $F9) is ranting with weird messages of 1 to 137 bytes in length.
I didn't process the log with a PERL script yet to see if they are valid messages (checking the stated length and then calculating a checksum to see if they match), so it may be jibberish. Also, I logged at 9600 as some sources say you can use 9600 in place 8192. I will try again later today at 8192 baud.
Some people say that the 2 transistor circuit is crap, and it fails to connect more than it works. So perhaps when the max232s arrive everything will be ok. Has anyone had any experiences with the A263 protocol -- regardless of success?
The ALDL files listed protocols for airbag and ABS computers too. Once I can talk to the PCM, I'm eventually going to see if I can get information from them too.
Comment