Need tunerpro XDF and ADX for 1228747 AKWA

[1leg]

That's a bad code, use a paper clip to pull the code. No need to mess with dataloging with that going on.

Also, could be a checksum error.

I tried the paper clip, but the CEL just blinks really fast. the truck still starts fine.

Where should i look to buy a new ECM? I might need a back up I need this truck running. Is autozone a good source?

[EagleMark]

Junk yard is cheaper. They usually don't go bad? Have you pulled the chip out and maybe bent a leg?

[93V8S10]

I never had one that couldn't be pulled with the paper clip, so I don't know on that one.

I always gotten ECM's from the junk yard. I've not had much luck with electronics from Auto Zone, try Advance Auto or NAPA, or maybe ask some local shops where they get there's.

[EagleMark]

Pretty sure I had a bad prom once that would not pull codes, guy put the chip in holder backwards and it would not pull codes... not even 12, just flash continuously.

[1leg]

I will pull the ECM tomorrow recheck flash chip, I'm pretty sure everything is good, this will reset the computer and i will give it one more try. Maybe i didn't get the ECM cables plugged in all the way or something like that. It's weird that it ran fine Sunday then this morning it was bad.

Could this be the reason i couldn't get it to link up to log?

[EagleMark]

Yup!

[jim_in_dorris]

I seemed to remember the flickering SES light problem being common on 747 ECMs. Moates even has a fix.

"The Socket Booster improves the signal conditioning at your chip or emulation socket. This is an active circuit which boosts the address and data information to and from your target ECU. This is a great fix for that flickering SES light on the old GM TBI setups (747, etc). Drives the information more cleanly across the ribbon cable, allowing longer cable runs (3+ feet). Facilitates both remote emulation (when used with Ostrich 2.0) or remote-mount chip installation (when used with EMUC-series emulation cable and Chip Extender 1.0 with optional S2 socket available separately)."

I ended up having to replace my ECU when that happend because I didn't know about this fix. It may be your problem

[EagleMark]

I seemed to remember the flickering SES light problem being common on 747 ECMs. Moates even has a fix.

"The Socket Booster improves the signal conditioning at your chip or emulation socket. This is an active circuit which boosts the address and data information to and from your target ECU. This is a great fix for that flickering SES light on the old GM TBI setups (747, etc). Drives the information more cleanly across the ribbon cable, allowing longer cable runs (3+ feet). Facilitates both remote emulation (when used with Ostrich 2.0) or remote-mount chip installation (when used with EMUC-series emulation cable and Chip Extender 1.0 with optional S2 socket available separately)."

I ended up having to replace my ECU when that happend because I didn't know about this fix. It may be your problem

I know the Ostrich needs the socket booster but the autoprom does not. I even got the longer ribbon cable for my AutoProm and still don't need it.

But your saying this could be needed even without aemulatorer?

[jim_in_dorris]

yes, I had the flashing SES on my truck with no outside connections to anything. I ended up having to replace the ECM, I didn't know about the socket booster. I would contact Craig at Moates.net and ask first to make sure, but I seem to remember it being a solution.

[1leg]

yes, I had the flashing SES on my truck with no outside connections to anything. I ended up having to replace the ECM, I didn't know about the socket booster. I would contact Craig at Moates.net and ask first to make sure, but I seem to remember it being a solution.

I will look into this. Thanks

[1leg]

I got home after work today. disconnected Bat, Remove ecu, wires looked to be plugged in and tight, I unplugged and opened ecu cover. Everything looked OK, plug ecu back in but did not re install under-dash left it laying on floor just in-case. Started truck and CEL turn off like normal. Turned of and restarted 3-4 times. every thing seemed good so i hurried to get the computer hooked up to log. Got everything working and went for a drive for a log. I will attach the log below using ($4F-1228747-LD-V1.1.adx). If anyone has some time to review the log i would like some input. I'm still learning, so if you could explain what you see wrong would be great.

