I have been using Winaldl from my laptop to capture data from my '87 GTA 350TPI. I recently downloaded tunerpro RT to be able to use the 8192 baud rate. I have gone through the setup for the com port 2, which is what my Winaldl is using at the moment, but I can't get any data from the ECM using this program. I have selected the definition file , 32bv.001.ecu and set the selection in setup on tunerpro to 8Hz. When i push connect to Ecm at the bottom of the screen, is shows monitoring but there is not data show on the sensor status screen. The packet count at the top right of the screen increases rapidly which apparently means there is no response back the Tunerpro program but the monitoring frequency just below that box shows 7.9Hz or so???

Wondering if I am overlooking something. I am running the 165 ECM and $32b mask and I am also using the homemade RS232 cable to plug into the diagnostics connector under the dash. I have used this cable always with the Winaldl program.

Any thoughts feel free....Thanks.

 

You need to also load the correct ".ads" file for your application.
Click the button with ... on it to open the browser window and select it.
The .ecu file is used for the editing functions, the .ads is used for communication.
Hope that solves your problem.

 

Already have tried that. The definition file I have selected is TunerproRT\Datastreams\1227165-160baud.ads. This is the only file that was listed that I could use.

Thanks for the response.

 

Does $32B use the same 160 baud datastream def as $6E? Does $32B even support 8192?

1227165_160 was built for $6E. I'm not sure if $32/$32B is the same.

 

I'm not too sure what's supported exactly. I guess I'll have to go back tomorrow and check out the website. I talked w/ Craig Moates and he said that there shouldn't be any problems.

I guess we'll see.

thanks for the feedback.

 

No, no. Your setup is supported, theres no doubt about that. Especially on the hardware side.

What I'm getting at is that you have to have the correct datastream definition to datalog! I don't think you're using the correct datastream definition (ads file).

 

I thought the 32 mask was just 160 baud? It's been a long time since I used that anyway.

-- Joe

 

Not sure. I could not find any info at the tunerpro website so i shipped off an email to Craig Moates.

 

I am having trouble getting data from the stream. TunerPro says that it is connected when I use the mask above.

Is there a place to get a $32B ads file for TunerPro? I think sparks454 and I are having the same problem.

 

I did get it to work. I went into edit datastream definition file and changed the 6E code in the code mask section to $32b. I'm not sure if that really makes a difference.

To get it to work it looks like the box that says 160 baud next to it needs to be checked. It did not work for me until is was checked off.
I followed the instructions in the help menu to replay, and it does not look like anything is happening. Now I just have to figure out how to replay the data. It takes some time to work through all this stuff.

-Chris

 

I am not getting any data at all, but I will try it again to see if I can get this thing to work. It seems to connect fine and doesn't give me any problems, but the sensors all look dead.

thanks for the update

 

You guys sound confused (or maybe I am).

There are two rates of output for GM OBDI ECMS, 160 baud and 8192 baud. Furthermore, each ECM outputs its data in a different manner, and each outputs different data.

TunerPro supports both types of output. You need to provide the correct definition file (ADS file) for your ECM. That definition file tell TunerPro how to connect to your application (in the case of 8192), and tells TunerPro what to do with the data that is outputted (both 8192 and 160).

I'm almost positive that $32 and $32B only support 160 baud.

So, for 160 baud, yes, you need to have the "160 baud" checkbox checked. In addition, in order to get valid data, you have to have the packet sizes set correctly.

160 baud interaction with TunerPro will be much better in the next release (4.0). If you need to create a $32/B datastream definition, start with the 1227165_160.ads file and modify it to match your ECM.

To get the ECM's 160 baud data template, download the following zip file and find your application in it. Use that to create your ADS file.

http://www.moates.net/files/4)%20Datastream%20Definitions/ALDLstuff.zip

Hope this helps.

Mark

 

Furthermore, changing the mask in your bin to $6E does nothing (good).

If you want to run $6E in your 1227165 car (which both of you can), burn a $6E bin to your chip and disable your cold start injector.

$6E can utilize 8192 baud.

 

That's useful info. Thanks for clearing that up. And yes, I only was able to see sensor data change when I selected 160 baud.

So it makes sense that only the 32mask is 160 baud only.

Thanks again.

 

the 32B mask can use 8192, i've done it. thats the 10K resistor jumper, you might need to do that, don't remember if you said you did that.

not sure about the 32 mask.

craigs aldl software can do either 32B or 6E, and i'm not sure he uses two different 'masks' for the datastream format.

the aldl.zip contains info that shows the 32B and 6E masks use a different definition, but maybe they are really close??

 

If ECM852 works with $32B, then you can use TunerPro with the 1227165_6E.ads file.

 

Doesn't that 10k jumper bring your idle up to like 1500 rpm?


-- Joe

 

Thanks guys. I do have the 10K resistor in place and the car does idle at about 1400rpm with it in there.

I will try the 165 6E datastream definition and see what happens. I know for the 6E there is no cold start injector used, but Is the 6E still for a MAF car for data logging purposes?? In the definition it is listed for a '89, not that it makes a whole lot of difference.

Thanks,
Chris

 

the idle goes high with the 10K in place, I think until the higher baud rate starts working, then it drops back to target idle. either that, or i dreamed that it did the last time i collected some data.

these ecms start chatter at 160 baud, and request the higher baud rate, then when the link is established, it automatcally switches, otherwise, it stays at 160baud.

 

$6e is the newer mask for the 165.. Personally, i'd switch to that if I was you..

-- Joe

 

I was looking at doing that maybe next week and started doing the research on that last night. If I go with the HSR setup I will have to do that anyway to remove the CS injector right???

It appears to be as simple as burning the 6E bin to your chip and then making sure that your tables from the 32 bin are all there. Let me know if that's accurate...

Thanks,
Chris

 

Once you establish a connection, you can remove the 10k, thereby getting rid of the fast idle (and advanced spark).

 

i just looked at both aldl definitions for the 32B and 6E, from the aldl.zip file that is floating around(def's A28.ds and A59.ds). they are extremely close, with three minor differences.

vats flags(used on 6E, there, but not used on 32B)
power steering cramp (used on 6E, there, but not used on 32B)
byte 59, cars mode word, different from 6E and 32B, but looks to not have much relevant info(for scan and tune purposes)

the 32B will most likely work with the 6E ads file.

 

Sweet. Thats good info for me to store. Thanks!

 

Okay so all I have to do is create a $6E copy of my $32B chip. Disable the VATS, CS injector, and match the other settings to my $32B and put chip in car. Then use the $6E ads file and it will work?

 

Nope. You don't need to use 6E (although its still recommended). Just use your 32B and use the 1227165_6E.ads file to scan it.

If you decide to go to 6E, don't simply make a "6E copy" of your 32B bin. Start with a 6E bin, and tune it. If you have a manual car, use ANZA, which is included with TunerPro.

 

I just tried to connect to the ecm using the 165 6E datastream definition w/ no luck. I am using the 32b chip yet. If I change the definition to the 165 32 it works. ??

I was going to transfer to the 6E mask maybe tonight, but looking at the arap code I have downloaded, my car is automatic also, the tables are not even close to mine. ie, the Maf tables show 0, 98, 0, 97, etc....starting at the zero volt mark. I'm curious as to how you can start with a bin like that. Maybe I am just used to tinkering with the 32b bin, but that 6E arap bin looks a little off to me. I can't believe the car would even run that way.
I am also aware of the major spark advance.....

Maybe I am overlooking something and that's the way that bin works, correct or not???

-Chris

 

I'm not sure what you mean by "If I change the definition to the 165 32 it works". Can you explain?

Also:

1) What hardware are you using to connect to the car?
2) How do you have TunerPro configured with regards to ALDL?

 

Well, now I am lost. I have tried to use the 1227165_6E.ads file and I get jibberish in the speed box and 1 packet error. It says it's connected, but I do not receive and data.

Let me try to cut this down a little bit.
In 'preferences/ALDL' I have set it from COM1 to AutoProm and left it at 10Hz. In the $6E definition file I have made sure that the 160 Baud box is checked. On the AutoProm I have the vertical switch in the furthest up (160) position and the horizontal switch in the left (ap) position.

Does this all sound right? Is there any other settings that I missed?

 

I really need to spend some time this week fixing the '749 $58 definition. Theres still a lot of problems with it, including a few I introduced when I submitted an update to Magnus.

-- Joe

 

No, doesn't sound right.

If you're using the AutoProm (and are not in passthrough mode):

1) Set the ALDL Interface type to AutoProm
2) COM should be grayed out (the AutoProm is auto-detected)
3) Click OK
4) Put the horizontal switch towards the USB/Serial port on the AutoProm
5) Put the vertical switch all the way towards the top (this places 10k between A & B)
6) Load 1227165_6E.ads file. *do not* check 160 baud (leave uncheced).
7) Press connect until it connects.

** If it doesn't connect, attempt to connect in passthrough mode:

1) Set ALDL Interface type to MAX232/2-Trans
2) Set COM to whatever COM port your AutoProm is using (if USB, probably 3, 4, or 5)
3) Click OK
4) Put the horizontal switch AWAY from the USB/Serial port
5) Put the vertical switch all the way up.
6) load the definition (as before, do not check 160 baud)
7) Press connect until it connects.

