I will update this thread with the newest version of the bin as it's updated.

*****This is a TEST BIN*****
USE AT YOUR OWN RISK.
YOU ACCEPT ALL LIABILITY IN RUNNING THIS IN YOUR CAR.

Please consider donating. I have put a ton of time and effort into this and to keep me developing please Donate. Include Any features you request!

DONATE

Features:

Timing tables expanded and extended to 200kpa and 6400rpm.

VE Upper table expanded and extended to 200kpa and 6400rpm.

MAT Timing adder table.
ADDs to timing output of upper and lower rpm Timing tables.

MAT VE adder table.
ADDs to VE output of upper and lower rpm VE tables.

KR CEL Flash
Flashes CEL when MAP above chosen threshold and KR above chosen threshold.
This feature is not perfect. It flashes CEL at keyoff. It also illuminates the CARS light when flashing CEL. Will be fixed in future updates.

 

Space saved.

 

Another space saved.

 

The Donate link does not work.

Does this require a modified ALDL definition to show map > 100kpa ?

Also, have you considered adding a 'boost' term to ALDL to be reported in a separate column?

-- Joe

 

I was wondering if I'd ever hear about the donate link! EDIT: FIXED

Yes, I will let my ADX file out too. And when I do I'll add boost. Good idea. The bin already outputs the Baro (logging variable 37) so all you have to do is subtract that from the MAP reading to get the boost/vacuum reading and convert from kpa. But, without my datalogging laptop in front of me I can't post up my ADX file yet.

 

Subscribed. I also have a 92 LB9 which I plan on boosting, auto tho as opposed to your manual.

I've been looking for a potential bin to use as base for tuning when I go to a ProCharger since I refuse to use their crappy FMU lol.

I a ways away from the upgrade but I'll be watching this...

 

ADX uploaded. Use MapLoad for Map kpa readings.
No boost yet.

 

Are you adding wideband support?

(For either just ALDL logging, or narrow band replacement)

-- Joe

 

Yeah it's already written in there. A couple edits in a hex editor and it's ready.
For now just for aldl logging.

It can read two pins easily right now.
F14 and a3? I think.

Code starts at f1d4. Add bdf1d4 to jsr to it but you'll need to know what you're doing to do that in the right place.
I can't tell you an easy place or way as I've already changed the code and addresses for new upgrades.

 

Actually f8c3 might be the place to put that. Then put 39 after to return to subroutine.
But again, that may be WRONG as I don't know if I changed that part.

Then you'll have to edit the aldl pointer tables to datalog that. And make the xdf read it and convert the value to voltage or to afr or whatever you prefer.

 

I have a wideband patch that will read 0-5v, and stuff it to ALDL overwriting the target AFR (so it will work with commercial scanners i.e datamaster). But having it on a new ALDL term would be great.

I wonder how much work it would be to modify the closed loop code to use wideband rather than narrowband. If I recall currently in interpolates between two voltage constants, and calculates how long it switches in each direction to determine stoich.

-- Joe

 

It wouldn't be a "new" aldl term, but it would replace one that I'd rarely if ever use. There are some that aren't even defined in the ADX files I've seen so there's certainly places to put whatever I want to log.

Definitely something I'd have to research and tear into. I don't know if it's worth it though. Narrowband has always worked just fine in a well tuned car for me.

Utilizing the Wideband input for other functions such as pulling timing if lean or even cutting fuel altogether or flashing CEL if WOT and leaner than a threshold is something I'll do more than likely.

 

Using wideband input for CL is straight forward. Make a new variable for WB2NB. When the WB value exceeds X then WB2NB reports lean, and vice versa for rich. Only one RAM and 2 ROM locations needed. If the WB2NB is in error, I resort to reading the stock NBO2. If you add a table for the lookup you can make the target AFR what ever you want it to be vs map and rpm and or speed. It works well.

 

However code $59 does it, that works well imo. Its def nice logging airfuel but can get away with out it

 

