after lots of comparisons for the 302 bin files there seem to be much to do with this peice of junk 302 ecm. mostly i am unimpressed with its ability to stably control the injectors. after trying sevral ecms and using an ossiciscope i just found out that with bigg injectors this ecm gets hurt in a hurry.

so my new plan is to swap to a 7165 ecu and use 808 code and toss the maff. ive been reading alot on the 808 code sd swaps and it seems pretty striaght forward. my only concern is my cunfusion over the memcal and such. what am i in for ??? swapping the ecu is the easy part i wanna know whats its gonna take to make the 808 code work ???do i have to modify the ecu itself ??or is there a webpage with iunfo on it that will save lenghty posts ??

 

ok i founda nice 808 bin to start with and the ecu file !! man thats a nice ecu file. anyways i still need to know about what kind of chip changes need to be made. so in short can i just burn the new code to another eprom and then work form there or is there anything else that need to be changed ?? i know the buad will be 160 and thats fine with me. (i looked over the 808 posts else where and answered the remianing questions i had) sorry to ask.

 

I am going to assume that this is for your friends car that has a turbo on a 2.8. If that's the case, forget every option you just came up with and use a SYTY ecm and code. The only screwy thing would be the netres but you could change them.

 

no this is for a mpfi s-10 me and a friend recently where working on. his truck has a 2.8 and the feul tables are vastly to rich for the stock 2.8 carb engine. i was hoping they would be close. being the 2.8 has deid with a rod knock (due to some very abusive driving) the plan is to swap in a 3.4. but the 302 ecm had a hard time controllng the stock injectors. maybe there just bad boards ??? lot of quality problems on those. anyway the 165 with 808 code offers the tunning potential for a completely rip snort engine. it comes down to time invested.im still gonna work on tearing down the 302 code becuase i have sevral friends who have these ecus and it makes sense tro have the code out there. but for this application the 302 just doesn;t make sense.

 

I haved done a 302 -808 conversion - its a snap.

like the boys said wont work for boosted applications unless you use kalmaker or adapt the 80-8 code for 2 bar.

The memcal that came with the car or correct number of cylinders will work with it - noraml discliamer it may not run too good in limp mode but it should run

Burn the 808 code straight onto the eprom.

For the 2.8 I believe it use a different dizzy than our DFI V6 3.8 over here that uses the 808 code so I would expect you will have to change the ref angle to something like 10 deg but that is only a guess. ( I did the 302 -808 conversion about 3 summers ago)


Daniel

 

i hope im not miss reading yr post. you either are running a 808 ecm in place of the 302. or did you burn the 808 code into a 302 ecm ??? my thought is yr ruuning a 808 ecm. if so do you still have yr pin swaps handy ?? it would just be a time saver.

 

thanx for the help !!!!!! i have in my hands some things that may
stop this form happengin but well see. still going over the basics agian feul pressure, base timing, testing the harness for inetgrity.
made 127 splices to get it nto that damn s-10. goto go over everything at least 1 more time to makes sure this is a ecm issue.
guys thanx for the help! is there anything i can do to repay you ?

 

160 baud rate? Thats the slow one like the '85 TPI computer, correct!?!?!?

 

yeah 160 baud rate

 

So thats only one data point every 2 or 3 seconds? Wow that would be a huge step backwards if it wasn't a MAP system. How does everyone else feel about this? I really don't feel like loosing the accuracy of my '165 just to get rif of the MAF.

 

I've tuned a 730 (8192 baud) and a 747 ECM (160 baud). The baud rate doesn't affect your ability to tune anything.

 

the 160 buad rate is easier to data log if you ask me. put a lot of load IE high gear low road speed and floor it. the slower refresh rate means less to look through in the data captures.for some its easier the other way i geuss but its all about preference.

 

Well I guess that makes sence, but am I right when I said one data point every 2 or 3 seconds... or is it a lttle faster?

 

capture a screen refresh with aldl every 1.5 secs.