Hey guys. From other posts you may think I'm worthless, and while that is usually the case I think Kyle and I are onto something here. We spent a couple hours playing with his '88 DIS L4 and CarBytes, and with Kyle being the driver and me being the brain, we figured out a few of the sensors/gauges by looking at the raw data from the serial byte stream. I just started learning how to use CarBytes V2 today so I'm going into this headfirst without really knowing what's going on, but we did get a few things to work:
Coolant Temperature
Throttle Position (this was the easy one!)
Tachometer/engine RPM
Vehicle Speed Sensor (50% sure)
Oxygen Sensor
Battery Voltage (70% sure)
What do you guys think, has this been done before? I'm pretty excited - it's really fun to watch Kyle drive around and see the graphs of throttle position vs. RPM.

Now for the problems. I copied a macro from the standard ALDL definition and I'm not sure if it's exactly what I need. The program is crashing on me a lot, and to get my definitions to work, I have to do this:
Open CarBytes
Click the start reading ALDL information
Open my definition file

If I need to change anything, I have to stop logging, edit, then save and close program, then reopen in that order. Weird, huh.

Anyway, exciting! Does anybody have any extra information on how to decode the byte stream on these DIS Dukes?

P.S. give me a positive, this is the first useful thing I've done!

------------------
1986 Pontiac Fiero GT 4.9.. IT RUNS!

[This message has been edited by Wipe0ut (edited 01-29-2006).]

Sent
TK

[This message has been edited by TK (edited 01-29-2006).]

Sent.

Adam

Maybe we can get this into a fully working file :]

I can spell, really...

Did it show up?

[This message has been edited by TK (edited 01-29-2006).]

What? You sent me a blank e-mail. :P

Pull the string tighter!

[This message has been edited by TK (edited 01-29-2006).]

WTF I'm pulling as hard as I can! Yeah I got it, I'll hopefully get all that stuff together tomorrow.. surprised you haven't yet TK!

I don't have a TBI L4 or I would have.

Ah, and it's coming together I don't either, but my roommate has two this makes it all so much easier.

Glad I could help.

I'm assuming that other '87, '88 DIS owners will be following this thread with interest. It would be nice to have a 'version' of WinALDL that works for us. Good luck, to say the least.

We just had a thread on this sort of thing awhile ago, although it never got anywhere, I have some more stuff I need to do with my DIS duke, then I can go right into reading data off the ecu, so it would be nice if we could put together a begining to end.

Well dark that's what I'm doing. I have the easy stuff figured out, and with the help of TK I'll be making the rest of it work. The program that I'm doing this for is CarBytes V2. We are using the very simple two transistor interface (not using the MAX232 chip) so we couldn't get EFIlive V4 to work.

Does anybody have experience writing ALDL definitions in CarBytes V2? I can handle most of the stuff myself but I'm not so sure on the macros. I'm sure an hour or two playing with that should get me somewhere, though. I copied the Holden V8, which has a lot of extra steps that aren't being used (it's trying to send a request for data to the ALDL like most cars need [but Fieros only need the 10k resistor]), but the cable and interface we are using is receive-only.

[This message has been edited by Wipe0ut (edited 01-30-2006).]

Im sorta curious about this whole carbytes thing... How the heck do I get it so that the computer is continuously sending data, and Carbytes is continuously displaying it. The way I have it now, I can send the ALDL macro 8 times and 4 or 5 full aldl samples come back and thats it. As far as I can tell, the data is all correct but It will only display as many times as the macro is run. Im pretty sure I am missing some key concept with the aldl requests page.

I am working on this with a Quad 4 H.O. W41 computer that I wrote the definition file for.

I have tried this program on several different model computers and none like to continuously display data, just a full sample from time to time.

Other programs seem to work fine, but none have the data stream modifiability that carbytes seems to have. It is a well written program.

So, what does it take to get the computer to send the data stream continuously?

This is typically what I get when I run the macro.

Send: $F4,$56,$08,$AE
Recv: $F4,$56,$08,$AE
Send: $F4,$57,$01,$00,$B4
Recv: $F4,$95,$01,$07,$E7,$00,$08,$00,$12,$00,$FF,$01,$00,$70,$00,$00,$00,$00,$82,$68,$01,$80,$80,
$13,$00,$96,$EE,$01,$E6,$00,$00,$FF,$00,$00,$1D,$27,$8B,$80,$00,$06,$00,$00,$D5,$01,$06,$00,$00,
$26,$47,$08,$00,$00,$00,$00,$00,$00,$00,$3F,$1C,$00,$40,$1D,$42,$00,$50,$80,$26
Send: $F4,$56,$09,$AD
Recv: $F4,$56,$09,$AD
Repeat: 1
Send: $F4,$56,$08,$AE
Recv: $F4,$56,$08,$AE
Send: $F4,$57,$01,$00,$B4
Recv:
Send: $F4,$56,$09,$AD
Recv: $F4,$56,$09,$AD
Repeat: 2
Send: $F4,$56,$08,$AE
Recv: $F4,$56,$08,$AE
Send: $F4,$57,$01,$00,$B4
Recv: $F4,$95,$01,$07,$E7,$00,$08,$00,$12,$00,$FF,$01,$00,$70,$00,$00,$00,$00,$82,$68,$01,$80,$80,
$13,$00,$96,$EE,$01,$E6,$00,$00,$FF,$00,$00,$1D,$27,$8B,$80,$00,$06,$00,$00,$D5,$01,$06,$00,
$00,$26,$47,$08,$00,$00,$00,$00,$00,$00,$00,$3F,$1C,$00,$40,$1D,$42,$00,$50,$80,$26
Send: $F4,$56,$09,$AD
Recv: $F4,$56,$09,$AD
Repeat: 3
Send: $F4,$56,$08,$AE
Recv:
Send: $F4,$57,$01,$00,$B4
Recv:
Send: $F4,$56,$09,$AD
Recv: $F4,$56,$09,$AD

[This message has been edited by Fierobsessed (edited 01-31-2006).]

You can't. You send the stop communications, then request ALDL, get the stream and request again. If you don't the ECM will revert to normal communications in about 5 seconds.

Terry

Are you using the MAX232 interface? I've heard of weird things happening with echoing.. but it doesn't look like that's goin on here. I really don't know on that one since all you have to do in a Fiero is jumper the two pins with a resistor

Edit: how in the **** do you get CarBytes to log?!#
Edit 2: oh wow, that was easy. Nevermind. I couldn't figure it out all last night. :x

[This message has been edited by Wipe0ut (edited 01-31-2006).]

ALDL is one wire so you have to deal with the echo no matter what you do. There are various ways to do it. Watch for it and dump it or watch for the ALDL header and just grab that as it goes by.

The MAX 232/233 has nothing to do with the problem. For ECMs that send out of the data when you connect a resistor to the diag line, it's easier since you don't have to send a shut/request command and then ignore those looping through the MAX chip. Luckily the Fiero 7748 ECM just needs the resistor.

[This message has been edited by TK (edited 01-31-2006).]

So basically it doesn't matter at all what I "send" to the ECM. I'm so clueless on this stuff. :]