People are downloading but not saying anything. Are you all just looking at blank or boring tables in tunerpro??

 

Yes, kinda. I spent about 40 minutes looking at it. I don't have a '730 in the shop to play with it.

If I have more time in a few weeks, I'll get a '730 on my test bench and play with it a little. I wanna make a tunercat TDF for it though so I don't have to use tunerpro.

If I pick up another C4 this fall, which is possible, I might give it a try on the road.

-- Joe

 

Very cool. It's pretty useless unless it's a boosted c4, but let me know if you have any complaints or questions/comments.

 

I always boost my C4's.

-- Joe

 

If i still had my turbo on the 305 i would be all over this. But that ship has sailed

 

If I get my hands on another third gen then I will be sure to test the code out just moments after I get the car to my house, so hopefully by then there will be features galore added. I will say though, and I'm sure many here will agree, it is refreshing to see someone actually accomplish this within weeks of setting out to do it. That says a lot in my book, and it shames quite a few who were running around in circles with their versions of a boosted $8D code that has been going on for almost a decade lol. Well done Vanilla, and like I said in another thread, you are a credit to this website.

Now, if only you can get RomRaider to work with these cars...

 

Thanks and you can definitely blame romraider for my coding ability. And working on new code makes these old computers scary simple. It's INCREDIBLE how much they've put into new ECUs.

 

Just tested my Wideband code. Ready to let it out for testing for anybody ready/willing/able.

 

Well i think i might just turbo my 305 car again...i wont be getting anywhere with the bbc build anytime soon so might as well rig up a cheap front mount, buddy has a 7875 for cheap so might give this a shot and test

 

The both of you need to install the turbo and run the bin, although Orr will have his done faster though because Vanilla is getting ready to paint as well as being in the middle of a restoration. I wanna see the results guys, long overdue, so get to it...!!!!!

 

More like 7 months, but we get your point.

I give him big props. A few more features, and maybe $35 in electronic components and it will be a DIY EBL.

-- Joe

 

5 months. And it was ready before that. And was and is still on a backburner.

 

You gotta excuse some of these guys, they are stuck in that same thinking. Traxion learned more from the Subaru guys after leaving here, which is why he more than likely never came back. I know Bailey supplies some of the Import guys too, so his thinking was different early on. This is what I meant when I said they're stuck on V6 code Vanilla, aftermarket ECU's were the only real option for the early DIY guys here because they couldn't transcend with what they had. Meanwhile, other websites were doing it with their eyes closed...

 

You still think v6 code and v8 code differ greatly? Interesting.

-- Joe

 

Still no interest in adding the NVSRAM code to it ?

That, IMO, is why $12p or whatever it's called is so popular on the other forums.



-- Joe

 

I'm already running the bin! Just not boosting it... And you're right about me. I'm a ways out from a turbo still. Lot to get accomplished prior. Plus it's fun driving a car to its limit on the street and staying legal for an hour and a half at full throttle trying to get to 60.

 

Oh I already knew you were running it, but we gotta get the two of you running it with the turbo's. If Justin does go front mount, it might take him awhile to sort everything out. If he goes rear mount again, he could probably be running the code this weekend with boost...

 

I constantly think about NVSRAM but not for flashing. For more features. Problem is that I like free. And I like sharing free stuff for people that can't do it on their own to further the community. The NVSRAM addon is a HUGE undertaking for 99% of people here. If it was plug and play and free I'd be all over it.
But I've worked around my love for ram with hard coded immediate lookups. Just as easy to do and don't tax ram space.

 

I understand where you are coming from, and I'm not criticizing your position. I just see the benefit to a single cable flash & tune configuration. One of my biggest complaints about the stock stuff (using a rom emulator and ALDL scanning) was two cables, two com ports, and the related software.

I agree though, building the NVSRAM stuff is probably too much for most users.

