guest

Second one in row that refuses to get off full retard. These are the 7060 ecu's both on l80e's.

Replaced everything with exception to the harness and have cont. tested all those connections.

Shows full retard always, key on/eng off, running, nothing changes it.

Obviously runs like crap. Have access to a chip burner.

Any help would be appreciated as Im at my wits end with this thing.

guest

Also, cant seem to connect to this thing quite right. On 160baud connect in tunerpro I get a "retard" flag. No codes though.

Other than knock sensor, dist module, wiring, coolant temp, tps, is there anything else that would flag the ecu to go full retard? Maybe some kind of starter wait? Ive unplugged everything just trying to see if there was something causing the flag.

Anything? Anyone?

Any ideas? Everything has been replaced with exception to the calpak. Which I dont have the address with me but it's ve table is zero'd out in the xdf I have. Figured is was just an address error as everything else in the xdf lines up perfect.

dimented24x7

iTrader: (2)

The 7060 is a PCM off the top of my head. Itll require you to use the 8192 baud connection rate and two transistor, bi-directional cable as it has a UART. Have you put a timing light on it yet? With the EST connected, it should give something like 15 degrees of advance or so at idle.

Do you know what mask it is? In each mask, the tables do move here and there as they made revisions along the way. Its important to make sure your using the correct definition file.

guest

I made one of the 2 transistor cables but no luck on connecting other than at 160.

Timing light was used to set timing to zero. Timing wire plugged it doesnt really rise and has the bad module/knock sensor bog/kick back. Ecm shows to be calling for retard as I do get a "retard" flag on in tunerpro.

Timing on a cheap scan tool shows knock retard to start at 8-11 degrees retarded before starting engine. Running it, the retard amount rises with coolant temp.

I used the $85 mask which other than the VE table lined up perfectly.

One other thing. The white wire to the dist module, which I understood to need 5 volts to allow ecu control, only has 1.7 volts on it. Is that a function of the ECU calling for default module timing? I have verified everything on the ecu pinout thats measurable. Its got a new ecu aswell. Everything is there, new and verified, but it still doesnt work.

Is there some phantom timing default parameter? Like timing kill for starter?

dimented24x7

iTrader: (2)

If thats at idle, then 1.7 volts sounds about right. The signal controls the advance. More voltage=more advance. Does the voltage increase as you rev the motor up? Put a timing light on it and watch the timing. It should be around 14-15 degrees or so at idle with the EST bypass plugged in. It sounds like the computer may be working properly, but the scan tools are reporting false info.

guest

Ehh some how the module 4 pin plug must have gave out. Pigtailed that one last night as I wasn't getting module switch over at the ecu plug anymore. Fixed that problem, for now.

Its still losing timing but atleast thats from motor noise and thats something I can fix.

Still cant connect at high baud rate though. Connects but shows "Packet error count" rising constantly. So somewhere Im missing something. The cable works fine on other ALDL's , could this 7060 ecu have different packet size?

dimented24x7

iTrader: (2)

In tunerpro RT, using the $0D ADS thats available from the FTP on moates.net should get you connected. Its likely similar enough to get it to hook up. Even if the handshake is wrong, the PCM will still default to the scantool data, so you should get something out of it so long as the cable isnt dumping data.

Have you tried using a timing light to monitor it yet? Thats the easiest way to see if its working. If its stuck at 0 degrees or the timing periodically drops out, then you know you have an issue for sure. Try that first before getting too hung up on connecting with the PCM.

guest

No luck on the timing, fixed knock sensor and now the module connector, still no timing what so ever. Shows 26deg knock retard on my handheld. Module tests good and switches over via voltage on the bypass. Any thoughts?

No luck on the ads either, $0d or any other one for that matter gets packet errors unless I set the offset to zero vs 4. Tried 4 then 3 and so on. No clean packets unless at 0 and then its improper data.

Anyway anyone got an idea on this offset? Maybe different size, string?


Oh and still in the same boat with the no VE table. Turns out this motor is gona need serious tuning. Its a 406 w/AFR 190's and a comp 256 xfi, long headers, and oh yea- a stock prom.

dimented24x7

iTrader: (2)

Damn, 406 with AFRs. No matter what, its going to run poorly on the stock calibration.

If your just starting out, then you might as well grab the $0D bin and burn it onto a prom and use that in the future since its one of the masks with lots of information available for it. With that setup, it wont be any farther off then what you have already. The TBI calibrations are really lame.

va454ss

iTrader: (1)

Do you have the correct knock sensor?

Good grounds?

dimented24x7

iTrader: (2)

IIRC, the later KS's have an internal resistance, so if the incorrect one is used, itll set a code. With the earlier setups with the external module, using a late model KS is what really screws things up.

guest, can you get the four letter broadcast code off of your memcal? It should be printed across the foil label over the UV erase hole on the memcals cover. That will help determine what mask teh PCM has on it. Either way, it still should datalog regardless. Im thinking there may be an issue with the cable if it doesnt work in tunerproRT.

guest

Y'all I been through every inch of wiring, grounds included, from the PCM out.

Its running a new 3900 ohm knock sensor. It had a MAS style when I first got to it. No codes show up just it never gets timing. Also, I get module switch over now at the PCM plug.

Ive got the memcal on my desk at work, I believe its a "BAAY" . The datalogger works on other trucks just not this one. It will connect but gets constant packet errors unless I set the offset to 0 vs 4, then it shows good packet count but all the info is off. Tried an 0D, 6E, -ehh tried then all but nothing would connect and not register packet errors if I didnt set the offset to 0.

Is there a smaller load size? Like maybe 59 vs 63?

Cause the offset looks like it needs to be 4 as I get ,ehh cant remember sitting here, but something to the effect of b4 01 ehcoed back with it set to to 0 on the offset. My adapter has a port listener.


Thanks, Joe

dimented24x7

iTrader: (2)

It goes without saying that with the new engine, its going to run extremly poorly untill you tune it. Mine ran the same way on the first startup with the PCM. Way too much fuel down low from the stock VE tables and no where near enough timing. The headers where glowing it was so bad.

With that said, have you actuallyput a timing light on it, and verified that the timing is stuck at 0 or 6 degrees? Im sure you have, but if you havent, do that first before chasing down any problems that might just be imaginary.

guest

Opps "BAAY 3074" is on the blue cover the eprom has 9107 on the erase hole cover. The $85 mask seems to line up nicely other than the VE table. I could host the image if it mattered.

This one does not get timing advance, via timing light nor does it show anything other than full retard.

Either way which image should I start with? From the few things Ive read about this PCM its got a different injector driver. yes? no? I suppose it would have to be something else with the l80e and matching PCM internals?


thank you, Joe

dimented24x7

iTrader: (2)

https://www.thirdgen.org/forums/diy-...highlight=7060

It looks like the PCM may be a hodge-podge. The bin I saw listed was only 32K in length, and not 64K like the other PCMs. Can you take a picture of the PCM? Does it have two 32 pin blue and red connectors? Or is does it have one 32 pin and one 24 pin connector? GM made so many variations of these that its nearly impossible to keep track of them all.

guest

Its got a 24 and 32 pin connector. I used a 512k as I thought thats what it came with.

Its got 2 images I believe, one for trans other for engine, both are 32k each.

dimented24x7

iTrader: (2)

Thats likely one of the earlier PCMs. It may very well only support the 160 baud ALDL. I have no idea what items it transmits.

Might try asking on the DFI/ECM board. There where a few people using it. They may have some more insight on how it operates.

TrevorH454

It is the 8192 baud. I had one in my truck for a while. I got Datamaster to work great on it, but never did get Tunerpro to work. I didn't spend too much time playing with it, though.

va454ss

iTrader: (1)

Same here.

guest

Well got it connected with 138 datastream @8192. Turns out it was a payload of 59 with a offset of 4.

Timing is now fixed with new module, holds 16 degrees @ idle fully warmed. Only thing left is the VE table location. Ive searched everywhere with no luck. Tried various other xdf's looking for possibles.


Anyone got an idea where to start? Such a dis. of 9107?


Ive got 2 different $85 mask xdf's and both show 086E as the starting point but its all zero'd.


Thanks for you'alls help. Joe.

dimented24x7

iTrader: (2)

Glad to hear its fixed

FWIW, the module and items attached to it is usually the first place to look when you develop ignition problems since the module is under alot of load from driving the coil and is also usually the first stop for any spark leakage in the coil or cap.

As for the PCM, one thing you could do is buy the tunercat definition and use the TDF editor to view all the locations and parameters of the tables and transpose it into an XDF. You wont be able to share it since its someone elses intelectual property, but itll get you up and running.

guest

It had been replaced several times before with the same no luck. The one I could get to change over after the connector swap tested good @ autozone yet could never get timing.

After verifying everything again I just put a new one in it out of desperation. I knew if I could get switch over on one atleast it would get a signal if the pcm sent it.

I found a few disassemblys of various 85 mask images and most had a 03aa start point on a 13/12 VE table. Looking into this one I got an 0d at 03a9 showing for the same 13 row table and the 2 previous spots called for 0, as in 0 minimums for rpm and map. Sooo made a table viewer in the XDF and its a VE table but theres this strange rift down the middle. Wonder where I would look to see if theres an adder some where else. Made me think I was looking at 2 tables but this rift of low numbers rose up diagonally through the table. Perhaps some minimum to added to based on motor option?



Oh and if someone could edit the previous post--the datastream is a 138 not a 183-sorry for the typo.

dimented24x7

iTrader: (2)

It sounds like its not set up properly in the definition file. I remember having this problem when I typed things in wrong. Get a wierd table with a ridge or a rift in the middle due to the rows/colums not being defined right. The table is actually one long hex string in the prom.

Also, you should be able to edit your own posts very soon. I think the admin added some lockout features for new posters.

y5mgisi

What exactly did you change and where did you go to do it? I am having trouble getting tunerpro to listen to a 7060 that im working on right now. Also, what adx/ads were you using?