I have finally gotten some free time in the nights and have started working on win ALDL again for the 3.1 ECM's. I am now writing it in visual basic.net which is a lot easier and its going along very smoothly, I should have a test version out sometime during this week. .

 

Told ya I would continue development .

 

ACK Headache .

 

keep up the good work

 

I finally got around to trying mine a few weeks ago. It didnt work, so thanks for working on this more!

 

visual basic does everything for you, if you were using c++ or C# then i would understand the headache, but vb.net is generated...

 

Doesn't make it any less complicated. I'm building an ALDL reader for the '86-89 '302 MAF 2.8s, in C++, big deal?

I did just make a nifty little program to calculate LV8 based on RPM vs Airflow from WinALDL though.

Makes tuning SOO much easier.

Programming isn't 'easy' by any means, no matter what language you use. Keep up the good work, Pasky!!

 

Doward, did you convert to maf? If not, PM the details on your reading program so I can get you some good details.

 

Yes, Doward's setup is still the '88 MAF setup that came on the car.

 

Kept thinking 3.1 1990

 

I am actually very proficient in C++ and was being sarcastic . I prefer VB for something like this because it is much easier to make the GUI. However, with your statement, why not make your own .

 

Did I ever release the source Doward? I cant find my original program as I had formatted my drive sometime in May because of a virus and lost it. Got a copy of the old ones? All I have are the source to my old functions.

 

Woops, already made a mistake in my program. asc() should be chr(). Tee hee. Been a while since i've looked at all the notes rbob has given me .

BTW:

I will be needing someone to test this as I no longer have my V6 ECM hooked up to any 3.1 engine, its just lying in my garage and if anyone is interested in it just PM, its just taking up space.

 

I'll take that offer on using program. Uses same cable as ALDL or your last program?

I belive I still have the zip file of your program around if you need me to email back to you.

Is the ECM an Auto or Manual one?

 

Yes sir, same cable. I will be able to write this for the v8's and 2.8's also, its just changing the request and how the data packet is recieved.

The ECM is for a manual.

I still have the old program as well, would like the source code but don't think i've ever released it. No biggy, its probably better to start over fresh.

 

I'll take the ECM.

Let me know when you need someone to try the program out.

 

Should have a version ready for you to test out Dale. You will need to install the .NET framework in order to run a .NET program (which this is being written in):

http://www.microsoft.com/downloads/d...displaylang=en

 

well that i understand, in c++ the gui are a pain to do, and look horrible. But i wouldnt do something like this because im not THAT good with programming, however for my senior project i am making a simulation with c++ and ogre3d(hopefully) or irrlicht graphics engines that will be a realistic 3d drag strip simulation.(with thirdgen camaro)

sorry for the crappy remark earlyer...

 

Thats alright, no harm done. I am by no means a short tempered person and understand why you would state such a thing without getting further information. I myself follow the general rule of thumb that I shouldn't open my mouth until I know my foot won't follow into it . Its just the program is not complicated enough for me to justify writing it in C++ to make the GUI. The GUI and displaying the data neatly in this program, a burden that would hinder the hastening of releasing the full version is totally nulled when I write it in Visual Basic. It basically boils down to:

Wait for chatter packet when the port is open.

Send request packet immediately after recieving a chatter packet.

Check to see if the port is recieving the requested data which is a 63 byte packet (it also sends back the echo of the request packet, so the actual packet size is 67....the request, 4 bytes and the sensor data, 63 bytes)

After recieving this packet, check to see if it an okay packet. This is done by adding all of the bytes in the 63 byte packet and it should equal a certain amount that I don't have with me here at work.

After verifying the packet was good, translate that sumofabitch into actual sensor data.

Request another packet

Wash, rinse, repeat.

I find it hardly practical to switch programming languages for something so simple.

 

I thougth the packets were pulse width modulated? How're you reading the pulses? Just curious, see if you can help me get on the right path

 

Pulse width modulated? Don't follow you there Doward.

When you open the comm port, the ECM should be sending out chatter packets consistently (F0 55 BB in hex). After recieving one of these chatter packets, you must send a request packet immediately after recieving one. Its a hit or miss. I used a loop to wait for one or if 10 seconds passed just give a msg box to try again. After recieving your first data packet, just send another request to get the next one within a 10ms interval. That is all I do.

(serial is the what controls the comm port)

do until chatter_r = true
serial.Read(3) ' (read three bytes of data aka chatter)
if input > "" then '(if the serial.read data is greater then 0)
if input = chr(240) & chr(forgot) & chr(forgot) ' this is F0 55 BB in the form the ECM is sending and recieving
then chatter_r = true
end if
end if
loop

After that

do until good_packet = true
input = "" ' reset input
serial.write(request_packet) ' send request
serial.read(67) ' read 67 bytes from the comm port
if input > "" then
if mid(input 4, 3) = valid_packet then ' Start with the 4th byte and 3 after and check if they have a good header
good_packet = true
end if
end if
loop
After that just translate and do a loop to send another request.

Sorry if it looks horrible on here, im heading home now and if you have any more questiosn i'll be glad to help.

 