M

 

Hit the SyTy forums. I'm working with some guys over there to get $58 working better.

 

Cool, I will try it first chance I get. Sorry for all the confusion.

 

Yeah? Didn't realize. IS there a more current ads file I should know about?

I noticed with back to back testing, the math is wrong or something with the current .ads. It shows different numeric readings than when using datamaster, for example.

-- Joe

 

Yes, there's a more current ADS file. Its not perfect yet. Turns out the SyTys ($58 in general) is a real beyotch to connect to (they're very, uh, verbose). I have to make some changes in the next version of RT to support connecting to these beasts in a user friendly manner. For now, there is a "hacky" method for connecting using TunerPro RT.

 

I was trying to get moates software to connect to a '749 for about a month. I gave up..

Thanks for the ads in email. I appreciate that. I'll give it a whirl tonight..

-- Joe

 

I have been following along in this thread since it started, since it's pretty close to my setup. Today I had some time to waste so I decided to play along. I have an 85 Vette, that I switched to a 165. I have not scanned the car since the swap because my cable broke. I built a new cable a few weeks ago, but still didnt scan the car (the car isnt driven, and its actually quite disassembled due to ongoing painting), so today was the day.

First, my new cable didnt work. So I took it apart, found a few problems, and put it back together. I downloaded Tunerpro RT, to try the ALDL communications part. I couldnt get it to communicate either, just like the others who posted. I have a 165 running an AUM OEM chip/$32 from an 86 Camaro (its the chip that came in the ECM). I set the data stream definition to 165_ 160 baud and made sure the 160 box was checked. I got data, but it sure was crazy!!

I just idled in the garage, and revv'd it a few times to see changes. I had off the wall temp readings- like -40degrees, and I saw like 200 MPH, rpms were all over the place, every reading was like reading a bin through the wrong ECU file. SO, I removed my prom and made sure it was the AUM as I remembered- and it was. Then I went out and started WinALDL, and its readings were normal- except the temp reading. Yesterday I got a code 15- something temp voltage- so I understand if its out of whack on both programs. My inlet air temp reading is also way off on WinALDL, showing 7 degrees F (its like 90 out right now) with a hot engine. The digital guage on my cluster shows engine temp at around 220F, and it came up from cold as normal.

The bottom line is that I think the ALDL definition is farther off from 32 to 32b to 6e than has been thought. Unless I just have some other problems going on- which is quite possible.

Then I tried to burn a new prom, to switch to 6e. I have the moates GP-3 switcher, with 29F040 chips, and an Epromer6, that some may remember wouldnt burn the 29F040's even though they said it would. I got that sorted out with the Epromer folks a few months ago, but wouldnt you know it- it wont burn the 29F040 today. I tried two different chips too, one burned once, one never burned before.

Then I burned an APYP (6e) doubled onto a 27c256 chip, and it wont run at all.

Today was very frustrating to say the least........

Did anyone get any farther than me?????

 

$32B is reasonably different from $32. I think $32B is closer to $6E than it is to $32.

That said, again, I'm unsure how close the $6E 160 baud definition is to the $32 160 baud def. You may want to confirm.

I feel terrible that this stuff isn't working out "easily" for you guys. I do my best to create the tools you need to get yourselves going (formats that allow you to create your own definitions).

All I can say is, this will get better over time (leaps and bounds in the next release alone). In the meantime, I'm willing to work with you guys to make things work.

 

We're trying!!!!! I guess you can say that. I have the same problem with the odd sensor readings using the $32b mask and 165 32 definition w/ 160 baud. Screwy rpms and temps. Even not running with the key on the rpm kept jumping between 2500 and 0 and 200...etc...etc...I don't know what to make of it.

I really like the fact that Mark compiled all the programs, prom burning, aldl logging, etc into one program. I guess the bottom line is that we all have upgrade our bins to the 6E mask for things to work out for us. It really appears that the program, for whatever reason, is not working with the 32 mask at 160 baud.

Really not a big deal I suppose. I will try in the next days or so to update my bin from the $32b to the 6E.

==Chris

 

Theoretically the program should work with whatever you throw at it.

Theoretically.

You shouldn't have to update to $6E just to get it to work. In fact, if someone says that moates's sofware works with $32B, then TunerPro should definately work with $32B with the 1227165_6E.ads.

Anyway, the next version should be even more solid.

M

 

I dont blame anybody for it not working, hell- it could be or could have been my car just as much as the program. It is nice to hear im not the only one with funny readings using it. That's a lttle relief right there. I greatly appreciate everything everyone contributes here, I just hope I can learn and retain it.