This was one of the things that I just couldn't wrap my head around with the EBL. All that work, the hardware mods, etc and you still are stuck using tunerpro to edit it. I really think he could have hit it home if he had written WUD to be a full tuning + logging GUI like Tunerstudio.

Which brings me to the point I was getting at. In theory, Tunerstudio should be able to work with the NVSram board. It would take some time to do all the .ini files, but it would be pretty darn cool if you could log + tune your modified $8d code with Tunerstudio.

-- Joe

 

I don't have a need for an emulator, so I only have one cable.

While it would be nice to have, it too is not necessary and is another expense not needed by anybody.

This is such a simple setup and burning a prom is too easy. I just like simple and free.

 

Agreed with simple and free, shouldn't make it too complicated for the user. In my opinion the idea is synonymous with $8F, just drop it in and go as if it were a stock boosted $8D prom, but with some features for the user. That's what it's all about...

As far as the EBL is concerned, I have a windows tablet where the radio used to be that does everything for me, and I also have a USB port ready dashboard. I only use the laptop for Tuner Pro because of the larger screen and I am used to the mouse. Not sure how much more people really need to be happy...

 

Right, and that's exactly what this is already. A drop in "tune." If you can load a tune you can use this .bin.

I said from the beginning that I like to make the backend incredibly complicated to make it simple for the user.

One of my plans is to make an XDF with an address list of ram variables for easy tuner pro logging changes without having to go anywhere extra. Then an ADS/X file could have them all commented or uncommented in order to read anything you desire quickly.

 

If I had my chip burning stuff id try it. I lost it when I moved years ago. I don't feel like buying that stuff again since im swapping to 411 ecm over this winter.

 

ugh. I have nothing with boost either. such a shame.

 

what makes you want an $8D boost tune? isn't code59 sufficient?

while burning chips is easy, there's nothing like sitting in the car with a laptop and adjusting parameters on the fly

 

code 59 while I liked it a lot. it did have a few missing things for us v8 guys. 8D has a lot more idle programing and considered more refined. which also made it harder to tune for me. I did like the lean cruise in 8D thou. but the target a/f excel spreadsheet for ve tables in 59 was really nice too. options are good. and this would probably be easier if your starting out with a stock car. no repinning or anything.


either way, any coding of this older stuff is good.

 

For the beginning starter tune, the $8d is much easier to start with and work with. I have tuned both $8d and few $59 deals. The initial conversion of a $59 v6 file to v8 turbo was rather difficult and time consuming. Runs good once you have a working v8 file and fuel maps are good.

 

Code $59 isn't what I started with and far easier to control everything when I control everything with no worry of other people's tangential projects and needs.

I've said it before: overrated.
And if I ever care to have that I'll get an ostrich.

 

on a side note, does this happen to have a 4 cyl switch?

 

Interesting project, any chance this would support 3 bar in the future?

 

It could easily support 3 bar with a few changes. You'd lose resolution and I've been told that drivability suffers a tad.
I can post the diff file and all you'd have to do is trace where the MAP is scaled alter it to values I posted in the dev thread then alter the tables a bit to deal with a different resolution. Basically the same as I already did except the diff file will show you where.

 

Well I'll be honest it's been years since I looked at this stuff or even my car for that matter. I would have to relearn a bunch of this but when I get time I'll look at it if you want to post the file.

 

You know what, you're right. I'm going to clean up this thread and move it to DIY PROM where it belongs.

-- Joe

 

I should be ready to do some boost testing by the end of the month if all goes well.
This has been a long drawn out project but its every close now.

 

I downloaded the files a while back but just now getting time to really look at them. My plan was to transfer my SAUJP data into this one to give me a good starting point. I'm not seeing where to select which VE tables to use. I'm was assuming this is kinda based on SAUJP, maybe thats where I'm going wrong.

Has anyone tested this code on a boosted car yet?

I wish I knew how to write code but wouldn't know where to start.

 

Expanded/extended are the only tables needed.
No feedback has been received so this is untested under boost but I am personally running it and have been for about a year.