Just got the Ostrich and TunerRT...getting started ?'s

[eclipsegst1990]

First of all, my flashdrive died today, so all the data and research I had for getting started with this unit is gone (bookmarks).

Anyway, I'm wondering whether I can set up my MAFT for stock injector size and then use the Ostrich to continue with my tuning until I am able to acquire a GM-map sensor and IAT? I know the point of the ostrich is to get rid of the PITA MAFT, but for now, I need to use it. I figure just set up the injector compensation for my PTE680s at 640 and set MAFT to the 450's. Also, is there a tech article that can help me get started with the Ostrich? I thought I saw one of these on this site, but of course, my bookmarks are gone and I don't have the site listed anymore. I'm anxious to get moving here. I do have some base-extended maps thanks to a fellow member.

Just to confirm, in the spreadsheet in turnerRT, (AFR) load is the Y axis and rpm is the x axis, correct? Geez, I have a lot to learn and read, so please don't flame me...I've had too much bad luck lately. How did all of you get started?

Thanks everyone and I'm glad my MAFT headaches are almost gone...
Brian

 

[1qkfwd]

I used the search bar plus I found this web site
http://autos.groups.yahoo.com/group/dsm-ecu/

They have over 6000 differant posts right now and there is a lot of useful stuff.
Do what I did and start from post one and that will give you an idea what you are looking at.

 

[eclipsegst1990]

thanks.

BTW, my 680's are compensated at a 640 airflow, does the program automatically adjust the dead time? I believe the dead time is 300, but at what voltage? I get 18.7v to 4.7v and anything remotely close to 300 is at 18.7 which is set at 456. I'll check the yahoo groups so I don't have to ask another FAQ.

 

[1qkfwd]

You do have to figure out the deadtime this web site might help with some of the definitions: http://users.wpi.edu/~ktarry/dsmtech/dsmromedit.html

 

[eclipsegst1990]

got it! Now I'm getting somewhere...thanks.

 

[1qkfwd]

Yup no problem.

 

[eclipsegst1990]

As posted above, is it possible to use my GM MAF with the Ostrich and TunerRT? I have the MAFT still hooked up, but I set it for the stock 450's or should I just zero the thing out? My idle sucks right now and my car running rich. I think there is a conflict with what I am doing with TunerRT and the MAFT. I do remember reading that the GM-MAF is close to the 2g MAS, but I don't remember where.

Anyway, I've adjusted the dead times accordingly by adding 12 to 12.5 to each voltage value in TunerRT, but it didn't seem to fix anything. When I have my injector compensation value set for 640 (along with the above), my car runs so rich it won't continue to run. However, if I use the slider in TunerRT "injector compensation" and move it toward the 280-300 mark, the car begins to idle better as the value gets smaller. Should I adjust it somewhere in the middle? Remember, I have a GVR4 and I do recall that the ECU setup is a little different. What am I doing wrong?

Thanks in advance. I just don't want to blow anything up when I drive the car.

 

[eclipsegst1990]

I assume these are the stock dead times for 450's as listed in TunerRT.

456.00
552.00
648.00
840.00
1152.00
2112.00
4056.00

 

[notsofastdsm55]

yup those are the stock deadtimes, you'll have to add deadtime(say 330 for 950s as an example) to all the voltage values. after that you'll have to log your fuel trims to see if you deen to adjust your deadtime like in dsmlink!

though I don't have an ostrich yet, I use tunerpro as well. also in the fuel and timing tables you should change the load table to g/rev instead of low,2,3 etc. I believe the off shoot of mmcd(the unofficial site) can log g/rev. which would making finding out exactly what cell your in while tuning much easier!!! If you want I can send you the file for the load values on both the stock maps and the extended ones. I would post it here as I got it from zenja but I don't know how he posted in the window/box looking thing

 

[eclipsegst1990]

Referring to the "Re: Wideband Code Modification" as found on DSM-ECU forums (see below): I found the old address and data located as follows by using the offset.

00005690: 57 BD EB 6A FD 01 55 8F E6 10 0E 03 E8 C0 96 CE [then the ascii box]

My question is, where is the rest of the line they list below? "d69e: 96 ce ldaa *0xce // O2 sensor"

I see the 96 and CE in the code, but where's the rest? Are they referring to the ASCII lines? Where do I put the ldaa *0xce // O2 sensor code?












Re: Wideband Code Modification


> Hopefully someone's got the full info. Does this simply require a
> wideband sensor, or does it also need the electronic box that the
> wideband o2 plugs into?

You MUST have the WBO2 box, period. Replace the stock NBO2 signal to
the ecu with the WBO2 box wideband 0-5v output.

>> I'm wondering if anyone's got a version of the
>> fixed code, or at least knows the link to that message.

See previously mentioned msg# 3267. Code changes are very simple -
Nick's got it all below and adjust your 80 / 7a WBO2 trigger points to
taste.

Works fine, no hiccups. It really is this simple - 10 code changes. I
set all of my triggers the same to get max cycling [~2.6Hz], YMMV.

Kyle "BlackHole"

*****************************************
> // old
> < d69e: 96 ce ldaa *0xce // O2 sensor
> < d6a0: 81 1f cmpa #31 // if O2 < 31 (.5v) (lean)
> < d6a2: 24 03 bcc 0xd6a7 // (branch carry clear)
>
> // new
> > d69e: 96 ce ldaa *0xce // WBO2 sensor
> > d6a0: 81 7a cmpa #122 // if WBO2 >= 122 (2.4v) (lean)
> > d6a2: 25 03 bcs 0xd6a7 // (branch carry set)
>
> d6bf: d6 ce ldab *0xce // WBO2 sensor
> d6c1: c1 7a cmpb #122 // if WBO2 >= 122 (2.4v) (lean)
> d6c3: 25 03 bcs 0xd6c8 // (branch carry set)
>
> d7fc: 96 ce ldaa *0xce // a = WBO2 sensor
> d7fe: 81 80 cmpa #128 // WBO2v >= 128 (2.5v) (lean)
> d800: 32 pula // a = O2trim
> d801: 25 07 bcs 0xd80a // if WBO2v >= 2.5v
>
> e61c: 96 ce ldaa *0xce
> e61e: 81 7a cmpa #122 // WBO2 < 2.4v (rich)
> e620: 24 02 bcc 0xe624
>
> f08b: d6 ce ldab *0xce // WBO2 sensor
> f08d: c1 80 cmpb #128 // WBO2v >= 128 (2.5v) (lean)
> f08f: 25 0d bcs 0xf09e

>> ...just change the target value 1A [26d=0.51v=14.7AF] for the
>> narrowband O2 to 80 [120d=2.5v=14.7AF] for the wideband O2...

 

[eclipsegst1990]

Found it!

I used winhex instead and expanded the window to 20bytes which gave me the rest of the code. Silly me, now I realize that the entered text is what they did to derrive the new code.

Here's the hex editor I used:

http://www.sweetscape.com/010editor/


Now lets see if the code works as planned. Now I have to figure out how to change my GVR4 stock boost gauge to a knock gauge. If anyone has anything else to add, please let me know.

Thanks again,
Brian