Engine
Chevy 5.7 stock replacement long block about 10,000 miles
Shorty headers, custom 2.5" Y pipe. 3" single pipe all the way to back hi-flow cat and flowmaster muffler
Edelbrock TBI intake manifold.
Edelbrock valve springs.
Edelbrock cam not the TBI cam

Camshaft: Performer-Plus Part #: #2102 Vehicle Type: CHEVROLET Engine Application: 265-400 V8 (1957-86) RPM Range: Idle-5500

DURATION AS ADVERTISED INTAKE: 278° EXHAUST: 288° DURATION @ .050 INTAKE: 204° EXHAUST: 214° LIFT @ CAM (Lobe) INTAKE: 0.28" EXHAUST: 0.295" LIFT @ VALVE INTAKE: 0.42" EXHAUST: 0.442"

LOBE SEPERATION: 112° INTAKE CENTERLINE: 107° IDLE VACUUM @ 1000 RPM: 14"

[EagleMark]

Have you played back your log yet? I tell everyone to right click on toolbar in TunerPro and check all the toolbars. learn the buttons! Click the play log button, then the List View button, then the History table button, then the Monitor button. These are all good to see how your running and where your tune is. There is also a Dashboard button, fancy but fluff compared to what others are telling you. You can click back and forth with them all open in tabs at bottom.

First thing I saw was you were in open loop for over 3 minutes and RICH the entire time and you hit 230f before it started to cool down to 212f. Little hot for me? Unless the ADX conversion is wrong, I'll look at it....

When the entire log has played back look at you BLM History table and click latests and average. Your rich at idle and low RPM and little lean high RPM. Exactly what I would expect for that cam. Is the chip stock? Also look at the knock history. Your knock count started at 6, this means nothing but if it increases then your having knock in those cells. You never had a knock. Daves small block chevy spark table may be a good start. Also need to do some work on VE tables to get fueling closer to 128 all over. Overall not bad at all! Just got way more potentail with tuning.

[1leg]

Have you played back your log yet? I tell everyone to right click on toolbar in TunerPro and check all the toolbars. learn the buttons! Click the play log button, then the List View button, then the History table button, then the Monitor button. These are all good to see how your running and where your tune is. There is also a Dashboard button, fancy but fluff compared to what others are telling you. You can click back and forth with them all open in tabs at bottom.

First thing I saw was you were in open loop for over 3 minutes and RICH the entire time and you hit 230f before it started to cool down to 212f. Little hot for me? Unless the ADX conversion is wrong, I'll look at it....

When the entire log has played back look at you BLM History table and click latests and average. Your rich at idle and low RPM and little lean high RPM. Exactly what I would expect for that cam. Is the chip stock? Also look at the knock history. Your knock count started at 6, this means nothing but if it increases then your having knock in those cells. You never had a knock. Daves small block chevy spark table may be a good start. Also need to do some work on VE tables to get fueling closer to 128 all over. Overall not bad at all! Just got way more potentail with tuning.

Yes I have been studying it for over 2 hours so far. I have exported the data to excel to play with the data. I did notice all that you wrote about and was about to ask some questions.

The temp is way hi. the gauge in the truck is no were near 200, something is way off? i have a 190' thermostat, and big rad and best pump on the market.
Spark advance doesn't change. this is a new distributor i'm worried?

[EagleMark]

I haven't had time to look at the adx file to see if there is a wrong conversion on coolant temp yet.

But I did remove the spark advance if that is what your talking about? It will not work with this adx file.

This ECM is almost identical to 1227747 and you seem to know how to work excel so look for Daves VE excel spreadsheet. It works awesome on 7747.

[1leg]

I haven't had time to look at the adx file to see if there is a wrong conversion on coolant temp yet.

But I did remove the spark advance if that is what your talking about? It will not work with this adx file.

This ECM is almost identical to 1227747 and you seem to know how to work excel so look for Daves VE excel spreadsheet. It works awesome on 7747.

Thanks,
Why disable spark adv? should I just trust the tables and not be concerned about? Can I reactivate it?