http://www.geocities.com/pasky13/newwinaldl.zip

Cut in paste into the browser.

Remember to install .NET framework

Let me know what that gives you Dale or whoever else gives it a whirl. I wrote a msg you won't forget if it works .

 

I just got done fixing my fubar from last night. I'm dl the stuff right now and will install and test tommorow night.

 

Sounds good.

BTW doward, thats not the actual code but gives you an idea.

 

On the 160 baud rate, I was told that the data is not in nice 'packets', but a 25 byte pulse width modulated datastream. Long pulse = 1, short pulse = 0, that sort of thing.

I'm curious as to whether the 8192 baud is the same, or if it's just my ancient ecm I'm dealing with?

 

It no worky

 

8192 is not the same. It comes in 63 byte data packets.

Dale:

What error did you get?

 

I didnt get an error, acted like it didnt even want to connect.

I tryed the older version, got an error msg, but didnt right it down as I figured you didnt care.

 

Did you select the correct com port? It should have exit the sub if it didn't recieve any data after trying 10 times and gave a msg box "could not connect". I'll code in a few more steps tonight that way you can help me keep track of how far it actually got.

 

First time I didnt select com port

Second time I did, didnt act any different(maybe I need to try all ports, but I only have 1 9pin plug).

I'll set it back up later tonight, and wright info down and/or take pic of the screen.

 

Yes, you need to make sure its the correct comm port. I don't havn't written anything to tell you it was the wrong one. I may have not even given it enough time to try and recieve a chatter packet so i'll fix that tonight and give it 5 seconds.

 

Updated it Dale:

Set it to wait 5 seconds for a chatter packet and if one was recieved it will open a msgbox and tell you.

It will also tell you if one wasn't recieved.

If you do not recieve either one of these msg boxes then you are not using the correct comm port:

Lets do this one step at a time. If I know this part works, i'll move on to the request. If I can request then we move on to translating it into real sensor data.

http://www.geocities.com/pasky13/newwinaldl.zip

Thanks for helping dale.

 

just dl it.

If I can find extension cord at work, I will test at lunch. Didnt bring my car adapter with me

 

Crap, noticed an error in that dale, just uploaded a new one version. I had it to loop while the chatter = true. Changed it to false. Go ahead and download it again please.

 

found another error on my part, fixed and uploaded a new version at 2:21PM (CENTRAL) 10/25/04

 

Updated again, 10/25/04 8:08PM (CENTRAL)

 

I just tested it, it is not recognizing any of my comm ports. I tryed hooking cable up both ways on my car.

That is, using both left ports. A and M I belive?

This is also the version that was useable at 6pm.

 

use the latest version and you need to use the right most ports (Towards passenger).

 

BTW dale, you have a dual snorkel setup or can come by one? Im in desperate need. PM if ya can give me a hand.

 

...

 

Nevermind, let me attach it, got one more left for this thread

 

ops, I said left, I mean right. I was using correct ports.

I'll try new version tommorow. Fixing to head to bed.

I have my own dual snorkle. KED 85 had a set forsale, contact him. If he cant help you out, I got 2 other contacts.

 

I can't think of any reason why this isn't working Dale. I corrected all errors.

Try this dale:

http://www.geocities.com/pasky13/RS232.zip

its just a basic comm port program, but select one of the comm ports and just open the port and set the baud rate to 8192. Set bytes to read to 10, im not sure on the status line, try all four, won't take long and set timeout to 5000. Then press the RX button near the status line and it will check the serial port for data. Allow it to sit for a while and see if you get a chatter packet:

F0 55 BB

If this one works, its definately my end. If not, check if your cable, serial port or ALDL port is damaged. Try both comm 1 and 2.

 

Dale, you might need to enable ALDL mode, via a 10k resistor across A and B.

 

Doward Huh?

Never heard of that.

Just DL new aldl, and that other thing you linked up. Will try at lunch.

 

Some of the ECUs require that you run a 10K resistor across terminals A and B in order to 'activate' ALDL mode. You then shut it back off, once you establish a link. Might think of wiring a switch from the back, with a 10k resistor in place, and see if that helps.

 

Don't need the 10K with the '90-'92 ECM. It isn't required and will put the ECM into a diagnostic mode.

Pasky, if you still have your stock ECM you can use it for testing. Just toss it on the bench and wire up +12 volts and ground to it.

Then pickup the ALDL output to your PC/Laptop through an ALDL cable. That is all that is required, no sensors or any other wiring needed.

RBob.

 

Hes got for a few more days. dont be telling him anything thats gonna fry it :nono:

 

Now would I go and do something like that Hmm, maybe I should post the pin numbers. . .

RBob.


{edit, pin numbers}

A8 - ALDL serial stream

A12 - ground

B1 - +12 v
A6 - +12v

Need +12 volts on both pins, one is battery and the other is ignition.

The pin numbers and connector referance letter can be found imprinted on the inside of the connector, next to the pins.

 

I was playing bob, you seem to know your crap.

Pasky. I just tested. Still not getting comm port connection.

I tryed that other program, and it "appears" its good. Says com port is avaliable. :shrug: