I know this is probably a dead end, but my brother has an '88 IROC 305 TBI w/ 700R4. I know that he is supposed to have the 8063 ecm and here are my questions...

- Four years ago he bought a Hypercrap chip from Summit for his car, but everything I've read (even from 2 years ago) says that the only company that made a chip for the 8063 was Jet. Is it possible that Hypertech had a chip that no one knew about, or is it more likely that Summit sold him the wrong chip and his car has been in "limp home" mode for 4 years?

- My brother's and I are going to start burning chips for our cars (including the '88 IROC) here shortly. Does anyone have a 8063.ecu definition file for use with GMECMEDIT or WinBin? I've searched on this one allready and know it's pretty much hopeless that anyone would have it. I know that Tunercat supports it, but considering a used 8746 ECM (which is a direct replacement for the 8063 except for VATS) is only $25 - $30 it wouldn't be worth it to buy Tunercat.

Any suggestions? The whole 8063 deal seem like a damned if you do and damned if you don't type situation. Either way, unless someone has hacked the 8063 for a .ecu file, we're gonna have to fork out more money than expected. Thanks in advance for any help you all can offer.

Later,
Harry

 

If you're desparate, one solution is to pay the $20 for the CATS definition, download their tdf editor, and create an ECU from the information. downside - costs $20. Upside, you don't need to spend the going rate for tunercat, AND you help anyone else out who might come along needing that particular ECU.

If you go this route, I can help you out offline if you like.

 

Well, now I'm either really confused or enlightened... As I said before, everything I've read here (even posts as recent as 2 years ago) said that Hypertech did not make a chip for the 8063. However, I cross-referenced the p/n on the chip (128863) with Hypertech's application guide and it is indeed for an '88 305 TBI/700R4 combo. How difficult would it be to hack the Tunercat definition file to make an 8063.ecu file? Would my brother see any advantages by switching to the 8746 ECM over his 8063 other than not having to deal with the hassle of making a different ecu definition file? I do not have extensive programming knowledge, but I DO have access to an 8746 for $32 shipped if I want it.

P.S. Thanks for the feedback Magnus, I may actually consider going this route if it isn't going to be too terribly difficult. Esp. because it would help out others on the board with 8063s. The decision is up to my brother though.

Later,
Harry

 

Well it looks as if we are switching his 8063 ECM over to the 8746 now. So now my attention turns in a different direction. What about an 8062? I have an '89 Jimmy with the 4.3 and 700R4. There isn't any chance that anyone would have a .ecu file for this is there? And if like the 8063, the 8062 is virtually unhacked, could I easily swap it over to a 746?

 

I would be very interested in this myself. My wifes 89 blazer uses the same computer(062). I have been considering buying the tunercat definition file, but if there is a cheaper/free solution, I'd be all for that. Mangus, if you're willing to help a somewhat limited rookie (computer wise), I'd maybe give it a shot. I have both winbin, and gmecm, and am very good at the tuning, but the computer knowledge is weak. I would be more than happy to post an ecu file on the web if one can be worked out. Email me if anyone is interested.
Thanks
Bob

 

I found a .ecu file for the 8062 on the diy-efi.org site. It's called 8062majorguessing.ecu It's a start I suppose, but every time I load it I get this error message: Invalid system Data/Syntax in item. Check for missing comma or }. Consult GMECM edit help for more info. Item number 6. I just read through the help file and didn't really see anything that would point me in the direction I need to go with this.

 

simply means the syntax of the 6th item in the ecu file (which is plain text - open it in notepad) is incorrect. open in notepad and correct it.

 

I've looked at it in notepad... I'm not a programmer by any means, but nothing looks out of place. Maybe it's a bad value? I dunno, I'm learning here and this is kinda over my head at the moment.

/* Item 6: Max RPM for Spark Slope(strts 3600) */
{
/*startAddr =C,
/*columns =1,
/*rows =1,
/*elementSize =1,
/*bitMask =0,
/*offset =0,
/*mulOrDivOrBit =0,
/*factor =25,
/*map_name =???Max RPM for Spark Slope(strts 3600),
/*ylabel =,
/*yaxis =,
/*xlabel =RPM,
/*xaxis =,,
};

 

be sure that its *actually* item six.

don't count the header (general). actually count down to the sixth item. once found, send me 3 items (the one before, the 6th item, and the one after it).

 

If this is of any use, I hav a hac of the .bin file for this vehicle (AMRW). If it would help, i could email it to you mangus.
Bob

 

sent you a PM.

 

Magnus,
You've got mail, well, a PM anyway... and I've got to go to work. Back around 3:30am EST if any of you are still up then. Sorry I can't stick around. It'll be awesome if we can piece together a file for the 8062 out of this.

Later,
Harry

 

Back at ya

 

problem is with the following item. in the map name, you'll notice a comma after "disable". Per the ECU syntax rules, a comma indicates the end of an item. remove this comma and things will be fine.

/* Item 5: Cold start throttle kicker (0=disable 64=enable) */
{
/*startAddr =8,
/*columns =1,
/*rows =1,
/*elementSize =1,
/*bitMask =0,
/*offset =0,
/*mulOrDivOrBit =0,
/*factor =1,
/*map_name =???Cold start throttle kicker (0=disable, 64=enable),
/*ylabel =,
/*yaxis =,
/*xlabel =,
/*xaxis =,,
};


mark

 

Thanks Magnus,

I'm not really supposed to be on here while I'm at work, but I will update the .ecu file when I get back home. and see if anything else turns up. Also, goneracin, if you could email me the hack of that .bin file that might help me take this thing a step further. This will be awesome if we can get support for all those out there with 8062s behind their 4.3 sawed off sixes.

 

PS - looking a little closer, the use of "=" in the text of an ECU item should also be discouraged ("=" and "," are used to delimit the information contained in the item fields).

 

I just found a .bin from a Bravada with the 8062 if that helps you guys out any ( ftp://ftp.diy-efi.org/pub/gmecm/bin_lib/1228062%204E/ ). I'm finally done with my friend's '65 C-10 so maybe I can dive back into this one now.

 

Wow, I didn't realize this thread had that many views... maybe there are more people out there needing support for their 8062s and 8063s than I realized.